From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: KVM <kvm@vger.kernel.org>,
Janosch Frank <frankja@linux.vnet.ibm.com>,
David Hildenbrand <david@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
linux-s390 <linux-s390@vger.kernel.org>,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: [GIT PULL 0/1] KVM: s390: Fix for 5.6
Date: Thu, 12 Mar 2020 15:27:49 +0100 [thread overview]
Message-ID: <20200312142750.3603-1-borntraeger@de.ibm.com> (raw)
Paolo,
one fix for the reset that was detected by some improved selftests:
The following changes since commit d718fdc3e752ba51ddb2b5554d3db98a09355cc2:
KVM: x86: remove stale comment from struct x86_emulate_ctxt (2020-03-03 17:38:22 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/kvm-s390-master-5.6-1
for you to fetch changes up to e93fc7b4544a5475cfdbc22f87e89f9829bf801c:
KVM: s390: Also reset registers in sync regs for initial cpu reset (2020-03-11 08:25:26 +0100)
----------------------------------------------------------------
KVM: s390: Fully do the CPU resets as intended
With 7de3f1423ff9 ("KVM: s390: Add new reset vcpu API") we clarified
the meaning of the reset ioctl to fully reset the CPU and not only the
parts that can not be handled by userspace. Turns out that we missed
some parts.
----------------------------------------------------------------
Christian Borntraeger (1):
KVM: s390: Also reset registers in sync regs for initial cpu reset
arch/s390/kvm/kvm-s390.c | 18 +++++++++++++++++-
1 file changed, 17 insertions(+), 1 deletion(-)
next reply other threads:[~2020-03-12 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 14:27 Christian Borntraeger [this message]
2020-03-12 14:27 ` [GIT PULL 1/1] KVM: s390: Also reset registers in sync regs for initial cpu reset Christian Borntraeger
2020-03-14 10:59 ` [GIT PULL 0/1] KVM: s390: Fix for 5.6 Paolo Bonzini
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=20200312142750.3603-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 \
/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.