public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu@kernel.org>
To: Nuno Das Neves <nunodasneves@linux.microsoft.com>
Cc: linux-hyperv@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
	wei.liu@kernel.org, mhklinux@outlook.com, kys@microsoft.com,
	haiyangz@microsoft.com, decui@microsoft.com,
	catalin.marinas@arm.com, will@kernel.org, tglx@linutronix.de,
	mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
	x86@kernel.org, hpa@zytor.com, arnd@arndb.de,
	jinankjain@linux.microsoft.com, muminulrussell@gmail.com,
	skinsburskii@linux.microsoft.com, mukeshrathor@microsoft.com
Subject: Re: [PATCH v3 0/2] hyperv: Move some features to common code
Date: Wed, 12 Feb 2025 04:10:04 +0000	[thread overview]
Message-ID: <Z6wfHOPNUL2KcSG8@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <1738955002-20821-1-git-send-email-nunodasneves@linux.microsoft.com>

On Fri, Feb 07, 2025 at 11:03:20AM -0800, Nuno Das Neves wrote:
> There are several bits of Hyper-V-related code that today live in
> arch/x86 but are not really specific to x86_64 and will work on arm64
> too.
> 
> Some of these will be needed in the upcoming mshv driver code (for
> Linux as root partition on Hyper-V). So this is a good time to move
> them to drivers/hv.
> 
> Signed-off-by: Nuno Das Neves <nunodasneves@linux.microsoft.com>
> ---
> Changes in v3:
> * Just use percpu input page for the hypercall [Michael Kelley]
> * Move the calls to hv_get_partition_id() back to arch code [Michael Kelley]
> * Rename struct hv_get_partition_id to hv_output_get_partition_id
>   [Michael Kelley]
> 
> Changes in v2:
> * Fix dependence on percpu output page by using a stack variable for the
>   hypercall output [Michael Kelley]
> * Remove unnecessary WARN()s [Michael Kelley]
> * Define hv_current_partition_id in hv_common.c [Michael Kelley]
> * Move entire hv_proc.c to drivers/hv [Michael Kelley]
> 
> Nuno Das Neves (2):
>   hyperv: Move hv_current_partition_id to arch-generic code
>   hyperv: Move arch/x86/hyperv/hv_proc.c to drivers/hv

Applied to hyperv-next. Thanks.

      parent reply	other threads:[~2025-02-12  4:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-07 19:03 [PATCH v3 0/2] hyperv: Move some features to common code Nuno Das Neves
2025-02-07 19:03 ` [PATCH v3 1/2] hyperv: Move hv_current_partition_id to arch-generic code Nuno Das Neves
2025-02-08 15:44   ` Michael Kelley
2025-02-07 19:03 ` [PATCH v3 2/2] hyperv: Move arch/x86/hyperv/hv_proc.c to drivers/hv Nuno Das Neves
2025-02-12  4:11   ` Wei Liu
2025-02-12  4:10 ` 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=Z6wfHOPNUL2KcSG8@liuwe-devbox-debian-v2 \
    --to=wei.liu@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=catalin.marinas@arm.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=decui@microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=hpa@zytor.com \
    --cc=jinankjain@linux.microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhklinux@outlook.com \
    --cc=mingo@redhat.com \
    --cc=mukeshrathor@microsoft.com \
    --cc=muminulrussell@gmail.com \
    --cc=nunodasneves@linux.microsoft.com \
    --cc=skinsburskii@linux.microsoft.com \
    --cc=tglx@linutronix.de \
    --cc=will@kernel.org \
    --cc=x86@kernel.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