From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>, qemu-devel@nongnu.org
Cc: jfrei@linux.vnet.ibm.com, agraf@suse.de
Subject: Re: [Qemu-devel] [PATCH 0/8] pending s390x patches for 2.2
Date: Thu, 09 Oct 2014 13:18:54 +0200 [thread overview]
Message-ID: <54366F1E.2080706@de.ibm.com> (raw)
In-Reply-To: <1412679515-19330-1-git-send-email-cornelia.huck@de.ibm.com>
Am 07.10.2014 12:58, schrieb Cornelia Huck:
> Here's what I currently have on
>
> git://github.com/cohuck/qemu s390-next
>
> A headers update, cpu state handling in qemu and migration, and a
> vhost-scsi-ccw bugfix. The gdb patch needs further discussion.
>
> I plan to send a pull request later this week.
FWIW, branch is
Tested-by: Christian Borntraeger <borntraeger@de.ibm.com>
>
> Cornelia Huck (1):
> s390x/virtio-ccw: fix vhost-scsi intialization
>
> David Hildenbrand (5):
> s390x/kvm: introduce proper states for s390 cpus
> s390x/kvm: proper use of the cpu states OPERATING and STOPPED
> s390x/kvm: propagate s390 cpu state to kvm
> s390x/kvm: reuse kvm_s390_reset_vcpu() to get rid of ifdefs
> s390x/kvm: synchronize the cpu state after SIGP (INITIAL) CPU RESET
>
> Jens Freimann (1):
> linux-headers: update to 3.17-rc7
>
> Thomas Huth (1):
> s390x/migration: migrate CPU state
>
> hw/s390x/ipl.c | 2 +-
> hw/s390x/s390-virtio.c | 32 -------
> hw/s390x/virtio-ccw.c | 2 +-
> linux-headers/asm-mips/kvm_para.h | 6 +-
> linux-headers/asm-powerpc/kvm.h | 2 +
> linux-headers/asm-x86/kvm.h | 3 +
> linux-headers/linux/kvm.h | 13 ++-
> linux-headers/linux/kvm_para.h | 3 +
> linux-headers/linux/vfio.h | 34 ++++++++
> linux-headers/linux/vhost.h | 2 +-
> target-s390x/cpu.c | 168 +++++++++++++++++++++++++++++++------
> target-s390x/cpu.h | 41 +++++++--
> target-s390x/helper.c | 19 ++---
> target-s390x/kvm.c | 58 +++++++++++--
> trace-events | 6 ++
> 15 files changed, 299 insertions(+), 92 deletions(-)
>
prev parent reply other threads:[~2014-10-09 11:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 10:58 [Qemu-devel] [PATCH 0/8] pending s390x patches for 2.2 Cornelia Huck
2014-10-07 10:58 ` [Qemu-devel] [PATCH 1/8] linux-headers: update to 3.17-rc7 Cornelia Huck
2014-10-07 10:58 ` [Qemu-devel] [PATCH 2/8] s390x/kvm: introduce proper states for s390 cpus Cornelia Huck
2014-10-07 10:58 ` [Qemu-devel] [PATCH 3/8] s390x/kvm: proper use of the cpu states OPERATING and STOPPED Cornelia Huck
2014-10-07 10:58 ` [Qemu-devel] [PATCH 4/8] s390x/kvm: propagate s390 cpu state to kvm Cornelia Huck
2014-10-07 10:58 ` [Qemu-devel] [PATCH 5/8] s390x/kvm: reuse kvm_s390_reset_vcpu() to get rid of ifdefs Cornelia Huck
2014-10-07 10:58 ` [Qemu-devel] [PATCH 6/8] s390x/kvm: synchronize the cpu state after SIGP (INITIAL) CPU RESET Cornelia Huck
2014-10-07 10:58 ` [Qemu-devel] [PATCH 7/8] s390x/migration: migrate CPU state Cornelia Huck
2014-10-07 10:58 ` [Qemu-devel] [PATCH 8/8] s390x/virtio-ccw: fix vhost-scsi intialization Cornelia Huck
2014-10-09 11:18 ` 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=54366F1E.2080706@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=agraf@suse.de \
--cc=cornelia.huck@de.ibm.com \
--cc=jfrei@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).