Here's a new version of MSI-X support patchset. I have completed
save/load support, and added a global option to disable MSI-X.
This is on top of qemu-kvm.git/queue
Todo: split patch up, support configurations without kernel irqchip,
apply to upstream qemu.git.
Anthony, please take a look at
This adds MSI-X support infrastructure and uses that to enable MSI-X
support in virtio net device. Also add a global option to disable MSI-X.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
Makefile.target|2 +-
hw/device-assignment.c |2 +
hw/msix.c | 447
For assigned devices, use common code to enable msi-x. We need a special
assigned option as assigned devices lack a standard way to get vector
usage.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
hw/device-assignment.c | 329
On Wed, May 20, 2009 at 08:44:31PM +0300, Blue Swirl wrote:
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, May 20, 2009 at 08:21:01PM +0300, Blue Swirl wrote:
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
define api for allocating/setting up msi-x irqs, and for
On Wed, May 20, 2009 at 08:44:31PM +0300, Blue Swirl wrote:
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, May 20, 2009 at 08:21:01PM +0300, Blue Swirl wrote:
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
define api for allocating/setting up msi-x irqs, and for
On Wed, May 20, 2009 at 08:21:01PM +0300, Blue Swirl wrote:
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
define api for allocating/setting up msi-x irqs, and for updating them
with msi-x vector information, supply implementation in ioapic. Please
comment on this API: I intend to
On 5/20/09, Avi Kivity a...@redhat.com wrote:
Blue Swirl wrote:
Sparc64 also uses packets (mondos, not implemented yet) for
interrupt vector data, there the packet size is 8 * 64 bits. I think
we should aim for a more generic API that covers this case also.
Is the packet structure
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, May 20, 2009 at 08:21:01PM +0300, Blue Swirl wrote:
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
define api for allocating/setting up msi-x irqs, and for updating them
with msi-x vector information, supply
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, May 20, 2009 at 08:44:31PM +0300, Blue Swirl wrote:
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, May 20, 2009 at 08:21:01PM +0300, Blue Swirl wrote:
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
Blue Swirl wrote:
Sparc64 also uses packets (mondos, not implemented yet) for
interrupt vector data, there the packet size is 8 * 64 bits. I think
we should aim for a more generic API that covers this case also.
Is the packet structure visible to software?
--
I have a truly marvellous
define api for allocating/setting up msi-x irqs, and for updating them
with msi-x vector information, supply implementation in ioapic. Please
comment on this API: I intend to port my msi-x patch to work on top of
it.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
hw/apic.c |1 -
On Wed, May 20, 2009 at 09:38:58PM +0300, Blue Swirl wrote:
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, May 20, 2009 at 08:44:31PM +0300, Blue Swirl wrote:
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, May 20, 2009 at 08:21:01PM +0300, Blue Swirl
On Wed, May 20, 2009 at 11:02:24PM +0300, Michael S. Tsirkin wrote:
On Wed, May 20, 2009 at 09:38:58PM +0300, Blue Swirl wrote:
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, May 20, 2009 at 08:44:31PM +0300, Blue Swirl wrote:
On 5/20/09, Michael S. Tsirkin
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, May 20, 2009 at 09:38:58PM +0300, Blue Swirl wrote:
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, May 20, 2009 at 08:44:31PM +0300, Blue Swirl wrote:
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, May 20, 2009 at 11:02:24PM +0300, Michael S. Tsirkin wrote:
On Wed, May 20, 2009 at 09:38:58PM +0300, Blue Swirl wrote:
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, May 20, 2009 at 08:44:31PM +0300, Blue
On Wed, May 20, 2009 at 11:18:56PM +0300, Blue Swirl wrote:
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, May 20, 2009 at 09:38:58PM +0300, Blue Swirl wrote:
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, May 20, 2009 at 08:44:31PM +0300, Blue Swirl
On Wed, May 20, 2009 at 11:26:42PM +0300, Blue Swirl wrote:
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, May 20, 2009 at 11:02:24PM +0300, Michael S. Tsirkin wrote:
On Wed, May 20, 2009 at 09:38:58PM +0300, Blue Swirl wrote:
On 5/20/09, Michael S. Tsirkin
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, May 20, 2009 at 11:26:42PM +0300, Blue Swirl wrote:
On 5/20/09, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, May 20, 2009 at 11:02:24PM +0300, Michael S. Tsirkin wrote:
On Wed, May 20, 2009 at 09:38:58PM +0300, Blue
Hi Vivek,
Anyway, how are you taking care of priorities with-in same class. How will
you make sure that a BE prio 0 request is not hidden behind BE prio 7
request? Same is true for prio with-in RT class.
I changed io_limit parameter of dm-ioband and ran your test script
again. io_limit is a
19 matches
Mail list logo
