From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Beulich <jbeulich@novell.com>
Cc: mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com,
jeremy.fitzhardinge@citrix.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86-64: improve e820_search_gap()
Date: Fri, 13 Mar 2009 10:37:20 -0700 [thread overview]
Message-ID: <49BA99D0.1040308@goop.org> (raw)
In-Reply-To: <49B8F5C4.76E4.0078.0@novell.com>
Jan Beulich wrote:
> Blindly putting the gap close after max_pfn might be fine for native
> (though even there I'm uncertain regarding memory hotplug), but will
> certainly present a problem on Xen. And properly searching for a gap
> above 4Gb shouldn't hurt native.
>
What Xen-related issue are you thinking of?
When booting dom0 I reashape the guest memory to match the host E820
map, and for domU my plan is to leave a hole at 3-4GB for pci
passthrough resources.
J
next prev parent reply other threads:[~2009-03-13 17:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 10:45 [PATCH] x86-64: improve e820_search_gap() Jan Beulich
2009-03-12 11:02 ` Ingo Molnar
2009-03-12 11:31 ` Jan Beulich
2009-03-13 17:37 ` Jeremy Fitzhardinge [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-06 12:07 Jan Beulich
2009-05-08 4:59 ` H. Peter Anvin
2009-05-08 6:40 ` Jan Beulich
2009-05-08 16:52 ` H. Peter Anvin
2009-05-08 19:22 ` Andi Kleen
2009-05-08 20:15 ` H. Peter Anvin
2009-05-08 20:53 ` Andi Kleen
2009-05-08 20:52 ` H. Peter Anvin
2009-05-09 10:00 ` Andi Kleen
2009-05-10 6:43 ` H. Peter Anvin
2009-05-10 15:18 ` Andi Kleen
2009-05-10 17:56 ` H. Peter Anvin
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=49BA99D0.1040308@goop.org \
--to=jeremy@goop.org \
--cc=hpa@zytor.com \
--cc=jbeulich@novell.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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