From: "tiejun.chen" <tiejun.chen@windriver.com>
To: Caraman Mihai Claudiu-B02008 <B02008@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"agraf@suse.de" <agraf@suse.de>,
"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [v1][KVM][PATCH 1/1] kvm:ppc:booehv: direct ISI exception to Guest
Date: Thu, 9 May 2013 19:40:26 +0800 [thread overview]
Message-ID: <518B8B2A.1020103@windriver.com> (raw)
In-Reply-To: <300B73AA675FCE4A93EB4FC1D42459FF3F7FBE@039-SN2MPN1-012.039d.mgd.msft.net>
On 05/09/2013 07:34 PM, Caraman Mihai Claudiu-B02008 wrote:
>>>> VF stands for virtualization fault see MAS8[VF] and we may use it for
>> virtualized
>>
>> Looks KVM PPC have no this mechanism currently since I don't find MAS8_VF
>> is
>> used in kernel, right?
>
> Yes but 'we may use it' in the feature, I have a functional POC with VF.
Any IO performance to be improved with this POC?
> Now we capture virtualized MMIO accesses as TLB misses (we don't write
> into HW TLB guest translation outside visible memslots).
Yes.
Tiejun
next prev parent reply other threads:[~2013-05-09 11: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
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 ` tiejun.chen
2013-05-09 11:34 ` Caraman Mihai Claudiu-B02008
2013-05-09 11:40 ` tiejun.chen [this message]
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=518B8B2A.1020103@windriver.com \
--to=tiejun.chen@windriver.com \
--cc=B02008@freescale.com \
--cc=B07421@freescale.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).