From mboxrd@z Thu Jan 1 00:00:00 1970 From: Borislav Petkov Subject: Re: [PATCH] KVM: X86: Allow userspace to define the microcode version Date: Mon, 26 Feb 2018 13:22:05 +0100 Message-ID: <20180226122205.GG4377@pd.tnic> References: <20180226111630.GB4377@pd.tnic> <20180226113000.GC4377@pd.tnic> <20180226114409.GD4377@pd.tnic> <46cecef2-b0fb-b0c2-bbf3-983328d52763@redhat.com> <20180226121509.GE4377@pd.tnic> <24cd527d-5287-f0be-ffe8-eab341bf1d94@redhat.com> <3866d359-0ef8-6a99-6254-84890be62b93@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: Wanpeng Li , LKML , kvm , Radim =?utf-8?B?S3LEjW3DocWZ?= To: Paolo Bonzini Return-path: Content-Disposition: inline In-Reply-To: <3866d359-0ef8-6a99-6254-84890be62b93@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Mon, Feb 26, 2018 at 01:18:07PM +0100, Paolo Bonzini wrote: > > In this context, "host-initiated" write means written by KVM userspace > > with ioctl(KVM_SET_MSR). It generally happens only on VM startup, reset > > or live migration. > > To be clear, the target of the write is still the vCPU's emulated MSR. So how am I to imagine this as a user: qemu-system-x86_64 --microcode-revision=0xdeadbeef... ? -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.