Re: [Xen-devel] [RFC v2 11/15] vmx: Add a global wake-up vector for VT-d Posted-Interrupts

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 12.06.15 at 11:40, <feng.wu@xxxxxxxxx> wrote:
>> From: xen-devel-bounces@xxxxxxxxxxxxx 
>> [mailto:xen-devel-bounces@xxxxxxxxxxxxx] On Behalf Of Jan Beulich
>> Sent: Tuesday, June 09, 2015 11:20 PM
>> >>> On 08.05.15 at 11:07, <feng.wu@xxxxxxxxx> wrote:
>> > +{
>> > +    struct vcpu *v;
>> > +    unsigned int cpu = smp_processor_id();
>> > +
>> > +    spin_lock(&per_cpu(blocked_vcpu_lock, cpu));
>> > +    list_for_each_entry(v, &per_cpu(blocked_vcpu, cpu),
>> > +                    blocked_vcpu_list) {
>> 
>> How long do you think such a list can grow? 
> 
> It depends on how many vCPU is current blocked on this specific pCPU.
> I am not sure how long it can grow. 
> 
> The basic idea here is that, when notification wakeup event happens,
> we need to find a way to find the right vCPU, and then wakeup it, do
> you have any better idea for this?

Not immediately, or else I would have spelled it out. But the list
perhaps growing to hundreds entries is something that needs to
be taken into consideration.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel