From: "H. Peter Anvin" <hpa@zytor.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Ian Campbell <ijc@hellion.org.uk>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Joel Becker <Joel.Becker@oracle.com>,
Jody Belka <lists-lkml@pimb.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Mika Penttila <mika.penttila@kolumbus.fi>
Subject: Re: 2.6.25-rc1 xen pvops regression
Date: Fri, 22 Feb 2008 08:27:05 -0800 [thread overview]
Message-ID: <47BEF7D9.50300@zytor.com> (raw)
In-Reply-To: <47BEA0DF.9070800@firstfloor.org>
Andi Kleen wrote:
> Alan Cox wrote:
>>> Actually I switched 64bit over to trust e820 completely and not
>>> reserve 640k-1MB explicitly some time ago
>>> and AFAIK there hasn't been any reports that it causes problems.
>>>
>>> So presumably trusting e802 is ok on modern systems (2003+)
>> Apparently so - at least 64bit capable ones.
>
> They should all use the same BIOS code bases, except perhaps
> some embedded weirdnesses.
Well, that, plus you still have to deal with a lot older stuff.
> We do still sort the entries
>> to remove zero length records and other suprises.
>
> That code could be actually dropped. And the sorting too.
> It's all not needed I think.
When I dealt with this for another project, I found that the e820 data
format is suboptimal. It's better to treat it as a sorted list of
(address, type) tuples (where type can be zero); the data from e820 can
be fed into such a data structure and it cleans it up nicely.
-hpa
next prev parent reply other threads:[~2008-02-22 16:32 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 23:54 2.6.25-rc1 xen pvops regression Jody Belka
2008-02-13 11:59 ` Jeremy Fitzhardinge
2008-02-13 12:13 ` Jody Belka
2008-02-13 12:23 ` Ingo Molnar
2008-02-14 2:27 ` Joel Becker
2008-02-14 7:50 ` Jeremy Fitzhardinge
2008-02-15 20:23 ` Joel Becker
2008-02-16 2:44 ` Jeremy Fitzhardinge
2008-02-16 8:54 ` Joel Becker
2008-02-16 11:46 ` Jeremy Fitzhardinge
2008-02-17 6:29 ` Joel Becker
2008-02-17 12:09 ` Jeremy Fitzhardinge
2008-02-17 6:39 ` Joel Becker
2008-02-17 18:49 ` Ian Campbell
2008-02-18 10:40 ` Joel Becker
2008-02-19 21:50 ` Ian Campbell
2008-02-19 21:59 ` Ian Campbell
2008-02-20 7:43 ` H. Peter Anvin
2008-02-20 8:51 ` Ian Campbell
2008-02-20 21:42 ` Joel Becker
2008-02-20 22:30 ` Ian Campbell
2008-02-20 21:58 ` Jeremy Fitzhardinge
2008-02-20 22:29 ` Ian Campbell
2008-02-21 21:16 ` Jeremy Fitzhardinge
2008-02-21 21:21 ` H. Peter Anvin
2008-02-21 21:37 ` Jeremy Fitzhardinge
2008-02-21 21:44 ` H. Peter Anvin
2008-02-21 22:12 ` Ian Campbell
2008-02-21 22:23 ` H. Peter Anvin
2008-02-21 22:49 ` Jeremy Fitzhardinge
2008-02-21 22:58 ` H. Peter Anvin
2008-02-22 7:25 ` Ian Campbell
2008-02-22 9:28 ` Alan Cox
2008-02-22 9:55 ` Andi Kleen
2008-02-22 10:00 ` Alan Cox
2008-02-22 10:15 ` Andi Kleen
2008-02-22 16:27 ` H. Peter Anvin [this message]
2008-02-22 19:25 ` Pavel Machek
2008-02-26 17:06 ` Mark McLoughlin
2008-02-26 20:05 ` Jeremy Fitzhardinge
2008-02-21 22:58 ` Joel Becker
2008-02-21 22:04 ` Eric W. Biederman
2008-02-21 23:14 ` Jeremy Fitzhardinge
2008-02-21 23:26 ` H. Peter Anvin
2008-02-21 23:46 ` Jeremy Fitzhardinge
2008-02-21 23:57 ` 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=47BEF7D9.50300@zytor.com \
--to=hpa@zytor.com \
--cc=Joel.Becker@oracle.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andi@firstfloor.org \
--cc=ebiederm@xmission.com \
--cc=ijc@hellion.org.uk \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists-lkml@pimb.org \
--cc=mika.penttila@kolumbus.fi \
--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 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.