From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1760031AbcBYIlE (ORCPT <rfc822;w@1wt.eu>);
	Thu, 25 Feb 2016 03:41:04 -0500
Received: from mail-wm0-f67.google.com ([74.125.82.67]:36239 "EHLO
	mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1758272AbcBYIlB (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Thu, 25 Feb 2016 03:41:01 -0500
Date: Thu, 25 Feb 2016 09:40:57 +0100
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>,
        =?iso-8859-1?Q?Fr=E9d=E9ric?= Weisbecker <fweisbec@gmail.com>
Subject: Re: [tip:x86/urgent] x86/entry/32: Add an ASM_CLAC to
 entry_SYSENTER_32
Message-ID: <20160225084056.GC12294@gmail.com>
References: <3e36be110724896e32a4a1fe73bacb349d3cba94.1456262295.git.luto@kernel.org>
 <tip-04d1d281dcfe683a53cddfab8371fc8bb302b069@git.kernel.org>
 <56CE9897.6080702@zytor.com>
 <CALCETrVz_24iYcwzG621Rjp0zzVYoO55Q4Yojtidf6Gr-G==8w@mail.gmail.com>
 <20160225081441.GA11615@gmail.com>
 <1456388974.3923.6.camel@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1456388974.3923.6.camel@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


* 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