On Fri, Mar 13, 2015 at 07:35:52AM +0800, Fam Zheng wrote:
On Thu, 03/12 17:22, Michael S. Tsirkin wrote:
On Wed, Mar 11, 2015 at 06:11:35PM +0800, Fam Zheng wrote:
On Wed, 03/11 10:06, Michael S. Tsirkin wrote:
On Wed, Mar 11, 2015 at 04:09:17PM +0800, Fam Zheng wrote:
Currently
On 12/03/2015 17:22, Michael S. Tsirkin wrote:
On Wed, Mar 11, 2015 at 06:11:35PM +0800, Fam Zheng wrote:
On Wed, 03/11 10:06, Michael S. Tsirkin wrote:
On Wed, Mar 11, 2015 at 04:09:17PM +0800, Fam Zheng wrote:
Currently shutdown is nop for virtio devices, but the core code could
remove
On Wed, Mar 11, 2015 at 06:11:35PM +0800, Fam Zheng wrote:
On Wed, 03/11 10:06, Michael S. Tsirkin wrote:
On Wed, Mar 11, 2015 at 04:09:17PM +0800, Fam Zheng wrote:
Currently shutdown is nop for virtio devices, but the core code could
remove things behind us such as MSI-X handler etc. For
On Thu, 03/12 17:22, Michael S. Tsirkin wrote:
On Wed, Mar 11, 2015 at 06:11:35PM +0800, Fam Zheng wrote:
On Wed, 03/11 10:06, Michael S. Tsirkin wrote:
On Wed, Mar 11, 2015 at 04:09:17PM +0800, Fam Zheng wrote:
Currently shutdown is nop for virtio devices, but the core code could
On Wed, 03/11 10:06, Michael S. Tsirkin wrote:
On Wed, Mar 11, 2015 at 04:09:17PM +0800, Fam Zheng wrote:
Currently shutdown is nop for virtio devices, but the core code could
remove things behind us such as MSI-X handler etc. For example in the
case of virtio-scsi-pci, the device may still
On Wed, Mar 11, 2015 at 04:09:17PM +0800, Fam Zheng wrote:
Currently shutdown is nop for virtio devices, but the core code could
remove things behind us such as MSI-X handler etc. For example in the
case of virtio-scsi-pci, the device may still try to send interupts,
which will be on IRQ lines
Currently shutdown is nop for virtio devices, but the core code could
remove things behind us such as MSI-X handler etc. For example in the
case of virtio-scsi-pci, the device may still try to send interupts,
which will be on IRQ lines seeing MSI-X disabled. Those interrupts will
be unhandled, and
