From: Glauber Costa <gcosta@redhat.com>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net, chrisw@sous-sol.org
Subject: Re: [PATCH 0/8] RFC: vcpu pinning at qemu start
Date: Wed, 05 Mar 2008 10:13:06 -0300 [thread overview]
Message-ID: <47CE9C62.6030905@redhat.com> (raw)
In-Reply-To: <47CE2F69.8070309@qumranet.com>
Avi Kivity wrote:
> Glauber Costa wrote:
>> 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!
>>
>>
>
> A monitor interface would be more useful than a command line option, as
> it allows you to migrate the vcpus at runtime, and also control
> hotplugged cpus. For unmanaged use, taskset is probably sufficient to
> control affinity from the command line.
>
> Normally I encourage splitting patches, but this is a bit extreme. 1
> and 3 are pointless without each other, 4 and 5, 7 and 8. Hope that
> doesn't interfere with any pay-per-patch contract.
>
I'll post a new series that just expose the thread ids, so the
management tools can use plain taskset. As for the split, there's
nothing in my contract, but after all the x86 integration, it became a
mania for me. Ingo made me this way.
-------------------------------------------------------------------------
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/
prev parent reply other threads:[~2008-03-05 13:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 16:21 [PATCH 0/8] RFC: vcpu pinning at qemu start Glauber Costa
2008-03-04 16:21 ` [PATCH 1/8] add thread id to vcpu structure Glauber Costa
2008-03-04 16:21 ` [PATCH 2/8] provide a gettid function Glauber Costa
2008-03-04 16:21 ` [PATCH 3/8] get thread id at thread's creation Glauber Costa
2008-03-04 16:21 ` [PATCH 4/8] store and set cpu affinities Glauber Costa
2008-03-04 16:21 ` [PATCH 5/8] initialize affinities Glauber Costa
2008-03-04 16:21 ` [PATCH 6/8] stabilish default affinity for newly created cpus Glauber Costa
2008-03-04 16:22 ` [PATCH 7/8] process a cpu affinity mask Glauber Costa
2008-03-04 16:22 ` [PATCH 8/8] provide -cpu-map option Glauber Costa
2008-03-04 17:26 ` [PATCH 0/8] RFC: vcpu pinning at qemu start Joerg Roedel
2008-03-04 18:11 ` Glauber Costa
2008-03-04 18:19 ` Joerg Roedel
2008-03-04 17:42 ` Anthony Liguori
2008-03-04 18:10 ` Glauber Costa
2008-03-04 19:28 ` Anthony Liguori
2008-03-04 19:42 ` Daniel P. Berrange
2008-03-04 20:00 ` Glauber Costa
2008-03-04 19:59 ` Glauber Costa
2008-03-05 3:43 ` Anthony Liguori
2008-03-05 6:44 ` Avi Kivity
2008-03-05 13:10 ` Glauber Costa
2008-03-05 5:35 ` Avi Kivity
2008-03-05 14:29 ` Anthony Liguori
2008-03-05 5:28 ` Avi Kivity
2008-03-05 13:13 ` Glauber Costa [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47CE9C62.6030905@redhat.com \
--to=gcosta@redhat.com \
--cc=avi@qumranet.com \
--cc=chrisw@sous-sol.org \
--cc=kvm-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox