From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Wei, Gang" <gang.wei@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 2/4] CPUIDLE: Avoid remnant LAPIC timer intr while force hpetbroadcast
Date: Thu, 11 Sep 2008 08:38:06 +0100 [thread overview]
Message-ID: <C4EE896E.1D0EB%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <8FED46E8A9CA574792FC7AACAC38FE7701ACD18DCE@PDSMSX501.ccr.corp.intel.com>
On 10/9/08 15:25, "Wei, Gang" <gang.wei@intel.com> 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?
-- Keir
next prev parent reply other threads:[~2008-09-11 7:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 8:28 [PATCH 2/4] CPUIDLE: Avoid remnant LAPIC timer intr while force hpetbroadcast Wei, Gang
2008-09-10 10:15 ` Keir Fraser
2008-09-10 14:25 ` Wei, Gang
2008-09-10 14:51 ` [PATCH 2/4] CPUIDLE: Avoid remnant LAPIC timer intrwhile " Tian, Kevin
2008-09-11 7:38 ` Keir Fraser [this message]
2008-09-11 7:46 ` [PATCH 2/4] CPUIDLE: Avoid remnant LAPIC timer intr while " Wei, Gang
2008-09-11 10:38 ` Keir Fraser
2008-09-11 10:59 ` [PATCH 2/4] CPUIDLE: Avoid remnant LAPIC timerintr " Tian, Kevin
2008-09-11 11:06 ` Keir Fraser
2008-09-11 15:22 ` Wei, Gang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C4EE896E.1D0EB%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=gang.wei@intel.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.