From: Wei Liu <wei.liu@kernel.org>
To: Michael Kelley <mikelley@microsoft.com>
Cc: sthemmin@microsoft.com, kys@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, daniel.lezcano@linaro.org,
tglx@linutronix.de, arnd@arndb.de, linux-kernel@vger.kernel.org,
linux-hyperv@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH 1/1] drivers: hv: Decouple Hyper-V clock/timer code from VMbus drivers
Date: Mon, 19 Jul 2021 09:24:15 +0000 [thread overview]
Message-ID: <20210719092415.vgx2xsk2vsppojzp@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <1626220906-22629-1-git-send-email-mikelley@microsoft.com>
On Tue, Jul 13, 2021 at 05:01:46PM -0700, Michael Kelley wrote:
> Hyper-V clock/timer code in hyperv_timer.c is mostly independent from
> other VMbus drivers, but building for ARM64 without hyperv_timer.c
> shows some remaining entanglements. A default implementation of
> hv_read_reference_counter can just read a Hyper-V synthetic register
> and be independent of hyperv_timer.c, so move this code out and into
> hv_common.c. Then it can be used by the timesync driver even if
> hyperv_timer.c isn't built on a particular architecture. If
> hyperv_timer.c *is* built, it can override with a faster implementation.
>
> Also provide stubs for stimer functions called by the VMbus driver when
> hyperv_timer.c isn't built.
>
> No functional changes.
>
> Signed-off-by: Michael Kelley <mikelley@microsoft.com>
Applied to hyperv-next. Thanks.
prev parent reply other threads:[~2021-07-19 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 0:01 [PATCH 1/1] drivers: hv: Decouple Hyper-V clock/timer code from VMbus drivers Michael Kelley
2021-07-14 9:52 ` Wei Liu
2021-07-19 9:24 ` Wei Liu [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=20210719092415.vgx2xsk2vsppojzp@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=arnd@arndb.de \
--cc=daniel.lezcano@linaro.org \
--cc=decui@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=sthemmin@microsoft.com \
--cc=tglx@linutronix.de \
/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).