From: Easwar Hariharan <eahariha@linux.microsoft.com>
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, kvm@vger.kernel.org,
iommu@lists.linux.dev, netdev@vger.kernel.org,
linux-pci@vger.kernel.org, linux-arch@vger.kernel.org,
virtualization@lists.linux.dev, eahariha@linux.microsoft.com,
kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
mhklinux@outlook.com, decui@microsoft.com,
catalin.marinas@arm.com, will@kernel.org, luto@kernel.org,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
seanjc@google.com, pbonzini@redhat.com, peterz@infradead.org,
daniel.lezcano@linaro.org, joro@8bytes.org, robin.murphy@arm.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, lpieralisi@kernel.org, kw@linux.com,
robh@kernel.org, bhelgaas@google.com, arnd@arndb.de,
sgarzare@redhat.com, jinankjain@linux.microsoft.com,
muminulrussell@gmail.com, skinsburskii@linux.microsoft.com,
mukeshrathor@microsoft.com, vkuznets@redhat.com,
ssengar@linux.microsoft.com, apais@linux.microsoft.com,
horms@kernel.org
Subject: Re: [PATCH v3 3/5] hyperv: Add new Hyper-V headers in include/hyperv
Date: Thu, 5 Dec 2024 21:12:56 -0800 [thread overview]
Message-ID: <3c5ec65e-93a9-48a2-a18f-f5b89e83e999@linux.microsoft.com> (raw)
In-Reply-To: <1732577084-2122-4-git-send-email-nunodasneves@linux.microsoft.com>
On 11/25/2024 3:24 PM, Nuno Das Neves wrote:
> These headers contain definitions for regular Hyper-V guests (as in
> hyperv-tlfs.h), as well as interfaces for more privileged guests like
> the root partition (aka Dom0).
>
> These files are derived from headers exported from Hyper-V, rather than
> being derived from the TLFS document. (Although, to preserve
> compatibility with existing Linux code, some definitions are copied
> directly from hyperv-tlfs.h too).
>
> The new files follow a naming convention according to their original
> use:
> - hdk "host development kit"
> - gdk "guest development kit"
> With postfix "_mini" implying userspace-only headers, and "_ext" for
> extended hypercalls.
>
> The use of multiple files and their original names is primarily to
> keep the provenance of exactly where they came from in Hyper-V
> code, which is helpful for manual maintenance and extension
> of these definitions. Microsoft maintainers importing new definitions
> should take care to put them in the right file. However, Linux kernel
> code that uses any of the definitions need not be aware of the multiple
> files or assign any meaning to the new names. Linux kernel code should
> always just include hvhdk.h
>
> Note the new headers contain both arm64 and x86_64 definitions. Some are
> guarded by #ifdefs, and some are instead prefixed with the architecture,
> e.g. hv_x64_*. These conventions are kept from Hyper-V code as another
> tactic to simplify the process of importing and maintaining the
> definitions, rather than splitting them up into their own files in
> arch/x86/ and arch/arm64/.
>
> These headers are a step toward importing headers directly from Hyper-V
> in the future, similar to Xen public files in include/xen/interface/.
>
> Signed-off-by: Nuno Das Neves <nunodasneves@linux.microsoft.com>
> ---
> MAINTAINERS | 5 +
> include/hyperv/hvgdk.h | 308 +++++++++
> include/hyperv/hvgdk_ext.h | 46 ++
> include/hyperv/hvgdk_mini.h | 1306 +++++++++++++++++++++++++++++++++++
> include/hyperv/hvhdk.h | 733 ++++++++++++++++++++
> include/hyperv/hvhdk_mini.h | 311 +++++++++
> 6 files changed, 2709 insertions(+)
> create mode 100644 include/hyperv/hvgdk.h
> create mode 100644 include/hyperv/hvgdk_ext.h
> create mode 100644 include/hyperv/hvgdk_mini.h
> create mode 100644 include/hyperv/hvhdk.h
> create mode 100644 include/hyperv/hvhdk_mini.h
Reviewed-by: Easwar Hariharan <eahariha@linux.microsoft.com>
next prev parent reply other threads:[~2024-12-06 5:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 23:24 [PATCH v3 0/5] Introduce new headers for Hyper-V Nuno Das Neves
2024-11-25 23:24 ` [PATCH v3 1/5] hyperv: Move hv_connection_id to hyperv-tlfs.h Nuno Das Neves
2024-12-09 0:07 ` Wei Liu
2024-12-09 19:19 ` Nuno Das Neves
2024-11-25 23:24 ` [PATCH v3 2/5] hyperv: Clean up unnecessary #includes Nuno Das Neves
2024-11-25 23:24 ` [PATCH v3 3/5] hyperv: Add new Hyper-V headers in include/hyperv Nuno Das Neves
2024-11-26 5:57 ` Michael Kelley
2024-12-06 5:12 ` Easwar Hariharan [this message]
2024-11-25 23:24 ` [PATCH v3 4/5] hyperv: Switch from hyperv-tlfs.h to hyperv/hvhdk.h Nuno Das Neves
2024-11-26 5:58 ` Michael Kelley
2024-12-06 5:13 ` Easwar Hariharan
2024-11-25 23:24 ` [PATCH v3 5/5] hyperv: Remove the now unused hyperv-tlfs.h files Nuno Das Neves
2024-11-26 5:59 ` Michael Kelley
2024-11-26 17:28 ` Nuno Das Neves
2024-12-06 5:14 ` Easwar Hariharan
2024-12-09 0:05 ` [PATCH v3 0/5] Introduce new headers for Hyper-V Wei Liu
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=3c5ec65e-93a9-48a2-a18f-f5b89e83e999@linux.microsoft.com \
--to=eahariha@linux.microsoft.com \
--cc=apais@linux.microsoft.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=haiyangz@microsoft.com \
--cc=horms@kernel.org \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux.dev \
--cc=jinankjain@linux.microsoft.com \
--cc=joro@8bytes.org \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kw@linux.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=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=luto@kernel.org \
--cc=mhklinux@outlook.com \
--cc=mingo@redhat.com \
--cc=mukeshrathor@microsoft.com \
--cc=muminulrussell@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nunodasneves@linux.microsoft.com \
--cc=pabeni@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=seanjc@google.com \
--cc=sgarzare@redhat.com \
--cc=skinsburskii@linux.microsoft.com \
--cc=ssengar@linux.microsoft.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux.dev \
--cc=vkuznets@redhat.com \
--cc=wei.liu@kernel.org \
--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