Received: by 10.223.185.116 with SMTP id b49csp3678251wrg; Mon, 26 Feb 2018 04:16:53 -0800 (PST) X-Google-Smtp-Source: AG47ELuOr6fwvh6nDgCvN5Jvu8wwW/8ZsCtyBSpyBGZ8c1GjydQwNNLMZrT/nnu4u4m1Of65nE7J X-Received: by 10.99.180.77 with SMTP id n13mr2512378pgu.361.1519647413383; Mon, 26 Feb 2018 04:16:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519647413; cv=none; d=google.com; s=arc-20160816; b=PPEzCtbhiuTJqii1aqmBBvT1CUc88yhE0Kt7zJPAGimfyJVYTt3tVNWBpe899kNM01 KuphWCRgmvB4DTkP6lHmfndrWw8DLGaGqUoty+BMygSQcHQ7S8jqV+mHOE1/PW5a/GRU 65hhBW6nH8bk9XCkeiI9ApLVhGjo87XVVTqME3RZqvKLA0zmGJEpsetI/Nd7rwY+Un73 al8suU0uFOn3VPHhl7WeEUWgcIeuQt9pR60pzvv4N0ZNv6w+SZAH1vNovsCRBLr/NffM RX3IqCjTkaLXn1INoH3WkiNpt1wCj7I0PNmeLnSRAMC4mw6PNCtCkdHN030IvpX1EtY/ OaVw== 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=p4zD/L2mBpH2SCxwa8zSAsKELu83jfiY8Ohh/6OPKZA=; b=BUFVYuI8sGvmHqkH1D3tEGQQHJzYB+CN8XyftXxw9bDDx5yhHK7u9FAWrDEkbIpsVB SuCUNLb+fkmYlbVIQux48YVATJAfYbXpcSy9RZNSRN/tZiKjsk0/655QAlMojZgqq+rp tnovuTflea2wYRZmL0PSf5S+jBK0CXwvPArJVKuPyTAUVNfkPZqFtEqlnlZsO0XeS/EI zz8HBZK2Sbebji6C3h5JoK/Ze2sWoWfsU3LmACUmPloR8CgjoqV9O+FL6wHwJf3mfe+X nNNBprj6B9iM6GVDgpse1L8j6b8UvpyX0wDTHvwRZMYQfURfo68GkakI3pagxa+j9ct1 y14g== 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 14-v6si6592512plb.444.2018.02.26.04.16.37; Mon, 26 Feb 2018 04:16:53 -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 S1752789AbeBZMPf (ORCPT + 99 others); Mon, 26 Feb 2018 07:15:35 -0500 Received: from mail.skyhub.de ([5.9.137.197]:54336 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752353AbeBZMPd (ORCPT ); Mon, 26 Feb 2018 07:15:33 -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 WE-onLtOsYmq; Mon, 26 Feb 2018 13:15:31 +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 4805B1EC0991; Mon, 26 Feb 2018 13:15:31 +0100 (CET) Date: Mon, 26 Feb 2018 13:15:09 +0100 From: Borislav Petkov To: Paolo Bonzini Cc: Wanpeng Li , LKML , kvm , Radim =?utf-8?B?S3LEjW3DocWZ?= Subject: Re: [PATCH] KVM: X86: Allow userspace to define the microcode version Message-ID: <20180226121509.GE4377@pd.tnic> References: <20180226094148.GA15539@pd.tnic> <20180226104921.GA4377@pd.tnic> <20180226111630.GB4377@pd.tnic> <20180226113000.GC4377@pd.tnic> <20180226114409.GD4377@pd.tnic> <46cecef2-b0fb-b0c2-bbf3-983328d52763@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <46cecef2-b0fb-b0c2-bbf3-983328d52763@redhat.com> 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 12:54:52PM +0100, Paolo Bonzini wrote: > I don't understand how one thing follows from the other. How are writes > to 0x8B related to having a virtualized microcode loaded (which is a > concept that actually makes no sense at all)? I'm questioning the whole idea. 0x8b is the MSR which gives you the microcode revision. Most CPUs don't even allow writing to it, AFAICT. (SDM says "may prevent writing" on VM transitions.) So how is that host-initiated write to 0x8b is even going to work, in reality? kvm module writes the microcode version in there? How does the admin work around that? > It has already been fixed for a few months, and fixing it is indeed the > right thing to do independent of this patch. Yap. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.