From: Christian Borntraeger <borntraeger@de.ibm.com>
To: "Jason J. Herne" <jjherne@us.ibm.com>,
afaerber@suse.de, agraf@suse.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3 v2] S390 SCLP improvements for CPU Hotplug
Date: Tue, 21 Jan 2014 16:39:14 +0100 [thread overview]
Message-ID: <52DE94A2.9010107@de.ibm.com> (raw)
In-Reply-To: <1390247510-12327-1-git-send-email-jjherne@us.ibm.com>
On 20/01/14 20:51, Jason J. Herne wrote:
> From: "Jason J. Herne" <jjherne@us.ibm.com>
>
> Improvements to SCLP, mainly the Read SCP/CPU Info subcommands, to support
> future cpu hotplug operations on the s390 target.
>
> Jason J. Herne (3):
> s390-sclp: Define New SCLP Codes
> s390-sclp: SCLP CPU Info
> s390-sclp: SCLP Event integration
>
> hw/s390x/Makefile.objs | 1 +
> hw/s390x/event-facility.c | 6 ++
> hw/s390x/sclp.c | 53 +++++++++++++++++-
> hw/s390x/sclpcpu.c | 112 ++++++++++++++++++++++++++++++++++++++
> include/hw/s390x/event-facility.h | 5 ++
> include/hw/s390x/sclp.h | 41 ++++++++++++++
> 6 files changed, 217 insertions(+), 1 deletion(-)
> create mode 100644 hw/s390x/sclpcpu.c
>
Applied all to my s390-next tree. Thanks
Christian
prev parent reply other threads:[~2014-01-21 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 19:51 [Qemu-devel] [PATCH 0/3 v2] S390 SCLP improvements for CPU Hotplug Jason J. Herne
2014-01-20 19:51 ` [Qemu-devel] [PATCH 1/3 v2] s390-sclp: Define New SCLP Codes Jason J. Herne
2014-01-20 19:51 ` [Qemu-devel] [PATCH 2/3 v2] s390-sclp: SCLP CPU Info Jason J. Herne
2014-01-21 15:54 ` Andreas Färber
2014-01-20 19:51 ` [Qemu-devel] [PATCH 3/3 v2] s390-sclp: SCLP Event integration Jason J. Herne
2014-01-21 15:44 ` Andreas Färber
2014-01-21 15:39 ` 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=52DE94A2.9010107@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=jjherne@us.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.