From: Alex Williamson <alex.williamson@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH] vfio/pci: Add ioeventfd support
Date: Tue, 6 Feb 2018 21:25:38 -0700 [thread overview]
Message-ID: <20180206212538.50ef0e13@w520.home> (raw)
In-Reply-To: <cfe31ae1-2557-d15a-45a2-0ba03d8d71fa@ozlabs.ru>
On Wed, 7 Feb 2018 15:09:22 +1100
Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
> On 07/02/18 11:08, Alex Williamson wrote:
> > diff --git a/include/uapi/linux/vfio.h b/include/uapi/linux/vfio.h
> > index e3301dbd27d4..07966a5f0832 100644
> > --- a/include/uapi/linux/vfio.h
> > +++ b/include/uapi/linux/vfio.h
> > @@ -503,6 +503,30 @@ struct vfio_pci_hot_reset {
> >
> > #define VFIO_DEVICE_PCI_HOT_RESET _IO(VFIO_TYPE, VFIO_BASE + 13)
> >
> > +/**
> > + * VFIO_DEVICE_IOEVENTFD - _IOW(VFIO_TYPE, VFIO_BASE + 14,
> > + * struct vfio_device_ioeventfd)
> > + *
> > + * Perform a write to the device at the specified device fd offset, with
> > + * the specified data and width when the provided eventfd is triggered.
> > + *
> > + * Return: 0 on success, -errno on failure.
> > + */
> > +struct vfio_device_ioeventfd {
> > + __u32 argsz;
> > + __u32 flags;
> > +#define VFIO_DEVICE_IOEVENTFD_8 (1 << 0) /* 1-byte write */
> > +#define VFIO_DEVICE_IOEVENTFD_16 (1 << 1) /* 2-byte write */
> > +#define VFIO_DEVICE_IOEVENTFD_32 (1 << 2) /* 4-byte write */
> > +#define VFIO_DEVICE_IOEVENTFD_64 (1 << 3) /* 8-byte write */
> > +#define VFIO_DEVICE_IOEVENTFD_SIZE_MASK (0xf)
> > + __u64 offset; /* device fd offset of write */
> > + __u64 data; /* data to be written */
> > + __s32 fd; /* -1 for de-assignment */
> > +};
> > +
> > +#define VFIO_DEVICE_IOEVENTFD _IO(VFIO_TYPE, VFIO_BASE + 14)
>
>
> Is this a first ioctl with endianness fixed to little-endian? I'd suggest
> to comment on that as things like vfio_info_cap_header do use the host
> endianness.
Look at our current read and write interface, we call leXX_to_cpu
before calling iowriteXX there and I think a user would logically
expect to use the same data format here as they would there. Also note
that iowriteXX does a cpu_to_leXX, so are we really defining the
interface as little-endian or are we just trying to make ourselves
endian neutral and counter that implicit conversion? Thanks,
Alex
next prev parent reply other threads:[~2018-02-07 4:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 0:08 [Qemu-devel] [RFC PATCH] vfio/pci: Add ioeventfd support Alex Williamson
2018-02-07 4:09 ` Alexey Kardashevskiy
2018-02-07 4:25 ` Alex Williamson [this message]
2018-02-07 4:48 ` Alexey Kardashevskiy
2018-02-07 14:12 ` Alex Williamson
2018-02-08 1:22 ` Alexey Kardashevskiy
2018-03-13 12:38 ` Auger Eric
2018-03-15 21:23 ` Alex Williamson
2018-02-07 15:46 ` Auger Eric
2018-02-07 16:57 ` Alex Williamson
2018-02-08 13:48 ` Auger Eric
2018-02-09 7:05 ` Peter Xu
2018-02-09 21:45 ` Alex Williamson
2018-02-11 3:09 ` Peter Xu
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=20180206212538.50ef0e13@w520.home \
--to=alex.williamson@redhat.com \
--cc=aik@ozlabs.ru \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).