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 S1751994AbdJPKQF (ORCPT <rfc822;w@1wt.eu>);
        Mon, 16 Oct 2017 06:16:05 -0400
Received: from mail.skyhub.de ([5.9.137.197]:44872 "EHLO mail.skyhub.de"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751376AbdJPKQE (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 16 Oct 2017 06:16:04 -0400
Date: Mon, 16 Oct 2017 12:15:48 +0200
From: Borislav Petkov <bp@alien8.de>
To: kernel test robot <xiaolong.ye@intel.com>,
        Andy Lutomirski <luto@kernel.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
        Markus Trippelsdorf <markus@trippelsdorf.de>,
        Adam Borowski <kilobyte@angband.pl>, Brian Gerst <brgerst@gmail.com>,
        Johannes Hirte <johannes.hirte@datenkhaos.de>, lkp@01.org
Subject: Re: [lkp-robot] [x86/mm]  c4c3c3c2d0:  will-it-scale.per_process_ops
 -61.0% regression
Message-ID: <20171016101548.v3l3jgcbdogrvbvh@pd.tnic>
References: <20171009170231.fkpraqokz6e4zeco@pd.tnic>
 <20171016023917.GG26196@yexl-desktop>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20171016023917.GG26196@yexl-desktop>
User-Agent: NeoMutt/20170113 (1.7.2)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, Oct 16, 2017 at 10:39:17AM +0800, kernel test robot wrote:
> 
> Greeting,
> 
> FYI, we noticed a -61.0% regression of will-it-scale.per_process_ops due to commit:
> 
> 
> commit: c4c3c3c2d00826c88b5c02c20e80704664424b9b ("x86/mm: Flush more aggressively in lazy TLB mode")
> url: https://github.com/0day-ci/linux/commits/Borislav-Petkov/x86-mm-Flush-more-aggressively-in-lazy-TLB-mode/20171011-115901
> 
> 
> in testcase: will-it-scale
> on test machine: 88 threads Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz with 64G memory

Say what now?

This is actually what got applied upstream:

b956575bed91 ("x86/mm: Flush more aggressively in lazy TLB mode")

and AFAICT, that machine is BDW and it should have PCID, right?

Or wait, that's a guest so PCID is probably not even usable for guests.
Or should we disable it in VMs?

I'm confused. Andy?

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.