mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: "Andy Lutomirski" <luto@amacapital.net>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Brian Gerst" <brgerst@gmail.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Andrew Lutomirski" <luto@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Borislav Petkov" <bp@alien8.de>,
	"Denys Vlasenko" <dvlasenk@redhat.com>,
	"linux-tip-commits@vger.kernel.org"
	<linux-tip-commits@vger.kernel.org>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>
Subject: Re: [tip:x86/urgent] x86/entry/32: Add an ASM_CLAC to entry_SYSENTER_32
Date: Thu, 25 Feb 2016 09:40:57 +0100	[thread overview]
Message-ID: <20160225084056.GC12294@gmail.com> (raw)
In-Reply-To: <1456388974.3923.6.camel@gmail.com>


* Mike Galbraith <umgwanakikbuti@gmail.com> wrote:

> On Thu, 2016-02-25 at 09:14 +0100, Ingo Molnar wrote:
> 
> > But but ... 'context tracking' is not really something that a regular distro 
> > kernel cares about much - it's a nohz-full special AFAICS.

Let me qualify that: with the timer code maintenance hat on I really love all nohz 
variants (the deeper the better), but now I have my x86 maintainer hat on, and as 
such I'm really annoyed at those nohz folks adding overhead to the syscall hot 
path! ;-)

> (psst.. distros are shipping it)

Yeah, indeed, Fedora does - but AFAICS:

 fomalhaut:~> grep NO_HZ /boot/config-4.1.13-100.fc21.x86_64 
 CONFIG_NO_HZ_COMMON=y
 # CONFIG_NO_HZ_IDLE is not set
 CONFIG_NO_HZ_FULL=y
 # CONFIG_NO_HZ_FULL_ALL is not set
 # CONFIG_NO_HZ_FULL_SYSIDLE is not set
 CONFIG_NO_HZ=y
 CONFIG_RCU_FAST_NO_HZ=y

... which won't result in actual full-nohz CPUs unless you boot it with a special 
boot parameter, right?

What is the easiest way to query which/how many CPUs are in nohz-full mode and do 
context tracking? I somehow thought /proc/timer_* had that info, but that does not 
appear to be the case.

Thanks,

	Ingo

  reply	other threads:[~2016-02-25  8:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23 21:19 [PATCH] " Andy Lutomirski
2016-02-24 15:46 ` Brian Gerst
2016-02-24 16:56   ` Andy Lutomirski
2016-02-25  5:53 ` [tip:x86/urgent] " tip-bot for Andy Lutomirski
2016-02-25  6:00   ` H. Peter Anvin
2016-02-25  8:07     ` Andy Lutomirski
2016-02-25  8:11       ` Andy Lutomirski
2016-02-25  8:14       ` Ingo Molnar
2016-02-25  8:29         ` Mike Galbraith
2016-02-25  8:40           ` Ingo Molnar [this message]
2016-02-25  9:08             ` Mike Galbraith
     [not found]     ` <CALCETrWqCnhxvQ5qNp_O_7K7KW1H3FmHiX=mp+C5oeBEx=3YVA@mail.gmail.com>
2016-02-25 13:47       ` Brian Gerst
2016-02-25 15:42         ` Brian Gerst
2016-02-25 18:20           ` Andy Lutomirski
2016-02-25 18:30             ` Linus Torvalds
2016-02-25 18:40               ` Andy Lutomirski
2016-02-25 19:31               ` Brian Gerst
2016-02-25 19:39                 ` Andy Lutomirski
2016-02-25 19:49                   ` Brian Gerst
2016-02-25 19:52                     ` Andy Lutomirski
2016-02-25 20:54                 ` Linus Torvalds

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=20160225084056.GC12294@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=dvlasenk@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=luto@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=umgwanakikbuti@gmail.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

Powered by JetHome