All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: Pass IFSR register to do_PrefetchAbort()
Date: Sun, 20 Sep 2009 09:15:50 +0100	[thread overview]
Message-ID: <20090920081550.GA830@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20090919110316.GA23452@n2100.arm.linux.org.uk>

On Sat, Sep 19, 2009 at 12:03:16PM +0100, Russell King - ARM Linux wrote:
> On Fri, Sep 18, 2009 at 11:55:42PM +0300, Kirill A. Shutemov wrote:
> > It needed for proper prefetch abort handling on ARMv7.
> 
> I think the only thing which is missing is an explaination about why
> this is desirable given that only later CPUs can give this additional
> information.

So you've posted it to the patch system, without further discussion here.

I think the solution is wrong - it makes instruction permission faults
unnecessarily noisy, which is not what the decoding table is supposed
to be doing.  The decoding table's bad entries are there to catch those
_unexpected_ cases.

Instead, I suggest that you have a look at this:

        if (fsr & (1 << 11)) /* write? */
                mask = VM_WRITE;
        else
                mask = VM_READ|VM_EXEC|VM_WRITE;

        fault = VM_FAULT_BADACCESS;
        if (!(vma->vm_flags & mask))
                goto out;

in __do_page_fault - if we are handling a prefetch abort, we really only
want to check that the VMA has VM_EXEC permission, not that it can be
read and written as well.

WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
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: Sun, 20 Sep 2009 09:15:50 +0100	[thread overview]
Message-ID: <20090920081550.GA830@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20090919110316.GA23452@n2100.arm.linux.org.uk>

On Sat, Sep 19, 2009 at 12:03:16PM +0100, Russell King - ARM Linux wrote:
> On Fri, Sep 18, 2009 at 11:55:42PM +0300, Kirill A. Shutemov wrote:
> > It needed for proper prefetch abort handling on ARMv7.
> 
> I think the only thing which is missing is an explaination about why
> this is desirable given that only later CPUs can give this additional
> information.

So you've posted it to the patch system, without further discussion here.

I think the solution is wrong - it makes instruction permission faults
unnecessarily noisy, which is not what the decoding table is supposed
to be doing.  The decoding table's bad entries are there to catch those
_unexpected_ cases.

Instead, I suggest that you have a look at this:

        if (fsr & (1 << 11)) /* write? */
                mask = VM_WRITE;
        else
                mask = VM_READ|VM_EXEC|VM_WRITE;

        fault = VM_FAULT_BADACCESS;
        if (!(vma->vm_flags & mask))
                goto out;

in __do_page_fault - if we are handling a prefetch abort, we really only
want to check that the VMA has VM_EXEC permission, not that it can be
read and written as well.

  reply	other threads:[~2009-09-20  8:15 UTC|newest]

Thread overview: 31+ 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 ` Kirill A. Shutemov
2009-09-18 20:55 ` [PATCH 2/2] ARM: Proper prefetch abort handling on ARMv7 Kirill A. Shutemov
2009-09-18 20:55   ` Kirill A. Shutemov
2009-09-19 11:03 ` [PATCH 1/2] ARM: Pass IFSR register to do_PrefetchAbort() Russell King - ARM Linux
2009-09-19 11:03   ` Russell King - ARM Linux
2009-09-20  8:15   ` Russell King - ARM Linux [this message]
2009-09-20  8:15     ` Russell King - ARM Linux
2009-09-20  9:35     ` Kirill A. Shutemov
2009-09-20  9:35       ` Kirill A. Shutemov
2009-09-20 12:24       ` Russell King - ARM Linux
2009-09-20 12:24         ` Russell King - ARM Linux
2009-09-20 14:34         ` Kirill A. Shutemov
2009-09-20 14:34           ` Kirill A. Shutemov
2009-09-21  7:06         ` Kirill A. Shutemov
2009-09-21  7:06           ` Kirill A. Shutemov
  -- strict thread matches above, loose matches on Subject: below --
2009-09-18 13:48 Kirill A. Shutemov
2009-09-18 13:48 ` Kirill A. Shutemov
2009-09-18 11:18 ` Aaro Koskinen
2009-09-18 11:18   ` Aaro Koskinen
2009-09-18 11:36   ` Kirill A. Shutemov
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 11:45     ` Kirill A. Shutemov
2009-09-18 14:52     ` Aaro Koskinen
2009-09-18 14:52       ` Aaro Koskinen
2009-09-18 15:08       ` Kirill A. Shutemov
2009-09-18 15:08         ` Kirill A. Shutemov
2009-09-18 15:38         ` Catalin Marinas
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=20090920081550.GA830@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 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.