Re: [Qemu-devel] virtio fixes pull for 4.0?

2015-03-23 Thread Pawel Moll
On Mon, 2015-03-09 at 07:13 +, Rusty Russell wrote: > > virtio_mmio: generation support > > virtio_mmio: fix endian-ness for mmio these two are waiting for ack by > > Pawel > > > > These two fix bugs in virtio 1.0 code for mmio. > > Host code for that was AFAIK not posted, so I can't t

Re: [Qemu-devel] [RFC PATCH] virtio-mmio: support for multiple irqs

2014-11-14 Thread Pawel Moll
On Thu, 2014-11-13 at 09:39 +, Shannon Zhao wrote: > When we use only virtio-mmio or vhost-net without irqfd, the device uses > qemu_set_irq(within qemu) > to inject interrupt and at the same time qemu update > "VIRTIO_MMIO_INTERRUPT_STATUS" to tell guest > driver whom this interrupt to. All

Re: [Qemu-devel] [RFC PATCH] virtio-mmio: support for multiple irqs

2014-11-12 Thread Pawel Moll
On Wed, 2014-11-12 at 08:32 +, Shannon Zhao wrote: > On 2014/11/11 23:11, Pawel Moll wrote: > > On Tue, 2014-11-04 at 09:35 +, Shannon Zhao wrote: > >> As the current virtio-mmio only support single irq, > >> so some advanced features such as vhost-net with i

Re: [Qemu-devel] [RFC PATCH] virtio-mmio: support for multiple irqs

2014-11-11 Thread Pawel Moll
On Tue, 2014-11-04 at 09:35 +, Shannon Zhao wrote: > As the current virtio-mmio only support single irq, > so some advanced features such as vhost-net with irqfd > are not supported. And the net performance is not > the best without vhost-net and irqfd supporting. Could you, please, help under

Re: [Qemu-devel] [RFC 0/4] virtio-mmio transport

2011-12-12 Thread Pawel Moll
On Mon, 2011-12-12 at 15:11 +, Stefan Hajnoczi wrote: > If there aren't already then pretty soon ARM-based systems will deal > with PCIe and Message Signalled Interrupts. Actually PCI is not an alien in ARM world - we had platforms with PCI long time ago. And new SOCs aimed at servers come wi

Re: [Qemu-devel] [RFC 0/4] virtio-mmio transport

2011-12-12 Thread Pawel Moll
On Mon, 2011-12-12 at 14:45 +, Paul Brook wrote: > I suggest that the device to buffer writes to the high part, and construct > the > actual 64-bit value when the low part is written. That allows 32-bit guests > can ignore the high part entirely. This sounds good to me. If we define the re

Re: [Qemu-devel] [RFC 0/4] virtio-mmio transport

2011-12-12 Thread Pawel Moll
On Mon, 2011-12-12 at 13:12 +, Michael S. Tsirkin wrote: > On Mon, Dec 12, 2011 at 12:28:27PM +0000, Pawel Moll wrote: > > On Mon, 2011-12-12 at 12:14 +, Stefan Hajnoczi wrote: > > > I noticed the virtio-mmio spec has an interrupt status register. On > > > x8

Re: [Qemu-devel] [RFC 0/4] virtio-mmio transport

2011-12-12 Thread Pawel Moll
On Mon, 2011-12-12 at 12:14 +, Stefan Hajnoczi wrote: > I noticed the virtio-mmio spec has an interrupt status register. On > x86 and virtio-pci things are moving towards Message Signalled > Interrupts and virtqueues having their own interrupts for better > performance and flexibility. Any th

Re: [Qemu-devel] [RFC 0/4] virtio-mmio transport

2011-12-12 Thread Pawel Moll
On Mon, 2011-12-12 at 02:52 +, Paul Brook wrote: > I've taken a look at the virtion-mmio spec, and it looks fairly > reasonable. > > The only thing I'd change is the GuestPageSize/QueuePFN mess. Seems like > just > using straight 64-bit addresses would be a better solution. Maybe split int

Re: [Qemu-devel] [RFC 0/4] virtio-mmio transport

2011-11-17 Thread Pawel Moll
On Wed, 2011-11-16 at 19:56 +, Anthony Liguori wrote: > On 11/16/2011 12:41 PM, Peter Maydell wrote: > > Pawel may have more detail, but to me the significant difference > > is that virtio-mmio is an implementation of a specification extension > > agreed with the virtio spec maintainers, wherea