Received: by 10.223.185.116 with SMTP id b49csp3623428wrg; Mon, 26 Feb 2018 03:18:25 -0800 (PST) X-Google-Smtp-Source: AG47ELsFJZOQghNygB2bcCy2FamWB40oIm7WynA2DSkAb2SLxQDb+MO7OyZ/hWSTid593IQTpBPE X-Received: by 10.98.238.2 with SMTP id e2mr2314520pfi.68.1519643905174; Mon, 26 Feb 2018 03:18:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519643905; cv=none; d=google.com; s=arc-20160816; b=Z+vN2uA65YmWPOtH+9WmipZD9dU2ECYeVX18ugI6iveK40qzbrIJdYwRbp64nXOj9C XXVUJ/eJ+B3Cf8Rqg248kMVllwA9gSkii/T730RtntIX0BW1knZvqicDU8mEwRK0cxhA l4YlUSqrUd9SDrVi2kX6nbx0ojwr31Dhk7J7DdeT8cjwGSCY+m5zXoXJpFIeFX4wYXWB AVa+N42cCGul+GGOJOvAc/Q4G62CWOH7Il6RE8W8xJjb+DrW4XUlJ3DE+qPcjAXd9G/n 0Edu7lJ2ZQhdLnxs+AsaaNkBcOYTG7ebXh9H3Y8zNcFu+T5JbZyqqNEA5AHaaP/n4pNO vU5g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=whlUqdpBgPPBauAhni9uBS2IY2misLAz4uEqcqo7u/w=; b=NyZI+udjhg2ZZ13OoTAUilsbmWb+/rl+Cucc/6KpH0F89WoBW9Y3x00ruoH/NsixeI e2/pY5lM4TDElIOrVyRQNYWopy7sm+cOwAVyY/NhaRyoLaZyl18Hum/8L+9YLMRtVFQ2 smvIx4QAB/6njGAObopSssAC2R6lWuq/pqTrj9ogAgxA2CscC4L+p8B9F0wUttwtCx9y 6rwziISNS0v2RN4xKSbexWetQiopNNDFLElm8ku+5YXV9b0p94OvEJJt8ngaEwZsczrR 1TJFR7gI4y82cDp+oqDU1QN4qVP9KqEjM1YmZUfufVaVv25jUQrmg7zw7TqJbIiiFiCt B8YQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u186si5413610pgc.462.2018.02.26.03.18.10; Mon, 26 Feb 2018 03:18:25 -0800 (PST) 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; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752736AbeBZLQ5 (ORCPT + 99 others); Mon, 26 Feb 2018 06:16:57 -0500 Received: from mail.skyhub.de ([5.9.137.197]:51904 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752157AbeBZLQw (ORCPT ); Mon, 26 Feb 2018 06:16:52 -0500 X-Virus-Scanned: Nedap ESD1 at mail.skyhub.de Received: from mail.skyhub.de ([127.0.0.1]) by localhost (blast.alien8.de [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Q78TRIY2vKyO; Mon, 26 Feb 2018 12:16:51 +0100 (CET) Received: from pd.tnic (p200300EC2BCE210020411134B639594E.dip0.t-ipconnect.de [IPv6:2003:ec:2bce:2100:2041:1134:b639:594e]) (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 665061EC0376; Mon, 26 Feb 2018 12:16:51 +0100 (CET) Date: Mon, 26 Feb 2018 12:16:30 +0100 From: Borislav Petkov To: Wanpeng Li Cc: LKML , kvm , Paolo Bonzini , Radim =?utf-8?B?S3LEjW3DocWZ?= Subject: Re: [PATCH] KVM: X86: Allow userspace to define the microcode version Message-ID: <20180226111630.GB4377@pd.tnic> References: <1519629838-4898-1-git-send-email-wanpengli@tencent.com> <20180226094148.GA15539@pd.tnic> <20180226104921.GA4377@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.3 (2018-01-21) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 26, 2018 at 07:02:29PM +0800, Wanpeng Li wrote: > > So a guest will have *two* microcode revisions - both of which are most > > likely wrong?! > > Just one revision. So what does "the non-sensical value which is written by the guest will not reflect to guest-visible microcode revision" even mean then? cat /proc/cpuinfo in the guest shows what exactly? And what would RDMSR 0x8b show then? > https://lkml.org/lkml/2017/12/9/29 The original discussion explain in > more details. My argument stands: exposing microcode revisions to guests is the wrong approach. Instead, the kernel should not look at microcode revisions if it runs virtualized. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.