From: David Gibson <david@gibson.dropbear.id.au>
To: linuxppc-embedded@lists.linuxppc.org
Cc: Dan Malek <dan@embeddededge.com>,
Tom Rini <trini@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: Do we need tlbsx at finish_tlb_load?
Date: Mon, 3 Jun 2002 12:43:44 +1000 [thread overview]
Message-ID: <20020603024344.GA6765@zax> (raw)
In-Reply-To: <20020530080434.GY16537@zax>
On Thu, May 30, 2002 at 06:04:34PM +1000, David Gibson wrote:
> A question to Dan and Tom in particular:
>
> At the moment on 4xx, just after finish_tlb_load, which is called by
> both the TLB miss handlers, we do a tlbsx to see if an entry for this
> virtual address already exists.
>
> Since this code is only called from the TLB miss handler, I can't see
> how there could ever be a valid TLB entry present at this point.
> There is a comment claiming that this path can be hit under some
> circumstances, but it doesn't make sense to me.
>
> Is there any situation where we can reach this point with a valid TLB
> entry existing for the faulting address?
Ok, not seeing any replies here. If no-one speaks up for this tlbsx
in the next couple of days, I'll remove it from 2_4_devel.
--
David Gibson | For every complex problem there is a
david@gibson.dropbear.id.au | solution which is simple, neat and
| wrong. -- H.L. Mencken
http://www.ozlabs.org/people/dgibson
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-03 2:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 8:04 Do we need tlbsx at finish_tlb_load? David Gibson
2002-06-03 2:43 ` David Gibson [this message]
2002-06-04 0:19 ` Dan Malek
2002-06-04 3:48 ` David Gibson
2002-06-04 12:52 ` Paul Mackerras
2002-06-04 17:49 ` Dan Malek
2002-06-06 2:04 ` Paul Mackerras
2002-06-06 5:06 ` Dan Malek
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=20020603024344.GA6765@zax \
--to=david@gibson.dropbear.id.au \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=paulus@samba.org \
--cc=trini@kernel.crashing.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.