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>,
	Alexander Graf <agraf@suse.de>,
	Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Jens Freimann <jfrei@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 00/10] s390x: move sigp handling to user space
Date: Tue, 24 Feb 2015 14:15:21 +0100	[thread overview]
Message-ID: <1424783731-43426-1-git-send-email-jfrei@linux.vnet.ibm.com> (raw)

Cornelia, Alex, Christian,

these patches move large parts of SIGP handling from kernel
to user space.

Please note: This series needs a linux-headers sync with v4.0-rc1 
to work and should be applied only after Michael Tsirkin's series 
"virtio: pull headers from linux" was applied and a header sync
was done with the new scripts and header files. 

regards
Jens

David Hildenbrand (10):
  s390x: introduce defines for SIGP condition codes
  s390x/kvm: more details for SIGP handler with one destination vcpu
  s390x/kvm: pass the SIGP instruction parameter to the SIGP handler
  s390x/kvm: helper to set the SIGP status in SigpInfo
  s390x/kvm: trace all SIGP orders
  s390x/kvm: implement handling of new SIGP orders
  s390x/kvm: SIGP START is only applicable when STOPPED
  s390x: add function to deliver restart irqs
  s390x/kvm: deliver SIGP RESTART directly if stopped
  s390x/kvm: enable the new SIGP handling in user space

 target-s390x/cpu.c         |   2 +
 target-s390x/cpu.h         |  25 ++-
 target-s390x/helper.c      |  35 ++++-
 target-s390x/kvm.c         | 371 ++++++++++++++++++++++++++++++++++++++-------
 target-s390x/machine.c     |   5 +-
 target-s390x/misc_helper.c |   4 +-
 trace-events               |   1 +
 7 files changed, 372 insertions(+), 71 deletions(-)

-- 
2.1.4

             reply	other threads:[~2015-02-24 13:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 13:15 Jens Freimann [this message]
2015-02-24 13:15 ` [Qemu-devel] [PATCH 01/10] s390x: introduce defines for SIGP condition codes Jens Freimann
2015-02-24 13:15 ` [Qemu-devel] [PATCH 02/10] s390x/kvm: more details for SIGP handler with one destination vcpu Jens Freimann
2015-02-24 13:15 ` [Qemu-devel] [PATCH 03/10] s390x/kvm: pass the SIGP instruction parameter to the SIGP handler Jens Freimann
2015-02-24 13:15 ` [Qemu-devel] [PATCH 04/10] s390x/kvm: helper to set the SIGP status in SigpInfo Jens Freimann
2015-02-24 13:15 ` [Qemu-devel] [PATCH 05/10] s390x/kvm: trace all SIGP orders Jens Freimann
2015-02-24 13:15 ` [Qemu-devel] [PATCH 06/10] s390x/kvm: implement handling of new " Jens Freimann
2015-02-24 13:15 ` [Qemu-devel] [PATCH 07/10] s390x/kvm: SIGP START is only applicable when STOPPED Jens Freimann
2015-02-24 13:15 ` [Qemu-devel] [PATCH 08/10] s390x: add function to deliver restart irqs Jens Freimann
2015-02-24 13:15 ` [Qemu-devel] [PATCH 09/10] s390x/kvm: deliver SIGP RESTART directly if stopped Jens Freimann
2015-02-24 13:15 ` [Qemu-devel] [PATCH 10/10] s390x/kvm: enable the new SIGP handling in user space Jens Freimann
2015-03-03 14:02 ` [Qemu-devel] [PATCH 00/10] s390x: move sigp handling to " 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=1424783731-43426-1-git-send-email-jfrei@linux.vnet.ibm.com \
    --to=jfrei@linux.vnet.ibm.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.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).