Re: [Xen-devel] [Patch] continue_hypercall_on_cpu rework using tasklets

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

On 14/04/2010 07:58, "Juergen Gross" <juergen.gross@xxxxxxxxxxxxxx> wrote:

>> The per-cpu area method should work fine, since Xen is non-preemptive? I
>> don't think the concurrency you are concerned about can happen.
> 
> The tasklet knows only on which cpu it is running, so the data has to be
> stored on the target cpu. And one pcpu can be the target of concurrent calls
> from different calling cpus...

A tasklet also takes an arbitrary ulong parameter, which you can cast to a
pointer to your informational structure. The parameter is specified via
tasklet_init(). That should suffice.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel