Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 18 Jul 2022 09:19:01 +0100
From:   Ken Moffat <zarniwhoop@ntlworld.com>
To:     linux-kernel@vger.kernel.org
Subject: Retbleed, Zen2 and STIBP
Message-ID: <YtUXda9ymAI0ED7n@llamedos.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/2.2.6 (2022-06-05)
Precedence: bulk

Probably like most people, I find the detail of the available
retbleed mitigations obscure.  In particular, for zen2 the options
*might* include ibpb or unret.

But I have failed to find what 'unret' actually means.  Any
pointers, please ?

While ibpb might be available (and slow), on my Renoir with
microcode level (0860106h) there were no newer microcode versions
available when I last looked (a few weeks ago) but note 7 at the
bottom of
https://www.amd.com/system/files/documents/technical-guidance-for-mitigating-branch-type-confusion_v
7_20220712.pdf
implies that the relevant bit is only set on Renoir in 0860109h and
later.

Some of the text in that pdf implies that at least one of the
options could be set if not already set from the microcode, but the
amount of detail leaves me totally lost.

Assuming, for the moment, that I might want to try this full
mitigation, is there any way to set this in the absence of newer
microcode ?

Or should I just accept that the best I can get is 'unret', whatever
that means ?

ĸen
-- 
 It is very easy to get ridiculously confused about the tenses of
 time travel, but most things can be resolved by a sufficiently
 large ego.        -- The Last Continent