From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: Andre Przywara <andre.przywara@amd.com>
Cc: Konrad Rzeszutek Wilk <konrad@darnok.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel <xen-devel@lists.xen.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Dom0 crash with old style AMD NUMA detection
Date: Fri, 21 Sep 2012 13:48:34 -0400 [thread overview]
Message-ID: <20120921174833.GC6821@phenom.dumpdata.com> (raw)
In-Reply-To: <505CA8AB.6000808@amd.com>
> Acked-by: Andre Przywara <andre.przywara@amd.com>
>
> I compiled and boot-tested this on my (single node ;-) test box.
> First bare-metal, dmesg: No NUMA configuration found
> Then again, but with numa=off on the cmd-line: NUMA turned off
> Then under Xen as Dom0 kernel: NUMA turned off
>
> So the code behaves under Xen as one would have explicitly specified
> numa=off, which is what we want.
Right.
> I couldn't get hold of the test machine (old K8 server) that the bug
> was once triggered, that's why I'm reluctant to give my Tested-by.
> Will try this ASAP.
OK, will wait with this - it would be a bit silly if the patch did not
fix the issue :-)
next prev parent reply other threads:[~2012-09-21 17:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 12:20 Dom0 crash with old style AMD NUMA detection Andre Przywara
2012-08-03 12:36 ` Konrad Rzeszutek Wilk
2012-08-17 14:22 ` Konrad Rzeszutek Wilk
2012-09-14 18:58 ` Konrad Rzeszutek Wilk
2012-09-17 7:29 ` Andre Przywara
2012-09-17 19:14 ` Konrad Rzeszutek Wilk
2012-09-18 9:57 ` Andre Przywara
2012-09-18 13:44 ` Konrad Rzeszutek Wilk
2012-09-18 16:50 ` Andre Przywara
2012-09-18 14:55 ` Konrad Rzeszutek Wilk
2012-09-21 17:49 ` Andre Przywara
2012-09-21 17:48 ` Konrad Rzeszutek Wilk [this message]
2012-09-21 23:46 ` Andre Przywara
2012-09-24 13:48 ` Konrad Rzeszutek Wilk
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=20120921174833.GC6821@phenom.dumpdata.com \
--to=konrad@kernel.org \
--cc=andre.przywara@amd.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=konrad@darnok.org \
--cc=xen-devel@lists.xen.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).