All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Thomas Weißschuh" <thomas@t-8ch.de>
Cc: qemu-devel@nongnu.org, Cornelia Huck <cohuck@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Thomas Huth <thuth@redhat.com>, Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] docs/specs/pvpanic: document shutdown event
Date: Tue, 12 Mar 2024 13:55:28 -0400	[thread overview]
Message-ID: <20240312135414-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240310-pvpanic-shutdown-spec-v1-1-b258e182ce55@t-8ch.de>

On Sun, Mar 10, 2024 at 04:04:51PM +0100, Thomas Weißschuh wrote:
> Shutdown requests are normally hardware dependent.
> By extending pvpanic to also handle shutdown requests, guests can
> submit such requests with an easily implementable and cross-platform
> mechanism.
> 
> Signed-off-by: Thomas Weißschuh <thomas@t-8ch.de>


Okay I merged this to get us out of the bind.
Pls post a fixup patch adding something like (to be implemented)
so people reading this do not become confused.

> ---
> This patch was split out from my earlier pvpanic-shutdown series [0].
> The original series dropped the usage of the linux/pvpanic.h UAPI
> header.
> As we decided to keep the linux header [1] this first commit only adds
> the spec definition.
> Then a patch to Linux will add the new events to linux/pvpanic.h.
> After this the rest of the changes to QEMU will be submitted again.
> 
> [0] https://lore.kernel.org/qemu-devel/20240208-pvpanic-shutdown-v6-0-965580ac057b@t-8ch.de/
> [1] https://lore.kernel.org/lkml/20240213053953-mutt-send-email-mst@kernel.org/
> ---
>  docs/specs/pvpanic.rst | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/docs/specs/pvpanic.rst b/docs/specs/pvpanic.rst
> index f894bc19555f..61a80480edb8 100644
> --- a/docs/specs/pvpanic.rst
> +++ b/docs/specs/pvpanic.rst
> @@ -29,6 +29,8 @@ bit 1
>    a guest panic has happened and will be handled by the guest;
>    the host should record it or report it, but should not affect
>    the execution of the guest.
> +bit 2
> +  a regular guest shutdown has happened and should be processed by the host
>  
>  PCI Interface
>  -------------
> 
> ---
> base-commit: f901bf11b3ddf852e591593b09b8aa7a177f9a0b
> change-id: 20240310-pvpanic-shutdown-spec-4ea2172529e8
> 
> Best regards,
> -- 
> Thomas Weißschuh <thomas@t-8ch.de>



      reply	other threads:[~2024-03-12 17:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-10 15:04 [PATCH] docs/specs/pvpanic: document shutdown event Thomas Weißschuh
2024-03-12 17:55 ` Michael S. Tsirkin [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=20240312135414-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=arnd@arndb.de \
    --cc=cohuck@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thomas@t-8ch.de \
    --cc=thuth@redhat.com \
    /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.