From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
maluta_tiago@yahoo.com.br, lguest@ozlabs.org,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
Ian Campbell <Ian.Campbell@eu.citrix.com>
Subject: Re: [Lguest] lguest: unhandled trap
Date: Mon, 20 Oct 2008 00:43:53 -0700 [thread overview]
Message-ID: <48FC36B9.6000704@goop.org> (raw)
In-Reply-To: <20081020072236.GD12131@elte.hu>
Ingo Molnar wrote:
> i think Xen can withstand DMI scanning just fine.
>
> without having seen any background, my general feeling is that lguest
> should either do what Xen does and reserve the classic BIOS ranges that
> we probe - or we should make DMI scanning more robust by making sure
> real RAM ranges are never probed. (only ranges that the BIOS itself
> marks as reserved in the e820 map)
We considered doing that, but decided that there was so many other
pieces of code around the place that assume that the ISA area is
special, that just reserving it was the best course of action.
J
next prev parent reply other threads:[~2008-10-20 7:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <713731.28571.qm@web50701.mail.re2.yahoo.com>
[not found] ` <200810201452.04932.rusty@rustcorp.com.au>
2008-10-20 7:22 ` [Lguest] lguest: unhandled trap Ingo Molnar
2008-10-20 7:43 ` Jeremy Fitzhardinge [this message]
2008-10-20 7:53 ` Ingo Molnar
2008-10-20 9:14 ` Ian Campbell
2008-10-20 9:27 ` Ingo Molnar
2008-10-20 19:01 ` H. Peter Anvin
2008-10-20 22:48 ` Rusty Russell
2008-10-20 23:22 ` Ingo Molnar
[not found] <559519.75404.qm@web50707.mail.re2.yahoo.com>
2008-10-19 23:39 ` Rusty Russell
2008-10-20 4:15 ` 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=48FC36B9.6000704@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@eu.citrix.com \
--cc=hpa@zytor.com \
--cc=lguest@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maluta_tiago@yahoo.com.br \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--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