From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jiri Slaby <jirislaby@kernel.org>,
Jason Andryuk <jason.andryuk@amd.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, xen-devel@lists.xenproject.org
Subject: Re: [PATCH] hvc/xen: Check console connection flag
Date: Fri, 13 Mar 2026 10:44:06 +0000 [thread overview]
Message-ID: <ff1cce61-abb4-463d-adce-0e5fc0a326df@citrix.com> (raw)
In-Reply-To: <8e5974b1-da6d-4718-9140-1f943cdd2404@kernel.org>
On 13/03/2026 8:33 am, Jiri Slaby wrote:
> On 12. 03. 26, 18:38, Jason Andryuk wrote:
>> --- a/include/xen/interface/io/console.h
>> +++ b/include/xen/interface/io/console.h
>> @@ -19,6 +19,19 @@ struct xencons_interface {
>> char out[2048];
>> XENCONS_RING_IDX in_cons, in_prod;
>> XENCONS_RING_IDX out_cons, out_prod;
>> +/*
>> + * Flag values signaling from backend to frontend whether the
>> console is
>> + * connected. i.e. Whether it will be serviced and emptied.
>> + *
>> + * The flag starts as disconnected.
>> + */
>> +#define XENCONSOLE_DISCONNECTED 1
>> +/*
>> + * The flag is set to connected when the backend connects and the
>> console
>> + * will be serviced.
>> + */
>> +#define XENCONSOLE_CONNECTED 0
>
> This all should be an enum. And you can document it using kernel-doc
> properly then.
>
>> + uint8_t connection;
>
> And type check as well.
This is a non-Linux header file being re-sync'd with it's original source.
It describes an ABI between VMs, where things like enum are forbidden.
~Andrew
next prev parent reply other threads:[~2026-03-13 10:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 17:38 [PATCH] hvc/xen: Check console connection flag Jason Andryuk
2026-03-13 8:33 ` Jiri Slaby
2026-03-13 10:44 ` Andrew Cooper [this message]
2026-03-13 15:36 ` Jason Andryuk
2026-03-13 22:35 ` Stefano Stabellini
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=ff1cce61-abb4-463d-adce-0e5fc0a326df@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=gregkh@linuxfoundation.org \
--cc=jason.andryuk@amd.com \
--cc=jgross@suse.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oleksandr_tyshchenko@epam.com \
--cc=sstabellini@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox