From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"x86@kernel.org" <x86@kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Jan Beulich <JBeulich@novell.com>
Subject: Re: [PATCH] x86/mm/init: respect memblock reserved regions when destroying mappings
Date: Thu, 10 Feb 2011 15:48:50 -0800 [thread overview]
Message-ID: <4D547962.8040403@goop.org> (raw)
In-Reply-To: <4D519AAA.8070309@zytor.com>
On 02/08/2011 11:34 AM, H. Peter Anvin wrote:
> On 02/07/2011 07:12 PM, Yinghai Lu wrote:
>> why punishing native path with those checking?
>>
> What happens if you end up with a reserved range in an unfortunate place
> on real hardware?
Yes, exactly. The reserved region code isn't very useful if you can't
rely on it to reserve stuff.
J
next prev parent reply other threads:[~2011-02-10 23:49 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 15:18 [PATCH] x86/mm/init: respect memblock reserved regions when destroying mappings Stefano Stabellini
2011-02-02 20:15 ` Jeremy Fitzhardinge
2011-02-03 5:05 ` H. Peter Anvin
2011-02-03 11:25 ` Stefano Stabellini
2011-02-03 17:02 ` H. Peter Anvin
2011-02-04 11:35 ` Stefano Stabellini
2011-02-05 1:18 ` Jeremy Fitzhardinge
2011-02-06 7:02 ` Yinghai Lu
2011-02-06 7:30 ` H. Peter Anvin
2011-02-06 17:49 ` Yinghai Lu
2011-02-06 19:24 ` Yinghai Lu
2011-02-07 16:50 ` Stefano Stabellini
2011-02-07 18:04 ` Yinghai Lu
2011-02-07 18:58 ` Stefano Stabellini
2011-02-07 19:00 ` Yinghai Lu
2011-02-07 19:18 ` Yinghai Lu
2011-02-07 21:56 ` Jeremy Fitzhardinge
2011-02-08 3:12 ` Yinghai Lu
2011-02-08 4:56 ` Jeremy Fitzhardinge
2011-02-08 5:09 ` Yinghai Lu
2011-02-08 14:55 ` Konrad Rzeszutek Wilk
2011-02-08 19:24 ` Jeremy Fitzhardinge
2011-02-08 20:26 ` Stefano Stabellini
2011-02-08 19:34 ` H. Peter Anvin
2011-02-10 23:48 ` Jeremy Fitzhardinge [this message]
2011-02-10 23:57 ` Yinghai Lu
2011-02-11 0:35 ` H. Peter Anvin
2011-02-11 0:54 ` Yinghai Lu
2011-02-14 16:26 ` Konrad Rzeszutek Wilk
2011-02-14 17:55 ` Yinghai Lu
2011-02-14 17:58 ` Stefano Stabellini
2011-02-14 18:09 ` Yinghai Lu
2011-02-14 20:02 ` H. Peter Anvin
2011-02-16 17:36 ` Stefano Stabellini
2011-02-07 19:00 ` Stefano Stabellini
2011-02-08 5:16 ` Yinghai Lu
2011-02-08 14:03 ` Stefano Stabellini
2011-02-08 16:04 ` Yinghai Lu
2011-02-07 16:02 ` Stefano Stabellini
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=4D547962.8040403@goop.org \
--to=jeremy@goop.org \
--cc=JBeulich@novell.com \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@kernel.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.