From: dwalker@codeaurora.org (Daniel Walker)
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 11:06:58 -0800 [thread overview]
Message-ID: <1266952018.24069.21.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <20100223190254.GB26434@n2100.arm.linux.org.uk>
On Tue, 2010-02-23 at 19:02 +0000, Russell King - ARM Linux wrote:
> > > 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.
"Can you not use hook_fault_code()"
Typo maybe ?
Daniel
next prev parent reply other threads:[~2010-02-23 19:06 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
2010-02-23 19:06 ` Daniel Walker [this message]
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=1266952018.24069.21.camel@c-dwalke-linux.qualcomm.com \
--to=dwalker@codeaurora.org \
--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).