From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Beulich <jbeulich@novell.com>
Cc: Ingo Molnar <mingo@elte.hu>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Chris Lalancette <clalance@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH]: Fix Xen domU boot with batched mprotect
Date: Fri, 17 Oct 2008 08:36:31 -0700 [thread overview]
Message-ID: <48F8B0FF.3010005@goop.org> (raw)
In-Reply-To: <48F8CBC4.76E4.0078.0@novell.com>
Jan Beulich wrote:
> Is e.g. 256Mb tiny? KERNEL_IMAGE_SIZE these days is 512Mb... Indeed,
> when it was 40Mb (up until a few releases ago), this indeed wouldn't
> matter.
>
Well, the real point is that anyone doing a test on such high kernel
addresses is almost certainly buggy anyway. I guess a more precise
statement is that it returns well-defined results for any va the calling
code could reasonably be using, not for any random bit pattern.
But I think we're getting into the weeds here.
J
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Beulich <jbeulich@novell.com>
Cc: Ingo Molnar <mingo@elte.hu>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Chris Lalancette <clalance@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: Fix Xen domU boot with batched mprotect
Date: Fri, 17 Oct 2008 08:36:31 -0700 [thread overview]
Message-ID: <48F8B0FF.3010005@goop.org> (raw)
In-Reply-To: <48F8CBC4.76E4.0078.0@novell.com>
Jan Beulich wrote:
> Is e.g. 256Mb tiny? KERNEL_IMAGE_SIZE these days is 512Mb... Indeed,
> when it was 40Mb (up until a few releases ago), this indeed wouldn't
> matter.
>
Well, the real point is that anyone doing a test on such high kernel
addresses is almost certainly buggy anyway. I guess a more precise
statement is that it returns well-defined results for any va the calling
code could reasonably be using, not for any random bit pattern.
But I think we're getting into the weeds here.
J
next prev parent reply other threads:[~2008-10-17 15:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 11:03 [PATCH]: Fix Xen domU boot with batched mprotect Chris Lalancette
2008-10-15 11:03 ` Chris Lalancette
2008-10-15 15:24 ` [Xen-devel] " Jan Beulich
2008-10-15 15:24 ` Jan Beulich
2008-10-15 16:23 ` Jeremy Fitzhardinge
2008-10-15 16:23 ` Jeremy Fitzhardinge
2008-10-16 7:28 ` [Xen-devel] " Jan Beulich
2008-10-16 7:28 ` Jan Beulich
2008-10-16 9:58 ` [Xen-devel] " Jan Beulich
2008-10-16 9:58 ` Jan Beulich
2008-10-16 16:10 ` Jeremy Fitzhardinge
2008-10-16 16:10 ` Jeremy Fitzhardinge
2008-10-17 7:12 ` [Xen-devel] " Jan Beulich
2008-10-17 7:12 ` Jan Beulich
2008-10-17 15:19 ` Jeremy Fitzhardinge
2008-10-17 15:19 ` Jeremy Fitzhardinge
2008-10-17 15:30 ` [Xen-devel] " Jan Beulich
2008-10-17 15:30 ` Jan Beulich
2008-10-17 15:36 ` Jeremy Fitzhardinge [this message]
2008-10-17 15:36 ` Jeremy Fitzhardinge
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=48F8B0FF.3010005@goop.org \
--to=jeremy@goop.org \
--cc=clalance@redhat.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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.