From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 05/12] arm: mm: retry on QSD icache parity errors
Date: Tue, 23 Feb 2010 19:02:54 +0000 [thread overview]
Message-ID: <20100223190254.GB26434@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1266950168.24069.1.camel@c-dwalke-linux.qualcomm.com>
On Tue, Feb 23, 2010 at 10:36:08AM -0800, Daniel Walker wrote:
> On Fri, 2010-01-29 at 11:11 +0000, Catalin Marinas wrote:
> > On Thu, 2010-01-28 at 22:59 +0000, Daniel Walker wrote:
> > > diff --git a/arch/arm/mm/fault.c b/arch/arm/mm/fault.c
> > > index 10e0680..bea3e75 100644
> > > --- a/arch/arm/mm/fault.c
> > > +++ b/arch/arm/mm/fault.c
> > [...]
> > > static struct fsr_info {
> > > int (*fn)(unsigned long addr, unsigned int fsr, struct pt_regs *regs);
> > > int sig;
> > > @@ -479,7 +513,7 @@ static struct fsr_info {
> > > { do_bad, SIGBUS, 0, "unknown 19" },
> > > { do_bad, SIGBUS, 0, "lock abort" }, /* xscale */
> > > { do_bad, SIGBUS, 0, "unknown 21" },
> > > - { do_bad, SIGBUS, BUS_OBJERR, "imprecise external abort" }, /* xscale */
> > > + { do_imprecise_ext, SIGBUS, BUS_OBJERR, "imprecise external abort" }, /* xscale */
> >
> > Can you not use hook_fault_code() and move the do_imprecise_ext() to a
> > platform-specific file (under arch/arm/mach-* maybe)?
> >
>
> How do you mean? I'm not sure how we would move this into
> arch/arm/mach- ..
Err, exactly as Catalin says. Use hook_fault_code() to hook into the
fault table at run time, just like platforms which have to handle
imprecise exceptions on PCI and the alignment fault handler do.
next prev parent reply other threads:[~2010-02-23 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 22:59 [RFC PATCH 05/12] arm: mm: retry on QSD icache parity errors Daniel Walker
2010-01-29 6:50 ` Pavel Machek
2010-01-29 11:11 ` Catalin Marinas
2010-02-23 18:36 ` Daniel Walker
2010-02-23 19:02 ` Russell King - ARM Linux [this message]
2010-02-23 19:06 ` Daniel Walker
2010-02-23 19:09 ` Russell King - ARM Linux
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=20100223190254.GB26434@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).