public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Erdem Aktas <erdemaktas@google.com>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	devel@edk2.groups.io, Jiewen Yao <jiewen.yao@intel.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Michael Roth <michael.roth@amd.com>, Min Xu <min.m.xu@intel.com>,
	Oliver Steffen <osteffen@redhat.com>
Subject: Re: [edk2-devel] [PATCH 1/1] OvmfPkg/ResetVector: send post codes to qemu debug console
Date: Mon, 29 Jan 2024 12:22:06 +0100	[thread overview]
Message-ID: <afadc5a4-271f-aee2-6247-036b2d8b8298@redhat.com> (raw)
In-Reply-To: <ucaazd7knu7le6xyh7wcmncc67tpj4g675d6h4nsxdvp7wjsfq@7lxiblh27mkn>

On 1/26/24 14:25, Gerd Hoffmann wrote:
> On Thu, Jan 25, 2024 at 08:47:56PM +0100, Laszlo Ersek wrote:
>> On 1/25/24 08:50, Gerd Hoffmann wrote:
>>> On Wed, Jan 24, 2024 at 05:43:29PM -0800, Erdem Aktas wrote:
>>>> Same for TDX, I did not run it but it should cause failure
>>>> as debugShowPostCode is called OvmfPkg/ResetVector/Ia32/IntelTdx.asm before
>>>> actually the #VE handlers are installed.
>>>>
>>>>> Had a meeting get canceled and so got a chance to test this. As I thought,
>>>>> this causes SEV-ES/SEV-SNP guest failures.
>>>
>>> Hmm, I guess that pretty much kills the idea.  The first post code is
>>> sent before probing for TDX/SEV happens ...
>>
>> Can we salvage it, but make it depend on a minimal source code tweak
>> (ungating)? Changing a single line for debugging (non-TDX / non-SEV-ES
>> guests, anyway) is much easier than coming up with this patch from zero,
>> whenever needed.
>>
>> Can we add "DebugCon.asm" to the tree, plus a *comment* near
>>
>> %include "DebugDisabled.asm"
>>
>> about "DebugCon.asm"?
> 
> Sure, can do that.  I assume the concern about the slowdown is moot if
> this requires an source code patch to be enabled?

Yes, absolutely! Since it's not enabled by default, only for dedicated
debugging sessions, the perf hit (if any) should be fine, IMO.

Laszlo



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#114684): https://edk2.groups.io/g/devel/message/114684
Mute This Topic: https://groups.io/mt/103933942/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



      reply	other threads:[~2024-01-29 11:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 15:31 [edk2-devel] [PATCH 1/1] OvmfPkg/ResetVector: send post codes to qemu debug console Gerd Hoffmann
2024-01-24 16:47 ` Laszlo Ersek
2024-01-24 19:24   ` Lendacky, Thomas via groups.io
2024-01-24 19:55     ` Lendacky, Thomas via groups.io
2024-01-25  1:43       ` Erdem Aktas via groups.io
2024-01-25  7:50         ` Gerd Hoffmann
2024-01-25 19:47           ` Laszlo Ersek
2024-01-26 13:25             ` Gerd Hoffmann
2024-01-29 11:22               ` Laszlo Ersek [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-list 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=afadc5a4-271f-aee2-6247-036b2d8b8298@redhat.com \
    --to=devel@edk2.groups.io \
    /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