Re: [Xen-devel] [PATCH, v2] reduce 'd' debug key's global impact

["Jan Beulich" <JBeulich@xxxxxxxxxx>]

>>> Keir Fraser <keir.fraser@xxxxxxxxxxxxx> 06.05.10 10:01 >>>
>Although I suppose the event-check vector has a cleaner interface for
>calling it and should be implemented for all architectures. If you add
>whatever new flag you need to irq_cpustat_t then it would be cheap to check,
>being a definite cache hit. I suppose each cpu would

Actually, in smp_event_check_interrupt(), irq_cpustat isn't being used
so far, so placing the new field there wouldn't be a definite cache hit.
Instead (if that has to remain, which I doubt) co-locating it with
__irq_regs would help here.

Otoh it seems like I will should add irq_enter()/irq_exit() now that the
function calls something non-trivial...

>check-and-check-and-clear it, and then set it for the next CPU when it is
>done. That doesn't sound too bad.

Jan


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