From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.com>,
Juergen Gross <juergen.gross@ts.fujitsu.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: ACPI-Tables corrupted?
Date: Fri, 6 Aug 2010 15:04:45 +0100 [thread overview]
Message-ID: <C881D50D.1CFDD%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4C5C2CB9020000780000EA96@vpn.id2.novell.com>
On 06/08/2010 14:39, "Jan Beulich" <JBeulich@novell.com> wrote:
>> If we don't zap the DMAR then every existing dom0 kernel will fail with new
>> hypervisor.
>
> Who decided that this zapping is going to work on all systems in the
> future?
Someone at Intel.
> E.g. I can't see why a BIOS shouldn't decide to put most of
> the ACPI tables in chipset write protected memory, if a chipset offers
> such? In such an environment, Dom0 would still see the original
> signature - shouldn't we thus correct the original mistake of fiddling
> with the ACPI tables as we now have to touch that code anyway?
Well it's harmless to try zapping it I think, now we reinstate it on kexec.
Trying to be smarter in dom0 *as well* is plausible I guess.
-- Keir
next prev parent reply other threads:[~2010-08-06 14:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 9:38 ACPI-Tables corrupted? Juergen Gross
2010-07-28 10:03 ` Keir Fraser
2010-07-28 11:26 ` Juergen Gross
2010-07-28 11:39 ` Keir Fraser
2010-07-28 12:13 ` Juergen Gross
2010-07-28 12:45 ` Keir Fraser
2010-07-28 13:27 ` Juergen Gross
2010-07-28 13:36 ` Konrad Rzeszutek Wilk
2010-07-29 6:19 ` Juergen Gross
2010-07-29 6:39 ` Keir Fraser
2010-07-29 6:48 ` Juergen Gross
2010-07-29 6:48 ` Keir Fraser
2010-07-29 6:53 ` Juergen Gross
2010-08-06 13:39 ` Jan Beulich
2010-08-06 14:04 ` Keir Fraser [this message]
2010-07-29 6:31 ` Jiang, Yunhong
2010-07-29 6:40 ` Keir Fraser
2010-07-29 6:48 ` Keir Fraser
2010-07-29 7:37 ` Jiang, Yunhong
2010-07-29 9:04 ` Juergen Gross
2010-07-29 9:33 ` Keir Fraser
2010-07-29 10:24 ` Keir Fraser
2010-07-30 4:47 ` Juergen Gross
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=C881D50D.1CFDD%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=juergen.gross@ts.fujitsu.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).