From: "Daniel P. Berrange" <berrange@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
Gleb Natapov <gleb@redhat.com>,
libvir-list@redhat.com, Joerg Roedel <joro@8bytes.org>,
X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
qemu-devel@nongnu.org, Andre Przywara <andre@andrep.de>,
KVM <kvm@vger.kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Jiri Denemark <jdenemar@redhat.com>, Borislav Petkov <bp@suse.de>
Subject: Re: [Qemu-devel] qemu, numa: non-contiguous cpusets
Date: Mon, 30 Sep 2013 09:15:11 +0100 [thread overview]
Message-ID: <20130930081511.GB23756@redhat.com> (raw)
In-Reply-To: <20130929151044.GB5426@pd.tnic>
On Sun, Sep 29, 2013 at 05:10:44PM +0200, Borislav Petkov wrote:
> Btw,
>
> while I got your attention, on a not-really related topic: how do we
> feel about adding support for specifying a non-contiguous set of cpus
> for a numa node in qemu with the -numa option? I.e., like this, for
> example:
>
> x86_64-softmmu/qemu-system-x86_64 -smp 8 -numa node,nodeid=0,cpus=0\;2\;4-5 -numa node,nodeid=1,cpus=1\;3\;6-7
>
> The ';' needs to be escaped from the shell but I'm open for better
> suggestions.
Use a ':' instead.
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2013-09-30 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 15:10 [Qemu-devel] qemu, numa: non-contiguous cpusets Borislav Petkov
2013-09-30 8:15 ` Daniel P. Berrange [this message]
2013-09-30 9:05 ` Paolo Bonzini
2013-09-30 9:49 ` Borislav Petkov
2013-09-30 12:18 ` Paolo Bonzini
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=20130930081511.GB23756@redhat.com \
--to=berrange@redhat.com \
--cc=andre@andrep.de \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=ehabkost@redhat.com \
--cc=gleb@redhat.com \
--cc=hpa@zytor.com \
--cc=jdenemar@redhat.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=libvir-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).