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:   Sun, 13 Aug 2023 11:35:02 +0200
From:   Borislav Petkov <bp@alien8.de>
To:     Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc:     Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
        x86@kernel.org
Subject: Re: [regression/bisected] Add IBPB decreases performance in two times
Message-ID: <20230813093502.GBZNijxgueFxBTxWwG@fat_crate.local>
References: <CABXGCsNTaNw3q1OciYq111vdr+-ouaRVmwVqVJH4iT0NqxFAcQ@mail.gmail.com>
 <20230813082413.GAZNiTLaOxUNUHPvlf@fat_crate.local>
 <CABXGCsNoNaGLsuvHLRA7aG9FCckQpnXaXWoUGvRwzfRKNB4xzA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CABXGCsNoNaGLsuvHLRA7aG9FCckQpnXaXWoUGvRwzfRKNB4xzA@mail.gmail.com>
Precedence: bulk

On Sun, Aug 13, 2023 at 02:17:25PM +0500, Mikhail Gavrilov wrote:
> > spec_rstack_overflow=off
> 
> Thanks, I checked this and it works!

Right, so you have Zen4 and it already uses the default mitigation and
no IBPB is mitigating retbleed because Zen4 is not affected. (If
retbleed mitigates with IBPB, that is also the SRSO mitigation but this
is not the case for your machine).

So yeah, I guess disabling the mitigation is one option.

Another could be if you supply:

spectre_v2_user=on spec_rstack_overflow=microcode

on the kernel command line after upgrading your microcode. That would at
least take care of protecting one user process from another.

There's no microcode for your machine yet, AFAICT, but you could still
try the above to see whether that mitigation type is better than no
mitigation at all wrt gameplay.

As to the microcode, I guess you'll get it with a BIOS update according
to:

https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7005.html

the table cell about 7000 series.

HTH.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette