From: Pierre Morel <pmorel@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, borntraeger@de.ibm.com,
frankja@linux.ibm.com, cohuck@redhat.com, david@redhat.com,
thuth@redhat.com, pmorel@linux.ibm.com
Subject: [PATCH v4 0/1] KVM: s390: diag9c (directed yield) forwarding
Date: Mon, 22 Feb 2021 13:41:00 +0100 [thread overview]
Message-ID: <1613997661-22525-1-git-send-email-pmorel@linux.ibm.com> (raw)
This patch will forward the yield_to hypercall (diag9c) if in the host
the target CPU is also not running. As we do not yet have performance
data (and recommendations) the default is turned off, but this can
be changed during runtime.
The documentation notation for the titles is kept coherent with
the other DIAGNOSE entries using the zVM notation DIAGNOSE 'X'9C,
While in the explanation part we use the standard Linux notation
DIAGNOSE 0x9c.
Regards,
Pierre
Pierre Morel (1):
KVM: s390: diag9c (directed yield) forwarding
Documentation/virt/kvm/s390-diag.rst | 33 ++++++++++++++++++++++++++++
arch/s390/include/asm/kvm_host.h | 1 +
arch/s390/include/asm/smp.h | 1 +
arch/s390/kernel/smp.c | 1 +
arch/s390/kvm/diag.c | 31 +++++++++++++++++++++++---
arch/s390/kvm/kvm-s390.c | 6 +++++
arch/s390/kvm/kvm-s390.h | 8 +++++++
7 files changed, 78 insertions(+), 3 deletions(-)
--
2.17.1
Changelog:
From v3:
- rewording of the commit message
(Connie)
- great rewording of the documentation
(Connie)
- Keep smp_yield_cpu symbol GPL
(Connie)
- More explicit diag9c_forwarding_hz parameter description
(Connie)
From v2:
- update overrun comparison, avoid comparison on unsigned
(Pierre)
From v1:
- more precise comments
(Connie)
- Documentation
(Janosch)
next reply other threads:[~2021-02-22 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 12:41 Pierre Morel [this message]
2021-02-22 12:41 ` [PATCH v4 1/1] KVM: s390: diag9c (directed yield) forwarding Pierre Morel
2021-02-23 11:14 ` Cornelia Huck
2021-02-23 11:32 ` Pierre Morel
2021-02-23 15:12 ` Christian Borntraeger
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=1613997661-22525-1-git-send-email-pmorel@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--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