From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
"Kay, Allen M" <allen.m.kay@intel.com>,
"Li, Xin" <xin.li@intel.com>,
"Li, Haicheng" <haicheng.li@intel.com>,
'xen-devel@lists.xensource.com'
Cc: "Cihula, Joseph" <joseph.cihula@intel.com>
Subject: Re: Critical bug: VT-d fault causes disk corruption or Dom0 kernel panic.
Date: Sat, 24 Jan 2009 09:26:56 +0000 [thread overview]
Message-ID: <C5A08F60.21CF5%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <C5A08CC2.21CF2%keir.fraser@eu.citrix.com>
On 24/01/2009 09:15, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:
>> I talked to Joe Cihula about this. He is suggesting map only the RAM memory
>> in E820 table. This is more secure than map everything below max_page. We
>> can do this for x86_64 and x86_32. For IA-64, we still map everything below
>> max_page as there is no tboot issue.
>>
>> What do you think of is approach?
>
> That's an orthogonal issue to avoiding Xen's RAM, but it at least ought to
> be easy to do. As long as it doesn't skip any private BIOS buffers for any
> devices which are still fully or partially under BIOS control (e.g., via
> SMM). But any such buffers above max_page would already be skipped.
>
> I can check in a patch for this as well as a patch to fix xen_in_range().
> I'll do both.
Changesets 19081 and 19082.
-- Keir
next prev parent reply other threads:[~2009-01-24 9:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 3:42 Critical bug: VT-d fault causes disk corruption or Dom0 kernel panic Li, Haicheng
2009-01-22 7:40 ` Keir Fraser
2009-01-22 8:58 ` Li, Xin
2009-01-22 9:23 ` Keir Fraser
2009-01-22 9:40 ` Critical bug: VT-d fault causes disk corruption orDom0 " Akio Takebe
2009-01-22 9:47 ` Keir Fraser
2009-01-23 1:01 ` Critical bug: VT-d fault causes disk corruption or Dom0 " Kay, Allen M
2009-01-23 8:33 ` Keir Fraser
2009-01-23 17:30 ` Kay, Allen M
2009-01-23 18:41 ` Keir Fraser
2009-01-23 18:44 ` Keir Fraser
2009-01-23 23:40 ` Kay, Allen M
2009-01-24 0:34 ` Cihula, Joseph
2009-01-24 9:15 ` Keir Fraser
2009-01-24 9:26 ` Keir Fraser [this message]
2009-01-24 19:07 ` Cihula, Joseph
2009-01-24 19:58 ` Keir Fraser
2009-01-24 2:19 ` Cihula, Joseph
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=C5A08F60.21CF5%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc='xen-devel@lists.xensource.com' \
--cc=allen.m.kay@intel.com \
--cc=haicheng.li@intel.com \
--cc=joseph.cihula@intel.com \
--cc=xin.li@intel.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.