From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] [Xen] Check FADT's signature Date: Fri, 10 Aug 2007 19:21:43 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1954076355==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefan Berger Cc: xen-devel , Jan Beulich List-Id: xen-devel@lists.xenproject.org > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --===============1954076355== Content-type: multipart/alternative; boundary="B_3269618503_25559067" > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --B_3269618503_25559067 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable On 10/8/07 18:00, "Stefan Berger" wrote: > (XEN) map_pages_to_xen : 3533 > (that's the line number) > (XEN) 0xfff9b000 was NOT present. >=20 > Something between (*) and here seems to trash this presence flag. > paging_init() and many others lie in between the upper call and this one = here. > Could be a side effect of this? Maybe that tlb flush at the right place i= n one > of these functions would solve the problem? Yes, this now looks likely and that=B9s rather scary. We=B9ll go after this nex= t week. -- Keir --B_3269618503_25559067 Content-type: text/html; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Re: [Xen-devel] [PATCH] [Xen] Check FADT's signature On 10= /8/07 18:00, "Stefan Berger" <stefanb@us.ibm.com> wrote:

(XEN) map_pages_to_xen : 3533      &= nbsp;            = ;            &nb= sp;            &= nbsp;          (that's the= line number)
(XEN) 0xfff9b000 was NOT present.

Something between (*) and here seem= s to trash this presence flag.=
paging_init() and many others lie i= n between the upper call and this one here. Could be a side effect of this? = Maybe that tlb flush at the right place in one of these functions would solv= e the problem?

Yes, this now looks likely and that’s rather scary. We’ll go af= ter this next week.

 -- Keir

 --B_3269618503_25559067-- --===============1954076355== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1954076355==--