From: Marc Zyngier <maz@kernel.org>
To: Eugene Huang <eugeneh@nvidia.com>
Cc: "kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>
Subject: Re: Timer delays in VM
Date: Tue, 08 Mar 2022 09:34:27 +0000 [thread overview]
Message-ID: <871qzc23fg.wl-maz@kernel.org> (raw)
In-Reply-To: <BYAPR12MB31928F0EECC9EDAEA01BA7F3D9099@BYAPR12MB3192.namprd12.prod.outlook.com>
Hi Eugene,
On Tue, 08 Mar 2022 07:50:50 +0000,
Eugene Huang <eugeneh@nvidia.com> wrote:
>
> Hi Marc,
>
> Looks like to effectively troubleshoot, we need to upgrade our guest
> kernel to the latest version 5.17. I have these questions.
>
> 1. Can you please point out the kernel source that programs the arm
> virtual timer?
drivers/clocksource/arm_arch_timer.c
> 2. is The Generic Timer section in ARM Architecture Reference Manual
> ARMv8 the correct reference that we should refer to?
Yes, section D7. You'll also need the GIC specifications (IHI0069H in
your case), because you can't really understand how KVM works without
looking at both.
> 3. From the kernel community point of view, which kernel in the
> guest is the better - the Ubuntu one or the upstream one?
Upstream. In general, distro kernels are only a nuisance when
debugging things.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
prev parent reply other threads:[~2022-03-08 9:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 18:02 Timer delays in VM Eugene Huang
2022-02-28 21:02 ` Marc Zyngier
2022-03-01 9:06 ` Andrew Jones
2022-03-01 19:03 ` Eugene Huang
2022-03-02 2:27 ` Eugene Huang
2022-03-02 7:28 ` Marc Zyngier
2022-03-03 5:49 ` Eugene Huang
2022-03-03 14:42 ` Marc Zyngier
2022-03-08 7:50 ` Eugene Huang
2022-03-08 9:34 ` 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=871qzc23fg.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=eugeneh@nvidia.com \
--cc=kvmarm@lists.cs.columbia.edu \
/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