[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1e880953645d966a9869531409e1296c2ae234f9.camel@intel.com>
Date: Thu, 19 May 2022 11:56:53 +1200
From: Kai Huang <kai.huang@...el.com>
To: Sagi Shahar <sagis@...gle.com>
Cc: Dave Hansen <dave.hansen@...el.com>, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, Sean Christopherson <seanjc@...gle.com>,
Paolo Bonzini <pbonzini@...hat.com>, len.brown@...el.com,
tony.luck@...el.com, rafael.j.wysocki@...el.com,
reinette.chatre@...el.com, dan.j.williams@...el.com,
peterz@...radead.org, ak@...ux.intel.com,
kirill.shutemov@...ux.intel.com,
sathyanarayanan.kuppuswamy@...ux.intel.com,
"Yamahata, Isaku" <isaku.yamahata@...el.com>
Subject: Re: [PATCH v3 09/21] x86/virt/tdx: Get information about TDX module
and convertible memory
On Wed, 2022-05-18 at 15:30 -0700, Sagi Shahar wrote:
> > >
> > > > + pr_info("TDX module: vendor_id 0x%x, major_version %u, minor_version
> > > > %u, build_date %u, build_num %u",
> > > > + tdx_sysinfo.vendor_id, tdx_sysinfo.major_version,
> > > > + tdx_sysinfo.minor_version, tdx_sysinfo.build_date,
> > > > + tdx_sysinfo.build_num);
> > > > +
> > > > + /* Print BIOS provided CMRs */
> > > > + print_cmrs(tdx_cmr_array, cmr_num, "BIOS-CMR");
> > > > +
>
> sanitize_cmrs already prints the cmrs in case of success. So for valid
> cmrs we are going to print them twice.
> Would it be better to only print cmrs here in case sanitize_cmrs fails?
The "BIOS-CMR" will always have 32 entries. It includes all the *empty* CMRs
after the valid CMRs, so the two are different. But yes it seems there's no
need to always print "BIOS-CMR".
--
Thanks,
-Kai
Powered by blists - more mailing lists