From: Hollis Blanchard <hollisb@us.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [kvm-ppc-devel] [PATCH] [3/4] Add userpace tlb access
Date: Thu, 31 Jan 2008 22:52:45 +0000 [thread overview]
Message-ID: <1201819965.16049.90.camel@basalt> (raw)
In-Reply-To: <12016963202210-git-send-email-ehrhardt@linux.vnet.ibm.com>
On Thu, 2008-01-31 at 09:32 +0100, Christian Ehrhardt wrote:
> Hollis Blanchard wrote:
> >
> > Didn't we agree not to export the shadow TLB?
>
> The last agreement I found was to export shadow TLB read only which is what I have here.
> But it's easy to remove if needed ;-)
> So do you think it is really completely useless e.g. on a tlb dump ? If yes we can remove it, but
> if it can give us even a small benefit we should keep the read only access.
OK, we can keep it.
We will need custom debug tool code to understand any TLB dump anyways.
> >> +struct kvm_tlbe {
> >> + __u32 index;
> >> + union {
> >> + struct tlbe tlbe_ppc440;
> >> + /* Fix the size of the union (hopefully) */
> >> + char padding[32];
> >> + };
> >> +};
> >
> > Are you sure 32 bytes will be large enough? I think Freescale uses a ton
> > of MAS registers for TLB insertion.
>
> Well I thought it should be enough but we can use 64bit just to be safer.
I guess you mean 64 bytes. Wei, how many bytes do you think are needed
to save current and future TLB entries?
--
Hollis Blanchard
IBM Linux Technology Center
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel
next prev parent reply other threads:[~2008-01-31 22:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 12:31 [kvm-ppc-devel] [PATCH] [3/4] Add userpace tlb access ehrhardt
2008-01-30 21:29 ` Hollis Blanchard
2008-01-31 8:32 ` Christian Ehrhardt
2008-01-31 14:56 ` ehrhardt
2008-01-31 15:00 ` Christian Ehrhardt
2008-01-31 22:52 ` Hollis Blanchard [this message]
2008-02-01 3:16 ` Zhang Wei
2008-02-01 13:32 ` Zhang Wei
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=1201819965.16049.90.camel@basalt \
--to=hollisb@us.ibm.com \
--cc=kvm-ppc@vger.kernel.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 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.