linux-kernel - Re: x86: Is there still value in having a special tlb flush IPI vector?

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]

Message-ID: <20080731205726.GE25138@elte.hu>
Date:	Thu, 31 Jul 2008 22:57:26 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Nick Piggin <nickpiggin@...oo.com.au>,
	Jens Axboe <jens.axboe@...cle.com>, Andi Kleen <ak@...e.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: x86: Is there still value in having a special tlb flush IPI
	vector?


* Jeremy Fitzhardinge <jeremy@...p.org> wrote:

> Peter Zijlstra wrote:
> > How about using just arch_send_call_function_single_ipi() to implement
> > smp_send_reschedule() ?
> >
> > The overhead of that is a smp_mb() and a list_empty() check in
> > generic_smp_call_function_single_interrupt() if there is indeed no work
> > to do.
> 
> Is doing a no-op interrupt sufficient on all architectures?  Is there 
> some change a function call IPI might not go through the normal 
> reschedule interrupt exit path?

We'd still use the smp_send_reschdule(cpu) API, so it's an architecture 
detail. On x86 we'd use arch_send_call_function_single_ipi().

	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/