[Xen-devel] RE: Xen 4.1 rc1 test report

["Wei, Gang" <gang.wei@xxxxxxxxx>]

Wei, Gang wrote on 2011-01-25:
>> 2. [VT-d]xen panic on function do_IRQ after many times NIC pass-throu
>> (Intel)
>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1706
> There are three points we may need to do:
> 1. Figure out the root cause why the pciback could not locate the device.
> I suspect the previous 'xl destroy' didn't return the device to
> pcistub successfully.
> 
> 2. Figure out the root cause why the guest pirq was not force unbound.
> Just found:
> Some time because if ( !IS_PRIV_FOR(current->domain, d) ) hit, so
> returned with -EINVAL; Sometime if ( !(desc->status & IRQ_GUEST) )
> hit, so do not unbind.
> 
> 3. Think about how we could prevent such cases from panic Xen.

Just found sometime while doing domain_destroy the current->domain is IDLE 
domain, so the if ( !IS_PRIV_FOR(current->domain, d) ) hit and skip the pirq 
forcible unbinding. How could it happen?

Jimmy



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