From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eduardo Habkost Subject: Re: [PATCH] KVM: X86: Allow userspace to define the microcode version Date: Mon, 23 Apr 2018 10:08:23 -0300 Message-ID: <20180423130823.GM29865@localhost.localdomain> References: <24cd527d-5287-f0be-ffe8-eab341bf1d94@redhat.com> <3866d359-0ef8-6a99-6254-84890be62b93@redhat.com> <20180226122205.GG4377@pd.tnic> <20180417202417.GA29865@localhost.localdomain> <20180418090329.GJ29865@localhost.localdomain> <20180423125849.GD22238@pd.tnic> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Paolo Bonzini , Wanpeng Li , LKML , kvm , Radim =?utf-8?B?S3LEjW3DocWZ?= To: Borislav Petkov Return-path: Content-Disposition: inline In-Reply-To: <20180423125849.GD22238@pd.tnic> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Mon, Apr 23, 2018 at 02:58:49PM +0200, Borislav Petkov wrote: > On Wed, Apr 18, 2018 at 12:36:37PM +0200, Paolo Bonzini wrote: > > On 18/04/2018 11:03, Eduardo Habkost wrote: > > >>> QEMU setting ucode_rev automatically using the host value when > > >>> using "-cpu host" (with no need for explicit ucode_rev option) > > >>> makes sense to me. > > >> QEMU can't get the host value by rdmsr MSR_IA32_UCODE_REV directly > > >> since rdmsr will #GP when ring !=0, any idea? > > > By looking at kvm_get_msr_feature(), it looks like > > > ioctl(system_fd, KVM_GET_MSRS) would return the host MSR value > > > for us. > > > > Yes, that's exactly what it was introduced for (together with other MSRs > > including VMX capabilities). > > Can't qemu do: > > grep microcode /proc/cpuinfo | awk '{ print $3 }' | head -n 1 It could, but why would QEMU do it if a real API already exists for that? -- Eduardo