From: Andre Przywara <andre.przywara@amd.com>
To: "Kamble, Nitin A" <nitin.a.kamble@intel.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>,
Christoph Egger <Christoph.Egger@amd.com>
Subject: Re: Re: c/s 21118: Magny-Coure breakage
Date: Wed, 14 Apr 2010 11:46:59 +0200 [thread overview]
Message-ID: <4BC58F13.5050008@amd.com> (raw)
In-Reply-To: <8EA2C2C4116BF44AB370468FBF85A7770125B64332@orsmsx504.amr.corp.intel.com>
Kamble, Nitin A wrote:
> Keir,
> Attached is the patch to take of the sockets_per_node information from the 21118 changeset.
Thanks Nitin, that looks better.
Unfortunately the patch itself does not work for me, xend crashes (and
keeps restarting) due to signal 11. It works though if I just revert
your patch (rebuilt both hypervisor and tools). I will try to further
debug this, but in general your patch looks clean to me.
BTW: I found the output of xm info now a bit too verbose, can we
introduce a -v option to show the NUMA information only when explicitly
requested?
On my 48 core/8 nodes machine I get a lot of text, this should be even
worse with 128 threads, right?
Regards,
Andre.
--
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 448-3567-12
next prev parent reply other threads:[~2010-04-14 9:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 10:07 c/s 21118: Magny-Coure breakage Christoph Egger
2010-04-12 10:41 ` Keir Fraser
2010-04-12 11:00 ` Keir Fraser
2010-04-12 12:48 ` Dan Magenheimer
2010-04-12 13:14 ` Andre Przywara
2010-04-12 13:24 ` Keir Fraser
2010-04-12 18:28 ` Kamble, Nitin A
2010-04-14 9:46 ` Andre Przywara [this message]
2010-04-14 17:13 ` Kamble, Nitin A
2010-04-15 11:33 ` [PATCH] xend: make NUMA in xm info optional Andre Przywara
2010-04-15 12:11 ` Keir Fraser
2010-04-15 12:14 ` Andre Przywara
2010-04-15 12:19 ` Keir Fraser
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=4BC58F13.5050008@amd.com \
--to=andre.przywara@amd.com \
--cc=Christoph.Egger@amd.com \
--cc=dan.magenheimer@oracle.com \
--cc=keir.fraser@eu.citrix.com \
--cc=nitin.a.kamble@intel.com \
--cc=xen-devel@lists.xensource.com \
/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.