linux-kernel - Re: Should irq_chip->mask disable percpu interrupts to all cpus, or just to this cpu?

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Wed, 24 Sep 2008 12:18:11 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Should irq_chip->mask disable percpu interrupts to all cpus,
	or just to this cpu?


* Eric W. Biederman <ebiederm@...ssion.com> wrote:

> Other than the beautiful way we print things in /proc/interrupts 
> IRQ_PER_CPU feels like a really bad idea.  Especially in that it 
> enshrines the nasty per cpu irq counters that scale horribly.

ok - i thought the idea was to still have a per cpu irq desc.

so lets fix /proc/interrupts in that model. Only a single entry for 
every class of interrupts or so?

	Ingo
--
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/