From: Pierre Morel <pmorel@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Janosch Frank <frankja@linux.vnet.ibm.com>,
KVM <kvm@vger.kernel.org>, David Hildenbrand <david@redhat.com>,
linux-s390 <linux-s390@vger.kernel.org>,
Thomas Huth <thuth@redhat.com>
Subject: Re: [PATCH 1/1] KVM: s390: diag9c forwarding
Date: Tue, 19 Jan 2021 20:51:17 +0100 [thread overview]
Message-ID: <ee6fef19-78b5-c897-0210-fedc52984369@linux.ibm.com> (raw)
In-Reply-To: <20210119175359.1a5ea5be.cohuck@redhat.com>
On 1/19/21 5:53 PM, Cornelia Huck wrote:
> On Mon, 18 Jan 2021 14:17:39 +0100
> Christian Borntraeger <borntraeger@de.ibm.com> wrote:
>
>> From: Pierre Morel <pmorel@linux.ibm.com>
>>
>> When we receive 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 is to not forward diag9c.
>>
>> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
>> ---
>> 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 ++++++++
>> 6 files changed, 45 insertions(+), 3 deletions(-)
>>
>
> (...)
>
>> @@ -167,9 +180,21 @@ static int __diag_time_slice_end_directed(struct kvm_vcpu *vcpu)
>> if (!tcpu)
>> goto no_yield;
>>
>> - /* target already running */
>> - if (READ_ONCE(tcpu->cpu) >= 0)
>> - goto no_yield;
>> + /* target VCPU already running */
>
> Maybe make this /* target guest VPCU already running */...
>
>> + if (READ_ONCE(tcpu->cpu) >= 0) {
>> + if (!diag9c_forwarding_hz || diag9c_forwarding_overrun())
>> + goto no_yield;
>> +
>> + /* target CPU already running */
>
> ...and this /* target host CPU already running */? I just read this
> several times and was confused before I spotted the difference :)
I can only agree then :) .
...
--
Pierre Morel
IBM Lab Boeblingen
prev parent reply other threads:[~2021-01-19 19:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 13:17 [PATCH 0/1] diag9c forwarding Christian Borntraeger
2021-01-18 13:17 ` [PATCH 1/1] KVM: s390: " Christian Borntraeger
2021-01-18 13:45 ` Janosch Frank
2021-01-18 13:57 ` Christian Borntraeger
2021-01-18 13:59 ` Christian Borntraeger
2021-01-18 14:56 ` Pierre Morel
2021-01-19 16:53 ` Cornelia Huck
2021-01-19 19:51 ` Pierre Morel [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=ee6fef19-78b5-c897-0210-fedc52984369@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=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=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