All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: qemu-devel@nongnu.org, ehabkost@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH uq/master 2/2] KVM: make XSAVE support more robust
Date: Mon, 09 Sep 2013 14:00:14 +0200	[thread overview]
Message-ID: <522DB84E.2080009@redhat.com> (raw)
In-Reply-To: <20130909104155.GP17294@redhat.com>

Il 09/09/2013 12:41, Gleb Natapov ha scritto:
>>>> In fact, perhaps even XSTATE_SUPPORTED is not restrictive enough here,
>>>> and we should hide all features that are not visible in CPUID.  It is
>>>> okay, however, to test it in cpu_post_load.
>>>
>>> The kernel should not even return state that is not visible in CPUID.
>>
>> That's an interesting point of view that I hadn't considered.  But just
>> like you asked me why it should return state that is not visible in
>> CPUID, I'm asking you why it should not...
>>
> For number of reasons. First because since a sate is not used there is no
> point in migrating it. Second to make interface more deterministic for
> QEMU. i.e QEMU configures only features it supports and gets
> exactly same state from the kernel no matter what host cpu is and what
> kernel version is. This patch will not be needed since kernel will do
> the job.

Good reasons, thanks.  Let's do it in the kernel then and avoid this
patch altogether.

Paolo

WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH uq/master 2/2] KVM: make XSAVE support more robust
Date: Mon, 09 Sep 2013 14:00:14 +0200	[thread overview]
Message-ID: <522DB84E.2080009@redhat.com> (raw)
In-Reply-To: <20130909104155.GP17294@redhat.com>

Il 09/09/2013 12:41, Gleb Natapov ha scritto:
>>>> In fact, perhaps even XSTATE_SUPPORTED is not restrictive enough here,
>>>> and we should hide all features that are not visible in CPUID.  It is
>>>> okay, however, to test it in cpu_post_load.
>>>
>>> The kernel should not even return state that is not visible in CPUID.
>>
>> That's an interesting point of view that I hadn't considered.  But just
>> like you asked me why it should return state that is not visible in
>> CPUID, I'm asking you why it should not...
>>
> For number of reasons. First because since a sate is not used there is no
> point in migrating it. Second to make interface more deterministic for
> QEMU. i.e QEMU configures only features it supports and gets
> exactly same state from the kernel no matter what host cpu is and what
> kernel version is. This patch will not be needed since kernel will do
> the job.

Good reasons, thanks.  Let's do it in the kernel then and avoid this
patch altogether.

Paolo

  reply	other threads:[~2013-09-09 12:00 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05 13:06 [PATCH uq/master 0/2] KVM: issues with XSAVE support Paolo Bonzini
2013-09-05 13:06 ` [Qemu-devel] " Paolo Bonzini
2013-09-05 13:06 ` [PATCH uq/master 1/2] x86: fix migration from pre-version 12 Paolo Bonzini
2013-09-05 13:06   ` [Qemu-devel] " Paolo Bonzini
2013-09-08 11:40   ` Gleb Natapov
2013-09-08 11:40     ` [Qemu-devel] " Gleb Natapov
2013-09-09  8:31     ` Paolo Bonzini
2013-09-09  8:31       ` [Qemu-devel] " Paolo Bonzini
2013-09-09  9:03       ` Gleb Natapov
2013-09-09  9:03         ` [Qemu-devel] " Gleb Natapov
2013-09-09  9:53         ` Paolo Bonzini
2013-09-09  9:53           ` [Qemu-devel] " Paolo Bonzini
2013-09-09 10:54           ` Gleb Natapov
2013-09-09 10:54             ` [Qemu-devel] " Gleb Natapov
2013-09-09 10:58             ` Gleb Natapov
2013-09-09 10:58               ` [Qemu-devel] " Gleb Natapov
2013-09-09 11:07             ` Paolo Bonzini
2013-09-09 11:07               ` [Qemu-devel] " Paolo Bonzini
2013-09-09 11:28               ` Gleb Natapov
2013-09-09 11:28                 ` [Qemu-devel] " Gleb Natapov
2013-09-09 11:46                 ` Paolo Bonzini
2013-09-09 11:46                   ` [Qemu-devel] " Paolo Bonzini
2013-09-09 12:00                   ` Gleb Natapov
2013-09-09 12:00                     ` [Qemu-devel] " Gleb Natapov
2013-09-05 13:06 ` [PATCH uq/master 2/2] KVM: make XSAVE support more robust Paolo Bonzini
2013-09-05 13:06   ` [Qemu-devel] " Paolo Bonzini
2013-09-08 11:52   ` Gleb Natapov
2013-09-08 11:52     ` [Qemu-devel] " Gleb Natapov
2013-09-09  8:51     ` Paolo Bonzini
2013-09-09  8:51       ` [Qemu-devel] " Paolo Bonzini
2013-09-09  9:18       ` Gleb Natapov
2013-09-09  9:18         ` [Qemu-devel] " Gleb Natapov
2013-09-09  9:50         ` Paolo Bonzini
2013-09-09  9:50           ` [Qemu-devel] " Paolo Bonzini
2013-09-09 10:41           ` Gleb Natapov
2013-09-09 10:41             ` [Qemu-devel] " Gleb Natapov
2013-09-09 12:00             ` Paolo Bonzini [this message]
2013-09-09 12:00               ` Paolo Bonzini

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=522DB84E.2080009@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.