[PATCH 0/6] ARM: cleanup fault handling · "Russell King (Oracle)" <linux@armlinux.org.uk> · 2026-02-27
[PATCH 1/6] ARM: ensure interrupts are enabled in __do_user_fault() · Russell King (Oracle) <hidden> · 2026-02-27
Re: [PATCH 1/6] ARM: ensure interrupts are enabled in __do_user_fault() · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2026-03-02
[PATCH 2/6] ARM: move vmalloc() lazy-page table population · Russell King (Oracle) <hidden> · 2026-02-27
Re: [PATCH 2/6] ARM: move vmalloc() lazy-page table population · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2026-03-02
Re: [PATCH 2/6] ARM: move vmalloc() lazy-page table population · "Russell King (Oracle)" <linux@armlinux.org.uk> · 2026-03-02
Re: [PATCH 2/6] ARM: move vmalloc() lazy-page table population · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2026-03-02
Re: [PATCH 2/6] ARM: move vmalloc() lazy-page table population · "Russell King (Oracle)" <linux@armlinux.org.uk> · 2026-03-02
Re: [PATCH 2/6] ARM: move vmalloc() lazy-page table population · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2026-03-02
[PATCH 3/6] ARM: move is_permission_fault() and is_translation_fault() to fault.h · Russell King (Oracle) <hidden> · 2026-02-27
Re: [PATCH 3/6] ARM: move is_permission_fault() and is_translation_fault() to fault.h · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2026-03-02
[PATCH 4/6] ARM: use BIT() and GENMASK() for fault status register fields · Russell King (Oracle) <hidden> · 2026-02-27
Re: [PATCH 4/6] ARM: use BIT() and GENMASK() for fault status register fields · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2026-03-02
[PATCH 5/6] ARM: move FSR fault status definitions before fsr_fs() · Russell King (Oracle) <hidden> · 2026-02-27
Re: [PATCH 5/6] ARM: move FSR fault status definitions before fsr_fs() · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2026-03-02
[PATCH 6/6] ARM: provide individual is_translation_fault() and is_permission_fault() · Russell King (Oracle) <hidden> · 2026-02-27
Re: [PATCH 6/6] ARM: provide individual is_translation_fault() and is_permission_fault() · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2026-03-02
Re: [PATCH 0/6] ARM: cleanup fault handling · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2026-03-02
Re: [PATCH 0/6] ARM: cleanup fault handling · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2026-03-19

Re: [PATCH 2/6] ARM: move vmalloc() lazy-page table population

From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Date: 2026-03-02 11:51:44
Also in: linux-rt-devel

On 2026-03-02 11:19:52 [+0000], Russell King (Oracle) wrote:

We've gone from the code always having interrupts disabled, to your
review response that always wants them to be enabled (which is what
*un*conditionally enable interrupts means) to now conditionally enable
interrupts.

I'm sorry but this got out of hand.
The wording was we must "not enable interrupts" and I was curious if
this is because we destroy some information (on the following fault/
interrupt) _or_ not. If we don't destroy anything then it would be okay
to enable them conditionally. At no point I am suggesting to do so.

Sorry for the confusion here.

Sebastian

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help