From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934946AbdKPNkI (ORCPT ); Thu, 16 Nov 2017 08:40:08 -0500 Received: from mx1.redhat.com ([209.132.183.28]:40644 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933959AbdKPNkA (ORCPT ); Thu, 16 Nov 2017 08:40:00 -0500 Subject: Re: [PATCH 1/2] x86,kvm: move qemu/guest FPU switching out to vcpu_run To: Quan Xu , Rik van Riel , "quan.xu04@gmail.com" Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, david@redhat.com, borntraeger@de.ibm.com, tglx@linutronix.de, rkrcmar@redhat.com References: <20171114215424.32214-1-riel@redhat.com> <20171114215424.32214-2-riel@redhat.com> <2e83dd3f-8f03-03ac-45e0-f2fae1d17013@gmail.com> <1510756981.21121.291.camel@redhat.com> <1510806094.21121.303.camel@redhat.com> <0fc15536-0b34-51b6-cc14-00989825b0bc@gmail.com> <9ba2d4c1-0781-419e-ddeb-77e0494583d2@redhat.com> <00231a24-f1a2-324e-1c32-0a5a7a3995f1@redhat.com> From: Paolo Bonzini Message-ID: <756023cd-5ba5-bb31-c7cc-7c91b6201632@redhat.com> Date: Thu, 16 Nov 2017 14:39:50 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Thu, 16 Nov 2017 13:40:00 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 16/11/2017 14:35, Quan Xu wrote: > but we introduce another method: > >       -- When the VCPU thread is scheduled back in, the context >          switch code will restore current->thread.fpu to the FPU >          registers. > > > there is still a window to restore current->thread.fpu to the FPU > registers before enter guest mode and > > preempt_disable(). That will always use the host PKRU. The guest PKRU is _never_ visible to the context switch code, because it's only ever used in a section that runs with preemption disabled. It's actually much simpler than before. Paolo > on target machine, after migration, the pkru value is source_host_pkru > in current->thread.fpu. > > in case, > >             source_host_pkru_value != guest_pkru_value, >             target_host_pkru_value == guest_pkru_value.. > > source_host_pkru_value may be restored to PKRU.. make pkru status > inconsistent..