From: Christian Borntraeger <borntraeger@de.ibm.com>
To: pbonzini@redhat.com
Cc: linux-s390@vger.kernel.org, kvm@vger.kernel.org, gleb@kernel.org,
qemu-devel@nongnu.org, agraf@suse.de,
Cornelia Huck <cornelia.huck@de.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/5] qemu: irqfds for s390x
Date: Thu, 27 Mar 2014 12:09:53 +0100 [thread overview]
Message-ID: <53340701.20002@de.ibm.com> (raw)
In-Reply-To: <1395406357-14766-1-git-send-email-cornelia.huck@de.ibm.com>
On 21/03/14 13:52, Cornelia Huck wrote:
> Here's the next iteration of the qemu patchset enabling irqfds for
> s390x, again a companion patchset for "KVM: irqfds for s390".
>
> Changes from v2:
> - rebased against current master
> - use object_resolve_path() to grab the flic
> - more explicit return code check for enabling KVM_CAP_S390_IRQCHIP
>
> Changes from v1:
> - rebased against current master
> - pick up changed capability numbers from the kvm patchset
> - use c99 struct initializers in patch 3
> - adapter interrupts are already upstream
>
> The git branch at
>
> https://github.com/cohuck/qemu.git s390x-irqfd
>
> has been updated accordingly.
The whole series looks good to me.
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
Tested-by: Christian Borntraeger <borntraeger@de.ibm.com>
Paolo,
since we also touch KVM code, and the necessary counter part in
in Linux kvm/next we could push this via the QEMU/KVM tree.
Are you willing to carry those patches in the KVM tree to be
merged after 2.0?
Christian
>
> Cornelia Huck (5):
> linux-headers: add new interfaces
> kvm: add kvm_enable_cap_{vm,vcpu}
> s390x: Add I/O adapter registration.
> s390x/virtio-ccw: reference-counted indicators
> s390x/virtio-ccw: Wire up irq routing and irqfds.
>
> hw/intc/s390_flic.c | 59 +++++++++++
> hw/s390x/css.c | 51 +++++++++
> hw/s390x/css.h | 4 +
> hw/s390x/virtio-ccw.c | 241 +++++++++++++++++++++++++++++++++++++-----
> hw/s390x/virtio-ccw.h | 16 ++-
> include/hw/s390x/adapter.h | 23 ++++
> include/qemu/typedefs.h | 1 +
> include/sysemu/kvm.h | 6 ++
> kvm-all.c | 57 +++++++++-
> kvm-stub.c | 5 +
> linux-headers/asm-s390/kvm.h | 24 +++++
> linux-headers/linux/kvm.h | 17 +++
> target-s390x/cpu.h | 33 ++++++
> target-s390x/kvm.c | 5 +
> 14 files changed, 513 insertions(+), 29 deletions(-)
> create mode 100644 include/hw/s390x/adapter.h
>
prev parent reply other threads:[~2014-03-27 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 12:52 [Qemu-devel] [PATCH v3 0/5] qemu: irqfds for s390x Cornelia Huck
2014-03-21 12:52 ` [Qemu-devel] [PATCH v3 1/5] linux-headers: add new interfaces Cornelia Huck
2014-03-21 12:52 ` [Qemu-devel] [PATCH v3 2/5] kvm: add kvm_enable_cap_{vm,vcpu} Cornelia Huck
2014-03-21 12:52 ` [Qemu-devel] [PATCH v3 3/5] s390x: Add I/O adapter registration Cornelia Huck
2014-03-21 12:52 ` [Qemu-devel] [PATCH v3 4/5] s390x/virtio-ccw: reference-counted indicators Cornelia Huck
2014-03-21 12:52 ` [Qemu-devel] [PATCH v3 5/5] s390x/virtio-ccw: Wire up irq routing and irqfds Cornelia Huck
2014-03-27 11:09 ` Christian Borntraeger [this message]
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=53340701.20002@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=agraf@suse.de \
--cc=cornelia.huck@de.ibm.com \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@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 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).