Re: [Xen-devel] Re: IRQs, move_in_progress, -EBUSY &c

[George Dunlap <George.Dunlap@xxxxxxxxxxxxx>]

Seems to work about 50/50.

Attached is a log of a successful boot (exile.008.log), and a failed
boot (exile.009.log).  Suspicious things about the failed case:  the
usb code starts to initialize before the SATA code finishes
initializing, and complains that "Controller is probably using the
wrong IRQ".

Keir: the machine in question (as you may have guessed) is exile; let
me know if you want to grab it and use it directly.

 -George

On Wed, Aug 11, 2010 at 4:59 PM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
> On 11/08/2010 15:56, "George Dunlap" <George.Dunlap@xxxxxxxxxxxxx> wrote:
>
>> However, it seems that moving IRQs is not handled properly.  Either
>> the pvops kernel should retry if it gets an -EBUSY, or the hypercall
>> should not fail, but wait until it can return success.
>
> Can you try the attached patch?
>
>  Thanks,
>  Keir
>
>> I discovered all this by adding debug statements to the IRQ path; the
>> patch is attached, if anyone else wants to use it.
>>
>>  -George
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
>

exile.008.log
Description: Text Data

exile.009.log
Description: Text Data

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