From: Paolo Bonzini <pbonzini@redhat.com>
To: Owen Tuz <qemu.owentuz@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] xsave instruction not passed through correctly on AMD hardware
Date: Mon, 11 Nov 2013 17:56:36 +0100 [thread overview]
Message-ID: <52810C44.3050106@redhat.com> (raw)
In-Reply-To: <CAAhzb2ao2ypX5cKd493gCWSsxt_TSu91dwVCYaPY3ybmREXmYA@mail.gmail.com>
Il 11/11/2013 16:43, Owen Tuz ha scritto:
> Thanks, Paolo. We will test and let you know.
> I'm not familiar with LWP (some reading to do there) - are there any
> plans to support this in future, or is this just something that we're
> not interested in emulating?
Given Linux does not support LWP, and AMD is not really trying to
compete with Intel anymore, it is quite unlikely that KVM will support
LWP in the future.
Paolo
next prev parent reply other threads:[~2013-11-11 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 14:30 [Qemu-devel] xsave instruction not passed through correctly on AMD hardware Owen Tuz
2013-11-11 15:25 ` Paolo Bonzini
2013-11-11 15:43 ` Owen Tuz
2013-11-11 16:56 ` Paolo Bonzini [this message]
2013-11-13 12:11 ` Owen Tuz
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=52810C44.3050106@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu.owentuz@gmail.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.