All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
	"Wei, Gang" <gang.wei@intel.com>,
	xen-devel@lists.xensource.com
Subject: Re: [PATCH 2/4] CPUIDLE: Avoid remnant LAPIC timerintr while force hpetbroadcast
Date: Thu, 11 Sep 2008 12:06:55 +0100	[thread overview]
Message-ID: <C4EEBA5F.26F66%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <D470B4E54465E3469E2ABBC5AFAC390F024D97B0@pdsmsx412.ccr.corp.intel.com>

On 11/9/08 11:59, "Tian, Kevin" <kevin.tian@intel.com> wrote:

>> Also, in your patch, you unmask LVTT after reprogramming the
>> LAPIC counter.
>> Isn't there a race where the LAPIC timer generates an
>> interrupt event before
>> you unmask the LVTT and hence you lose the interrupt (since I
>> assume the
>> LAPIC interrupt is basically an internal one-shot signal which
>> does not get
>> latched in any way)? So you'd probably need to reprogram_timer(0), then
>> enable the timer, then reprogram_timer(<actual value>).
>> 
> 
> You're correct. It will be fixed.

Thanks. I'm not sure whether the reprogram_timer(0) before re-enabling is
really required. It looks like Linux doesn't do similar (although if course
it does re-programming after re-enabling to avoid the above race).

I suppose repogram_timer(0) is cheap so you might choose to do it anyway.
It's up to you...

 -- Keir

  reply	other threads:[~2008-09-11 11:06 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     ` [PATCH 2/4] CPUIDLE: Avoid remnant LAPIC timer intr while " Keir Fraser
2008-09-11  7:46       ` 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 [this message]
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=C4EEBA5F.26F66%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=gang.wei@intel.com \
    --cc=kevin.tian@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.