From: Ingo Molnar <mingo@kernel.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Andy Lutomirski <luto@kernel.org>,
Andy Henroid <andrew.d.henroid@intel.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>, X86 ML <x86@kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: Getting rid of i7300_idle's idle notifier?
Date: Fri, 5 Jun 2015 08:52:19 +0200 [thread overview]
Message-ID: <20150605065219.GA19628@gmail.com> (raw)
In-Reply-To: <CALCETrUb6yhLAZ5P3J86h7DVR-vq0aVD9EHTc3YRPU2E735ETg@mail.gmail.com>
* Andy Lutomirski <luto@amacapital.net> wrote:
> On Thu, Jun 4, 2015 at 4:32 PM, Andy Lutomirski <luto@kernel.org> wrote:
>
> > AFAICT the sole purpose for the hideous x86_64 idle_notifier mess is to
> > support i7300_idle. IMO this junk does not belong in IRQ handling, etc. Can
> > we redo this to work in some kind of generic way?
> >
> > I have no idea why it makes sense to twiddle I/O AT registers in the beginning
> > of whatever IRQ wakes up the CPU.
> >
> > Note that, if absolutely necessary, the ECX bit 0 MWAIT extension can be used
> > to reliably execute code before handling interrupts that wake us from idle.
> > That is, there could be a real cpuidle driver for that chip that does:
> >
> > cli;
> > poke ioat;
> > mwait(ecx = 1);
> > poke ioat;
> > sti;
> >
> > Or we could delete the driver entirely.
>
> It's even easier than that. Just shove the hooks into acpi_idle_do_entry or
> similar and remove them from every other exit_idle call site in the kernel.
Yes!
Interested in doing a patch?
Thanks,
Ingo
next prev parent reply other threads:[~2015-06-05 6:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 23:32 Getting rid of i7300_idle's idle notifier? Andy Lutomirski
2015-06-05 0:31 ` Andy Lutomirski
2015-06-05 6:52 ` Ingo Molnar [this message]
2015-06-06 16:06 ` Andy Lutomirski
2015-06-30 20:09 ` 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=20150605065219.GA19628@gmail.com \
--to=mingo@kernel.org \
--cc=andrew.d.henroid@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
/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.