From: Andi Kleen <andi@firstfloor.org>
To: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
Cc: Shaohua Li <shaohua.li@intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"lenb@kernel.org" <lenb@kernel.org>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
"andi@firstfloor.org" <andi@firstfloor.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH]new ACPI processor driver to force CPUs idle
Date: Tue, 7 Jul 2009 01:43:46 +0200 [thread overview]
Message-ID: <20090706234346.GA8072@basil.fritz.box> (raw)
In-Reply-To: <20090706180312.GC26831@dirshya.in.ibm.com>
On Mon, Jul 06, 2009 at 11:33:12PM +0530, Vaidyanathan Srinivasan wrote:
> > >
> > > How do we handle interrupts and timers during this interval? You seem
> > > to disable interrupts and hold the cpu at idle for 0.95 sec. It may
> > > cause timeouts and overflows for network interrupts right?
> > The x86 mwait/monitor instruction can detect interrupt and complete execution
> > even interrupt is disabled, so this isn't an issue.
>
> Cool, this will save a lot of trouble :)
This is only available in newer Intel CPUs.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-07-06 23:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 4:13 [PATCH]new ACPI processor driver to force CPUs idle Shaohua Li
2009-06-24 6:39 ` Peter Zijlstra
2009-06-24 7:47 ` Shaohua Li
2009-06-24 8:03 ` Peter Zijlstra
2009-06-24 8:21 ` Shaohua Li
2009-06-26 18:16 ` Vaidyanathan Srinivasan
2009-06-29 2:54 ` Shaohua Li
2009-07-06 18:03 ` Vaidyanathan Srinivasan
2009-07-06 23:43 ` Andi Kleen [this message]
2009-07-07 0:50 ` Pallipadi, Venkatesh
2009-07-10 19:31 ` Len Brown
2009-06-24 17:20 ` Len Brown
2009-06-26 7:46 ` Peter Zijlstra
2009-06-26 16:46 ` Len Brown
2009-06-26 18:42 ` Vaidyanathan Srinivasan
2009-07-10 19:47 ` Len Brown
2009-06-26 19:49 ` Matthew Garrett
2009-07-10 20:29 ` Len Brown
2009-06-30 8:02 ` Shaohua Li
2009-07-07 8:26 ` Peter Zijlstra
2009-07-07 8:24 ` Peter Zijlstra
2009-07-10 20:41 ` Len Brown
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=20090706234346.GA8072@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=a.p.zijlstra@chello.nl \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=shaohua.li@intel.com \
--cc=svaidy@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox