Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 31 Jan 2018 01:41:55 +0100
From:   Borislav Petkov <bp@alien8.de>
To:     Tim Chen <tim.c.chen@linux.intel.com>
Cc:     David Woodhouse <dwmw@amazon.co.uk>, arjan@linux.intel.com,
        tglx@linutronix.de, karahmed@amazon.de, x86@kernel.org,
        linux-kernel@vger.kernel.org, peterz@infradead.org,
        pbonzini@redhat.com, ak@linux.intel.com,
        torvalds@linux-foundation.org, gregkh@linux-foundation.org,
        mingo@kernel.org, luto@kernel.org, linux@dominikbrodowski.net
Subject: Re: [PATCH] x86/speculation: Use Indirect Branch Prediction Barrier
 in context switch
Message-ID: <20180131004155.r2iz6vl7mmlav2yn@pd.tnic>
References: <1517263487-3708-1-git-send-email-dwmw@amazon.co.uk>
 <20180130203836.bsgme6kf6hstgbrx@pd.tnic>
 <024dd53b-1912-34fa-deb8-550c111df521@linux.intel.com>
 <20180130215731.pszc5u4gcc32ds4v@pd.tnic>
 <296de30b-515b-6eab-1b13-bb2f71451004@linux.intel.com>
 <20180130224340.2zdfqttupugtqww5@pd.tnic>
 <74fd9c82-cd18-562b-8df6-69f629da460b@linux.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <74fd9c82-cd18-562b-8df6-69f629da460b@linux.intel.com>
User-Agent: NeoMutt/20170609 (1.8.3)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, Jan 30, 2018 at 04:25:26PM -0800, Tim Chen wrote:
> As dumpable is a property in mm->flags, it affects all threads running
> on other cpus sharing the same mm.

It is not about sharing the same mm - it is about sharing the RSB. How
many logical CPUs share an RSB? If it is per core (which can have two
threads) then issuing the barrier should have effect on both threads.
Thus one barrier is enough.

IOW, the granularity is determined by how many logical CPUs share the
RSB not by how many logical CPUs share an mm.

-- 
Regards/Gruss,
    Boris.

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