From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: KVM <kvm@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [RFC PATCH v2 3/4] KVM: ioeventfd for s390 css devices.
Date: Mon, 25 Feb 2013 09:49:01 +0100 [thread overview]
Message-ID: <20130225094901.7dac374e@gondolin> (raw)
In-Reply-To: <20130224094750.GD25269@redhat.com>
On Sun, 24 Feb 2013 11:47:50 +0200
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Fri, Feb 22, 2013 at 01:09:48PM +0100, Cornelia Huck wrote:
> > Enhance KVM_IOEVENTFD with a new flag that allows to attach to s390 css
> > devices.
> >
> > Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
> > ---
> > Documentation/virtual/kvm/api.txt | 7 +++++++
> > include/uapi/linux/kvm.h | 2 ++
> > virt/kvm/eventfd.c | 8 ++++++--
> > 3 files changed, 15 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt
> > index c2534c3..40e799c 100644
> > --- a/Documentation/virtual/kvm/api.txt
> > +++ b/Documentation/virtual/kvm/api.txt
> > @@ -1468,15 +1468,22 @@ struct kvm_ioeventfd {
> > __u8 pad[36];
> > };
> >
> > +For the special case of s390 css devices, the ioevent is matched to a
> > +subchannel/virtqueue tuple instead.
> > +
> > The following flags are defined:
> >
> > #define KVM_IOEVENTFD_FLAG_DATAMATCH (1 << kvm_ioeventfd_flag_nr_datamatch)
> > #define KVM_IOEVENTFD_FLAG_PIO (1 << kvm_ioeventfd_flag_nr_pio)
> > #define KVM_IOEVENTFD_FLAG_DEASSIGN (1 << kvm_ioeventfd_flag_nr_deassign)
> > +#define KVM_IOEVENTFD_FLAG_CSS (1 << kvm_ioeventfd_flag_nr_css)
> >
> > If datamatch flag is set, the event will be signaled only if the written value
> > to the registered address is equal to datamatch in struct kvm_ioeventfd.
> >
> > +For css devices, addr contains the subchannel id and datamatch the virtqueue
> > +index.
> > +
> >
> > 4.60 KVM_DIRTY_TLB
> >
> > diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h
> > index 9a2db57..1df0766 100644
> > --- a/include/uapi/linux/kvm.h
> > +++ b/include/uapi/linux/kvm.h
> > @@ -448,12 +448,14 @@ enum {
> > kvm_ioeventfd_flag_nr_datamatch,
> > kvm_ioeventfd_flag_nr_pio,
> > kvm_ioeventfd_flag_nr_deassign,
> > + kvm_ioeventfd_flag_nr_css,
> > kvm_ioeventfd_flag_nr_max,
> > };
> >
> > #define KVM_IOEVENTFD_FLAG_DATAMATCH (1 << kvm_ioeventfd_flag_nr_datamatch)
> > #define KVM_IOEVENTFD_FLAG_PIO (1 << kvm_ioeventfd_flag_nr_pio)
> > #define KVM_IOEVENTFD_FLAG_DEASSIGN (1 << kvm_ioeventfd_flag_nr_deassign)
> > +#define KVM_IOEVENTFD_FLAG_CSS (1 << kvm_ioeventfd_flag_nr_css)
>
> So let's explicitly name is KVM_IOEVENTFD_S390_VIRTIO_CCW or even
> KVM_IOEVENTFD_S390_VIRTIO_CCW_NOTIFY?
How about KVM_IOEVENTFD_FLAG_VIRTIO_CCW_NOTIFY?
> Also, maybe we want to add KVM_IOEVENTFD_S390_VIRTIO_NOTIFY as well?
No, since s390-virtio is a dead end.
>
> >
> > #define KVM_IOEVENTFD_VALID_FLAG_MASK ((1 << kvm_ioeventfd_flag_nr_max) - 1)
> >
> > diff --git a/virt/kvm/eventfd.c b/virt/kvm/eventfd.c
> > index f0ced1a..7347652 100644
> > --- a/virt/kvm/eventfd.c
> > +++ b/virt/kvm/eventfd.c
> > @@ -679,11 +679,13 @@ static int
> > kvm_assign_ioeventfd(struct kvm *kvm, struct kvm_ioeventfd *args)
> > {
> > int pio = args->flags & KVM_IOEVENTFD_FLAG_PIO;
> > - enum kvm_bus bus_idx = pio ? KVM_PIO_BUS : KVM_MMIO_BUS;
> > + int css = args->flags & KVM_IOEVENTFD_FLAG_CSS;
> > + enum kvm_bus bus_idx;
> > struct _ioeventfd *p;
> > struct eventfd_ctx *eventfd;
> > int ret;
> >
> > + bus_idx = pio ? KVM_PIO_BUS : css ? KVM_CSS_BUS: KVM_MMIO_BUS;
> > /* must be natural-word sized */
> > switch (args->len) {
> > case 1:
> > @@ -759,11 +761,13 @@ static int
> > kvm_deassign_ioeventfd(struct kvm *kvm, struct kvm_ioeventfd *args)
> > {
> > int pio = args->flags & KVM_IOEVENTFD_FLAG_PIO;
> > - enum kvm_bus bus_idx = pio ? KVM_PIO_BUS : KVM_MMIO_BUS;
> > + int css = args->flags & KVM_IOEVENTFD_FLAG_CSS;
> > + enum kvm_bus bus_idx;
> > struct _ioeventfd *p, *tmp;
> > struct eventfd_ctx *eventfd;
> > int ret = -ENOENT;
> >
> > + bus_idx = pio ? KVM_PIO_BUS : css ? KVM_CSS_BUS: KVM_MMIO_BUS;
> > eventfd = eventfd_ctx_fdget(args->fd);
> > if (IS_ERR(eventfd))
> > return PTR_ERR(eventfd);
> > --
> > 1.7.12.4
>
next prev parent reply other threads:[~2013-02-25 8:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 12:09 [RFC PATCH v2 0/4] kvm: Make ioeventfd usable on s390 Cornelia Huck
2013-02-22 12:09 ` [RFC PATCH v2 1/4] KVM: Initialize irqfd from kvm_init() Cornelia Huck
2013-02-22 12:09 ` [RFC PATCH v2 2/4] KVM: Introduce KVM_CSS_BUS Cornelia Huck
2013-02-24 9:57 ` Michael S. Tsirkin
2013-02-25 8:50 ` Cornelia Huck
2013-02-22 12:09 ` [RFC PATCH v2 3/4] KVM: ioeventfd for s390 css devices Cornelia Huck
2013-02-24 9:47 ` Michael S. Tsirkin
2013-02-25 8:49 ` Cornelia Huck [this message]
2013-02-22 12:09 ` [RFC PATCH v2 4/4] KVM: s390: Wire up ioeventfd Cornelia Huck
2013-02-24 9:45 ` Michael S. Tsirkin
2013-02-25 8:46 ` Cornelia Huck
2013-02-24 9:40 ` [RFC PATCH v2 0/4] kvm: Make ioeventfd usable on s390 Michael S. Tsirkin
2013-02-24 9:56 ` Michael S. Tsirkin
2013-02-25 8:43 ` Cornelia Huck
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=20130225094901.7dac374e@gondolin \
--to=cornelia.huck@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mst@redhat.com \
--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 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.