linux-kernel - Re: [RFC][PATCH 0/7] sched: Remove finish_arch

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:	Fri, 31 Jul 2015 10:51:34 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	linux-kernel@...r.kernel.org, will.deacon@....com,
	linux@....linux.org.uk, ralf@...ux-mips.org, egtvedt@...fundet.no,
	michael@...rulasolutions.com, cmetcalf@...hip.com
Subject: Re: [RFC][PATCH 0/7] sched: Remove finish_arch_switch()


* Peter Zijlstra <peterz@...radead.org> wrote:

> On Wed, Jul 29, 2015 at 09:08:48PM +0200, Peter Zijlstra wrote:
> > Hi,
> > 
> > There were only a few architectures utilizing finish_arch_switch() and it looks
> > like they can all do without.
> > 
> > This means we can remove finish_arch_switch(); partly to make up for
> > introducing finish_arch_post_lock_switch(), partly to reduce the number of arch
> > hooks to consider.
> > 
> > Much thanks to Ralf, Will and Chris for helping out with this!
> 
> So the mips patch is already in Ralf's mips-next tree, which means I
> have to wait for that to his Linus' tree before I can commit the last
> patch in this series.
> 
> It also means that all the other patches can go through their respective
> arch tree.
> 
> So anybody who feels so inclined, go ahead, I'll check after the next
> merge window and commit everything that's left -- unless there's
> objections of course :-)

Sounds sensible to me!

Thanks,

	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/