From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"Russell King - ARM Linux admin" <linux@armlinux.org.uk>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Arnd Bergmann <arnd@arndb.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"yadi.hu@windriver.com" <yadi.hu@windriver.com>
Subject: Re: [RFC PATCH] ARM: enable irq in translation/section permission fault handlers
Date: Thu, 21 Feb 2019 08:06:25 +0000 [thread overview]
Message-ID: <f05d2cae-5664-6cc7-51c8-933d6d1403ec@hotmail.de> (raw)
In-Reply-To: <20190220110039.2p2iglhqlf6xapsb@linutronix.de>
On 2/20/19 12:00 PM, Sebastian Andrzej Siewior wrote:
>
> Bernd Edlinger explained the missing piece to me. With
> PAGE_OFFSET=0xC0000000 and without LPAE a R/W of 0xbffffff0 will ends up
> with:
>
I am unable to reproduce on my target, wheter do_page_fault is directly taken,
or do_translation_fault is taken depends on whether the page table root directory
permission bits deny the access or the second level page table deny the access?
But if there is a way to get into the code path do_DataAbort->do_page_fault with
addr > TASK_SIZE, then I don't see why that works without the RT patch,
since the interrupts are enabled here:
do_page_fault(unsigned long addr, unsigned int fsr, struct pt_regs *regs)
{
struct task_struct *tsk;
struct mm_struct *mm;
int sig, code;
vm_fault_t fault;
unsigned int flags = FAULT_FLAG_ALLOW_RETRY | FAULT_FLAG_KILLABLE;
if (notify_page_fault(regs, fsr))
return 0;
tsk = current;
mm = tsk->mm;
/* Enable interrupts if they were enabled in the parent context. */
if (interrupts_enabled(regs))
local_irq_enable();
Is preemption disabled at this point, without the RT patch?
I still don't quite see why is this no issue without the RT patch.
Can someone explain that?
Thanks
Bernd.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-02-21 8:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 20:05 [RFC PATCH] ARM: enable irq in translation/section permission fault handlers Sebastian Andrzej Siewior
2019-02-15 21:57 ` Bernd Edlinger
2019-02-20 10:50 ` Sebastian Andrzej Siewior
2019-02-16 11:33 ` Russell King - ARM Linux admin
2019-02-20 11:00 ` Sebastian Andrzej Siewior
2019-02-21 8:06 ` Bernd Edlinger [this message]
2019-02-21 9:31 ` Bernd Edlinger
2019-02-21 9:57 ` Sebastian Andrzej Siewior
2019-02-21 14:03 ` Bernd Edlinger
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=f05d2cae-5664-6cc7-51c8-933d6d1403ec@hotmail.de \
--to=bernd.edlinger@hotmail.de \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=tglx@linutronix.de \
--cc=yadi.hu@windriver.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).