public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: kvm@vger.kernel.org, linux-s390@vger.kernel.org, qemu-devel@nongnu.org
Cc: borntraeger@de.ibm.com, agraf@suse.de, pbonzini@redhat.com,
	gleb@kernel.org, Cornelia Huck <cornelia.huck@de.ibm.com>
Subject: [PATCH v2 0/5] KVM: irqfds for s390
Date: Mon, 17 Mar 2014 19:11:34 +0100	[thread overview]
Message-ID: <1395079899-29239-1-git-send-email-cornelia.huck@de.ibm.com> (raw)

Hi,

here's the next iteration of my patchset introducing irqfds for s390.

Changes from v1:
- rebased against current kvm/queue, bumping capability numbers
- guest adapter interrupt support is already in the kvm tree

I'd really like to get some feedback for the architecture independent
changes (and perhaps some thoughts on the restrictions described in the
last patch).

Again, find it on

git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git kvms390-irqfd

Cornelia Huck (5):
  KVM: eventfd: Fix lock order inversion.
  KVM: Add per-vm capability enablement.
  KVM: s390: adapter interrupt sources
  KVM: s390: irq routing for adapter interrupts.
  KVM: Bump KVM_MAX_IRQ_ROUTES for s390

 Documentation/virtual/kvm/api.txt               |   27 ++-
 Documentation/virtual/kvm/devices/s390_flic.txt |   45 ++++
 arch/s390/include/asm/kvm_host.h                |   30 +++
 arch/s390/include/uapi/asm/kvm.h                |   22 ++
 arch/s390/kvm/Kconfig                           |    2 +
 arch/s390/kvm/Makefile                          |    2 +-
 arch/s390/kvm/interrupt.c                       |  287 ++++++++++++++++++++++-
 arch/s390/kvm/irq.h                             |   22 ++
 arch/s390/kvm/kvm-s390.c                        |   42 ++++
 arch/s390/kvm/kvm-s390.h                        |    2 +
 include/linux/kvm_host.h                        |   13 +
 include/uapi/linux/kvm.h                        |   16 ++
 virt/kvm/eventfd.c                              |    8 +-
 13 files changed, 506 insertions(+), 12 deletions(-)
 create mode 100644 arch/s390/kvm/irq.h

-- 
1.7.9.5

             reply	other threads:[~2014-03-17 18:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-17 18:11 Cornelia Huck [this message]
2014-03-17 18:11 ` [PATCH v2 1/5] KVM: eventfd: Fix lock order inversion Cornelia Huck
2014-03-17 21:55   ` Christian Borntraeger
2014-03-18  9:18     ` Cornelia Huck
2014-03-18 16:05     ` Paolo Bonzini
2014-03-17 18:11 ` [PATCH v2 2/5] KVM: Add per-vm capability enablement Cornelia Huck
2014-03-17 22:09   ` Christian Borntraeger
2014-03-21  9:12   ` Christian Borntraeger
2014-03-17 18:11 ` [PATCH v2 3/5] KVM: s390: adapter interrupt sources Cornelia Huck
2014-03-18  8:11   ` Heiko Carstens
2014-03-18  8:41     ` Cornelia Huck
2014-03-21  9:26   ` Christian Borntraeger
2014-03-21 10:07     ` Cornelia Huck
2014-03-17 18:11 ` [PATCH v2 4/5] KVM: s390: irq routing for adapter interrupts Cornelia Huck
2014-03-21  9:32   ` Christian Borntraeger
2014-03-21 10:08     ` Cornelia Huck
2014-03-17 18:11 ` [PATCH v2 5/5] KVM: Bump KVM_MAX_IRQ_ROUTES for s390 Cornelia Huck
2014-03-18 16:07   ` Paolo Bonzini

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=1395079899-29239-1-git-send-email-cornelia.huck@de.ibm.com \
    --to=cornelia.huck@de.ibm.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@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