From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Ostrovsky Subject: Re: [PATCH] x86, microcode: Don't initialize microcode code on paravirt Date: Tue, 02 Dec 2014 09:36:40 -0500 Message-ID: <547DCE78.1020906@oracle.com> References: <1417469264-31470-1-git-send-email-boris.ostrovsky@oracle.com> <20141201220057.GC4730@pd.tnic> <547CEC5C.9070201@oracle.com> <20141201223708.GF4730@pd.tnic> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: x86@kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org, david.vrabel@citrix.com, konrad.wilk@oracle.com, pbonzini@redhat.com, gleb@kernel.org, kvm@vger.kernel.org To: Borislav Petkov Return-path: In-Reply-To: <20141201223708.GF4730@pd.tnic> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 12/01/2014 05:37 PM, Borislav Petkov wrote: > On Mon, Dec 01, 2014 at 05:31:56PM -0500, Boris Ostrovsky wrote: >> I think so. The problem we have now is __pa() macro that we only use >> on 32-bit. I'll queue this for overnight tests to make sure and if it >> indeed works then 3.19 should be fine. > Cool, thanks. All tests passed. > I'd still take your patch for 3.19 though because I'm fixing the 32-bit > reloading path properly and will remove the ifdef afterwards. > > And even then, I'd like to prevent loading the module on a paravirt > guest if it is totally unneeded there. > I wonder whether we should prevent all guests (not just paravirt) from loading microcode driver (and from doing early microcode loading). -boris