From: "Michael S. Tsirkin" <mst@redhat.com>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Cedric Le Goater <clg@fr.ibm.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-ppc] [PATCH] virtio-pci: fix host notifiers on bi-endian architectures
Date: Thu, 12 Mar 2015 08:10:16 +0100 [thread overview]
Message-ID: <20150312080833-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <20150311235213.6967e39c@bahia.local>
On Wed, Mar 11, 2015 at 11:52:13PM +0100, Greg Kurz wrote:
> On Thu, 12 Mar 2015 09:18:38 +1100
> Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> > On Wed, 2015-03-11 at 23:03 +0100, Greg Kurz wrote:
> >
> > > /* The host notifier will be swapped in adjust_endianness() according to the
> > > * target default endianness. We need to negate this swap if the device uses
> > > * an endianness that is not the default (ppc64le for example).
> > > */
> > >
> > > > > +static uint16_t cpu_to_host_notifier16(VirtIODevice *vdev, uint16_t val)
> > > > > +{
> > > > > + return virtio_is_big_endian(vdev) ? val : bswap16(val);
> > > > > +}
> >
> > But but but ... The above ... won't it do things like break x86 ? Ie,
> > shouldn't we swap only if TARGET_BIG_ENDIAN and !virtio_is_big_endian ?
> > Or better, "fixed target endian" ^ "virtio endian" to cover all cases ?
> >
>
> Yeah you're right, it's a mess :)
>
> To avoid virtio-pci.o being built per target, we can use virtio_default_endian()
> instead (to be exported from virtio.c):
>
> return vdev->device_endian() != virtio_default_endian() ? val : bswap16(val);
>
> I shall test on x86 and post a v2.
>
> Thanks.
>
> --
> G
It's a mess because the issue is not in virtio I think.
virtio common region is just a simple device, using
fixed LE format.
It's some bug in ioeventfd support. Need to understand
whether it's in kernel (and maybe do a work-around)
or in qemu memory core.
> > Cheers,
> > Ben.
> >
> > > > > static int virtio_pci_set_host_notifier_internal(VirtIOPCIProxy *proxy,
> > > > > int n, bool assign, bool set_handler)
> > > > > {
> > > > > @@ -150,10 +155,12 @@ static int virtio_pci_set_host_notifier_internal(VirtIOPCIProxy *proxy,
> > > > > }
> > > > > virtio_queue_set_host_notifier_fd_handler(vq, true, set_handler);
> > > > > memory_region_add_eventfd(&proxy->bar, VIRTIO_PCI_QUEUE_NOTIFY, 2,
> > > > > - true, n, notifier);
> > > > > + true, cpu_to_host_notifier16(vdev, n),
> > > > > + notifier);
> > > > > } else {
> > > > > memory_region_del_eventfd(&proxy->bar, VIRTIO_PCI_QUEUE_NOTIFY, 2,
> > > > > - true, n, notifier);
> > > > > + true, cpu_to_host_notifier16(vdev, n),
> > > > > + notifier);
> > > > > virtio_queue_set_host_notifier_fd_handler(vq, false, false);
> > > > > event_notifier_cleanup(notifier);
> > > > > }
> > > >
> > >
> >
> >
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: Cedric Le Goater <clg@fr.ibm.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] virtio-pci: fix host notifiers on bi-endian architectures
Date: Thu, 12 Mar 2015 08:10:16 +0100 [thread overview]
Message-ID: <20150312080833-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <20150311235213.6967e39c@bahia.local>
On Wed, Mar 11, 2015 at 11:52:13PM +0100, Greg Kurz wrote:
> On Thu, 12 Mar 2015 09:18:38 +1100
> Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> > On Wed, 2015-03-11 at 23:03 +0100, Greg Kurz wrote:
> >
> > > /* The host notifier will be swapped in adjust_endianness() according to the
> > > * target default endianness. We need to negate this swap if the device uses
> > > * an endianness that is not the default (ppc64le for example).
> > > */
> > >
> > > > > +static uint16_t cpu_to_host_notifier16(VirtIODevice *vdev, uint16_t val)
> > > > > +{
> > > > > + return virtio_is_big_endian(vdev) ? val : bswap16(val);
> > > > > +}
> >
> > But but but ... The above ... won't it do things like break x86 ? Ie,
> > shouldn't we swap only if TARGET_BIG_ENDIAN and !virtio_is_big_endian ?
> > Or better, "fixed target endian" ^ "virtio endian" to cover all cases ?
> >
>
> Yeah you're right, it's a mess :)
>
> To avoid virtio-pci.o being built per target, we can use virtio_default_endian()
> instead (to be exported from virtio.c):
>
> return vdev->device_endian() != virtio_default_endian() ? val : bswap16(val);
>
> I shall test on x86 and post a v2.
>
> Thanks.
>
> --
> G
It's a mess because the issue is not in virtio I think.
virtio common region is just a simple device, using
fixed LE format.
It's some bug in ioeventfd support. Need to understand
whether it's in kernel (and maybe do a work-around)
or in qemu memory core.
> > Cheers,
> > Ben.
> >
> > > > > static int virtio_pci_set_host_notifier_internal(VirtIOPCIProxy *proxy,
> > > > > int n, bool assign, bool set_handler)
> > > > > {
> > > > > @@ -150,10 +155,12 @@ static int virtio_pci_set_host_notifier_internal(VirtIOPCIProxy *proxy,
> > > > > }
> > > > > virtio_queue_set_host_notifier_fd_handler(vq, true, set_handler);
> > > > > memory_region_add_eventfd(&proxy->bar, VIRTIO_PCI_QUEUE_NOTIFY, 2,
> > > > > - true, n, notifier);
> > > > > + true, cpu_to_host_notifier16(vdev, n),
> > > > > + notifier);
> > > > > } else {
> > > > > memory_region_del_eventfd(&proxy->bar, VIRTIO_PCI_QUEUE_NOTIFY, 2,
> > > > > - true, n, notifier);
> > > > > + true, cpu_to_host_notifier16(vdev, n),
> > > > > + notifier);
> > > > > virtio_queue_set_host_notifier_fd_handler(vq, false, false);
> > > > > event_notifier_cleanup(notifier);
> > > > > }
> > > >
> > >
> >
> >
next prev parent reply other threads:[~2015-03-12 7:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 18:04 [PATCH] virtio-pci: fix host notifiers on bi-endian architectures Greg Kurz
2015-03-11 18:04 ` [Qemu-devel] " Greg Kurz
2015-03-11 20:06 ` Michael S. Tsirkin
2015-03-11 20:06 ` [Qemu-devel] " Michael S. Tsirkin
2015-03-11 22:03 ` Greg Kurz
2015-03-11 22:03 ` [Qemu-devel] " Greg Kurz
2015-03-11 22:18 ` [Qemu-devel] [Qemu-ppc] " Benjamin Herrenschmidt
2015-03-11 22:52 ` Greg Kurz
2015-03-11 22:52 ` [Qemu-devel] " Greg Kurz
2015-03-12 7:10 ` Michael S. Tsirkin [this message]
2015-03-12 7:10 ` Michael S. Tsirkin
2015-03-11 22:18 ` Benjamin Herrenschmidt
2015-03-12 7:08 ` Michael S. Tsirkin
2015-03-12 7:08 ` [Qemu-devel] " Michael S. Tsirkin
2015-03-12 16:25 ` Paolo Bonzini
2015-03-12 16:25 ` [Qemu-devel] " Paolo Bonzini
2015-03-13 8:03 ` Greg Kurz
2015-03-13 8:03 ` [Qemu-devel] " Greg Kurz
2015-03-13 8:11 ` [Qemu-devel] [PATCH 1/2] memory: make adjust_endianness() generic Greg Kurz
2015-03-13 8:11 ` [Qemu-devel] [PATCH 2/2] memory: fix the eventfd data endianness according to the host Greg Kurz
2015-03-13 11:06 ` Paolo Bonzini
2015-03-13 11:32 ` Greg Kurz
2015-03-13 14:52 ` Paolo Bonzini
2015-03-13 15:24 ` Michael S. Tsirkin
2015-03-13 14:23 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150312080833-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=clg@fr.ibm.com \
--cc=gkurz@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.