|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] [PATCH] Dom0 Kernel - Fixes forsaving/restoringMSI/MSI-X
Jan,
I have checked the code again. I still can not find where AHCI driver finalize
and reinitialize the MSI. The driver simply writes its internal registers so
that the device does not *generate* interrupts and invoke pci_save_state (which
will invoke our MSI code). Similar is the resume process.
For cannot-rebind-because-already-bound error, I do not mean it is the error
cause by device rebinding MSI. It is us not the device driver that force
unbinds MSI. After resume, no one does the rebinding work now.
Best Regards
Shan Haitao
-----Original Message-----
From: Jan Beulich [mailto:jbeulich@xxxxxxxxxx]
Sent: 2008年11月24日 23:33
To: Shan, Haitao; Tian, Kevin
Cc: 'Keir Fraser'; 'xen-devel@xxxxxxxxxxxxxxxxxxx'
Subject: RE: [Xen-devel] [PATCH] Dom0 Kernel - Fixes
forsaving/restoringMSI/MSI-X across Dom0 S3
>>> "Shan, Haitao" <haitao.shan@xxxxxxxxx> 24.11.08 14:55 >>>
>Yes, clear enough as Kevin said. That is what I saw why S3 failed when AHCI is
>enabled (AHCI uses MSI). I do not know whether it
>is also the reason that Jan sees the need to add force unbind support of MSI.
>I have another question for saving/restoring in Xen if we do not use a new
>hypercall. Devices are controller by dom0. At the point
>Xen wants to save MSI during S3, dom0 may already places that device in D3hot
>state, or it may also cease the device's function
>via pci_disable_device. I doubt whether Xen can read device MMIO at that time.
But - as asked before - shouldn't the device undergo full re-initialization
after coming out of D3? Iirc, the AHCI/S3 bug results in a
cannot-rebind-because-already-bound error, which would indicate to me that the
driver tries to create a new binding, and hence doesn't really need the
device's state saved (admitted, I didn't look closely at the driver's code so
far). It instead may just need Xen to clean up its internal state properly. But
really, I'm in no way a suspend/resume expert...
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] [PATCH] Dom0 Kernel - Fixes for saving/restoring MSI/MSI-X across Dom0 S3, Shan, Haitao
- Re: [Xen-devel] [PATCH] Dom0 Kernel - Fixes for saving/restoringMSI/MSI-X across Dom0 S3, Jan Beulich
- Re: [Xen-devel] [PATCH] Dom0 Kernel - Fixes for saving/restoringMSI/MSI-X across Dom0 S3, Keir Fraser
- RE: [Xen-devel] [PATCH] Dom0 Kernel - Fixes for saving/restoringMSI/MSI-X across Dom0 S3, Tian, Kevin
- RE: [Xen-devel] [PATCH] Dom0 Kernel - Fixes forsaving/restoringMSI/MSI-X across Dom0 S3, Jan Beulich
- RE: [Xen-devel] [PATCH] Dom0 Kernel - Fixes forsaving/restoringMSI/MSI-X across Dom0 S3, Tian, Kevin
- RE: [Xen-devel] [PATCH] Dom0 Kernel - Fixes forsaving/restoringMSI/MSI-X across Dom0 S3, Shan, Haitao
- RE: [Xen-devel] [PATCH] Dom0 Kernel - Fixes forsaving/restoringMSI/MSI-X across Dom0 S3, Jan Beulich
- RE: [Xen-devel] [PATCH] Dom0 Kernel - Fixes forsaving/restoringMSI/MSI-X across Dom0 S3,
Shan, Haitao <=
- RE: [Xen-devel] [PATCH] Dom0 Kernel - Fixes for saving/restoringMSI/MSI-X across Dom0 S3, Shan, Haitao
Re: [Xen-devel] [PATCH] Dom0 Kernel - Fixes for saving/restoring MSI/MSI-X across Dom0 S3, Keir Fraser
|
|
|
|
|