tdx_quirk_reset_paddr() was renamed to reflect that, in fact, the clearing
is necessary only for hardware with a certain quirk. That is dealt with in
a subsequent patch.
Rename reset_pamt functions to contain "quirk" to reflect the new
functionality, and remove the now misleading comment.
Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
---
Changes in V6:
None
Changes in V5:
New patch
arch/x86/virt/vmx/tdx/tdx.c | 16 ++++------------
1 file changed, 4 insertions(+), 12 deletions(-)
diff --git a/arch/x86/virt/vmx/tdx/tdx.c b/arch/x86/virt/vmx/tdx/tdx.c
index fc8d8e444f15..9e4638f68ba0 100644
--- a/arch/x86/virt/vmx/tdx/tdx.c
+++ b/arch/x86/virt/vmx/tdx/tdx.c
@@ -660,17 +660,17 @@ void tdx_quirk_reset_page(struct page *page)
}
EXPORT_SYMBOL_GPL(tdx_quirk_reset_page);
-static void tdmr_reset_pamt(struct tdmr_info *tdmr)
+static void tdmr_quirk_reset_pamt(struct tdmr_info *tdmr)
{
tdmr_do_pamt_func(tdmr, tdx_quirk_reset_paddr);
}
-static void tdmrs_reset_pamt_all(struct tdmr_info_list *tdmr_list)
+static void tdmrs_quirk_reset_pamt_all(struct tdmr_info_list *tdmr_list)
{
int i;
for (i = 0; i < tdmr_list->nr_consumed_tdmrs; i++)
- tdmr_reset_pamt(tdmr_entry(tdmr_list, i));
+ tdmr_quirk_reset_pamt(tdmr_entry(tdmr_list, i));
}
static unsigned long tdmrs_count_pamt_kb(struct tdmr_info_list *tdmr_list)
@@ -1142,15 +1142,7 @@ static int init_tdx_module(void)
* to the kernel.
*/
wbinvd_on_all_cpus();
- /*
- * According to the TDX hardware spec, if the platform
- * doesn't have the "partial write machine check"
- * erratum, any kernel read/write will never cause #MC
- * in kernel space, thus it's OK to not convert PAMTs
- * back to normal. But do the conversion anyway here
- * as suggested by the TDX spec.
- */
- tdmrs_reset_pamt_all(&tdx_tdmr_list);
+ tdmrs_quirk_reset_pamt_all(&tdx_tdmr_list);
err_free_pamts:
tdmrs_free_pamt_all(&tdx_tdmr_list);
err_free_tdmrs:
--
2.48.1
On 7/24/2025 9:03 PM, Adrian Hunter wrote: > tdx_quirk_reset_paddr() was renamed to reflect that, in fact, the clearing > is necessary only for hardware with a certain quirk. That is dealt with in > a subsequent patch. > > Rename reset_pamt functions to contain "quirk" to reflect the new > functionality, and remove the now misleading comment. > > Signed-off-by: Adrian Hunter <adrian.hunter@intel.com> Reviewed-by: Binbin Wu <binbin.wu@linux.intel.com> > --- > > > Changes in V6: > > None > > Changes in V5: > > New patch > > > arch/x86/virt/vmx/tdx/tdx.c | 16 ++++------------ > 1 file changed, 4 insertions(+), 12 deletions(-) > > diff --git a/arch/x86/virt/vmx/tdx/tdx.c b/arch/x86/virt/vmx/tdx/tdx.c > index fc8d8e444f15..9e4638f68ba0 100644 > --- a/arch/x86/virt/vmx/tdx/tdx.c > +++ b/arch/x86/virt/vmx/tdx/tdx.c > @@ -660,17 +660,17 @@ void tdx_quirk_reset_page(struct page *page) > } > EXPORT_SYMBOL_GPL(tdx_quirk_reset_page); > > -static void tdmr_reset_pamt(struct tdmr_info *tdmr) > +static void tdmr_quirk_reset_pamt(struct tdmr_info *tdmr) > { > tdmr_do_pamt_func(tdmr, tdx_quirk_reset_paddr); > } > > -static void tdmrs_reset_pamt_all(struct tdmr_info_list *tdmr_list) > +static void tdmrs_quirk_reset_pamt_all(struct tdmr_info_list *tdmr_list) > { > int i; > > for (i = 0; i < tdmr_list->nr_consumed_tdmrs; i++) > - tdmr_reset_pamt(tdmr_entry(tdmr_list, i)); > + tdmr_quirk_reset_pamt(tdmr_entry(tdmr_list, i)); > } > > static unsigned long tdmrs_count_pamt_kb(struct tdmr_info_list *tdmr_list) > @@ -1142,15 +1142,7 @@ static int init_tdx_module(void) > * to the kernel. > */ > wbinvd_on_all_cpus(); > - /* > - * According to the TDX hardware spec, if the platform > - * doesn't have the "partial write machine check" > - * erratum, any kernel read/write will never cause #MC > - * in kernel space, thus it's OK to not convert PAMTs > - * back to normal. But do the conversion anyway here > - * as suggested by the TDX spec. > - */ > - tdmrs_reset_pamt_all(&tdx_tdmr_list); > + tdmrs_quirk_reset_pamt_all(&tdx_tdmr_list); > err_free_pamts: > tdmrs_free_pamt_all(&tdx_tdmr_list); > err_free_tdmrs:
On Thu, 2025-07-24 at 16:03 +0300, Hunter, Adrian wrote: > tdx_quirk_reset_paddr() was renamed to reflect that, in fact, the clearing > is necessary only for hardware with a certain quirk. That is dealt with in > a subsequent patch. > > Rename reset_pamt functions to contain "quirk" to reflect the new > functionality, and remove the now misleading comment. > > Signed-off-by: Adrian Hunter <adrian.hunter@intel.com> > Acked-by: Kai Huang <kai.huang@intel.com>
© 2016 - 2025 Red Hat, Inc.