public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Huang, Kai" <kai.huang@intel.com>
To: Dan Williams <dan.j.williams@intel.com>, <dave.hansen@intel.com>,
	<kirill.shutemov@linux.intel.com>, <tglx@linutronix.de>,
	<bp@alien8.de>, <peterz@infradead.org>, <mingo@redhat.com>,
	<hpa@zytor.com>, <seanjc@google.com>, <pbonzini@redhat.com>
Cc: <x86@kernel.org>, <linux-kernel@vger.kernel.org>,
	<kvm@vger.kernel.org>, <rick.p.edgecombe@intel.com>,
	<isaku.yamahata@intel.com>, <adrian.hunter@intel.com>,
	<nik.borisov@suse.com>
Subject: Re: [PATCH v6 03/10] x86/virt/tdx: Use auto-generated code to read global metadata
Date: Tue, 29 Oct 2024 11:47:46 +1300	[thread overview]
Message-ID: <554e098b-f640-4dda-a829-5bcd3f6ea2e2@intel.com> (raw)
In-Reply-To: <6720064bf2c69_bc69d2947b@dwillia2-xfh.jf.intel.com.notmuch>


>>    1) Using the generated C is simple.
>>    2) Adding a field is dirty simple, e.g., the script just pulls the
> 
> Probably meant "dirt simple", but if this is fixed up on apply I'd drop
> the idiom and just say "simple".

Yeah "dirt simple".  I missed this.  Will just say "simple" if a new 
version is needed.

[...]

>>
>> Link: https://lore.kernel.org/lkml/4b3adb59-50ea-419e-ad02-e19e8ca20dee@intel.com/ [1]
>> Link: https://lore.kernel.org/all/fc0e8ab7-86d4-4428-be31-82e1ece6dd21@intel.com/ [2]
>> Link: https://lore.kernel.org/kvm/0853b155ec9aac09c594caa60914ed6ea4dc0a71.camel@intel.com/ [5]
> 
> Just an fyi, that lore accepts the simple:
> 
> https://lore.kernel.org/$msg_id
> 
> ...format, no need to record the list name in the URL (127734e23aed
> ("Documentation: best practices for using Link trailers"))

Thanks for the info.  I got those link by clicking the "permalink" on 
the webpage, and then I just paste.

Yeah "https://lore.kernel.org/$msg_id" works, but if I open the page 
using this format the like is changed to:

   "https://lore.kernel.org/all/$msg_id"

So I thought I just don't bother to remove the "all/lkml/kvm" in the 
link.  I'll change to use the simple format in the future since it is 
said in the Documentation.

> 
>> Link: https://github.com/canonical/tdx/issues/135 [3]
>> Link: https://cdrdv2.intel.com/v1/dl/getContent/795381 [4]
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> Co-developed-by: Kai Huang <kai.huang@intel.com>
>> Signed-off-by: Kai Huang <kai.huang@intel.com>
> 
> Looks good to me, with or without the above nits addressed.
> 
> Reviewed-by: Dan Williams <dan.j.williams@intel.com>

Thanks.  I'll fixup if a new version is needed.


  reply	other threads:[~2024-10-28 22:47 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28 12:41 [PATCH v6 00/10] TDX host: metadata reading tweaks, bug fix and info dump Kai Huang
2024-10-28 12:41 ` [PATCH v6 01/10] x86/virt/tdx: Rename 'struct tdx_tdmr_sysinfo' to reflect the spec better Kai Huang
2024-10-28 12:41 ` [PATCH v6 02/10] x86/virt/tdx: Start to track all global metadata in one structure Kai Huang
2024-10-28 21:37   ` Dan Williams
2024-10-28 12:41 ` [PATCH v6 03/10] x86/virt/tdx: Use auto-generated code to read global metadata Kai Huang
2024-10-28 21:46   ` Dan Williams
2024-10-28 22:47     ` Huang, Kai [this message]
2024-10-28 12:41 ` [PATCH v6 04/10] x86/virt/tdx: Use dedicated struct members for PAMT entry sizes Kai Huang
2024-10-28 13:29   ` Nikolay Borisov
2024-10-28 21:51   ` Dan Williams
2024-10-28 12:41 ` [PATCH v6 05/10] x86/virt/tdx: Add missing header file inclusion to local tdx.h Kai Huang
2024-10-28 13:35   ` Nikolay Borisov
2024-10-28 21:55   ` Dan Williams
2024-10-28 12:41 ` [PATCH v6 06/10] x86/virt/tdx: Switch to use auto-generated global metadata reading code Kai Huang
2024-10-28 14:55   ` Nikolay Borisov
2024-10-28 22:08   ` Dan Williams
2024-10-28 12:41 ` [PATCH v6 07/10] x86/virt/tdx: Trim away tail null CMRs Kai Huang
2024-10-28 22:12   ` Dan Williams
2024-10-28 12:41 ` [PATCH v6 08/10] x86/virt/tdx: Reduce TDMR's reserved areas by using CMRs to find memory holes Kai Huang
2024-10-28 22:26   ` Dan Williams
2024-10-28 23:22     ` Huang, Kai
2024-10-28 12:41 ` [PATCH v6 09/10] x86/virt/tdx: Require the module to assert it has the NO_RBP_MOD mitigation Kai Huang
2024-10-28 12:41 ` [PATCH v6 10/10] x86/virt/tdx: Print TDX module version Kai Huang
2024-10-28 22:36   ` Dan Williams
2024-10-28 22:59     ` Huang, Kai
2024-10-28 17:59 ` [PATCH v6 00/10] TDX host: metadata reading tweaks, bug fix and info dump Paolo Bonzini
2024-10-28 21:50   ` Huang, Kai
2024-10-28 18:35 ` Paolo Bonzini
2024-10-28 21:39   ` Huang, Kai
2024-10-29  0:23     ` Huang, Kai
2024-10-30 14:48       ` Paolo Bonzini
2024-10-30 20:40         ` Huang, Kai
2024-10-31 10:44 ` [PATCH 9/8] x86/virt/tdx: Add the global metadata code generation script Kai Huang
2024-11-06 11:00 ` [PATCH v6 00/10] TDX host: metadata reading tweaks, bug fix and info dump Huang, Kai

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=554e098b-f640-4dda-a829-5bcd3f6ea2e2@intel.com \
    --to=kai.huang@intel.com \
    --cc=adrian.hunter@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