From: Andrew Jones <ajones@ventanamicro.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Colton Lewis <coltonlewis@google.com>,
qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-arm@nongnu.org, kvm@vger.kernel.org,
Andrew Jones <andrew.jones@linux.dev>,
qemu-trivial@nongnu.org, qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PATCH] arm64: Restore trapless ptimer access
Date: Fri, 8 Sep 2023 10:42:01 +0200 [thread overview]
Message-ID: <20230908-c42425ed51b75d247052cfde@orel> (raw)
In-Reply-To: <7d3615d0-d501-a28c-eebc-b3f7a599fc23@tls.msk.ru>
On Thu, Sep 07, 2023 at 10:31:20PM +0300, Michael Tokarev wrote:
> 31.08.2023 22:00, Colton Lewis wrote:
> > Due to recent KVM changes, QEMU is setting a ptimer offset resulting
> > in unintended trap and emulate access and a consequent performance
> > hit. Filter out the PTIMER_CNT register to restore trapless ptimer
> > access.
> >
> > Quoting Andrew Jones:
> >
> > Simply reading the CNT register and writing back the same value is
> > enough to set an offset, since the timer will have certainly moved
> > past whatever value was read by the time it's written. QEMU
> > frequently saves and restores all registers in the get-reg-list array,
> > unless they've been explicitly filtered out (with Linux commit
> > 680232a94c12, KVM_REG_ARM_PTIMER_CNT is now in the array). So, to
> > restore trapless ptimer accesses, we need a QEMU patch to filter out
> > the register.
> >
> > See
> > https://lore.kernel.org/kvmarm/gsntttsonus5.fsf@coltonlewis-kvm.c.googlers.com/T/#m0770023762a821db2a3f0dd0a7dc6aa54e0d0da9
> > for additional context.
> >
> > Signed-off-by: Andrew Jones <andrew.jones@linux.dev>
> > ---
> > target/arm/kvm64.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/target/arm/kvm64.c b/target/arm/kvm64.c
> > index 4d904a1d11..2dd46e0a99 100644
> > --- a/target/arm/kvm64.c
> > +++ b/target/arm/kvm64.c
> > @@ -672,6 +672,7 @@ typedef struct CPRegStateLevel {
> > */
> > static const CPRegStateLevel non_runtime_cpregs[] = {
> > { KVM_REG_ARM_TIMER_CNT, KVM_PUT_FULL_STATE },
> > + { KVM_REG_ARM_PTIMER_CNT, KVM_PUT_FULL_STATE },
> > };
> > int kvm_arm_cpreg_level(uint64_t regidx)
>
> While this patch itself is one-liner and trivial and all, I'd rather
> not apply this to the trivial-patches tree, - it requires a little
> bit more than trivial expertise in this area.
>
> So basically, ping for qemu-arm@ ? :)
>
I agree that qemu-trivial should not have been CC'ed for this patch.
Thanks,
drew
next prev parent reply other threads:[~2023-09-08 8:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 19:00 [PATCH] arm64: Restore trapless ptimer access Colton Lewis
2023-09-01 0:36 ` Richard Henderson
2023-09-01 7:35 ` Andrew Jones
2023-09-01 19:23 ` Colton Lewis
2023-09-04 8:18 ` Claudio Fontana
2023-09-04 11:07 ` Andrew Jones
2023-09-04 12:05 ` Claudio Fontana
2023-09-07 19:31 ` Michael Tokarev
2023-09-08 8:42 ` Andrew Jones [this message]
2023-09-08 9:45 ` Peter Maydell
2023-09-08 13:00 ` Peter Maydell
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=20230908-c42425ed51b75d247052cfde@orel \
--to=ajones@ventanamicro.com \
--cc=andrew.jones@linux.dev \
--cc=coltonlewis@google.com \
--cc=kvm@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=qemu-trivial@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).