From: Marcelo Tosatti <mtosatti@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Avi Kivity <avi@redhat.com>, kvm <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH][uq/master] kvm: x86: Avoid runtime allocation of xsave buffer
Date: Tue, 8 Nov 2011 18:44:21 -0200 [thread overview]
Message-ID: <20111108204421.GA19493@amt.cnet> (raw)
In-Reply-To: <4EA99426.9060208@siemens.com>
On Thu, Oct 27, 2011 at 07:25:58PM +0200, Jan Kiszka wrote:
> Keep a per-VCPU xsave buffer for kvm_put/get_xsave instead of
> continuously allocating and freeing it on state sync.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> target-i386/cpu.h | 3 ++-
> target-i386/kvm.c | 15 +++++++--------
> 2 files changed, 9 insertions(+), 9 deletions(-)
Applied both, thanks.
prev parent reply other threads:[~2011-11-08 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 17:25 [Qemu-devel] [PATCH][uq/master] kvm: x86: Avoid runtime allocation of xsave buffer Jan Kiszka
2011-11-08 20:44 ` Marcelo Tosatti [this message]
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=20111108204421.GA19493@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).