From: Dave Hansen <dave.hansen@intel.com>
To: "Verma, Vishal L" <vishal.l.verma@intel.com>,
"rdunlap@infradead.org" <rdunlap@infradead.org>,
"corbet@lwn.net" <corbet@lwn.net>,
"x86@kernel.org" <x86@kernel.org>,
"kas@kernel.org" <kas@kernel.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
"skhan@linuxfoundation.org" <skhan@linuxfoundation.org>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] x86/early_printk: Add earlyprintk=tdx to drive the UART with TDVMCALLs
Date: Tue, 22 Sep 2026 11:24:55 -0700 [thread overview]
Message-ID: <ba472411-aebc-43f7-b0f4-0003b71905c7@intel.com> (raw)
In-Reply-To: <94ea99fc4ba332a07530ced72284c2193aaedecd.camel@intel.com>
On 9/22/26 11:18, Verma, Vishal L wrote:
> As a thought exercise, I changed this to just use ttyS0 which is the
> defined default, and that changes the setup hunks to look like below
> (not thoroughly tested or anything yet). Would you prefer this instead?
That looks fine to me.
prev parent reply other threads:[~2026-09-22 18:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 19:52 [PATCH v2 0/2] x86/tdx: Use TDVMCALLs directly for earlyprintk Vishal Verma
2026-09-21 19:52 ` [PATCH v2 1/2] x86/tdx: Move port I/O definitions to a shared header Vishal Verma
2026-09-21 19:52 ` [PATCH v2 2/2] x86/early_printk: Add earlyprintk=tdx to drive the UART with TDVMCALLs Vishal Verma
2026-09-21 19:58 ` Dave Hansen
2026-09-21 20:11 ` Verma, Vishal L
2026-09-22 18:18 ` Verma, Vishal L
2026-09-22 18:24 ` Dave Hansen [this message]
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=ba472411-aebc-43f7-b0f4-0003b71905c7@intel.com \
--to=dave.hansen@intel.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=skhan@linuxfoundation.org \
--cc=vishal.l.verma@intel.com \
--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
all inboxes | Powered by JetHome®