mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: Len Brown <lenb@kernel.org>,
	x86@kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Len Brown <len.brown@intel.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 2/5] x86: remove idle_notifier
Date: Thu, 8 Dec 2016 23:53:16 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1612082340170.3609@nanos> (raw)
In-Reply-To: <20161208220548.GC12472@amd>

On Thu, 8 Dec 2016, Pavel Machek wrote:
> On Thu 2016-12-08 10:18:13, Thomas Gleixner wrote:
> > I'm dealing with low-speed systems for 20 years now and that LED was never
> > important for me, quite the contrary, it's annoying to have the extra work
> > in the idle wakeup path which causes extra pointless latency. If you can't
> > figure out your keypress lag without that LED then feel free to patch your
> > own kernel, but stop trying to impose that nonsense on everyone.
> 
> The kernel already has the hooks, and they did not seem to bother
> anyone.

The have bothered a lot of people up to the point where we could remove
them, simply because they are pointless ballast and overhead in the wake
from idle path.

> Arm already has the functionality, and it is useful. You may
> not care, but so what. Leds are broken on x86, plain and simple.

BlinkenLEDs for idle were never available on x86 to begin with, so they
can't be broken.

Aisde of that the vast majority of x86 systems simply do not have LEDs
which are accessible from that context. So just to support a very
questionable use case with a very limited usefulness you want to impose
extra code into a code path which is already known to be too heavy weight
and people working on it to reduce the overhead.

> Perhaps that should not be your decision?

Feel free to complain to Linus. My maintainer decision stands.

> Feel free to patch it out of your kernel. Or feel free to argue that it
> needs to be removed from arm. But having unneccessary differences between
> architectures is just ugly.

Following that argumentation would require to add this to the core idle
code, so _ALL_ architetures have access to this, but that got turned down
by the core maintainers a more than a year ago for the very same reason.

Thanks,

	tglx

  reply	other threads:[~2016-12-08 22:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18  6:23 [PATCH 0/5] x86: remove idle notifier Len Brown
2016-11-18  6:23 ` [PATCH 1/5] i7300_idle: remove this driver Len Brown
2016-11-18  6:23   ` [PATCH 2/5] x86: remove idle_notifier Len Brown
2016-11-18 11:19     ` [tip:x86/idle] x86/idle: Remove idle_notifier tip-bot for Len Brown
2016-12-06 16:54     ` [PATCH 2/5] x86: remove idle_notifier Pavel Machek
2016-12-07 11:46       ` Thomas Gleixner
2016-12-07 13:40         ` Pavel Machek
2016-12-08  9:18           ` Thomas Gleixner
2016-12-08 22:05             ` Pavel Machek
2016-12-08 22:53               ` Thomas Gleixner [this message]
2016-11-18  6:23   ` [PATCH 3/5] x86: remove is_idle flag Len Brown
2016-11-18 11:20     ` [tip:x86/idle] x86/idle: Remove " tip-bot for Len Brown
2016-11-18  6:23   ` [PATCH 4/5] x86: remove x86_test_and_clear_bit_percpu() Len Brown
2016-11-18 11:20     ` [tip:x86/idle] x86: Remove x86_test_and_clear_bit_percpu() tip-bot for Len Brown
2016-11-18  6:23   ` [PATCH 5/5] x86: remove enter_idle(), exit_idle() Len Brown
2016-11-18 11:21     ` [tip:x86/idle] x86/idle: Remove " tip-bot for Len Brown
2016-11-18 11:19   ` [tip:x86/idle] i7300_idle: Remove this driver tip-bot for Len Brown
2016-11-18  8:17 ` [PATCH 0/5] x86: remove idle notifier Ingo Molnar

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=alpine.DEB.2.20.1612082340170.3609@nanos \
    --to=tglx@linutronix.de \
    --cc=len.brown@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --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 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®