linux-kernel - Re: [RFC PATCH] x86-64: software IRQ masking and handling

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] [day] [month] [year] [list]

Message-Id: <201008041139.06739.rusty@rustcorp.com.au>
Date:	Wed, 4 Aug 2010 11:39:05 +0930
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Tejun Heo <tj@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Peter Zijlstra <peterz@...radead.org>,
	"the arch/x86 maintainers" <x86@...nel.org>,
	lkml <linux-kernel@...r.kernel.org>,
	Christoph Lameter <cl@...ux-foundation.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [RFC PATCH] x86-64: software IRQ masking and handling

On Wed, 4 Aug 2010 07:07:16 am Jeremy Fitzhardinge wrote:
> Of course if it becomes core to the x86 architecture or the kernel 
> overall, then most of the irq-related paravirt-ops can go away and be 
> limited to the actual interrupt handler and the machinery needed to 
> really mask/unmask the hardware and set the pending flag (which would 
> likely just be contained within the hypervisor-specific code, and not 
> need any new kernel interfaces to replace the dropped paravirt irq ones).

Yep, we sweat over the cli/sti paravirtual implementations because it's so
common.  If the kernel used soft cli/sti we could simply implement it with
a hypercall and be much happier (though iret possibly still an issue).

Cheers,
Rusty.
--
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/