From: Michael Ellerman <mpe@ellerman.id.au>
To: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>, Nicholas Piggin <npiggin@gmail.com>,
Vaibhav Jain <vaibhav@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org,
kvm-ppc@vger.kernel.org
Cc: Jordan Niethe <jniethe5@gmail.com>,
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
mikey@neuling.org, paulus@ozlabs.org, sbhat@linux.ibm.com,
gautam@linux.ibm.com, kconsul@linux.vnet.ibm.com,
amachhiw@linux.vnet.ibm.com, David.Laight@ACULAB.COM,
Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [PATCH] KVM: PPC: Book3S HV nestedv2: Cancel pending HDEC exception
Date: Fri, 05 Apr 2024 14:20:21 +1100 [thread overview]
Message-ID: <87sf007ax6.fsf@mail.lhotse> (raw)
In-Reply-To: <a4f022e8-1f84-4bbb-b00d-00f1eba1f877@leemhuis.info>
"Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info> writes:
> Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
> for once, to make this easily accessible to everyone.
>
> Was this regression ever resolved? Doesn't look like it, but maybe I
> just missed something.
I'm not sure how it ended up on the regression list. IMHO it's not
really a regression. It was an attempt at a performance optimisation,
which is no longer needed due to changes in (unreleased) firmware.
I haven't merged it because Nick's reply contained several questions for
Vaibhav, so I'm expecting either a reply to those or a new version of
the patch.
cheers
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> If I did something stupid, please tell me, as explained on that page.
>
> #regzbot poke
>
> On 20.03.24 14:43, Nicholas Piggin wrote:
>> On Wed Mar 13, 2024 at 5:26 PM AEST, Vaibhav Jain wrote:
>>> This reverts commit 180c6b072bf360b686e53d893d8dcf7dbbaec6bb ("KVM: PPC:
>>> Book3S HV nestedv2: Do not cancel pending decrementer exception") which
>>> prevented cancelling a pending HDEC exception for nestedv2 KVM guests. It
>>> was done to avoid overhead of a H_GUEST_GET_STATE hcall to read the 'HDEC
>>> expiry TB' register which was higher compared to handling extra decrementer
>>> exceptions.
>>>
>>> This overhead of reading 'HDEC expiry TB' register has been mitigated
>>> recently by the L0 hypervisor(PowerVM) by putting the value of this
>>> register in L2 guest-state output buffer on trap to L1. From there the
>>> value of this register is cached, made available in kvmhv_run_single_vcpu()
>>> to compare it against host(L1) timebase and cancel the pending hypervisor
>>> decrementer exception if needed.
>>
>> Ah, I figured out the problem here. Guest entry never clears the
>> queued dec, because it's level triggered on the DEC MSB so it
>> doesn't go away when it's delivered. So upstream code is indeed
>> buggy and I think I take the blame for suggesting this nestedv2
>> workaround.
>>
>> I actually don't think that is necessary though, we could treat it
>> like other interrupts. I think that would solve the problem without
>> having to test dec here.
>>
>> I am wondering though, what workload slows down that this patch
>> was needed in the first place. We'd only get here after a cede
>> returns, then we'd dequeue the dec and stop having to GET_STATE
>> it here.
>>
>> Thanks,
>> Nick
>>
>>>
>>> Fixes: 180c6b072bf3 ("KVM: PPC: Book3S HV nestedv2: Do not cancel pending decrementer exception")
>>> Signed-off-by: Vaibhav Jain <vaibhav@linux.ibm.com>
>>> ---
>>> arch/powerpc/kvm/book3s_hv.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/arch/powerpc/kvm/book3s_hv.c b/arch/powerpc/kvm/book3s_hv.c
>>> index 0b921704da45..e47b954ce266 100644
>>> --- a/arch/powerpc/kvm/book3s_hv.c
>>> +++ b/arch/powerpc/kvm/book3s_hv.c
>>> @@ -4856,7 +4856,7 @@ int kvmhv_run_single_vcpu(struct kvm_vcpu *vcpu, u64 time_limit,
>>> * entering a nested guest in which case the decrementer is now owned
>>> * by L2 and the L1 decrementer is provided in hdec_expires
>>> */
>>> - if (!kvmhv_is_nestedv2() && kvmppc_core_pending_dec(vcpu) &&
>>> + if (kvmppc_core_pending_dec(vcpu) &&
>>> ((tb < kvmppc_dec_expires_host_tb(vcpu)) ||
>>> (trap == BOOK3S_INTERRUPT_SYSCALL &&
>>> kvmppc_get_gpr(vcpu, 3) == H_ENTER_NESTED)))
>>
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>, Nicholas Piggin <npiggin@gmail.com>,
Vaibhav Jain <vaibhav@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org,
kvm-ppc@vger.kernel.org
Cc: mikey@neuling.org,
Linux kernel regressions list <regressions@lists.linux.dev>,
sbhat@linux.ibm.com, amachhiw@linux.vnet.ibm.com,
Jordan Niethe <jniethe5@gmail.com>,
gautam@linux.ibm.com, David.Laight@ACULAB.COM,
kconsul@linux.vnet.ibm.com,
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
Subject: Re: [PATCH] KVM: PPC: Book3S HV nestedv2: Cancel pending HDEC exception
Date: Fri, 05 Apr 2024 14:20:21 +1100 [thread overview]
Message-ID: <87sf007ax6.fsf@mail.lhotse> (raw)
In-Reply-To: <a4f022e8-1f84-4bbb-b00d-00f1eba1f877@leemhuis.info>
"Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info> writes:
> Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
> for once, to make this easily accessible to everyone.
>
> Was this regression ever resolved? Doesn't look like it, but maybe I
> just missed something.
I'm not sure how it ended up on the regression list. IMHO it's not
really a regression. It was an attempt at a performance optimisation,
which is no longer needed due to changes in (unreleased) firmware.
I haven't merged it because Nick's reply contained several questions for
Vaibhav, so I'm expecting either a reply to those or a new version of
the patch.
cheers
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> If I did something stupid, please tell me, as explained on that page.
>
> #regzbot poke
>
> On 20.03.24 14:43, Nicholas Piggin wrote:
>> On Wed Mar 13, 2024 at 5:26 PM AEST, Vaibhav Jain wrote:
>>> This reverts commit 180c6b072bf360b686e53d893d8dcf7dbbaec6bb ("KVM: PPC:
>>> Book3S HV nestedv2: Do not cancel pending decrementer exception") which
>>> prevented cancelling a pending HDEC exception for nestedv2 KVM guests. It
>>> was done to avoid overhead of a H_GUEST_GET_STATE hcall to read the 'HDEC
>>> expiry TB' register which was higher compared to handling extra decrementer
>>> exceptions.
>>>
>>> This overhead of reading 'HDEC expiry TB' register has been mitigated
>>> recently by the L0 hypervisor(PowerVM) by putting the value of this
>>> register in L2 guest-state output buffer on trap to L1. From there the
>>> value of this register is cached, made available in kvmhv_run_single_vcpu()
>>> to compare it against host(L1) timebase and cancel the pending hypervisor
>>> decrementer exception if needed.
>>
>> Ah, I figured out the problem here. Guest entry never clears the
>> queued dec, because it's level triggered on the DEC MSB so it
>> doesn't go away when it's delivered. So upstream code is indeed
>> buggy and I think I take the blame for suggesting this nestedv2
>> workaround.
>>
>> I actually don't think that is necessary though, we could treat it
>> like other interrupts. I think that would solve the problem without
>> having to test dec here.
>>
>> I am wondering though, what workload slows down that this patch
>> was needed in the first place. We'd only get here after a cede
>> returns, then we'd dequeue the dec and stop having to GET_STATE
>> it here.
>>
>> Thanks,
>> Nick
>>
>>>
>>> Fixes: 180c6b072bf3 ("KVM: PPC: Book3S HV nestedv2: Do not cancel pending decrementer exception")
>>> Signed-off-by: Vaibhav Jain <vaibhav@linux.ibm.com>
>>> ---
>>> arch/powerpc/kvm/book3s_hv.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/arch/powerpc/kvm/book3s_hv.c b/arch/powerpc/kvm/book3s_hv.c
>>> index 0b921704da45..e47b954ce266 100644
>>> --- a/arch/powerpc/kvm/book3s_hv.c
>>> +++ b/arch/powerpc/kvm/book3s_hv.c
>>> @@ -4856,7 +4856,7 @@ int kvmhv_run_single_vcpu(struct kvm_vcpu *vcpu, u64 time_limit,
>>> * entering a nested guest in which case the decrementer is now owned
>>> * by L2 and the L1 decrementer is provided in hdec_expires
>>> */
>>> - if (!kvmhv_is_nestedv2() && kvmppc_core_pending_dec(vcpu) &&
>>> + if (kvmppc_core_pending_dec(vcpu) &&
>>> ((tb < kvmppc_dec_expires_host_tb(vcpu)) ||
>>> (trap == BOOK3S_INTERRUPT_SYSCALL &&
>>> kvmppc_get_gpr(vcpu, 3) == H_ENTER_NESTED)))
>>
next prev parent reply other threads:[~2024-04-05 3:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 7:26 [PATCH] KVM: PPC: Book3S HV nestedv2: Cancel pending HDEC exception Vaibhav Jain
2024-03-13 7:26 ` Vaibhav Jain
2024-03-20 13:43 ` Nicholas Piggin
2024-03-20 13:43 ` Nicholas Piggin
2024-04-04 8:35 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-04 8:35 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-05 3:20 ` Michael Ellerman [this message]
2024-04-05 3:20 ` Michael Ellerman
2024-04-05 5:54 ` Thorsten Leemhuis
2024-04-05 5:54 ` Thorsten Leemhuis
2024-04-08 5:20 ` Michael Ellerman
2024-04-08 5:20 ` Michael Ellerman
2024-04-10 4:28 ` Nicholas Piggin
2024-04-10 4:28 ` Nicholas Piggin
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=87sf007ax6.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=David.Laight@ACULAB.COM \
--cc=amachhiw@linux.vnet.ibm.com \
--cc=gautam@linux.ibm.com \
--cc=jniethe5@gmail.com \
--cc=kconsul@linux.vnet.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=npiggin@gmail.com \
--cc=paulus@ozlabs.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=sbhat@linux.ibm.com \
--cc=svaidy@linux.vnet.ibm.com \
--cc=vaibhav@linux.ibm.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.