From: Scott Wood <scottwood@freescale.com>
To: Tiejun Chen <tiejun.chen@windriver.com>
Cc: <agraf@suse.de>, <kvm-ppc@vger.kernel.org>, <kvm@vger.kernel.org>,
<linuxppc-dev@lists.ozlabs.org>
Subject: Re: [v1][KVM][PATCH 1/1] kvm:ppc:booehv: direct ISI exception to Guest
Date: Tue, 7 May 2013 18:40:43 -0500 [thread overview]
Message-ID: <1367970043.3398.39@snotra> (raw)
In-Reply-To: <1367924791-24394-1-git-send-email-tiejun.chen@windriver.com> (from tiejun.chen@windriver.com on Tue May 7 06:06:30 2013)
On 05/07/2013 06:06:30 AM, Tiejun Chen wrote:
> We also can direct ISI exception to Guest like DSI.
>
> Signed-off-by: Tiejun Chen <tiejun.chen@windriver.com>
> ---
> arch/powerpc/kvm/booke_emulate.c | 3 +++
> arch/powerpc/kvm/e500mc.c | 3 ++-
> 2 files changed, 5 insertions(+), 1 deletion(-)
Are you seeing a real performance improvement from this? This will
interfere somewhat with using the VF bit, if we were to ever do so,
since VF only affects data accesses (and so the guest would see an ISI
storm rather than a machine check if it tries to execute from such an
address).
-Scott
next prev parent reply other threads:[~2013-05-07 23:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 11:06 [v1][KVM][PATCH 1/1] kvm:ppc:booehv: direct ISI exception to Guest Tiejun Chen
2013-05-07 23:40 ` Scott Wood [this message]
2013-05-08 1:53 ` tiejun.chen
2013-05-08 9:20 ` Caraman Mihai Claudiu-B02008
2013-05-08 9:28 ` tiejun.chen
2013-05-09 10:23 ` [v1][PATCH " tiejun.chen
2013-05-09 11:34 ` [v1][KVM][PATCH " Caraman Mihai Claudiu-B02008
2013-05-09 11:40 ` tiejun.chen
2013-05-09 12:36 ` Caraman Mihai Claudiu-B02008
2013-05-10 17:57 ` Alexander Graf
2013-05-10 19:22 ` Scott Wood
2013-05-10 19:39 ` Alexander Graf
2013-05-13 2:04 ` tiejun.chen
2013-05-08 19:09 ` Scott Wood
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=1367970043.3398.39@snotra \
--to=scottwood@freescale.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tiejun.chen@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox