From: Peter Zijlstra <peterz@infradead.org>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>,
Thomas Gleixner <tglx@linutronix.de>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Loongson (and other $ARCHs?) idle VS timer enqueue
Date: Sat, 22 Apr 2023 10:08:14 +0200 [thread overview]
Message-ID: <20230422080814.GA1214746@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <ZEK+IeTYsauHLozy@lothringen>
On Fri, Apr 21, 2023 at 06:47:29PM +0200, Frederic Weisbecker wrote:
> > *HOWEVER*
> >
> > intel_idle_irq() is affected -- except that we only (normally) use that
> > for very shallow idle states and it won't interact with NOHZ (because we
> > only disable the tick for deep idle states).
>
> Well I don't know, that doesn't look comfortable... :)
>
> Also why does it need to enable IRQs if ecx=1 ?
Supposedly this is some interrupt latency hack. See commit:
c227233ad64c ("intel_idle: enable interrupts before C1 on Xeons")
next prev parent reply other threads:[~2023-04-22 8:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 12:36 Frederic Weisbecker
2023-04-21 14:24 ` Peter Zijlstra
2023-04-21 16:47 ` Frederic Weisbecker
2023-04-22 8:08 ` Peter Zijlstra [this message]
2023-04-22 11:38 ` Peter Zijlstra
2023-04-22 14:48 ` Frederic Weisbecker
2023-04-21 15:24 ` Thomas Gleixner
2023-04-21 16:55 ` Frederic Weisbecker
2023-04-21 20:28 ` Thomas Gleixner
2023-04-22 8:17 ` Peter Zijlstra
2023-04-22 8:22 ` Peter Zijlstra
2023-04-22 14:21 ` Frederic Weisbecker
2023-04-22 15:04 ` Peter Zijlstra
2023-04-23 13:52 ` bibo, mao
2023-04-24 8:26 ` Frederic Weisbecker
2023-04-24 11:23 ` maobibo
2023-04-25 11:49 ` Peter Zijlstra
2023-04-25 13:25 ` maobibo
2023-04-25 13:28 ` WANG Xuerui
2023-04-26 0:46 ` maobibo
2023-04-26 2:10 ` WANG Xuerui
2023-04-26 2:23 ` maobibo
2023-06-06 22:07 ` Frederic Weisbecker
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=20230422080814.GA1214746@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=anna-maria@linutronix.de \
--cc=chenhuacai@kernel.org \
--cc=frederic@kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®