From: Cornelia Huck <cohuck@redhat.com>
To: Pierre Morel <pmorel@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
borntraeger@de.ibm.com, frankja@linux.ibm.com, david@redhat.com,
thuth@redhat.com
Subject: Re: [PATCH v4 1/1] KVM: s390: diag9c (directed yield) forwarding
Date: Tue, 23 Feb 2021 12:14:44 +0100 [thread overview]
Message-ID: <20210223121444.28543783.cohuck@redhat.com> (raw)
In-Reply-To: <1613997661-22525-2-git-send-email-pmorel@linux.ibm.com>
On Mon, 22 Feb 2021 13:41:01 +0100
Pierre Morel <pmorel@linux.ibm.com> wrote:
> When we intercept a DIAG_9C from the guest we verify that the
> target real CPU associated with the virtual CPU designated by
> the guest is running and if not we forward the DIAG_9C to the
> target real CPU.
>
> To avoid a diag9c storm we allow a maximal rate of diag9c forwarding.
>
> The rate is calculated as a count per second defined as a new
> parameter of the s390 kvm module: diag9c_forwarding_hz .
>
> The default value of 0 is to not forward diag9c.
>
> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
> ---
> 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(-)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2021-02-23 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 12:41 [PATCH v4 0/1] KVM: s390: diag9c (directed yield) forwarding Pierre Morel
2021-02-22 12:41 ` [PATCH v4 1/1] " Pierre Morel
2021-02-23 11:14 ` Cornelia Huck [this message]
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=20210223121444.28543783.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pmorel@linux.ibm.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