From: "Arnd Bergmann" <arnd@arndb.de>
To: "Thomas Weißschuh" <linux@weissschuh.net>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, "Zhangjin Wu" <falcon@tinylab.org>,
"Willy Tarreau" <w@1wt.eu>, "Yuan Tan" <tanyuan@tinylab.org>
Subject: Re: [PATCH RFC] misc/pvpanic: add support for normal shutdowns
Date: Wed, 28 Feb 2024 08:02:15 +0100 [thread overview]
Message-ID: <200055c2-30a2-4b3a-a102-abacda522c22@app.fastmail.com> (raw)
In-Reply-To: <ae7a35e9-16f6-4877-8075-a0fb9fe5bfff@t-8ch.de>
On Wed, Feb 28, 2024, at 07:48, Thomas Weißschuh wrote:
> Hi Michael,
>
> On 2024-02-13 05:41:48-0500, Michael S. Tsirkin wrote:
>> On Sat, Nov 04, 2023 at 02:05:02PM +0100, Greg Kroah-Hartman wrote:
>> > > diff --git a/include/uapi/misc/pvpanic.h b/include/uapi/misc/pvpanic.h
>> > > index 54b7485390d3..82fc618bfbcf 100644
>> > > --- a/include/uapi/misc/pvpanic.h
>> > > +++ b/include/uapi/misc/pvpanic.h
>> > > @@ -5,5 +5,6 @@
>> > >
>> > > #define PVPANIC_PANICKED (1 << 0)
>> > > #define PVPANIC_CRASH_LOADED (1 << 1)
>> > > +#define PVPANIC_SHUTDOWN (1 << 2)
>> >
>> > Why are these in a uapi file?
>> >
>> > And if they need to be here, why not use the proper BIT() macro for it?
>> >
>>
>> This is interface with hypervisor not userspace, but for PV historically
>> we do this since the compatibility implications are about the same,
>> hypervisors (e.g. QEMU) are mostly userspace and so it is convenient for
>> them to reuse the same machinery to export the headers.
>>
>> Let's stick to that, cleaner than duplicating everything I think.
>
> as Greg seems to be busy with other stuff I'd like to go ahead with
> submitting this again using the existing header file.
FWIW, I agree using the uapi header for APIs shared between
kernel and qemu is fine, and we don't really have any other
place for those, so please add
Acked-by: Arnd Bergmann <arnd@arndb.de>
prev parent reply other threads:[~2024-02-28 7:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 11:29 Thomas Weißschuh
2023-11-04 13:05 ` Greg Kroah-Hartman
2023-11-04 13:16 ` Thomas Weißschuh
2023-11-04 13:28 ` Greg Kroah-Hartman
2023-11-04 13:53 ` Thomas Weißschuh
2023-11-04 13:56 ` Willy Tarreau
2023-11-04 17:07 ` Greg Kroah-Hartman
2023-11-04 17:32 ` Thomas Weißschuh
2023-11-05 6:59 ` Willy Tarreau
2024-02-13 10:41 ` Michael S. Tsirkin
2024-02-21 17:18 ` Thomas Weißschuh
2024-02-28 6:48 ` Thomas Weißschuh
2024-02-28 7:02 ` Arnd Bergmann [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=200055c2-30a2-4b3a-a102-abacda522c22@app.fastmail.com \
--to=arnd@arndb.de \
--cc=falcon@tinylab.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=mst@redhat.com \
--cc=tanyuan@tinylab.org \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®