From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: KVM <kvm@vger.kernel.org>, Cornelia Huck <cohuck@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
linux-s390 <linux-s390@vger.kernel.org>,
Janosch Frank <frankja@linux.vnet.ibm.com>,
David Hildenbrand <david@redhat.com>,
Thomas Huth <thuth@redhat.com>
Subject: [PULL 00/12] s390x qemu updates 20190930
Date: Fri, 31 Jan 2020 16:01:55 +0100 [thread overview]
Message-ID: <20200131150207.73127-1-borntraeger@de.ibm.com> (raw)
Peter,
The following changes since commit 786d36ad416c6c199b18b78cc31eddfb784fe15d:
Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20190927' into staging (2019-09-30 11:02:22 +0100)
are available in the Git repository at:
git://github.com/borntraeger/qemu.git tags/s390x-20190930
for you to fetch changes up to c5b9ce518c0551d0198bcddadc82e03de9ac8de9:
s390/kvm: split kvm mem slots at 4TB (2019-09-30 13:51:50 +0200)
----------------------------------------------------------------
- do not abuse memory_region_allocate_system_memory and split the memory
according to KVM memslots in KVM code instead (Paolo, Igor)
- change splitting to split at 4TB (Christian)
- do not claim s390 (31bit) support in configure (Thomas)
- sclp error checking (Janosch, Claudio)
- new s390 pci maintainer (Matt, Collin)
- fix s390 pci (again) (Matt)
----------------------------------------------------------------
Christian Borntraeger (1):
s390/kvm: split kvm mem slots at 4TB
Claudio Imbrenda (1):
s390x: sclp: Report insufficient SCCB length
Igor Mammedov (2):
kvm: split too big memory section on several memslots
s390: do not call memory_region_allocate_system_memory() multiple times
Janosch Frank (3):
s390x: sclp: refactor invalid command check
s390x: sclp: boundary check
s390x: sclp: fix error handling for oversize control blocks
Matthew Rosato (2):
MAINTAINERS: Update S390 PCI Maintainer
s390: PCI: fix IOMMU region init
Paolo Bonzini (2):
kvm: extract kvm_log_clear_one_slot
kvm: clear dirty bitmaps from all overlapping memslots
Thomas Huth (1):
configure: Remove s390 (31-bit mode) from the list of supported CPUs
MAINTAINERS | 2 +-
accel/kvm/kvm-all.c | 237 ++++++++++++++++++++++++++++-----------------
configure | 2 +-
hw/s390x/event-facility.c | 3 -
hw/s390x/s390-pci-bus.c | 7 +-
hw/s390x/s390-virtio-ccw.c | 30 +-----
hw/s390x/sclp.c | 37 ++++++-
include/sysemu/kvm_int.h | 1 +
target/s390x/kvm.c | 10 ++
9 files changed, 202 insertions(+), 127 deletions(-)
next reply other threads:[~2020-01-31 15:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 15:01 Christian Borntraeger [this message]
2020-01-31 15:01 ` [PULL 01/12] MAINTAINERS: Update S390 PCI Maintainer Christian Borntraeger
2020-01-31 15:01 ` [PULL 02/12] s390: PCI: fix IOMMU region init Christian Borntraeger
2020-01-31 15:01 ` [PULL 03/12] s390x: sclp: refactor invalid command check Christian Borntraeger
2020-01-31 15:01 ` [PULL 04/12] s390x: sclp: boundary check Christian Borntraeger
2020-01-31 15:02 ` [PULL 05/12] s390x: sclp: fix error handling for oversize control blocks Christian Borntraeger
2020-01-31 15:02 ` [PULL 06/12] s390x: sclp: Report insufficient SCCB length Christian Borntraeger
2020-01-31 15:02 ` [PULL 07/12] configure: Remove s390 (31-bit mode) from the list of supported CPUs Christian Borntraeger
2020-01-31 15:02 ` [PULL 08/12] kvm: extract kvm_log_clear_one_slot Christian Borntraeger
2020-01-31 15:02 ` [PULL 09/12] kvm: clear dirty bitmaps from all overlapping memslots Christian Borntraeger
2020-01-31 15:02 ` [PULL 10/12] kvm: split too big memory section on several memslots Christian Borntraeger
2020-01-31 15:02 ` [PULL 11/12] s390: do not call memory_region_allocate_system_memory() multiple times Christian Borntraeger
2020-01-31 15:02 ` [PULL 12/12] s390/kvm: split kvm mem slots at 4TB Christian Borntraeger
2020-01-31 15:03 ` [PULL 00/12] s390x qemu updates 20190930 Christian Borntraeger
-- strict thread matches above, loose matches on Subject: below --
2019-09-30 13:19 Christian Borntraeger
2019-10-01 10:40 ` Peter Maydell
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=20200131150207.73127-1-borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=thuth@redhat.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).