From: Michael Kelley <mhklinux@outlook.com>
To: Nuno Das Neves <nunodasneves@linux.microsoft.com>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"virtualization@lists.linux.dev" <virtualization@lists.linux.dev>
Cc: "kys@microsoft.com" <kys@microsoft.com>,
"haiyangz@microsoft.com" <haiyangz@microsoft.com>,
"wei.liu@kernel.org" <wei.liu@kernel.org>,
"decui@microsoft.com" <decui@microsoft.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>,
"luto@kernel.org" <luto@kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"seanjc@google.com" <seanjc@google.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
"joro@8bytes.org" <joro@8bytes.org>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"lpieralisi@kernel.org" <lpieralisi@kernel.org>,
"kw@linux.com" <kw@linux.com>,
"robh@kernel.org" <robh@kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"sgarzare@redhat.com" <sgarzare@redhat.com>,
"jinankjain@linux.microsoft.com" <jinankjain@linux.microsoft.com>,
"muminulrussell@gmail.com" <muminulrussell@gmail.com>,
"skinsburskii@linux.microsoft.com"
<skinsburskii@linux.microsoft.com>,
"mukeshrathor@microsoft.com" <mukeshrathor@microsoft.com>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
"ssengar@linux.microsoft.com" <ssengar@linux.microsoft.com>,
"apais@linux.microsoft.com" <apais@linux.microsoft.com>
Subject: RE: [PATCH v2 4/4] hyperv: Switch from hyperv-tlfs.h to hyperv/hvhdk.h
Date: Fri, 15 Nov 2024 21:54:14 +0000 [thread overview]
Message-ID: <SN6PR02MB4157DE83D677F2E463774393D4242@SN6PR02MB4157.namprd02.prod.outlook.com> (raw)
In-Reply-To: <e832dd94-04f3-413a-a1a9-870849b4bc53@linux.microsoft.com>
From: Nuno Das Neves <nunodasneves@linux.microsoft.com> Sent: Friday, November 15, 2024 1:15 PM
>
> On 11/10/2024 8:13 PM, Michael Kelley wrote:
> > From: Nuno Das Neves <nunodasneves@linux.microsoft.com> Sent: Thursday, November 7, 2024 2:32 PM
> >>
> >> Switch to using hvhdk.h everywhere in the kernel. This header includes
> >> all the new Hyper-V headers in include/hyperv, which form a superset of
> >> the definitions found in hyperv-tlfs.h.
> >>
> >> This makes it easier to add new Hyper-V interfaces without being
> >> restricted to those in the TLFS doc (reflected in hyperv-tlfs.h).
> >>
> >> To be more consistent with the original Hyper-V code, the names of some
> >> definitions are changed slightly. Update those where needed.
> >>
> >> hyperv-tlfs.h is no longer included anywhere - hvhdk.h can serve
> >> the same role, but with an easier path for adding new definitions.
> >
> > Is hyperv-tlfs.h and friends being deleted? If not, the risk is that
> > someone adds a new #include of it without realizing that it has been
> > superseded by hvhdk.h.
> >
>
> I was hesitant to delete it because I thought someone may still have
> a use for a header file that (mostly) reflects the TLFS document and
> nothing more.
>
> But in practical terms, this patchset makes it much more difficult to
> use because all the helper code (i.e. mshyperv.h) now uses hvhdk.h.
> So, maybe there is no point keeping it.
>
> > Note also that this patch does not apply cleanly to 6.12 rc's, or to
> > current linux-next trees. There's an unrelated #include added to
> > arch/x86/include/asm/kvm_host.h that causes a merge failure
> > in that file.
> >
>
> I've been developing this series based on hyperv-next. Should I be
> basing it on linux-next?
>
Yes, base it on linux-next. hyperv-next was last sync'ed with
upstream at 6.11-rc4 back in mid-August, so it's pretty far
out-of-date. Wei will need to sync it before picking up any
new patches.
Michael
next prev parent reply other threads:[~2024-11-15 21:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 22:32 [PATCH v2 0/4] Add new headers for Hyper-V Dom0 Nuno Das Neves
2024-11-07 22:32 ` [PATCH v2 1/4] hyperv: Move hv_connection_id to hyperv-tlfs.h Nuno Das Neves
2024-11-08 4:23 ` Easwar Hariharan
2024-11-11 4:13 ` Michael Kelley
2024-11-07 22:32 ` [PATCH v2 2/4] hyperv: Clean up unnecessary #includes Nuno Das Neves
2024-11-08 4:24 ` Easwar Hariharan
2024-11-11 4:13 ` Michael Kelley
2024-11-07 22:32 ` [PATCH v2 3/4] hyperv: Add new Hyper-V headers in include/hyperv Nuno Das Neves
2024-11-08 5:59 ` Naman Jain
2024-11-11 17:55 ` Nuno Das Neves
2024-11-11 4:13 ` Michael Kelley
2024-11-11 18:45 ` Nuno Das Neves
2024-11-11 19:31 ` Michael Kelley
2024-11-13 23:32 ` Nuno Das Neves
2024-11-07 22:32 ` [PATCH v2 4/4] hyperv: Switch from hyperv-tlfs.h to hyperv/hvhdk.h Nuno Das Neves
2024-11-11 4:13 ` Michael Kelley
2024-11-15 21:14 ` Nuno Das Neves
2024-11-15 21:54 ` Michael Kelley [this message]
2024-11-14 21:35 ` Easwar Hariharan
2024-11-11 4:12 ` [PATCH v2 0/4] Add new headers for Hyper-V Dom0 Michael Kelley
2024-11-11 17:59 ` Nuno Das Neves
2024-11-11 19:36 ` Michael Kelley
2024-11-11 18:52 ` [EXTERNAL] " MUKESH RATHOR
2024-11-11 21:28 ` Michael Kelley
2024-11-11 23:10 ` MUKESH RATHOR
2024-11-11 23:41 ` Michael Kelley
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=SN6PR02MB4157DE83D677F2E463774393D4242@SN6PR02MB4157.namprd02.prod.outlook.com \
--to=mhklinux@outlook.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=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=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
all inboxes | Powered by JetHome®