Re: [PATCH 0/2] hw/block/nvme: fixes for interrupt behavior

qemu-block

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 0/2] hw/block/nvme: fixes for interrupt behavior

From:	Klaus Jensen
Subject:	Re: [PATCH 0/2] hw/block/nvme: fixes for interrupt behavior
Date:	Mon, 11 May 2020 11:59:11 +0200

On May 11 09:09, Philippe Mathieu-Daudé wrote:
> + Michael & Marcel for MSIX,
> and ping to Keith :)
> 

I'll await some feedback here before moving these fixes into my "nvme:
refactoring and cleanups" series. Not sure if this should go directly to
master or block-next.

[Prev in Thread]

Current Thread

[Next in Thread]

[PATCH 0/2] hw/block/nvme: fixes for interrupt behavior, Klaus Jensen, 2020/05/05
- [PATCH 2/2] hw/block/nvme: allow use of any valid msix vector, Klaus Jensen, 2020/05/05
- [PATCH 1/2] hw/block/nvme: fix pin-based interrupt behavior, Klaus Jensen, 2020/05/05
- Re: [PATCH 0/2] hw/block/nvme: fixes for interrupt behavior, Philippe Mathieu-Daudé, 2020/05/11
  - Re: [PATCH 0/2] hw/block/nvme: fixes for interrupt behavior, Klaus Jensen <=

Prev by Date: Re: [PATCH v2 4/4] exec: Rename qemu_ram_writeback() as qemu_ram_msync()
Next by Date: Re: [PATCH 1/2] When del child, next_child_index need to subtract 1. Otherwise, the index will get bigger and bigger.
Previous by thread: Re: [PATCH 0/2] hw/block/nvme: fixes for interrupt behavior
Next by thread: Re: backing chain & block status & filters
Index(es):
- Date
- Thread