From: Paolo Bonzini <pbonzini@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Alexander Graf <agraf@suse.de>, KVM <kvm@vger.kernel.org>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Jens Freimann <jfrei@linux.vnet.ibm.com>,
linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: [GIT PULL 00/16] KVM: s390: Fixes and features for kvm/next (4.3)
Date: Wed, 29 Jul 2015 12:56:05 +0200 [thread overview]
Message-ID: <55B8B145.8040008@redhat.com> (raw)
In-Reply-To: <1438160766-108179-1-git-send-email-borntraeger@de.ibm.com>
On 29/07/2015 11:05, Christian Borntraeger wrote:
> Paolo,
>
> this time only some small changes for s390, mostly serviceability
> changes and small fixes/optimizations.
>
> Christian
>
> The following changes since commit 5492830370171b6a4ede8a3bfba687a8d0f25fa5:
>
> KVM: svm: handle KVM_X86_QUIRK_CD_NW_CLEARED in svm_get_mt_mask (2015-07-23 08:30:27 +0200)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/kvm-s390-next-20150728
>
> for you to fetch changes up to c92ea7b9f7d256cabf7ee08a7627a5227e356dec:
>
> KVM: s390: log capability enablement and vm attribute changes (2015-07-29 11:02:36 +0200)
>
> ----------------------------------------------------------------
> KVM: s390: Fixes and features for kvm/next (4.3)
>
> 1. Rework logging infrastructure (s390dbf) to integrate feedback learned
> when debugging performance and test issues
> 2. Some cleanups and simplifications for CMMA handling
> 3. Fix gdb debugging and single stepping on some instructions
> 4. Error handling for storage key setup
>
> ----------------------------------------------------------------
> Christian Borntraeger (10):
> KVM: s390: add kvm stat counter for all diagnoses
> KVM: s390: Improve vcpu event debugging for diagnoses
> KVM: s390: VCPU_EVENT cleanup for prefix changes
> KVM: s390: add more debug data for the pfault diagnoses
> KVM: s390: Fixup interrupt vcpu event messages and levels
> KVM: s390: remove outdated documentation
> KVM: s390: improve debug feature usage
> KVM: s390: adapt debug entries for instruction handling
> KVM: s390: Provide global debug log
> KVM: s390: log capability enablement and vm attribute changes
>
> David Hildenbrand (3):
> KVM: s390: filter space-switch events when PER is enforced
> KVM: s390: remove "from (user|kernel)" from irq injection messages
> KVM: s390: more irq names for trace events
>
> Dominik Dingel (3):
> KVM: s390: propagate error from enable storage key
> KVM: s390: clean up cmma_enable check
> KVM: s390: only reset CMMA state if it was enabled before
>
> Documentation/s390/00-INDEX | 2 -
> Documentation/s390/kvm.txt | 125 ---------------------------------------
> arch/s390/include/asm/kvm_host.h | 4 +-
> arch/s390/kvm/diag.c | 13 +++-
> arch/s390/kvm/guestdbg.c | 35 +++++++++++
> arch/s390/kvm/interrupt.c | 88 +++++++++++++--------------
> arch/s390/kvm/kvm-s390.c | 73 +++++++++++++++++------
> arch/s390/kvm/kvm-s390.h | 11 +++-
> arch/s390/kvm/priv.c | 26 ++++----
> arch/s390/kvm/sigp.c | 13 ++--
> arch/s390/kvm/trace-s390.h | 33 ++++++-----
> include/uapi/linux/kvm.h | 1 +
> 12 files changed, 194 insertions(+), 230 deletions(-)
> delete mode 100644 Documentation/s390/kvm.txt
>
Pulled, thanks.
Paolo
prev parent reply other threads:[~2015-07-29 10:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 9:05 [GIT PULL 00/16] KVM: s390: Fixes and features for kvm/next (4.3) Christian Borntraeger
2015-07-29 9:05 ` [GIT PULL 01/16] KVM: s390: propagate error from enable storage key Christian Borntraeger
2015-07-29 9:05 ` [GIT PULL 02/16] KVM: s390: filter space-switch events when PER is enforced Christian Borntraeger
2015-07-29 9:05 ` [GIT PULL 03/16] KVM: s390: clean up cmma_enable check Christian Borntraeger
2015-07-29 9:05 ` [GIT PULL 04/16] KVM: s390: only reset CMMA state if it was enabled before Christian Borntraeger
2015-07-29 9:05 ` [GIT PULL 05/16] KVM: s390: add kvm stat counter for all diagnoses Christian Borntraeger
2015-07-29 9:05 ` [GIT PULL 06/16] KVM: s390: Improve vcpu event debugging for diagnoses Christian Borntraeger
2015-07-29 9:05 ` [GIT PULL 07/16] KVM: s390: VCPU_EVENT cleanup for prefix changes Christian Borntraeger
2015-07-29 9:05 ` [GIT PULL 08/16] KVM: s390: remove "from (user|kernel)" from irq injection messages Christian Borntraeger
2015-07-29 9:05 ` [GIT PULL 09/16] KVM: s390: add more debug data for the pfault diagnoses Christian Borntraeger
2015-07-29 9:06 ` [GIT PULL 10/16] KVM: s390: Fixup interrupt vcpu event messages and levels Christian Borntraeger
2015-07-29 9:06 ` [GIT PULL 11/16] KVM: s390: more irq names for trace events Christian Borntraeger
2015-07-29 9:06 ` [GIT PULL 12/16] KVM: s390: remove outdated documentation Christian Borntraeger
2015-07-29 9:06 ` [GIT PULL 13/16] KVM: s390: improve debug feature usage Christian Borntraeger
2015-07-29 9:06 ` [GIT PULL 14/16] KVM: s390: adapt debug entries for instruction handling Christian Borntraeger
2015-07-29 9:06 ` [GIT PULL 15/16] KVM: s390: Provide global debug log Christian Borntraeger
2015-07-29 9:06 ` [GIT PULL 16/16] KVM: s390: log capability enablement and vm attribute changes Christian Borntraeger
2015-07-29 10:56 ` Paolo Bonzini [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=55B8B145.8040008@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.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).