From: Igor Mammedov <imammedo@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Andrew Jones <drjones@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
He Chen <he.chen@linux.intel.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v9] Allow setting NUMA distance for different NUMA nodes
Date: Thu, 27 Apr 2017 16:46:26 +0200 [thread overview]
Message-ID: <20170427164626.78f65611@nial.brq.redhat.com> (raw)
In-Reply-To: <874lxa2bex.fsf@dusky.pond.sub.org>
On Thu, 27 Apr 2017 16:05:42 +0200
Markus Armbruster <armbru@redhat.com> wrote:
> Igor Mammedov <imammedo@redhat.com> writes:
>
> > On Thu, 27 Apr 2017 07:54:31 -0500
> > Eric Blake <eblake@redhat.com> wrote:
> >
> >> On 04/26/2017 09:35 PM, He Chen wrote:
> >> > This patch is going to add SLIT table support in QEMU, and provides
> >> > additional option `dist` for command `-numa` to allow user set vNUMA
> >> > distance by QEMU command.
> >> >
> >> > With this patch, when a user wants to create a guest that contains
> >> > several vNUMA nodes and also wants to set distance among those nodes,
> >> > the QEMU command would like:
> >> >
> >> > ```
> >> > -numa node,nodeid=0,cpus=0 \
> >> > -numa node,nodeid=1,cpus=1 \
> >> > -numa node,nodeid=2,cpus=2 \
> >> > -numa node,nodeid=3,cpus=3 \
> >> > -numa dist,src=0,dst=1,val=21 \
> >> > -numa dist,src=0,dst=2,val=31 \
> >> > -numa dist,src=0,dst=3,val=41 \
> >> > -numa dist,src=1,dst=2,val=21 \
> >> > -numa dist,src=1,dst=3,val=31 \
> >> > -numa dist,src=2,dst=3,val=21 \
> >> > ```
> >> >
> >> > Signed-off-by: He Chen <he.chen@linux.intel.com>
> >> >
> >> > ---
> >> > Changes since v8:
> >> > * numa_{node, distance}_parse --> parse_numa_{node, distance}
> >> > * Comments refinement.
> >>
> >>
> >> > ---
> >> > hw/acpi/aml-build.c | 26 +++++++++
> >> > hw/i386/acpi-build.c | 4 ++
> >> > include/hw/acpi/aml-build.h | 1 +
> >> > include/sysemu/numa.h | 2 +
> >> > include/sysemu/sysemu.h | 4 ++
> >> > numa.c | 137 +++++++++++++++++++++++++++++++++++++++++++-
> >> > qapi-schema.json | 30 +++++++++-
> >> > qemu-options.hx | 16 +++++-
> >> > 8 files changed, 215 insertions(+), 5 deletions(-)
> >>
> >> Markus has asked that all new QMP commands have some testsuite exposure;
> >> he may have some advice on what test would be best to modify to give us
> >> some coverage of this feature.
>
> I can't see the QMP command here, but...
>
> > Since it's basically validation of SLIT table, the test case
> > should be added to tests/bios-tables-test.c
>
> ... I figure there's new stuff to test all the same.
it could be a patch on top and doesn't have to hold this one if author promises to write testcase
next prev parent reply other threads:[~2017-04-27 14:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 2:35 [Qemu-devel] [PATCH v9] Allow setting NUMA distance for different NUMA nodes He Chen
2017-04-27 9:21 ` Igor Mammedov
2017-04-27 9:27 ` Andrew Jones
2017-04-27 9:33 ` Daniel P. Berrange
2017-04-27 12:54 ` Eric Blake
2017-04-27 13:32 ` Igor Mammedov
2017-04-27 14:05 ` Markus Armbruster
2017-04-27 14:46 ` Igor Mammedov [this message]
2017-04-27 20:25 ` Eduardo Habkost
2017-04-28 9:39 ` He Chen
2017-04-28 9:55 ` Igor Mammedov
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=20170427164626.78f65611@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=armbru@redhat.com \
--cc=drjones@redhat.com \
--cc=ehabkost@redhat.com \
--cc=he.chen@linux.intel.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.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;
as well as URLs for NNTP newsgroup(s).