[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] [PATCH 2/4] CPUIDLE: Avoid remnant LAPIC timer intr while force hpetbroadcast


  • To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Wei, Gang" <gang.wei@xxxxxxxxx>
  • Date: Thu, 11 Sep 2008 15:46:34 +0800
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Cc:
  • Delivery-date: Thu, 11 Sep 2008 00:47:04 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AckSVfqaFjPrXqrARTKdgjxn6iTeJQA2DOERAAhrdiAAJF4X8QAAHviA
  • Thread-topic: [Xen-devel] [PATCH 2/4] CPUIDLE: Avoid remnant LAPIC timer intr while force hpetbroadcast

On Thursday, September 11, 2008 3:38 PM, Keir Fraser wrote:
> On 10/9/08 15:25, "Wei, Gang" <gang.wei@xxxxxxxxx> wrote:
>
>>> It's not clear to me the disable/enable_LAPIC_timer() work is worthwhile for
>>> the few timer interrupts it is likely to avoid. The other bit of the patch
>>> is a good bugfix though. I've taken just the latter part.
>>
>> Thanks for accept most of these patches. As to disable/enable_LAPIC_timer(),
>> I add them because some platforms require the LAPIC timer intr being disabled
>> before entering C3, otherwise there may be some unexpected things. As a
>> reference, Linux kernel always do so.
>
> Is this a documented aspect of C3, or just one of those things? Do you know
> what kind of 'unexpected things' can happen?

Currently let's just regard it as one of those things. I think kevin's reply 
can explain it better from another perspective.

Jimmy

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.