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 S1760270AbcBYJJL (ORCPT <rfc822;w@1wt.eu>);
	Thu, 25 Feb 2016 04:09:11 -0500
Received: from mail-wm0-f51.google.com ([74.125.82.51]:38523 "EHLO
	mail-wm0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1754819AbcBYJJC (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Thu, 25 Feb 2016 04:09:02 -0500
Message-ID: <1456391333.3709.8.camel@gmail.com>
Subject: Re: [tip:x86/urgent] x86/entry/32: Add an ASM_CLAC to
 entry_SYSENTER_32
From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Ingo Molnar <mingo@kernel.org>
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>
Date: Thu, 25 Feb 2016 10:08:53 +0100
In-Reply-To: <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>
	 <20160225084056.GC12294@gmail.com>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.16.5 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, 2016-02-25 at 09:40 +0100, Ingo Molnar wrote:
> * 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?

Yeah, you have to manually enable it unless you (in a suicidal moment)
enable CONFIG_NO_HZ_FULL_ALL.

> 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.

/sys/devices/system/cpu/nohz_full

	-Mike