RFC: vcpu pinning at qemu start
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest8 patches 16 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/8 | add thread id to vcpu structureqemu/ | +1 | 0 replies | |
| 2/8 | provide a gettid functionqemu/ | +6 | 0 replies | |
| 3/8 | get thread id at thread's creationqemu/ | +2 | 0 replies | |
| 4/8 | store and set cpu affinitiesqemu/ | +17 | 0 replies | |
| 5/8 | initialize affinitiesqemu/ | +3 | 0 replies | |
| 6/8 | stabilish default affinity for newly created cpusqemu/ | +8 | 0 replies | |
| 7/8 | process a cpu affinity maskqemu/ | +17 | 0 replies | |
| 8/8 | provide -cpu-map optionqemu/ | +13 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/8] RFC: vcpu pinning at qemu start
Hi guys,
Here's a first series of patch aiming at vcpu pinning support in qemu. Ideally, as vcpu as just normal threads, the usual userspace tools can be used to set cpu affinities mask.
However, It makes it very difficult to _start_ a vm with vcpus pinned, since we don't know the thread ids from qemu in advance, nor do we know when are the vcpus created.
The patches introduce a -cpu-map option, that, if specified, starts the virtual cpus with the specified affinities.
Comments? Welcome. Random rants? Not welcome, but... how can I stop you? So go ahead!
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/