From: Paolo Bonzini <pbonzini@redhat.com>
To: Andy Lutomirski <luto@amacapital.net>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: Wanpeng Li <wanpeng.li@linux.intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
stable@vger.kernel.org, Nadav Amit <namit@cs.technion.ac.il>
Subject: Re: [CFT PATCH 2/2] KVM: x86: support XSAVES usage in the host
Date: Fri, 21 Nov 2014 22:58:19 +0100 [thread overview]
Message-ID: <546FB57B.3000303@redhat.com> (raw)
In-Reply-To: <546F9B59.7060800@amacapital.net>
On 21/11/2014 21:06, Andy Lutomirski wrote:
>> > + cpuid_count(XSTATE_CPUID, index,
>> > + &size, &offset, &ecx, &edx);
>> > + memcpy(dest + offset, src, size);
> Is this really the best way to do this? cpuid is serializing, so this
> is possibly *very* slow.
The data is in arch/x86/kernel/xsave.c, but it is not exported. But
this is absolutely not a hotspot.
Paolo
next prev parent reply other threads:[~2014-11-21 21:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 18:31 [CFT PATCH 0/2] KVM: support XSAVES usage in the host Paolo Bonzini
2014-11-21 18:31 ` [CFT PATCH 1/2] kvm: x86: mask out XSAVES Paolo Bonzini
2014-11-21 18:31 ` [CFT PATCH 2/2] KVM: x86: support XSAVES usage in the host Paolo Bonzini
2014-11-21 20:06 ` Andy Lutomirski
2014-11-21 21:58 ` Paolo Bonzini [this message]
2014-11-24 2:10 ` Wanpeng Li
2014-11-24 10:07 ` Paolo Bonzini
2014-11-23 8:16 ` [CFT PATCH 0/2] KVM: " Nadav Amit
2014-11-23 8:24 ` Wanpeng Li
2014-11-23 8:31 ` Nadav Amit
2014-11-23 8:31 ` Nadav Amit
2014-11-23 8:34 ` Wanpeng Li
2014-11-24 11:39 ` Paolo Bonzini
2014-11-24 15:28 ` Nadav Amit
2014-11-24 15:54 ` Paolo Bonzini
2014-11-24 17:53 ` Paolo Bonzini
2014-11-24 18:31 ` Nadav Amit
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=546FB57B.3000303@redhat.com \
--to=pbonzini@redhat.com \
--cc=fenghua.yu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=namit@cs.technion.ac.il \
--cc=stable@vger.kernel.org \
--cc=wanpeng.li@linux.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.