From: Scott Wood <scottwood@freescale.com>
To: Bhushan Bharat-R65777 <R65777@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"agraf@suse.de" <agraf@suse.de>,
"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>,
"paulus@samba.org" <paulus@samba.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 5/6 v5] kvm: booke: clear host tlb reference flag on guest tlb invalidation
Date: Fri, 20 Sep 2013 13:08:10 -0500 [thread overview]
Message-ID: <1379700490.16231.19.camel@aoeu.buserror.net> (raw)
In-Reply-To: <6A3DF150A5B70D4F9B66A25E3F7C888D0717AEA1@039-SN2MPN1-011.039d.mgd.msft.net>
On Fri, 2013-09-20 at 13:04 -0500, Bhushan Bharat-R65777 wrote:
>
> > -----Original Message-----
> > From: Wood Scott-B07421
> > Sent: Friday, September 20, 2013 9:48 PM
> > To: Bhushan Bharat-R65777
> > Cc: Wood Scott-B07421; benh@kernel.crashing.org; agraf@suse.de;
> > paulus@samba.org; kvm@vger.kernel.org; kvm-ppc@vger.kernel.org; linuxppc-
> > dev@lists.ozlabs.org
> > Subject: Re: [PATCH 5/6 v5] kvm: booke: clear host tlb reference flag on guest
> > tlb invalidation
> >
> > On Thu, 2013-09-19 at 23:19 -0500, Bhushan Bharat-R65777 wrote:
> > > We uses these bit flags only for TLB1 and if size of stlbe is 4K then
> > > we set E500_TLB_TLB0 otherwise we set E500_TLB_BITMAP. Although I
> > > think that E500_TLB_BITMAP should be set only if stlbe size is less
> > > than gtlbe size.
> >
> > Why? Even if there's only one bit set in the map, we need it to keep track of
> > which entry was used.
>
> If there is one entry then will not this be simple/faster to not lookup bitmap and guest->host array?
> A flag indicate it is 1:1 map and this is physical address.
The difference would be negligible, and you'd have added overhead (both
runtime and complexity) of making this a special case.
-Scott
next prev parent reply other threads:[~2013-09-20 18:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 6:02 [PATCH 0/6 v5] kvm: powerpc: use cache attributes from linux pte Bharat Bhushan
2013-09-19 6:02 ` [PATCH 1/6 v5] powerpc: book3e: _PAGE_LENDIAN must be _PAGE_ENDIAN Bharat Bhushan
2013-09-19 6:02 ` [PATCH 2/6 v5] kvm: powerpc: allow guest control "E" attribute in mas2 Bharat Bhushan
2013-09-19 6:02 ` [PATCH 3/6 v5] kvm: powerpc: allow guest control "G" " Bharat Bhushan
2013-09-19 6:02 ` [PATCH 4/6 v5] kvm: powerpc: keep only pte search logic in lookup_linux_pte Bharat Bhushan
2013-10-04 13:27 ` Alexander Graf
2013-10-04 13:44 ` Bhushan Bharat-R65777
2013-09-19 6:02 ` [PATCH 5/6 v5] kvm: booke: clear host tlb reference flag on guest tlb invalidation Bharat Bhushan
2013-09-19 21:07 ` Scott Wood
2013-09-20 4:19 ` Bhushan Bharat-R65777
2013-09-20 16:18 ` Scott Wood
2013-09-20 18:04 ` Bhushan Bharat-R65777
2013-09-20 18:08 ` Scott Wood [this message]
2013-09-20 18:11 ` Bhushan Bharat-R65777
2013-09-19 6:02 ` [PATCH 6/6 v5] kvm: powerpc: use caching attributes as per linux pte Bharat Bhushan
2013-10-04 14:03 ` [PATCH 0/6 v5] kvm: powerpc: use cache attributes from " Alexander Graf
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=1379700490.16231.19.camel@aoeu.buserror.net \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=R65777@freescale.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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).