public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat•com>
To: Michael Kelley <mikelley@microsoft•com>
Cc: "mark.rutland@arm•com" <mark.rutland@arm•com>,
	"linux-hyperv@vger•kernel.org" <linux-hyperv@vger•kernel.org>,
	"marc.zyngier@arm•com" <marc.zyngier@arm•com>,
	"catalin.marinas@arm•com" <catalin.marinas@arm•com>,
	"jasowang@redhat•com" <jasowang@redhat•com>,
	"will.deacon@arm•com" <will.deacon@arm•com>,
	"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
	"marcelo.cerri@canonical•com" <marcelo.cerri@canonical•com>,
	"olaf@aepfle•de" <olaf@aepfle•de>,
	"gregkh@linuxfoundation•org" <gregkh@linuxfoundation•org>,
	"apw@canonical•com" <apw@canonical•com>,
	Sunil Muthuswamy <sunilmut@microsoft•com>,
	KY Srinivasan <kys@microsoft•com>,
	"linux-arm-kernel@lists•infradead.org"
	<linux-arm-kernel@lists•infradead.org>
Subject: Re: [PATCH v2 0/2] Drivers: hv: Move Hyper-V clock/timer code to separate clocksource driver
Date: Thu, 21 Mar 2019 15:24:46 +0100	[thread overview]
Message-ID: <874l7we24x.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <1552849512-10063-1-git-send-email-mikelley@microsoft.com>

Michael Kelley <mikelley@microsoft•com> writes:

> This patch series moves Hyper-V clock/timer code to a separate Hyper-V
> clocksource driver. Previously, Hyper-V clock/timer code and data
> structures were mixed in with other Hyper-V code in the ISA independent
> drivers/hv code as well as in arch dependent code. The new Hyper-V
> clocksource driver is ISA independent, with a just few dependencies on
> arch specific functions. The patch series does not change any behavior
> or functionality -- it only reorganizes the existing code and fixes up
> the linkages. A few places outside of Hyper-V code are fixed up to use
> the new #include file structure.
>
> This restructuring is in response to Marc Zyngier's review comments
> on supporting Hyper-V running on ARM64, and is a good idea in general.
> It increases the amount of code shared between the x86 and ARM64
> architectures, and reduces the size of the new code for supporting
> Hyper-V on ARM64. A new version of the Hyper-V on ARM64 patches will
> follow once this clocksource restructuring is accepted.
>
> The code is currently diff'ed against Linux 5.0.  I'll rebase
> to linux-next once 5.1-rc1 is available.
>
> Changes in v2:
> * Revised commit short descriptions so the distinction between
> the two patches is clearer [GregKH]
> * Renamed new clocksource driver files and functions to use
> existing "timer" and "stimer" names instead of introducing
> "syntimer". [Vitaly Kuznetsov]
> * Introduced CONFIG_HYPER_TIMER to fix build problem when
> CONFIG_HYPERV=m [Vitaly Kuznetsov]

Actually, it is "CONFIG_HYPERV_TIMER" but the typo appears only in this
blurb :-)

> * Added "Suggested-by: Marc Zyngier"
>
> Michael Kelley (2):
>   Drivers: hv: Create Hyper-V clocksource driver from existing
>     clockevents code
>   Drivers: hv: Move Hyper-V clocksource code to new clocksource driver

Thanks for fixing v1 issues!

Reviewed-by: Vitaly Kuznetsov <vkuznets@redhat•com>

>
>  MAINTAINERS                          |   2 +
>  arch/x86/entry/vdso/vclock_gettime.c |   1 +
>  arch/x86/entry/vdso/vma.c            |   2 +-
>  arch/x86/hyperv/hv_init.c            |  91 +---------
>  arch/x86/include/asm/hyperv-tlfs.h   |   6 +
>  arch/x86/include/asm/mshyperv.h      |  80 ++-------
>  arch/x86/kernel/cpu/mshyperv.c       |   2 +
>  arch/x86/kvm/x86.c                   |   1 +
>  drivers/clocksource/Makefile         |   1 +
>  drivers/clocksource/hyperv_timer.c   | 328 +++++++++++++++++++++++++++++++++++
>  drivers/hv/Kconfig                   |   3 +
>  drivers/hv/hv.c                      | 154 ----------------
>  drivers/hv/hyperv_vmbus.h            |   3 -
>  drivers/hv/vmbus_drv.c               |  39 +++--
>  include/clocksource/hyperv_timer.h   | 104 +++++++++++
>  15 files changed, 485 insertions(+), 332 deletions(-)
>  create mode 100644 drivers/clocksource/hyperv_timer.c
>  create mode 100644 include/clocksource/hyperv_timer.h

-- 
Vitaly

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2019-03-21 14:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-17 19:06 [PATCH v2 0/2] Drivers: hv: Move Hyper-V clock/timer code to separate clocksource driver Michael Kelley
2019-03-17 19:06 ` [PATCH v2 1/2] Drivers: hv: Create Hyper-V clocksource driver from existing clockevents code Michael Kelley
2019-03-17 19:06 ` [PATCH v2 2/2] Drivers: hv: Move Hyper-V clocksource code to new clocksource driver Michael Kelley
2019-03-21 14:24 ` Vitaly Kuznetsov [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=874l7we24x.fsf@vitty.brq.redhat.com \
    --to=vkuznets@redhat$(echo .)com \
    --cc=apw@canonical$(echo .)com \
    --cc=catalin.marinas@arm$(echo .)com \
    --cc=gregkh@linuxfoundation$(echo .)org \
    --cc=jasowang@redhat$(echo .)com \
    --cc=kys@microsoft$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-hyperv@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=marc.zyngier@arm$(echo .)com \
    --cc=marcelo.cerri@canonical$(echo .)com \
    --cc=mark.rutland@arm$(echo .)com \
    --cc=mikelley@microsoft$(echo .)com \
    --cc=olaf@aepfle$(echo .)de \
    --cc=sunilmut@microsoft$(echo .)com \
    --cc=will.deacon@arm$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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