WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [PATCH] Fix xen hang on intel westmere-EP

To: "Zhang, Yang Z" <yang.z.zhang@xxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH] Fix xen hang on intel westmere-EP
From: Keir Fraser <keir.xen@xxxxxxxxx>
Date: Tue, 23 Aug 2011 08:32:08 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 23 Aug 2011 00:34:08 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=QVTtjhpoiUdV7ZCSmvE2mSb91DHAcRg5m0EuFiupqdA=; b=oGdSjuuTzzelK/kgdP+fIixHUuPX49Vl09zN97hYkK5jUEqlcXhgS6U+egQPH5OrSc OU8ijFFt7tkAM/dk+clVAdmLuT8qoJPDdThbSqXCfUJTpO/3egINfPd9+U+FYiB+QBe9 WUK0less6LRC8qOxaBffAFZxXhpr1Xs40R1E0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <749B9D3DBF0F054390025D9EAFF47F2212D123FF52@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acxg1o39NltmdPMdRwe+6OdPuDvibwAaSKsQAAnEsMY=
Thread-topic: [PATCH] Fix xen hang on intel westmere-EP
User-agent: Microsoft-Entourage/12.30.0.110427
On 23/08/2011 04:52, "Zhang, Yang Z" <yang.z.zhang@xxxxxxxxx> wrote:

>> Further I'm opposed to introducing further instances of legacy brute- force
>> PCI
>> bus scans.
>> 
>> And I don't think you got something along these lines accepted into Linux,
>> did
>> you? It ought to be DMI based there, too.
> I don't know why you think using DMI is a better way? For BDF based way, we
> only need to know the device ID. But for DMI base way, I don't know which
> condition should be matched.
> 
> Actually, the best way to solve it is to enable the ACPI mode in Xen instead
> of in dom0. For enable ACPI, we need to write the value from FADT.ACPI_ENABLE
> to SMI_CMD. After writing the value, the SMI ownership will be disable by ACPI
> hardware and it also will disable some logic which is able to cause SMI. For
> example, the legacy USB circuit will be masked too. Because at this point,
> there have no need to use legacy usb emulation. This is also what linux
> upstream did. But I think it is too complicated to port this logic to xen.
> Anyway, if you have interesting, you can add this logic to xen and there have
> no need for this patch again.

It sounds like quite a good idea, and not very complicated at all. The main
concern would be potential other fall out from making the change.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel