From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: ACPI-Tables corrupted? Date: Fri, 6 Aug 2010 15:04:45 +0100 Message-ID: References: <4C5C2CB9020000780000EA96@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C5C2CB9020000780000EA96@vpn.id2.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich , Juergen Gross Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 06/08/2010 14:39, "Jan Beulich" 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