qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jens Freimann <jfrei@linux.vnet.ibm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	Alexander Graf <agraf@suse.de>
Cc: Jens Freimann <jfrei@linux.vnet.ibm.com>,
	Thomas Huth <thuth@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org,
	Andreas Faerber <afaerber@suse.de>
Subject: [Qemu-devel] [PATCH v2 0/2] KVM: s390: add floating irq controller
Date: Fri,  6 Sep 2013 14:19:15 +0200	[thread overview]
Message-ID: <1378469957-62290-1-git-send-email-jfrei@linux.vnet.ibm.com> (raw)

This series adds a kvm_device that acts as a irq controller for floating
interrupts.  As a first step it implements functionality to retrieve and inject
interrupts for the purpose of migration and for hardening the reset code by
allowing user space to explicitly remove all pending floating interrupts.
 
PFAULT patches will also use this device for enabling/disabling pfault, therefore
the pfault patch series will be reworked to use this device.
 
* Patch 1/2 adds a new data structure to hold interrupt information. The current
  one (struct kvm_s390_interrupt) does not allow to inject every kind of interrupt,
  e.g. some data for program interrupts and machine check interruptions were
  missing.
 
* Patch 2/2 adds a kvm_device which supports getting/setting currently pending
  floating interrupts as well as deleting all currently pending interrupts


Jens Freimann (2):
  KVM: s390: add and extend interrupt information data structs
  KVM: s390: add floating irq controller

 Documentation/virtual/kvm/devices/s390_flic.txt |  36 +++
 arch/s390/include/asm/kvm_host.h                |  35 +--
 arch/s390/include/uapi/asm/kvm.h                |   5 +
 arch/s390/kvm/interrupt.c                       | 304 ++++++++++++++++++++----
 arch/s390/kvm/kvm-s390.c                        |   1 +
 include/linux/kvm_host.h                        |   1 +
 include/uapi/linux/kvm.h                        |  65 +++++
 virt/kvm/kvm_main.c                             |   5 +
 8 files changed, 368 insertions(+), 84 deletions(-)
 create mode 100644 Documentation/virtual/kvm/devices/s390_flic.txt

-- 
1.8.3.4

             reply	other threads:[~2013-09-06 12:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-06 12:19 Jens Freimann [this message]
2013-09-06 12:19 ` [Qemu-devel] [PATCH v2 1/2] KVM: s390: add and extend interrupt information data structs Jens Freimann
2013-09-06 13:20   ` Christian Borntraeger
2013-10-04 23:38   ` Alexander Graf
2013-09-06 12:19 ` [Qemu-devel] [PATCH v2 2/2] KVM: s390: add floating irq controller Jens Freimann
2013-09-06 13:22   ` Christian Borntraeger
2013-10-04 23:53   ` Alexander Graf
2013-10-08 10:38     ` Jens Freimann
2013-09-06 13:30 ` [Qemu-devel] [PATCH v2 0/2] " Christian Borntraeger
2013-09-15 10:47   ` Gleb Natapov
2013-10-04 23:54   ` Alexander Graf
2013-10-07 19:00     ` Christian Borntraeger

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=1378469957-62290-1-git-send-email-jfrei@linux.vnet.ibm.com \
    --to=jfrei@linux.vnet.ibm.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@linux.vnet.ibm.com \
    /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).