From: Keir Fraser <keir@xen.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 3 of 4] KEXEC: Allocate crash structures in low memory
Date: Fri, 09 Mar 2012 16:30:25 +0000 [thread overview]
Message-ID: <CB7FE0A1.3B319%keir@xen.org> (raw)
In-Reply-To: <4F5A2EBA.6090702@citrix.com>
On 09/03/2012 16:24, "Andrew Cooper" <andrew.cooper3@citrix.com> wrote:
> On 09/03/12 15:52, Keir Fraser wrote:
>> On 09/03/2012 14:42, "Andrew Cooper" <andrew.cooper3@citrix.com> wrote:
>>
>>> On 64bit Xen with 32bit dom0 and crashkernel, xmalloc'ing items such
>>> as the CPU crash notes will go into the xenheap, which tends to be in
>>> upper memory. This causes problems on machines with more than 64GB
>>> (or 4GB if no PAE support) of ram as the crashkernel physically cant
>>> access the crash notes.
>> Why wouldn't you run a 64-bit crashkernel?
>>
>> -- Keir
>
> There is certainly an argument to be made along those lines, and I
> personally lean to that side of the argument. However, as our dom0
> kernel is 32bits, there is no substantial testing of the drivers built
> for 64bit.
Yes, I suppose this sounds pretty reasonable.
-- Keir
next prev parent reply other threads:[~2012-03-09 16:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 14:42 [PATCH 0 of 4] KEXEC subsystem fixes and changes Andrew Cooper
2012-03-09 14:42 ` [PATCH 1 of 4] KEXEC: Allocate crash notes on boot Andrew Cooper
2012-03-09 15:41 ` Jan Beulich
2012-03-09 16:08 ` Andrew Cooper
2012-03-09 16:58 ` Jan Beulich
2012-03-09 14:42 ` [PATCH 2 of 4] x86: Introduce "top_of_mem" Andrew Cooper
2012-03-09 15:43 ` Jan Beulich
2012-03-09 16:46 ` Andrew Cooper
2012-03-09 17:00 ` Jan Beulich
2012-03-09 14:42 ` [PATCH 3 of 4] KEXEC: Allocate crash structures in low memory Andrew Cooper
2012-03-09 15:52 ` Keir Fraser
2012-03-09 16:24 ` Andrew Cooper
2012-03-09 16:30 ` Keir Fraser [this message]
2012-03-09 15:55 ` Jan Beulich
2012-03-09 17:01 ` Andrew Cooper
2012-03-09 14:42 ` [PATCH 4 of 4] KEXEC: Introduce new crashtables interface Andrew Cooper
2012-03-09 16:11 ` Jan Beulich
2012-03-09 17:33 ` Andrew Cooper
2012-03-11 9:59 ` Jan Beulich
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=CB7FE0A1.3B319%keir@xen.org \
--to=keir@xen.org \
--cc=andrew.cooper3@citrix.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 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).