Re: [PATCH v1 3/7] util: Introduce ThreadContext user-creatable object

2022-09-29 Thread David Hildenbrand
+## +# @ThreadContextProperties: +# +# Properties for thread context objects. +# +# @cpu-affinity: the CPU affinity for all threads created in the thread +#context (default: QEMU main thread affinity) +# +# Since: 7.2 +## +{ 'struct': 'ThreadContextProperties', + 'data': { '*cpu-a

Re: [PATCH v1 3/7] util: Introduce ThreadContext user-creatable object

2022-09-29 Thread Markus Armbruster
David Hildenbrand writes: > On 29.09.22 13:12, Markus Armbruster wrote: >> David Hildenbrand writes: >> >>> Setting the CPU affinity of QEMU threads is a bit problematic, because >>> QEMU doesn't always have permissions to set the CPU affinity itself, >>> for example, with seccomp after initial

Re: [PATCH v1 3/7] util: Introduce ThreadContext user-creatable object

2022-09-29 Thread David Hildenbrand
On 29.09.22 13:12, Markus Armbruster wrote: David Hildenbrand writes: Setting the CPU affinity of QEMU threads is a bit problematic, because QEMU doesn't always have permissions to set the CPU affinity itself, for example, with seccomp after initialized by QEMU: -sandbox enable=on,resourc

Re: [PATCH v1 3/7] util: Introduce ThreadContext user-creatable object

2022-09-29 Thread Markus Armbruster
David Hildenbrand writes: > Setting the CPU affinity of QEMU threads is a bit problematic, because > QEMU doesn't always have permissions to set the CPU affinity itself, > for example, with seccomp after initialized by QEMU: > -sandbox enable=on,resourcecontrol=deny > > While upper layers are

[PATCH v1 3/7] util: Introduce ThreadContext user-creatable object

2022-09-28 Thread David Hildenbrand
Setting the CPU affinity of QEMU threads is a bit problematic, because QEMU doesn't always have permissions to set the CPU affinity itself, for example, with seccomp after initialized by QEMU: -sandbox enable=on,resourcecontrol=deny While upper layers are already aware how to handl;e CPU affin