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:   Tue, 11 Dec 2018 22:19:44 +0100
From:   Borislav Petkov <bp@alien8.de>
To:     "Lendacky, Thomas" <Thomas.Lendacky@amd.com>
Cc:     "x86@kernel.org" <x86@kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Andrea Arcangeli <aarcange@redhat.com>,
        Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
        Jiri Kosina <jkosina@suse.cz>, Ingo Molnar <mingo@redhat.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        Tim Chen <tim.c.chen@linux.intel.com>,
        David Woodhouse <dwmw@amazon.co.uk>
Subject: Re: [PATCH] x86/speculation: Add support for STIBP always-on
 preferred mode
Message-ID: <20181211211944.GT27375@zn.tnic>
References: <20181211190959.28321.56433.stgit@tlendack-t1.amdoffice.net>
 <3308b5d2-0c59-fa33-472b-f56633d39575@amd.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <3308b5d2-0c59-fa33-472b-f56633d39575@amd.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, Dec 11, 2018 at 07:19:09PM +0000, Lendacky, Thomas wrote:
> Alternatively, I can reuse SPECTRE_V2_USER_STRICT and issue pr_info_once()
> to show that the method has been switched.  This would reduce the changes
> to the code, but then the sysfs information doesn't show the switch (which
> may be just fine).

You can still query X86_FEATURE_AMD_STIBP_ALWAYS_ON in stibp_state(),
no?

But yeah, forcing SPECTRE_V2_USER_STRICT on STIBP_ALWAYS_ON makes sense
to me, with the already gazillion options we have :-\

-- 
Regards/Gruss,
    Boris.

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