From: Kiryl Shutsemau <kas@kernel.org>
To: "Verma, Vishal L" <vishal.l.verma@intel.com>
Cc: "corbet@lwn.net" <corbet@lwn.net>,
"rdunlap@infradead.org" <rdunlap@infradead.org>,
"Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"skhan@linuxfoundation.org" <skhan@linuxfoundation.org>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] x86/early_printk: Add earlyprintk=tdx to drive the UART with TDVMCALLs
Date: Sun, 4 Oct 2026 00:34:33 +0100 [thread overview]
Message-ID: <asGQ6wkOmLGkeYsL@thinkstation> (raw)
In-Reply-To: <dfe6e3aa7bd37679d2d5e559b9af8e254d88044f.camel@intel.com>
On Fri, Oct 02, 2026 at 07:31:00PM +0000, Verma, Vishal L wrote:
> > +/* Only referenced when X86_FEATURE_TDX_GUEST is enabled, no stubs needed */
> > +unsigned int tdx_serial_in(unsigned long addr, int offset);
> > +void tdx_serial_out(unsigned long addr, int offset, int value);
> > +
> >
>
> .. Should these also be:
>
> +__noendbr unsigned int tdx_serial_in(unsigned long addr, int offset);
> +__noendbr void tdx_serial_out(unsigned long addr, int offset, int value);
Yes, my bad.
--
Kiryl Shutsemau / Kirill A. Shutemov
prev parent reply other threads:[~2026-10-03 23:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 20:20 [PATCH v3 0/2] x86/tdx: Use TDVMCALLs directly for earlyprintk Vishal Verma
2026-09-22 20:20 ` [PATCH v3 1/2] x86/tdx: Move port I/O definitions to a shared header Vishal Verma
2026-09-22 20:20 ` [PATCH v3 2/2] x86/early_printk: Add earlyprintk=tdx to drive the UART with TDVMCALLs Vishal Verma
2026-09-25 11:30 ` Kiryl Shutsemau
2026-09-28 23:07 ` Verma, Vishal L
2026-10-02 14:59 ` Kiryl Shutsemau
2026-10-02 19:31 ` Verma, Vishal L
2026-10-03 23:34 ` Kiryl Shutsemau [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=asGQ6wkOmLGkeYsL@thinkstation \
--to=kas@kernel.org \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--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®