From: Marc Zyngier <maz@kernel.org>
To: oupton@kernel.org, kvmarm@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
Vincent Donnefort <vdonnefort@google.com>
Cc: joey.gouly@arm.com, seiden@linux.ibm.com, suzuki.poulose@arm.com,
yuzenghui@huawei.com, catalin.marinas@arm.com, will@kernel.org,
kernel-team@android.com, fuad.tabba@linux.dev,
qperret@google.com
Subject: Re: [PATCH v1 0/2] KVM: arm64: Fixes for hyp_trace
Date: Sat, 10 Oct 2026 10:48:27 +0100 [thread overview]
Message-ID: <179162570115.845708.14917673397009490198.b4-ty@b4> (raw)
In-Reply-To: <20261008104212.3134550-1-vdonnefort@google.com>
On Thu, 08 Oct 2026 11:42:10 +0100, Vincent Donnefort wrote:
> Here's a couple of fixes for hyp_trace:
>
> The first one fixes a potential 64 bits overflow in the hypervisor trace
> clock.
>
> The second may prevent tracing loading for certain buffer_size_kb
> configuration. This one depends on the allocator, so I have based the
> series on kvmarm/next.
>
> [...]
Applied to next, thanks!
[1/2] KVM: arm64: Prevent 64-bit overflow when computing hyp clock rate
commit: 6164ce3491bcc3a27a2e2e9260a286eb2df2301e
[2/2] KVM: arm64: Fix bpages backing allocation size in hyp_trace
commit: aac4560e1287c36196fd2d78bf04d0c1c2559e3e
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2026-10-10 9:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 10:42 [PATCH v1 0/2] KVM: arm64: Fixes for hyp_trace Vincent Donnefort
2026-10-08 10:42 ` [PATCH v1 1/2] KVM: arm64: Prevent 64-bit overflow when computing hyp clock rate Vincent Donnefort
2026-10-08 19:12 ` Fuad Tabba
2026-10-08 10:42 ` [PATCH v1 2/2] KVM: arm64: Fix bpages backing allocation size in hyp_trace Vincent Donnefort
2026-10-08 19:13 ` Fuad Tabba
2026-10-09 8:39 ` Vincent Donnefort
2026-10-10 9:48 ` Marc Zyngier [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=179162570115.845708.14917673397009490198.b4-ty@b4 \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kernel-team@android.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oupton@kernel.org \
--cc=qperret@google.com \
--cc=seiden@linux.ibm.com \
--cc=suzuki.poulose@arm.com \
--cc=vdonnefort@google.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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