All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: Avi Kivity <avi@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH 1/3] KVM-userspace: introduce -nodes command line option
Date: Fri, 28 Nov 2008 10:15:15 +0000	[thread overview]
Message-ID: <20081128101513.GA26647@redhat.com> (raw)
In-Reply-To: <492F1E48.4000500@amd.com>

On Thu, Nov 27, 2008 at 11:25:12PM +0100, Andre Przywara wrote:
> The attached patch parses a list of host nodes given on the command line 
> and passes it on to lower levels (namely qemu-kvm.c)


> diff --git a/qemu/sysemu.h b/qemu/sysemu.h
> index 5abda5c..07acaf4 100644
> --- a/qemu/sysemu.h
> +++ b/qemu/sysemu.h
> @@ -99,6 +99,11 @@ extern int win2k_install_hack;
>  extern int alt_grab;
>  extern int usb_enabled;
>  extern int smp_cpus;
> +
> +#define MAX_NODES 64
> +extern int numnumanodes;
> +extern int hostnodes[MAX_NODES];

This is rather less than Linux / libnuma seems to allow for max
nodes. In numa.h there is

#if defined(__x86_64__) || defined(__i386__) 
#define NUMA_NUM_NODES  128
#else
#define NUMA_NUM_NODES  2048
#endif

Should we just use that NUMA_NUM_NODES constant directly from numa.h
when numa is compiled in, so we're guarenteed to match.

Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

      reply	other threads:[~2008-11-28 10:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27 22:25 [PATCH 1/3] KVM-userspace: introduce -nodes command line option Andre Przywara
2008-11-28 10:15 ` Daniel P. Berrange [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=20081128101513.GA26647@redhat.com \
    --to=berrange@redhat.com \
    --cc=andre.przywara@amd.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.