Re: [RFC 1/3] Unified NMI delayed call mechanism

Andi Kleen
2010-06-18T13:23:35Z

On Fri, Jun 18, 2010 at 03:12:49PM +0200, Peter Zijlstra wrote:
> On Fri, 2010-06-18 at 15:09 +0200, Andi Kleen wrote:
> > > You generally want to pass more information along anyway, now your
> > > callback function needs to go look for it. Much better to pass a
> > > work_struct like thing around that is contained in the state it needs.
> >
> > But how would you allocate the work queue in an NMI?
> >
> > If it's only a single instance (like this bit) it can be always put
> > into a per cpu variable.
>
> Pre-allocate. For the perf-event stuff we use the perf_event allocated
> at creation time. But yeah, per-cpu storage also works.

So you could just preallocate the bits instead ?

-Andi

--
ak@linux.intel.com -- Speaking for myself only.