Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755378AbcJZVk5 (ORCPT ); Wed, 26 Oct 2016 17:40:57 -0400 Received: from mx1.redhat.com ([209.132.183.28]:45702 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754810AbcJZVkz (ORCPT ); Wed, 26 Oct 2016 17:40:55 -0400 Subject: Re: [PATCH 0/2] KVM: x86: emulate fxsave and fxrstor To: =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , linux-kernel@vger.kernel.org, kvm@vger.kernel.org References: <20161026205014.19801-1-rkrcmar@redhat.com> Cc: Paolo Bonzini From: Laszlo Ersek Message-ID: <0e5108b0-15f0-56c1-b9e5-626ecff644d7@redhat.com> Date: Wed, 26 Oct 2016 23:40:52 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161026205014.19801-1-rkrcmar@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Wed, 26 Oct 2016 21:40:54 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1369 Lines: 36 On 10/26/16 22:50, Radim Krčmář wrote: > [1/2] adds the emulation (and could be split into two patches if you'd like), > [2/2] just refactors the code. > > This should fix an issue that users are hitting. Laszlo found several reports: > - https://bugs.launchpad.net/qemu/+bug/1623276 > - https://bugzilla.proxmox.com/show_bug.cgi?id=1182 > - https://bugs.archlinux.org/task/50778 > > I have only tested it with a simple kvm-unit-tests, though. Reproducing the > iPXE issue is on the way ... > > > Radim Krčmář (2): > KVM: x86: emulate fxsave and fxrstor > KVM: x86: save one bit in ctxt->d > > arch/x86/kvm/emulate.c | 110 ++++++++++++++++++++++++++++++++++++++++++------- > 1 file changed, 94 insertions(+), 16 deletions(-) > I was just about to post iPXE patches that would disable the FXSAVE / FXRSTOR instructions in the CONFIG=qemu build (*), but you beat me to it with the KVM emulation code ;) (*) If you look at the iPXE commit that added them, they are a workaround for a Tivoli VMM bug; i.e., irrelevant for QEMU/KVM guests. ... Actually, those iPXE patches that conditionalize FXSAVE / FXRSTOR may still make sense -- we can rebuild iPXE, and bundle the refreshed binaries with QEMU v2.7.1, and swiftly at that. Whereas the KVM patches could take more time to propagate to users?... Not sure. What do you guys think? Thanks Laszlo