search for: haoyu

On 11/18/2014 09:37 AM, Zhang Haoyu wrote: >> On Mon, Nov 17, 2014 at 01:58:20PM +0200, Michael S. Tsirkin wrote: >>> On Mon, Nov 17, 2014 at 01:22:07PM +0200, Gleb Natapov wrote: >>>> On Mon, Nov 17, 2014 at 12:38:16PM +0200, Michael S. Tsirkin wrote: >>>>> On Mon, Nov 17, 2014 at 09:44:23AM...

On 11/18/2014 09:37 AM, Zhang Haoyu wrote: >> On Mon, Nov 17, 2014 at 01:58:20PM +0200, Michael S. Tsirkin wrote: >>> On Mon, Nov 17, 2014 at 01:22:07PM +0200, Gleb Natapov wrote: >>>> On Mon, Nov 17, 2014 at 12:38:16PM +0200, Michael S. Tsirkin wrote: >>>>> On Mon, Nov 17, 2014 at 09:44:23AM...

...ne behind virtio-scsi, who still is waiting for msix. "Hence, the interrupt will not be acknowledged and the guest becomes flooded with IRQ 11 interrupt." Fortunately it's not a livelock for upstream, because of: commit 184564efae4d775225c8fe3b762a56956fb1f827 Author: Zhang Haoyu <zhanghy at sangfor.com> Date: Thu Sep 11 16:47:04 2014 +0800 kvm: ioapic: conditionally delay irq delivery duringeoi broadcast But we still should do the shutdown right. I also propose to not shutdown msix from pci core shutdown if the device doesn't have shutdown function:...

...ne behind virtio-scsi, who still is waiting for msix. "Hence, the interrupt will not be acknowledged and the guest becomes flooded with IRQ 11 interrupt." Fortunately it's not a livelock for upstream, because of: commit 184564efae4d775225c8fe3b762a56956fb1f827 Author: Zhang Haoyu <zhanghy at sangfor.com> Date: Thu Sep 11 16:47:04 2014 +0800 kvm: ioapic: conditionally delay irq delivery duringeoi broadcast But we still should do the shutdown right. I also propose to not shutdown msix from pci core shutdown if the device doesn't have shutdown function:...

...------------------------------------------------------- People who touched revisions under test: Andres Lagar-Cavilla <andres@lagarcavilla.org> Anthony Liguori <aliguori@us.ibm.com> Boris Ostrovsky <boris.ostrovsky@amd.com> Christoph Egger <Christoph.Egger@amd.com> Haoyu Zhang <haoyu.zhang@huawei.com> Ian Campbell <Ian.Campbell@citrix.com> Jan Beulich <jbeulich@suse.com> Keir Fraser <keir@xen.org> Liang Wang <hzwangliang.wang@huawei.com> ------------------------------------------------------------ jobs: build-amd64...

On Mon, Nov 17, 2014 at 12:38:16PM +0200, Michael S. Tsirkin wrote: > On Mon, Nov 17, 2014 at 09:44:23AM +0200, Gleb Natapov wrote: > > On Sun, Nov 16, 2014 at 08:56:04PM +0200, Michael S. Tsirkin wrote: > > > On Sun, Nov 16, 2014 at 06:18:18PM +0200, Gleb Natapov wrote: > > > > Hi Michael, > > > > > > > > I am playing with vhost multiqueue

On Mon, Nov 17, 2014 at 12:38:16PM +0200, Michael S. Tsirkin wrote: > On Mon, Nov 17, 2014 at 09:44:23AM +0200, Gleb Natapov wrote: > > On Sun, Nov 16, 2014 at 08:56:04PM +0200, Michael S. Tsirkin wrote: > > > On Sun, Nov 16, 2014 at 06:18:18PM +0200, Gleb Natapov wrote: > > > > Hi Michael, > > > > > > > > I am playing with vhost multiqueue

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 try to send interupts, > > which will be on IRQ lines seeing MSI-X

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 try to send interupts, > > which will be on IRQ lines seeing MSI-X

...den@gmail.com> Zang MingJie <zealot0630@gmail.com> Zdenek Kabelac <zkabelac@redhat.com> Zefir Kurtisi <zefir.kurtisi@neratec.com> Zeng Zhaoming <zengzm.kernel@gmail.com> Zero.Lin <Zero.Lin@mediatek.com> Zhang Hang <bob.zhanghang@huawei.com> Zhang Haoyu <haoyu.zhang@huawei.com> Zhang Rui <rui.zhang@intel.com> Zhang Xiantao <xiantao.zhang@intel.com> Zhang Xianwei <zhang.xianwei8@zte.com.cn> zhang xiaomei <xiaomei.zhang@stericsson.com> Zhang Yanfei <zhangyanfei@cn.fujitsu.com> Zhangfei Gao <zhangfei...

...t0630@gmail.com> Zbigniew Bodek <zbb@semihalf.com> Zdenek Kabelac <zkabelac@redhat.com> Zefir Kurtisi <zefir.kurtisi@neratec.com> Zeng Zhaoming <zengzm.kernel@gmail.com> Zero.Lin <Zero.Lin@mediatek.com> Zhang Hang <bob.zhanghang@huawei.com> Zhang Haoyu <haoyu.zhang@huawei.com> Zhang Rui <rui.zhang@intel.com> Zhang Xiantao <xiantao.zhang@intel.com> Zhang Xianwei <zhang.xianwei8@zte.com.cn> zhang xiaomei <xiaomei.zhang@stericsson.com> Zhang Yanfei <zhangyanfei@cn.fujitsu.com> Zhang Yi <zhang.yi20@z...

...t0630@gmail.com> Zbigniew Bodek <zbb@semihalf.com> Zdenek Kabelac <zkabelac@redhat.com> Zefir Kurtisi <zefir.kurtisi@neratec.com> Zeng Zhaoming <zengzm.kernel@gmail.com> Zero.Lin <Zero.Lin@mediatek.com> Zhang Hang <bob.zhanghang@huawei.com> Zhang Haoyu <haoyu.zhang@huawei.com> Zhang Rui <rui.zhang@intel.com> Zhang Xiantao <xiantao.zhang@intel.com> Zhang Xianwei <zhang.xianwei8@zte.com.cn> zhang xiaomei <xiaomei.zhang@stericsson.com> Zhang Yanfei <zhangyanfei@cn.fujitsu.com> Zhang Yi <zhang.yi20@z...