[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200326191356.GC2452@worktop.programming.kicks-ass.net>
Date: Thu, 26 Mar 2020 20:13:56 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Nadav Amit <namit@...are.com>
Cc: x86 <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
"rostedt@...dmis.org" <rostedt@...dmis.org>,
"mhiramat@...nel.org" <mhiramat@...nel.org>,
"bristot@...hat.com" <bristot@...hat.com>,
"jbaron@...mai.com" <jbaron@...mai.com>,
"torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
tglx <tglx@...utronix.de>, "mingo@...nel.org" <mingo@...nel.org>,
"hpa@...or.com" <hpa@...or.com>, Andy Lutomirski <luto@...nel.org>,
"ard.biesheuvel@...aro.org" <ard.biesheuvel@...aro.org>,
"jpoimboe@...hat.com" <jpoimboe@...hat.com>
Subject: Re: [RESEND][PATCH v3 06/17] static_call: Add basic static call
infrastructure
On Thu, Mar 26, 2020 at 07:02:33PM +0000, Nadav Amit wrote:
> On another note - it may be beneficial to see if the infrastructure that you
> built can accommodate notifier-chains. It is not the most painful point, but
> it would be nice to deal with those as well. Since many of those are changed
> asynchronously, I am not sure it is the easiest thing to do.
You mean, like patch 12 does?
Powered by blists - more mailing lists