From: Alex Ionescu <aionescu@gmail.com>
To: linux-hyperv@vger.kernel.org
Subject: Incorrect definition of hv_enable_vp_vtl in hyperv-tlfs.h
Date: Mon, 16 Oct 2023 07:49:56 -0400 [thread overview]
Message-ID: <CAJ-90N+sS6tuzMtRLOSan7WMZZ2g1H-iFc1F1ne631d2kgoi_g@mail.gmail.com> (raw)
Hi,
In arch/x86/include/asm/hyperv-tlfs.h, the following definition at
line 786 (in Linus' tree), I believe to be incorrect.
struct hv_enable_vp_vtl {
u64 partition_id;
u32 vp_index;
union hv_input_vtl target_vtl; <==== Here
For this hypercall, the TLFS and MSDN documentation states this field
is HV_VTL (u8) and not HV_INPUT_VTL (the bit-field used for targeting
hypercalls to specific target VTLs, which is not the case here).
I realize this is essentially a no-op in code at the moment, but for
correctness should be addressed? I'm happy to make a patch, but wanted
to make sure this isn't a mistake in TLFS/MSDN to begin with
(although, my copy of GDK headers would corroborate it's indeed HV_VTL
as well).
Best regards,
Alex Ionescu
next reply other threads:[~2023-10-16 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 11:49 Alex Ionescu [this message]
2023-10-19 16:18 ` Incorrect definition of hv_enable_vp_vtl in hyperv-tlfs.h Nuno Das Neves
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=CAJ-90N+sS6tuzMtRLOSan7WMZZ2g1H-iFc1F1ne631d2kgoi_g@mail.gmail.com \
--to=aionescu@gmail.com \
--cc=linux-hyperv@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).