From: Keir Fraser <keir@xen.org>
To: Andre Przywara <andre.przywara@amd.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 3/5] svm: implement instruction fetch part of DecodeAssist
Date: Mon, 18 Apr 2011 13:37:21 +0100 [thread overview]
Message-ID: <C9D1EF11.2CBA1%keir@xen.org> (raw)
In-Reply-To: <4DA83889.5060306@amd.com>
On 15/04/2011 13:22, "Andre Przywara" <andre.przywara@amd.com> wrote:
> Newer SVM implementations (Bulldozer) copy up to 15 bytes from the
> instruction stream into the VMCB when a #PF or #NPF exception is
> intercepted. This patch makes use of this information if available.
> This saves us from a) traversing the guest's page tables, b) mapping
> the guest's memory and c) copy the instructions from there into the
> hypervisor's address space.
> This speeds up #NPF intercepts quite a lot and avoids cache and TLB
> trashing.
Rewritten quite a bit and applied as c/s 23238. You probably should check it
still works and with the performance improvement you expect. :-)
-- Keir
> Signed-off-by: Andre Przywara <andre.przywara@amd.com>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-04-18 12:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 12:16 [PATCH 0/5] svm: implement new DecodeAssist feature Andre Przywara
2011-04-15 12:21 ` [PATCH 1/5] vmx/hvm: move mov-cr handling functions to generic HVM code Andre Przywara
2011-04-18 8:48 ` Keir Fraser
2011-04-15 12:21 ` [PATCH 2/5] svm: add bit definitions for SVM DecodeAssist Andre Przywara
2011-04-15 12:22 ` [PATCH 3/5] svm: implement instruction fetch part of DecodeAssist Andre Przywara
2011-04-18 9:10 ` Keir Fraser
2011-04-18 12:37 ` Keir Fraser [this message]
2011-04-15 12:23 ` [PATCH 4/5] svm: implement CR access " Andre Przywara
2011-04-15 12:24 ` [PATCH 5/5] svm: implement INVLPG " Andre Przywara
2011-04-18 9:07 ` Keir Fraser
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=C9D1EF11.2CBA1%keir@xen.org \
--to=keir@xen.org \
--cc=andre.przywara@amd.com \
--cc=xen-devel@lists.xensource.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.