All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Kuppuswamy Sathyanarayanan  <sathyanarayanan.kuppuswamy@linux.intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Andy Lutomirski <luto@kernel.org>, Peter H Anvin <hpa@zytor.com>,
	Dave Hansen <dave.hansen@intel.com>,
	Tony Luck <tony.luck@intel.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Andi Kleen <ak@linux.intel.com>,
	Kirill Shutemov <kirill.shutemov@linux.intel.com>,
	Kuppuswamy Sathyanarayanan <knsathya@kernel.org>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 04/10] x86/tdx: Handle early IO operations
Date: Wed, 9 Jun 2021 22:10:49 +0000	[thread overview]
Message-ID: <YME8aZVqI8x/a/Ld@google.com> (raw)
In-Reply-To: <20210609214555.1955404-5-sathyanarayanan.kuppuswamy@linux.intel.com>

On Wed, Jun 09, 2021, Kuppuswamy Sathyanarayanan wrote:
> +/*
> + * Handle early IO, mainly for early printks serial output.
> + * This avoids anything that doesn't work early on, like tracing
> + * or printks, by calling the low level functions directly. Any
> + * problems are handled by falling back to a standard early exception.
> + *
> + * Assumes the IO instruction was using ax, which is enforced
> + * by the standard io.h macros.
> + */
> +static __init bool tdx_early_io(struct pt_regs *regs, u32 exit_qual)

If y'all insist on shoving "tdg" down people's throats, at least get it right.

  reply	other threads:[~2021-06-09 22:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09 21:45 [PATCH v1 00/10] Add TDX Guest Support (#VE handler support) Kuppuswamy Sathyanarayanan
2021-06-09 21:45 ` [PATCH v1 01/10] x86: Introduce generic protected guest abstraction Kuppuswamy Sathyanarayanan
2021-06-09 21:45 ` [PATCH v1 02/10] x86/io: Allow to override inX() and outX() implementation Kuppuswamy Sathyanarayanan
2021-06-09 21:45 ` [PATCH v1 03/10] x86/tdx: Handle port I/O in decompression code Kuppuswamy Sathyanarayanan
2021-06-09 21:45 ` [PATCH v1 04/10] x86/tdx: Handle early IO operations Kuppuswamy Sathyanarayanan
2021-06-09 22:10   ` Sean Christopherson [this message]
2021-06-09 22:47     ` Kuppuswamy, Sathyanarayanan
2021-06-09 21:45 ` [PATCH v1 05/10] x86/tdx: Handle port I/O Kuppuswamy Sathyanarayanan
2021-06-09 21:45 ` [PATCH v1 06/10] x86/insn-eval: Introduce insn_get_modrm_reg_ptr() Kuppuswamy Sathyanarayanan
2021-06-09 21:45 ` [PATCH v1 07/10] x86/insn-eval: Introduce insn_decode_mmio() Kuppuswamy Sathyanarayanan
2021-06-09 21:45 ` [PATCH v1 08/10] x86/sev-es: Use insn_decode_mmio() for MMIO implementation Kuppuswamy Sathyanarayanan
2021-06-09 21:45 ` [PATCH v1 09/10] x86/tdx: Handle in-kernel MMIO Kuppuswamy Sathyanarayanan
2021-06-09 21:45 ` [PATCH v1 10/10] x86/tdx: Handle MWAIT and MONITOR Kuppuswamy Sathyanarayanan

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=YME8aZVqI8x/a/Ld@google.com \
    --to=seanjc@google.com \
    --cc=ak@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@intel.com \
    --cc=hpa@zytor.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=knsathya@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=sathyanarayanan.kuppuswamy@linux.intel.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.