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 8CDB5C64EC7 for ; Tue, 28 Feb 2023 20:39:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229790AbjB1UjH (ORCPT ); Tue, 28 Feb 2023 15:39:07 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57192 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229518AbjB1UjE (ORCPT ); Tue, 28 Feb 2023 15:39:04 -0500 Received: from smtp-fw-9103.amazon.com (smtp-fw-9103.amazon.com [207.171.188.200]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 85D9D34C3B; Tue, 28 Feb 2023 12:39:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1677616743; x=1709152743; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=rl35dc1iPnbWuVVxE9D4Cxh5CG/w80f3pFsgYUgu3M8=; b=iu0vx/w7ByuM3K5svEztWEhgkrnQ4GVe/WOpMszve4lXG+A8HgHP+X3N sL6Nj2/13f7orx3sLtzqCBYgN3IkqLnatJ/0C/Dc3msU9ZEJVdwZNpwI0 ZM7yoMH7ld/lMulBON0MI4ayd8wFBGzMuNg9cKYXnYMHkDXL65Sv5wm3N 4=; X-IronPort-AV: E=Sophos;i="5.98,222,1673913600"; d="scan'208";a="1107738852" Received: from pdx4-co-svc-p1-lb2-vlan3.amazon.com (HELO email-inbound-relay-iad-1d-m6i4x-d23e07e8.us-east-1.amazon.com) ([10.25.36.214]) by smtp-border-fw-9103.sea19.amazon.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Feb 2023 19:42:11 +0000 Received: from EX13MTAUWB002.ant.amazon.com (iad12-ws-svc-p26-lb9-vlan3.iad.amazon.com [10.40.163.38]) by email-inbound-relay-iad-1d-m6i4x-d23e07e8.us-east-1.amazon.com (Postfix) with ESMTPS id 121C781208; Tue, 28 Feb 2023 19:42:08 +0000 (UTC) Received: from EX19D002ANA003.ant.amazon.com (10.37.240.141) by EX13MTAUWB002.ant.amazon.com (10.43.161.202) with Microsoft SMTP Server (TLS) id 15.0.1497.45; Tue, 28 Feb 2023 19:42:07 +0000 Received: from b0f1d8753182.ant.amazon.com (10.106.83.6) by EX19D002ANA003.ant.amazon.com (10.37.240.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.2.1118.24; Tue, 28 Feb 2023 19:42:03 +0000 From: Takahiro Itazuri To: CC: , , , , , , , , , Subject: Re: [PATCH 0/2] KVM: x86: Propagate AMD-specific IBRS bits to guests Date: Tue, 28 Feb 2023 19:41:53 +0000 Message-ID: <20230228194153.46995-1-itazur@amazon.com> X-Mailer: git-send-email 2.38.0 In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Originating-IP: [10.106.83.6] X-ClientProxiedBy: EX19D035UWB002.ant.amazon.com (10.13.138.97) To EX19D002ANA003.ant.amazon.com (10.37.240.141) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Date: Tue, 28 Feb 2023 20:24:12 +0100 From: Borislav Petkov > I'd prefer if VMMs did supply whatever they prefer to the guests > instead. None of those bits are used in the kernel for mitigations, as > you've realized. It is true that the kernel does not use those bits at all, but any codes could be run inside guests. One of examples is the following spectre/meltdown checker scipt used as de facto standard. https://github.com/speed47/spectre-meltdown-checker/blob/master/spectre-meltdown-checker.sh#L2768 Best regards, Takahiro Itazuri