From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Dan Malek <dan@embeddedalley.com>
Cc: Scott Wood <scottwood@freescale.com>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Rex Feany <RFeany@mrv.com>
Subject: Re: [PATCH 0/8] Fix 8xx MMU/TLB
Date: Tue, 27 Oct 2009 11:00:53 +1100 [thread overview]
Message-ID: <1256601653.2076.51.camel@pasglop> (raw)
In-Reply-To: <21C04675-E563-49E2-B2E6-7CAB9D8BE985@embeddedalley.com>
On Mon, 2009-10-26 at 16:26 -0700, Dan Malek wrote:
> Just be careful the get_user() doesn't regenerate the same
> translation error you are trying to fix by being here......
It shouldn't since it will always come up with a proper DAR but
you may want to double check before hand that your instruction
address you are loading from is -not- your marker value for bad DAR.
> It is nice doing things in C code, but you have to be aware
> of the environment and the side effects when in this kind
Yup.
Cheers,
Ben.
next prev parent reply other threads:[~2009-10-27 0:01 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 9:04 [PATCH 0/8] Fix 8xx MMU/TLB Joakim Tjernlund
2009-10-15 9:04 ` [PATCH 1/8] 8xx: invalidate non present TLBs Joakim Tjernlund
2009-10-15 9:04 ` [PATCH 2/8] 8xx: Update TLB asm so it behaves as linux mm expects Joakim Tjernlund
2009-10-15 9:04 ` [PATCH 3/8] 8xx: Tag DAR with 0x00f0 to catch buggy instructions Joakim Tjernlund
2009-10-15 9:04 ` [PATCH 4/8] 8xx: Fixup DAR from buggy dcbX instructions Joakim Tjernlund
2009-10-15 9:04 ` [PATCH 5/8] 8xx: Add missing Guarded setting in DTLB Error Joakim Tjernlund
2009-10-15 9:04 ` [PATCH 6/8] 8xx: Restore _PAGE_WRITETHRU Joakim Tjernlund
2009-10-15 9:04 ` [PATCH 7/8] 8xx: start using dcbX instructions in various copy routines Joakim Tjernlund
2009-10-15 9:04 ` [PATCH 8/8] 8xx: Remove DIRTY pte handling in DTLB Error Joakim Tjernlund
2009-10-15 16:56 ` [PATCH 0/8] Fix 8xx MMU/TLB Rex Feany
2009-10-16 8:16 ` Joakim Tjernlund
2009-10-16 20:25 ` Rex Feany
2009-10-17 11:24 ` Joakim Tjernlund
[not found] ` <OF2BB5EF59.1EE0A77D-ONC1257652.003D79DC-C1257652.003EA687@LocalDomain>
2009-10-17 12:01 ` Joakim Tjernlund
2009-10-26 22:47 ` Benjamin Herrenschmidt
2009-10-26 23:26 ` Dan Malek
2009-10-27 0:00 ` Benjamin Herrenschmidt [this message]
2009-10-27 9:16 ` Joakim Tjernlund
2009-10-27 15:58 ` Scott Wood
2009-10-27 16:38 ` Joakim Tjernlund
2009-10-30 0:12 ` Scott Wood
2009-10-30 0:51 ` Joakim Tjernlund
2009-10-30 17:16 ` Scott Wood
2009-10-30 17:37 ` Scott Wood
2009-10-31 10:31 ` Joakim Tjernlund
2009-11-03 13:32 ` Joakim Tjernlund
2009-11-03 16:59 ` Scott Wood
2009-11-03 17:16 ` Joakim Tjernlund
2009-10-15 22:04 ` Scott Wood
-- strict thread matches above, loose matches on Subject: below --
2009-10-11 16:35 Joakim Tjernlund
2009-10-14 17:23 ` Scott Wood
2009-10-14 18:46 ` Joakim Tjernlund
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=1256601653.2076.51.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=RFeany@mrv.com \
--cc=dan@embeddedalley.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
/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).