Hi,
There seems to be a bug in the VirtIO guest device driver (tested with
2.6.31.5 kernel).
The bug causes frequent excessive VIRTIO_PCI_ISR reads (causing PIO
vm-exits) for a device that is not being used.
The setup I’m using includes two VirtIO block devices – vda vdb.
While running heavy
yep!
What do I have to do to turn on MSI-x?
Make this PCI capability in QEMU's virtio??
Thanks,
Saul
On Wed, Oct 28, 2009 at 4:59 PM, Michael Tokarev m...@tls.msk.ru wrote:
[snip]
So the next question is how to use MSI-x.. ;)
Thanks!
/mjt
--
To unsubscribe from this list: send the line
- MAbort- SERR- PERR- INTx-
Interrupt: pin A routed to IRQ 10
Region 0: I/O ports at c800 [size=1K]
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci
Thanks,
Saul
On Wed, Oct 28, 2009 at 5:04 PM, Saul Tamari stam...@gmail.com wrote:
yep!
What do I have
Hi,
The current qemu-kvm from the git indeed adds the MSI-x capability to
the virtio block device.
With MSI-x enabled on the virtio block device, there aren't
VIRTIO_PCI_ISR reads on the unused device.
Thanks,
Saul
On Thu, Oct 29, 2009 at 12:10 PM, Avi Kivity a...@redhat.com wrote:
[snip]
You are right.
After enabling MSI-x for the virtio block device I now only see
VIRTIO_PCI_QUEUE_NOTIFY writes and there aren't any VIRTIO_PCI_ISR
reads anymore.
Thanks,
Saul
On Sun, Nov 1, 2009 at 11:23 AM, Avi Kivity a...@redhat.com wrote:
On 10/29/2009 05:47 PM, Saul Tamari wrote:
Hi
' variable to the end of VirtIOBlockReq and
clearing only upto the address of the 'elem.in_addr' field, the
memset() call now clears only 80 bytes.
Signed-off-by: Saul Tamari st...@gmail.com
---
diff --git a/hw/virtio-blk.c b/hw/virtio-blk.c
index 2630b99..fd44371 100644
--- a/hw/virtio-blk.c
On Sun, Nov 8, 2009 at 3:07 PM, Avi Kivity a...@redhat.com wrote:
[snip]
Thanks for the comments. I'll soon resubmit the corrected patch.
I don't understand what the comment below means.
Submit to qemu-de...@nongnu.org since this came from upstream.
Thanks,
Saul
--
To unsubscribe from this
(VirtIOBlockReq) equals 41040 bytes on my x86-64 machine.
By moving the 'elem' variable to the end of VirtIOBlockReq and
clearing only upto the address of the 'elem.in_addr' field, the
memset() call now clears only 80 bytes.
Signed-off-by: Saul Tamari stam...@gmail.com
---
diff --git a/hw/virtio-blk.c b/hw
upto the address of the 'elem.in_addr' field, the
memset() call now clears only 80 bytes.
Signed-off-by: Saul Tamari stam...@gmail.com
-
diff --git a/hw/virtio-blk.c b/hw/virtio-blk.c
index 2630b99..de74b00 100644
--- a/hw/virtio-blk.c
+++ b/hw/virtio
Hi,
I'm looking to find some information about the current status of the
Windows virtio drivers.
Are they certified by Microsoft?
Is there a timeline for this?
Will the drivers be included in future MS operating system DVD distribution?
Thanks,
Saul
--
To unsubscribe from this list: send the
Hi,
Are you talking about both network block drivers?
Thanks,
Saul
On Mon, Jan 11, 2010 at 5:49 PM, Yan Vugenfirer yvuge...@redhat.com wrote:
-Original Message-
From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On
Behalf Of Saul Tamari
Sent: Monday, January 11
Hi,
Where can I view the kvm qemu-kvm open bugs list?
Saul
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi,
While using kvm88, I tried comparing the read throughput between PIIX
IDE and the LSI 53c895a emulation.
My test code is:
while : ; do dd if=/dev/sda1 of=/dev/null bs=4096 count=1024000
results_file 21; done
I averaged the results with:
cat results_file | grep -v records | cut
13 matches
Mail list logo
