From: Scott Wood <scottwood@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/2] powerpc/e6500: TLB miss handler with hardware tablewalk support
Date: Fri, 15 Jun 2012 11:50:06 -0500 [thread overview]
Message-ID: <4FDB67BE.9040000@freescale.com> (raw)
In-Reply-To: <1339722302.9220.175.camel@pasglop>
On 06/14/2012 08:05 PM, Benjamin Herrenschmidt wrote:
>> - It has threads, but no "tlbsrx." -- so we need a spinlock and
>> a normal "tlbsx". Because we need this lock, hardware tablewalk
>> is mandatory on e6500 unless we want to add spinlock+tlbsx to
>> the normal bolted TLB miss handler.
>
> Isn't this a violation of the architecture ? (Isn't tlbsrx. mandatory ?
> in 2.06 MAV2 ?).
I don't think so -- not only does it have a category name, there's a
MAV2-specific bit in MMUCSR indicating whether the category is present.
I still don't understand why Freescale omitted it from a chip that has
threads, though.
-Scott
next prev parent reply other threads:[~2012-06-15 16:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 23:41 [PATCH 2/2] powerpc/e6500: TLB miss handler with hardware tablewalk support Scott Wood
2012-06-15 1:05 ` Benjamin Herrenschmidt
2012-06-15 16:50 ` Scott Wood [this message]
2012-06-15 22:02 ` Benjamin Herrenschmidt
2012-07-19 20:12 ` Scott Wood
2012-09-08 23:09 ` Benjamin Herrenschmidt
2012-09-07 4:41 ` Benjamin Herrenschmidt
[not found] ` <504A4C3D.3040709@freescale.com>
2012-09-07 23:01 ` Scott Wood
2012-09-07 23:50 ` Benjamin Herrenschmidt
2012-09-08 0:55 ` Nishanth Aravamudan
2012-09-08 10:15 ` Benjamin Herrenschmidt
2012-09-11 0:26 ` Scott Wood
2012-09-11 17:06 ` Caraman Mihai Claudiu-B02008
2012-09-11 17:24 ` 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=4FDB67BE.9040000@freescale.com \
--to=scottwood@freescale.com \
--cc=benh@kernel.crashing.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).