From: Anthony Liguori <anthony@codemonkey.ws>
To: Andre Przywara <andre.przywara@amd.com>
Cc: qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] Re: [PATCH 3/8] v2: add info numa monitor command
Date: Tue, 16 Dec 2008 15:16:29 -0600 [thread overview]
Message-ID: <49481AAD.5060501@codemonkey.ws> (raw)
In-Reply-To: <4947B819.9090307@amd.com>
Andre Przywara wrote:
> Signed-off-by: Andre Przywara <andre.przywara@amd.com>
>
> # HG changeset patch
> # User Andre Przywara <andre.przywara@amd.com>
> # Date 1229430525 -3600
> # Node ID 0f3054b66373c2a8b65a5be6d83af63f807dd88f
> # Parent a0a2e3026d4acffdce91b776d8c2d733767693c5
> add info numa command to the monitor
>
> diff -r a0a2e3026d4a -r 0f3054b66373 monitor.c
> --- a/monitor.c Tue Dec 16 13:28:24 2008 +0100
> +++ b/monitor.c Tue Dec 16 13:28:45 2008 +0100
> @@ -1281,6 +1281,20 @@ static void do_info_kvm(void)
> #endif
> }
>
> +static void do_info_numa(void)
> +{
> + int i, j;
> +
> + term_printf("%d nodes\n", numnumanodes);
> + for (i = 0; i < numnumanodes; i++) {
> + term_printf("node %d cpus:", i);
> + for (j = 0; j < 64; j++)
> + if (node_to_cpus[i] & (1ULL << j)) term_printf(" %d", j);
>
So the current code limits us to 64-cpus? That's a pretty serious
limitation IMHO. I think that strongly suggests we're using the wrong
structures for node_to_cpus--especially to be in the BIOS FW interface.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2008-12-16 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 14:15 [Qemu-devel] [PATCH 3/8] v2: add info numa monitor command Andre Przywara
2008-12-16 21:16 ` Anthony Liguori [this message]
2008-12-16 23:52 ` [Qemu-devel] " Andre Przywara
2008-12-17 0:11 ` Anthony Liguori
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=49481AAD.5060501@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=andre.przywara@amd.com \
--cc=avi@redhat.com \
--cc=qemu-devel@nongnu.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.