All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Melody (Huibo) Wang" <huibo.wang@amd.com>
To: "Jon Lange" <jlange@microsoft.com>,
	"Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
	"Jörg Rödel" <joro@8bytes.org>,
	coconut-svsm@lists.linux.dev
Subject: Re: Alternate Injection related questions
Date: Tue, 27 May 2025 10:52:13 -0700	[thread overview]
Message-ID: <8dee65f4-24eb-4f33-ac85-59e1101c8a83@amd.com> (raw)
In-Reply-To: <cfdc763b-2c6d-4f80-8fa3-ed8d07994021@amd.com>


Sorry for re-sending this since I had the wrong mailing list in the previous one. 

On 5/27/2025 10:39 AM, Melody (Huibo) Wang wrote:
> Hi Folks,
> 
> I have a few questions, can you please help?
> 
> I found that when an #HV arrives when interrupts are disabled in the SVSM, the #HV handler will postpone the #HV, but the postponing simply returns.
> 
> Who should re-inject this #HV again?
> 
>     postpone_hv:
>            // HV gets postponed
>            popq    %rcx
>            popq    %rbx
>            popq    %rax
>            addq    $8, %rsp
>            iretq
> 
> Is the hypervisor supposed to re-inject the #HV hoping that interrupts will be enabled?
> 
> How is the hypervisor supposed to know whether a #HV which was postponed, was actually handled so that it doesn't inject it again?
> 
> In SVSM code now, the SVSM will read the doorbell page for extended interrupt information without checking even there is a #HV coming in. Why are we doing this? I think this needs to be triggered by a #HV handler instead of reading the doorbell page automatically. Right?
> 
> I have one more question about gdb tool, "https://coconut-svsm.github.io/svsm/installation/INSTALL/#debugging-using-gdb". I tried to use the tool, but it does not work, I have enabled it :
> 
>  "kernel": {
>        "svsm": {
>            "features": "enable-gdb",
> But not able to make it work. This is the log: 
> 
> $ sudo gdb --ex "target extended-remote /dev/pts/4"
> GNU gdb (Ubuntu 15.0.50.20240403-0ubuntu1) 15.0.50.20240403-git
> Copyright (C) 2024 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Type "show copying" and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <https://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
>     <http://www.gnu.org/software/gdb/documentation/>.
> 
> For help, type "help".
> Type "apropos word" to search for commands related to "word".
> Remote debugging using /dev/pts/4
> Ignoring packet error, continuing...
> warning: unrecognized item "timeout" in "qSupported" response
> Ignoring packet error, continuing...
> Ignoring packet error, continuing...
> Remote replied unexpectedly to 'vMustReplyEmpty': timeout
> (gdb) quit
> 
> 
> Thanks,
> Melody
> 


       reply	other threads:[~2025-05-27 17:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cfdc763b-2c6d-4f80-8fa3-ed8d07994021@amd.com>
2025-05-27 17:52 ` Melody (Huibo) Wang [this message]
2025-05-27 18:23   ` [EXTERNAL] Re: Alternate Injection related questions Jon Lange

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=8dee65f4-24eb-4f33-ac85-59e1101c8a83@amd.com \
    --to=huibo.wang@amd.com \
    --cc=Thomas.Lendacky@amd.com \
    --cc=coconut-svsm@lists.linux.dev \
    --cc=jlange@microsoft.com \
    --cc=joro@8bytes.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.