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

Re: [Xen-devel] [PATCH] C6 state with EOI issue fix for some Intel proce

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] [PATCH] C6 state with EOI issue fix for some Intel processors
From: Sheng Yang <sheng@xxxxxxxxxxxxxxx>
Date: Wed, 15 Sep 2010 15:18:50 +0800
Cc: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Wed, 15 Sep 2010 00:18:16 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <201009151510.44090.sheng@xxxxxxxxxxxxxxx>
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>
Organization: Intel Opensource Technology Center
References: <201009151510.44090.sheng@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.13.2 (Linux/2.6.32-24-generic; KDE/4.4.2; x86_64; ; )
On Wednesday 15 September 2010 15:10:43 Sheng Yang wrote:
> There is an errata in some of Intel processors.
> 
> AAJ72. EOI Transaction May Not be Sent if Software Enters Core C6 During
> an Interrupt Service Routine
> 
> If core C6 is entered after the start of an interrupt service routine but
> before a write to the APIC EOI register, the core may not send an EOI
> transaction (if needed) and further interrupts from the same priority
> level or lower may be blocked.
> 
> This patch fix this issue, by checking if ISR is pending before enter deep
> Cx state. If so, it would use power->safe_state instead of deep Cx state
> to prevent the above issue happen.

Signed-off-by: Sheng Yang <sheng@xxxxxxxxxxxxxxx>

--
regards
Yang, Sheng

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