linux-kernel - [PATCH 0/2] arm64: make it possible to enable threadirqs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 21 Apr 2015 17:05:53 +0200
From:	Anders Roxell <anders.roxell@...aro.org>
To:	catalin.marinas@....com, will.deacon@....com
Cc:	a.p.zijlstra@...llo.nl, paulus@...ba.org, mingo@...hat.com,
	acme@...nel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, khilman@...aro.org,
	steve.capper@...aro.org, Anders Roxell <anders.roxell@...aro.org>
Subject: [PATCH 0/2] arm64: make it possible to enable threadirqs

Hi,

This patchset makes it possible to pass "threadirqs" on the CONFIG_CMDLINE to
make IRQs threaded.
This is safe to use now because all timer interrupts and the perf interrupt are
marked NO_THREAD.

NOTE: I had to add this patch [1] to be able to test this on a juno board.
Without this patch, I see unhandled IRQs in mainline. However, it is unclear
whether or not this will be the actual fix that appears in mainline [2].

Cheers,
Anders

[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/319901.html
[2] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-February/322251.html

Anders Roxell (2):
  arm64: Mark PMU interrupt IRQF_NO_THREAD
  arm64: Allow forced irq threading

 arch/arm64/Kconfig             | 1 +
 arch/arm64/kernel/perf_event.c | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)

-- 
2.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/