All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roedel, Joerg" <Joerg.Roedel@amd.com>
To: Avi Kivity <avi@redhat.com>
Cc: "Hao, Xudong" <xudong.hao@intel.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"Zhang, Xiantao" <xiantao.zhang@intel.com>
Subject: Re: [PATCH] kvm/fpu: Enable fully eager restore kvm FPU
Date: Mon, 20 Aug 2012 12:53:45 +0200	[thread overview]
Message-ID: <20120820105345.GH2582@amd.com> (raw)
In-Reply-To: <503214BE.8050706@redhat.com>

On Mon, Aug 20, 2012 at 01:43:10PM +0300, Avi Kivity wrote:
> On 08/20/2012 01:14 PM, Roedel, Joerg wrote:
> > On Mon, Aug 20, 2012 at 01:08:14PM +0300, Avi Kivity wrote:
> >> On 08/20/2012 12:24 PM, Roedel, Joerg wrote:
> > 
> >> So it was broken all along?  Yikes.
> > 
> > There is no LWP support in the kernel and thus KVM can't expose it to
> > guests. So for now nothing should be broken, no?
> 
> Oh, we mask out xcr0 bits not supported by the host.
> 
> So it's broken in another way: it isn't exposed.  Pity, it's such a nice
> feature.

Right, that is very sad. We can support it in KVM even without Linux
host support, but there is no OS which enables this feature yet, so it
is rather useless to do it in KVM only.


	Joerg



  reply	other threads:[~2012-08-20 10:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-16  5:14 [PATCH] kvm/fpu: Enable fully eager restore kvm FPU Xudong Hao
2012-08-16  9:08 ` Avi Kivity
2012-08-16  9:48   ` Hao, Xudong
2012-08-16 10:59     ` Avi Kivity
2012-08-16 11:50       ` Hao, Xudong
2012-08-20  9:24       ` Roedel, Joerg
2012-08-20 10:08         ` Avi Kivity
2012-08-20 10:14           ` Roedel, Joerg
2012-08-20 10:43             ` Avi Kivity
2012-08-20 10:53               ` Roedel, Joerg [this message]
2012-08-23  8:51               ` Hao, Xudong
2012-09-03  9:23                 ` Avi Kivity
2012-09-05  1:10                   ` Hao, Xudong

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=20120820105345.GH2582@amd.com \
    --to=joerg.roedel@amd.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=xiantao.zhang@intel.com \
    --cc=xudong.hao@intel.com \
    /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.