From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Bityutskiy Artem <Artem.Bityutskiy@nokia.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Koskinen Aaro <aaro.koskinen@nokia.com>
Subject: Re: [PATCH 1/2] ARM: Pass IFSR register to do_PrefetchAbort()
Date: Mon, 21 Sep 2009 10:06:42 +0300 [thread overview]
Message-ID: <cc557aab0909210006n2f423bf9lf208e355bed0fada@mail.gmail.com> (raw)
In-Reply-To: <20090920122411.GA5413@n2100.arm.linux.org.uk>
On Sun, Sep 20, 2009 at 3:24 PM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Sun, Sep 20, 2009 at 12:35:19PM +0300, Kirill A. Shutemov wrote:
>> Ok, so __do_page_fault() should know where we are: in data abort or in
>> prefetch abort. What is right way to do it? Should we create one more
>> argument or use one of reserved bits IFSR?
>
> Well, this is my solution to the problem - could you test it please?
Yes, it works. But I still think that ignoring IFSR is a mistake. I'll send
updated patches
next prev parent reply other threads:[~2009-09-21 7:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 20:55 [PATCH 1/2] ARM: Pass IFSR register to do_PrefetchAbort() Kirill A. Shutemov
2009-09-18 20:55 ` [PATCH 2/2] ARM: Proper prefetch abort handling on ARMv7 Kirill A. Shutemov
2009-09-19 11:03 ` [PATCH 1/2] ARM: Pass IFSR register to do_PrefetchAbort() Russell King - ARM Linux
2009-09-20 8:15 ` Russell King - ARM Linux
2009-09-20 9:35 ` Kirill A. Shutemov
2009-09-20 12:24 ` Russell King - ARM Linux
2009-09-20 14:34 ` Kirill A. Shutemov
2009-09-21 7:06 ` Kirill A. Shutemov [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-18 13:48 Kirill A. Shutemov
2009-09-18 11:18 ` Aaro Koskinen
2009-09-18 11:36 ` Kirill A. Shutemov
2009-09-18 11:28 ` Aaro Koskinen
2009-09-18 11:45 ` Kirill A. Shutemov
2009-09-18 14:52 ` Aaro Koskinen
2009-09-18 15:08 ` Kirill A. Shutemov
2009-09-18 15:38 ` Catalin Marinas
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=cc557aab0909210006n2f423bf9lf208e355bed0fada@mail.gmail.com \
--to=kirill@shutemov.name \
--cc=Artem.Bityutskiy@nokia.com \
--cc=aaro.koskinen@nokia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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