From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH]ACPI: workaround for S3 fail in two facs tables case Date: Thu, 25 Feb 2010 10:39:22 +0000 Message-ID: References: <4B86452C020000780003136C@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4B86452C020000780003136C@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 , Gang Wei Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 25/02/2010 08:38, "Jan Beulich" wrote: >> /* Now FACS... */ >> - if (fadt->header.revision >= FADT2_REVISION_ID) >> + if (fadt->header.revision >= FADT2_REVISION_ID && fadt->facs == 0) >> facs_pa = fadt->Xfacs; >> else >> facs_pa = (uint64_t)fadt->facs; > > Wouldn't that generally suppress using fadt->Xfacs, since I think in > order to be pre-2.0-OS compatible a BIOS would not normally set > facs to zero when Xfacs is non-zero? Or is that a requirement by the > spec? Good question would be: What does Linux do here? -- Keir