Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B5573C636D6 for ; Mon, 20 Feb 2023 19:20:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232866AbjBTTUu (ORCPT ); Mon, 20 Feb 2023 14:20:50 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51002 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232416AbjBTTUr (ORCPT ); Mon, 20 Feb 2023 14:20:47 -0500 Received: from mail.skyhub.de (mail.skyhub.de [5.9.137.197]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7B4411286B for ; Mon, 20 Feb 2023 11:20:46 -0800 (PST) Received: from zn.tnic (p5de8e9fe.dip0.t-ipconnect.de [93.232.233.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 028471EC04DA; Mon, 20 Feb 2023 20:20:45 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1676920845; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=5Q9htt2FScRK2Padeb0fDI2W5lo6XN2QsQTinSxh1I8=; b=ZmPYq/DDbgj4DMWYBXGJ5pXVpF40/pidorLOojp/Wchsp0KPtW+QH17EUV+D9NHW1AoZ/c X2AXk/OAKTe/8Zzj+KmqGoj++7sO5QCnCELsk7QzrRxPJyWHQhIc4+aCYv+Ql/6vWOt94y zz6uFVyaH8yTK1j3dbuD4UFlEugSpPE= Date: Mon, 20 Feb 2023 20:20:41 +0100 From: Borislav Petkov To: Josh Poimboeuf Cc: KP Singh , linux-kernel@vger.kernel.org, pjt@google.com, evn@google.com, tglx@linutronix.de, mingo@redhat.com, dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com, peterz@infradead.org, pawan.kumar.gupta@linux.intel.com, kim.phillips@amd.com, alexandre.chartre@oracle.com, daniel.sneddon@linux.intel.com, =?utf-8?B?Sm9zw6k=?= Oliveira , Rodrigo Branco , Alexandra Sandulescu , Jim Mattson Subject: Re: [PATCH] x86/bugs: Allow STIBP with IBRS Message-ID: References: <20230220121350.aidsipw3kd4rsyss@treble> <20230220163442.7fmaeef3oqci4ee3@treble> <20230220175929.2laflfb2met6y3kc@treble> <20230220182717.uzrym2gtavlbjbxo@treble> <20230220190908.gfd2c4tuzeb7cft6@treble> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20230220190908.gfd2c4tuzeb7cft6@treble> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 20, 2023 at 11:09:08AM -0800, Josh Poimboeuf wrote: > No it was supposed to be "no STIBP with *eIBRS*". Ok, good. > As far as I can tell, that document was never updated to describe > spectre_v2=ibrs in the first place. That would be a whole 'nother patch > which I'm not volunteering for. Nice try ;-) What do you think the maintainers are for? To clean up after people... ;-\ As a matter of fact, updating the documentation is already on my ever-growing TODO list. But for this patch I'd like to ask whoever of you does it, to add a one or two sentences about why we need to allow STIBP selection with IBRS. The rest of the documentation we'll flesh out in time. Thx. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette