From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Alejandro Vallejo <alejandro.garciavallejo@amd.com>
Cc: xen-devel@lists.xenproject.org,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [XTF PATCH v2 2/2] x86: Allow exiting QEMU in TCG/QEMU
Date: Thu, 2 Oct 2025 16:22:36 +0200 [thread overview]
Message-ID: <aN6KrO6LPPJFK17M@Mac.lan> (raw)
In-Reply-To: <20251002135542.28076-3-alejandro.garciavallejo@amd.com>
On Thu, Oct 02, 2025 at 03:55:34PM +0200, Alejandro Vallejo wrote:
> If QEMU has a debug isa-debug-exit device, we can simply write to it
> to exit rather than spinning after a failed hypercall.
>
> While at it, reorder an out-of-order include.
>
> Signed-off-by: Alejandro Vallejo <alejandro.garciavallejo@amd.com>
> ---
> arch/x86/hvm/traps.c | 16 +++++++++++++++-
> arch/x86/pv/traps.c | 5 +++++
> common/lib.c | 2 +-
> common/report.c | 8 +++++---
> include/xtf/framework.h | 3 +++
> 5 files changed, 29 insertions(+), 5 deletions(-)
>
> diff --git a/arch/x86/hvm/traps.c b/arch/x86/hvm/traps.c
> index ad7b8cb..b8c4d0c 100644
> --- a/arch/x86/hvm/traps.c
> +++ b/arch/x86/hvm/traps.c
> @@ -1,5 +1,6 @@
> -#include <xtf/traps.h>
> +#include <xtf/hypercall.h>
> #include <xtf/lib.h>
> +#include <xtf/traps.h>
>
> #include <arch/idt.h>
> #include <arch/lib.h>
> @@ -139,6 +140,19 @@ void arch_init_traps(void)
> virt_to_gfn(__end_user_bss));
> }
>
> +void arch_shutdown(unsigned int reason)
> +{
> + hypercall_shutdown(reason);
This relies on the hypercall page being poised with `ret`, which is
IMO fragile. I would rather have it poisoned with `int3` and prevent
such stray accesses in the first place.
> +
> + /*
> + * Not running under Xen. Attempt exit via the QEMU ISA debug exit device on
> + * its default port.
> + *
> + * QEMU's rc is (reason << 1) | 1, if "-device isa-debug-exit" is set.
> + */
> + outb(reason, 0x501);
That's kind of weird? So even if we pass reason == 0, the exit code
from QEMU will be 1 (and error)?
Isn't there anyway to signal a clean shutdown, and hence QEMU exit
code being 0?
Thanks, Roger.
next prev parent reply other threads:[~2025-10-02 14:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 13:55 [XTF PATCH v2 0/2] Remove Xen as a hard requirement to run XTF Alejandro Vallejo
2025-10-02 13:55 ` [XTF PATCH v2 1/2] x86: " Alejandro Vallejo
2025-10-02 13:55 ` [XTF PATCH v2 2/2] x86: Allow exiting QEMU in TCG/QEMU Alejandro Vallejo
2025-10-02 14:22 ` Roger Pau Monné [this message]
2025-10-02 14:48 ` Alejandro Vallejo
2025-10-02 15:37 ` Roger Pau Monné
2025-10-02 17:48 ` Alejandro Vallejo
2025-10-03 8:06 ` Roger Pau Monné
2025-10-03 9:54 ` Alejandro Vallejo
2025-11-13 9:23 ` [XTF PATCH v2 0/2] Remove Xen as a hard requirement to run XTF Alejandro Vallejo
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=aN6KrO6LPPJFK17M@Mac.lan \
--to=roger.pau@citrix.com \
--cc=alejandro.garciavallejo@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xenproject.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.