From: "Huang, Kai" <kai.huang@intel.com>
To: "nik.borisov@suse.com" <nik.borisov@suse.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
"bp@alien8.de" <bp@alien8.de>, "x86@kernel.org" <x86@kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"kirill.shutemov@linux.intel.com"
<kirill.shutemov@linux.intel.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"seanjc@google.com" <seanjc@google.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"binbin.wu@linux.intel.com" <binbin.wu@linux.intel.com>,
"Yamahata, Isaku" <isaku.yamahata@intel.com>
Subject: Re: [PATCH 5/9] x86/virt/tdx: Move field mapping table of getting TDMR info to function local
Date: Tue, 18 Jun 2024 23:44:34 +0000 [thread overview]
Message-ID: <de8de1c36810fa46c58433f550e5c63409ba6c3d.camel@intel.com> (raw)
In-Reply-To: <e79e8576-1cdd-468f-9ee8-5543b8c6b1d5@suse.com>
On Tue, 2024-06-18 at 14:47 +0300, Nikolay Borisov wrote:
>
> On 16.06.24 г. 15:01 ч., Kai Huang wrote:
> > For now the kernel only reads "TD Memory Region" (TDMR) related global
> > metadata fields to a 'struct tdx_tdmr_sysinfo' for initializing the TDX
> > module. The kernel populates the relevant metadata fields into the
> > structure using a "field mapping table" of metadata field IDs and the
> > structure members.
> >
> > Currently the scope of this "field mapping table" is the entire C file.
> > Future changes will need to read more global metadata fields that will
> > be organized in other structures and use this kind of field mapping
> > tables for other structures too.
> >
> > Move the field mapping table to the function local to limit its scope so
> > that the same name can also be used by other functions.
>
> nit: I think all of this could be condensed simply to :
>
> "The mapping table is only used by foo() so move it there, no functional
> changes". The consideration for future usage seems somewhat moot with
> respect to such a trivial change.
>
Without future usage I am not sure whether it is worth to do such change,
so I would at least keep the future usage part.
And to explain "future usage", I think it would be helpful to have some
background text here. So I tend to keep the current way. But I am open
on this if other people have comments.
> In any case:
>
> Reviewed-by: Nikolay Borisov <nik.borisov@suse.com>
Thanks!
>
>
> >
> > Signed-off-by: Kai Huang <kai.huang@intel.com>
> > ---
> > arch/x86/virt/vmx/tdx/tdx.c | 18 +++++++++---------
> > 1 file changed, 9 insertions(+), 9 deletions(-)
> >
> > diff --git a/arch/x86/virt/vmx/tdx/tdx.c b/arch/x86/virt/vmx/tdx/tdx.c
> > index c68fbaf4aa15..fad42014ca37 100644
> > --- a/arch/x86/virt/vmx/tdx/tdx.c
> > +++ b/arch/x86/virt/vmx/tdx/tdx.c
> > @@ -322,17 +322,17 @@ static int stbuf_read_sysmd_multi(const struct field_mapping *fields,
> > #define TD_SYSINFO_MAP_TDMR_INFO(_field_id, _member) \
> > TD_SYSINFO_MAP(_field_id, struct tdx_tdmr_sysinfo, _member)
> >
> > -/* Map TD_SYSINFO fields into 'struct tdx_tdmr_sysinfo': */
> > -static const struct field_mapping fields[] = {
> > - TD_SYSINFO_MAP_TDMR_INFO(MAX_TDMRS, max_tdmrs),
> > - TD_SYSINFO_MAP_TDMR_INFO(MAX_RESERVED_PER_TDMR, max_reserved_per_tdmr),
> > - TD_SYSINFO_MAP_TDMR_INFO(PAMT_4K_ENTRY_SIZE, pamt_entry_size[TDX_PS_4K]),
> > - TD_SYSINFO_MAP_TDMR_INFO(PAMT_2M_ENTRY_SIZE, pamt_entry_size[TDX_PS_2M]),
> > - TD_SYSINFO_MAP_TDMR_INFO(PAMT_1G_ENTRY_SIZE, pamt_entry_size[TDX_PS_1G]),
> > -};
> > -
> > static int get_tdx_tdmr_sysinfo(struct tdx_tdmr_sysinfo *tdmr_sysinfo)
> > {
> > + /* Map TD_SYSINFO fields into 'struct tdx_tdmr_sysinfo': */
> > + static const struct field_mapping fields[] = {
> > + TD_SYSINFO_MAP_TDMR_INFO(MAX_TDMRS, max_tdmrs),
> > + TD_SYSINFO_MAP_TDMR_INFO(MAX_RESERVED_PER_TDMR, max_reserved_per_tdmr),
> > + TD_SYSINFO_MAP_TDMR_INFO(PAMT_4K_ENTRY_SIZE, pamt_entry_size[TDX_PS_4K]),
> > + TD_SYSINFO_MAP_TDMR_INFO(PAMT_2M_ENTRY_SIZE, pamt_entry_size[TDX_PS_2M]),
> > + TD_SYSINFO_MAP_TDMR_INFO(PAMT_1G_ENTRY_SIZE, pamt_entry_size[TDX_PS_1G]),
> > + };
> > +
> > /* Populate 'tdmr_sysinfo' fields using the mapping structure above: */
> > return stbuf_read_sysmd_multi(fields, ARRAY_SIZE(fields), tdmr_sysinfo);
> > }
next prev parent reply other threads:[~2024-06-18 23:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-16 12:01 [PATCH 0/9] TDX host: metadata reading tweaks, bug fix and info dump Kai Huang
2024-06-16 12:01 ` [PATCH 1/9] x86/virt/tdx: Rename _offset to _member for TD_SYSINFO_MAP() macro Kai Huang
2024-06-16 12:01 ` [PATCH 2/9] x86/virt/tdx: Unbind global metadata read with 'struct tdx_tdmr_sysinfo' Kai Huang
2024-06-18 11:23 ` Nikolay Borisov
2024-06-18 23:29 ` Huang, Kai
2024-06-16 12:01 ` [PATCH 3/9] x86/virt/tdx: Support global metadata read for all element sizes Kai Huang
2024-06-18 11:42 ` Nikolay Borisov
2024-06-18 23:28 ` Huang, Kai
2024-06-19 8:05 ` Nikolay Borisov
2024-06-19 9:51 ` Huang, Kai
2024-06-16 12:01 ` [PATCH 4/9] x86/virt/tdx: Abstract reading multiple global metadata fields as a helper Kai Huang
2024-06-18 11:45 ` Nikolay Borisov
2024-06-18 23:42 ` Huang, Kai
2024-06-16 12:01 ` [PATCH 5/9] x86/virt/tdx: Move field mapping table of getting TDMR info to function local Kai Huang
2024-06-18 11:47 ` Nikolay Borisov
2024-06-18 23:44 ` Huang, Kai [this message]
2024-06-16 12:01 ` [PATCH 6/9] x86/virt/tdx: Start to track all global metadata in one structure Kai Huang
2024-06-18 13:17 ` Nikolay Borisov
2024-06-18 23:54 ` Huang, Kai
2024-06-16 12:01 ` [PATCH 7/9] x86/virt/tdx: Print TDX module basic information Kai Huang
2024-06-18 13:52 ` Nikolay Borisov
2024-06-19 0:22 ` Huang, Kai
2024-06-16 12:01 ` [PATCH 8/9] x86/virt/tdx: Exclude memory region hole within CMR as TDMR's reserved area Kai Huang
2024-06-17 10:54 ` Chao Gao
2024-06-18 0:12 ` Huang, Kai
2024-06-18 15:10 ` Nikolay Borisov
2024-06-19 1:23 ` Huang, Kai
2024-06-19 4:58 ` Huang, Kai
2024-07-05 3:00 ` Binbin Wu
2024-07-05 9:36 ` Huang, Kai
2024-06-16 12:01 ` [PATCH 9/9] x86/virt/tdx: Don't initialize module that doesn't support NO_RBP_MOD feature Kai Huang
2024-06-18 15:12 ` Nikolay Borisov
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=de8de1c36810fa46c58433f550e5c63409ba6c3d.camel@intel.com \
--to=kai.huang@intel.com \
--cc=binbin.wu@linux.intel.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=isaku.yamahata@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nik.borisov@suse.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--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