From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Wei Liu <wei.liu@kernel.org>
Cc: Michael Kelley <mikelley@microsoft.com>,
Linux on Hyper-V List <linux-hyperv@vger.kernel.org>
Subject: Re: Field names inside ms_hyperv_info
Date: Fri, 30 Oct 2020 16:24:18 +0100 [thread overview]
Message-ID: <87lffnzqhp.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <20201028150323.tz5wamibt42dgx7f@liuwe-devbox-debian-v2>
Wei Liu <wei.liu@kernel.org> writes:
> Hi all
>
> During my work to make Linux boot as root partition on MSHV, I found out
> that a privilege mask was not collected in ms_hyperv_info.
>
> Looking at the code, the field names of ms_hyperv_info are not
> consistent with the names defined in TLFS. That makes it difficult to
> choose a name for the field that stores the privilege mask.
>
> I've got a local patch to make the existing fields closer to TLFS. The
> suffix "_a" means the value comes from EAX.
>
> Given that this structure is also used on ARM, so having x86 suffix is
> probably not the best idea. Do people care?
>
> diff --git a/include/asm-generic/mshyperv.h b/include/asm-generic/mshyperv.h
> index c57799684170..913af5e93cce 100644
> --- a/include/asm-generic/mshyperv.h
> +++ b/include/asm-generic/mshyperv.h
> @@ -26,9 +26,9 @@
> #include <asm/hyperv-tlfs.h>
>
> struct ms_hyperv_info {
> - u32 features;
> - u32 misc_features;
> - u32 hints;
> + u32 features_a;
> + u32 features_d;
> + u32 recommendations;
> u32 nested_features;
> u32 max_vp_index;
> u32 max_lp_index;
>
> Any comment on this? I'm normally bad at naming things so any suggestion
> is welcomed.
My take: let's avoid ambiguous '_a', '_d' and use full register names,
it's only three letters after all. Let's also avoid suffix-less names as
eventually we'll need to add non-eax parts. That is:
u32 features_eax;
u32 features_edx;
u32 recommendations_eax;
u32 nested_features_eax;
...
I would also feel comfortable with these names sortened,
u32 feat_eax;
u32 feat_edx;
u32 recomm_eax;
u32 nested_feat_eax;
...
--
Vitaly
next prev parent reply other threads:[~2020-10-30 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 15:03 Field names inside ms_hyperv_info Wei Liu
2020-10-30 15:24 ` Vitaly Kuznetsov [this message]
2020-10-30 16:29 ` Michael Kelley
2020-10-30 17:09 ` ** POTENTIAL FRAUD ALERT - RED HAT ** " Vitaly Kuznetsov
2020-11-01 18:19 ` 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=87lffnzqhp.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=wei.liu@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