mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Quan Xu <quan.xu0@gmail.com>, Rik van Riel <riel@redhat.com>,
	"quan.xu04@gmail.com" <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
Subject: Re: [PATCH 1/2] x86,kvm: move qemu/guest FPU switching out to vcpu_run
Date: Thu, 16 Nov 2017 11:21:39 +0100	[thread overview]
Message-ID: <9ba2d4c1-0781-419e-ddeb-77e0494583d2@redhat.com> (raw)
In-Reply-To: <0fc15536-0b34-51b6-cc14-00989825b0bc@gmail.com>

On 16/11/2017 06:06, Quan Xu wrote:
> when vcpu thread is scheduled out, the pkru value in
> current->thread.fpu.state may be the host pkru value, instead of
> guest pkru value (of course, this _assumes_ that the pkru is in
> current->thread.fpu.state as well). in this way, the pkru may be a
> coner case.

Rik may correct me, but I think this is not possible.  Preemption is
disabled all the time while PKRU = guest_pkru (which is only during
vmx_vcpu_run).

Context switching will only happen in vcpu_enter_guest() after
preempt_enable() for a preemptible kernel, or in vcpu_run via
cond_resched() for a non-preemptible kernel.

Thanks,

Paolo

> 
> VM migration again, in case,
>            source_host_pkru_value != guest_pkru_value,
>            target_host_pkru_value == guest_pkru_value..
> 
> the pkru status would be inconsistent..

  reply	other threads:[~2017-11-16 10:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14 21:54 [PATCH v2 0/2] x86,kvm: move qemu/guest FPU switching out to kvm_arch_vcpu_ioctl_run riel
2017-11-14 21:54 ` [PATCH 1/2] x86,kvm: move qemu/guest FPU switching out to vcpu_run riel
2017-11-15  0:47   ` Wanpeng Li
2017-11-15  3:03     ` Rik van Riel
2017-11-15  4:33       ` Wanpeng Li
2017-11-15 14:40         ` Rik van Riel
2017-11-16  5:54           ` Wanpeng Li
2017-11-15  6:53   ` quan.xu04
2017-11-15 14:43     ` Rik van Riel
2017-11-15 15:09       ` Paolo Bonzini
2017-11-16  2:50       ` Quan Xu
2017-11-16  4:21         ` Rik van Riel
2017-11-16  5:06           ` Quan Xu
2017-11-16 10:21             ` Paolo Bonzini [this message]
2017-11-16 12:12               ` Quan Xu
2017-11-16 12:18                 ` Paolo Bonzini
2017-11-16 13:35                   ` Quan Xu
2017-11-16 13:39                     ` Paolo Bonzini
     [not found]                       ` <d67cef62-3165-50cd-36e8-be7c555dc79e@gmail.com>
2017-11-16 17:50                         ` Paolo Bonzini
2017-11-17  2:54                           ` Quan Xu
2017-11-14 21:54 ` [PATCH 2/2] x86,kvm: remove KVM emulator get_fpu / put_fpu riel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9ba2d4c1-0781-419e-ddeb-77e0494583d2@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=david@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quan.xu04@gmail.com \
    --cc=quan.xu0@gmail.com \
    --cc=riel@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®