qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jens Freimann <jfrei@linux.vnet.ibm.com>
To: Alexander Graf <agraf@suse.de>
Cc: Heinz Graalfs <graalfs@linux.vnet.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Einar Lueck <elelueck@linux.vnet.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Jens Freimann <jfrei@linux.vnet.ibm.com>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	Andreas Faerber <afaerber@suse.de>
Subject: [Qemu-devel] [PATCH 0/4 v4] s390: sclp patch set
Date: Mon, 20 Aug 2012 16:28:42 +0200	[thread overview]
Message-ID: <1345472926-21528-1-git-send-email-jfrei@linux.vnet.ibm.com> (raw)

This patch-set improves the Service-Call Logical Processor support for s390.

changes v3->v4:
- Event Facility was moved to the main system bus and we now keep the 
  event_facility pointer within the current machine's global property-list 
  as opaque pointer
- removed locking
- some code refactoring in response to Alexander Graf's and Andreas Faerber's
  review comments (variables/functions renamed, return codes changed)

Patch 1 adds/changes some base SCLP support. Patch 2 adds code
to support the SCLP commands Write Event Mask, Write Event Data, and
Read Event Data. Patch 3 and 4 add code to implement the commands for the
particular SCLP events Signal Quiesce (system_powerdown), and ASCII Console
data.

Heinz Graalfs (4):
  s390: sclp base support
  s390: sclp event support
  s390: sclp signal quiesce support
  s390: sclp ascii console support

 hw/s390-virtio.c          |   4 +
 hw/s390x/Makefile.objs    |   3 +
 hw/s390x/event-facility.c | 398 ++++++++++++++++++++++++++++++++++++++++++++++
 hw/s390x/event-facility.h |  96 +++++++++++
 hw/s390x/sclp.c           | 152 ++++++++++++++++++
 hw/s390x/sclp.h           | 118 ++++++++++++++
 hw/s390x/sclpconsole.c    | 306 +++++++++++++++++++++++++++++++++++
 hw/s390x/sclpquiesce.c    | 112 +++++++++++++
 target-s390x/cpu.h        |  14 +-
 target-s390x/kvm.c        |   5 +-
 target-s390x/op_helper.c  |  31 +---
 11 files changed, 1197 insertions(+), 42 deletions(-)
 create mode 100644 hw/s390x/event-facility.c
 create mode 100644 hw/s390x/event-facility.h
 create mode 100644 hw/s390x/sclp.c
 create mode 100644 hw/s390x/sclp.h
 create mode 100644 hw/s390x/sclpconsole.c
 create mode 100644 hw/s390x/sclpquiesce.c

-- 
1.7.11.5

             reply	other threads:[~2012-08-20 14:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-20 14:28 Jens Freimann [this message]
2012-08-20 14:28 ` [Qemu-devel] [PATCH 1/4] s390: sclp base support Jens Freimann
2012-09-26 15:00   ` Alexander Graf
2012-09-26 16:06     ` Christian Borntraeger
2012-09-26 19:01       ` Alexander Graf
2012-09-26 19:25         ` Christian Borntraeger
2012-09-26 19:27           ` Alexander Graf
2012-08-20 14:28 ` [Qemu-devel] [PATCH 2/4] s390: sclp event support Jens Freimann
2012-08-20 14:28 ` [Qemu-devel] [PATCH 3/4] s390: sclp signal quiesce support Jens Freimann
2012-08-20 14:28 ` [Qemu-devel] [PATCH 4/4] s390: sclp ascii console support Jens Freimann

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=1345472926-21528-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=elelueck@linux.vnet.ibm.com \
    --cc=graalfs@linux.vnet.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).