All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Anthony PERARD" <anthony.perard@vates.tech>
To: "Jürgen Groß" <jgross@suse.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2] tools/xl: fix channel configuration setting
Date: Fri, 28 Feb 2025 17:34:17 +0000	[thread overview]
Message-ID: <Z8HzmC4evOxa6yPs@l14> (raw)
In-Reply-To: <e49861d8-2f8f-4747-8d26-59b6defce7c1@suse.com>

On Thu, Feb 27, 2025 at 04:10:25PM +0100, Jürgen Groß wrote:
> On 26.02.25 16:55, Anthony PERARD wrote:
> > On Tue, Feb 25, 2025 at 08:30:33AM +0100, Juergen Gross wrote:
> > > Channels work differently than other device types: their devid should
> > > be -1 initially in order to distinguish them from the primary console
> > > which has the devid of 0.
> > >
> > > So when parsing the channel configuration, use
> > > ARRAY_EXTEND_INIT_NODEVID() in order to avoid overwriting the devid
> > > set by libxl_device_channel_init().
> > >
> > > Signed-off-by: Juergen Gross <jgross@suse.com>
> >
> > This might want a:
> >      Fixes: 3a6679634766 ("libxl: set channel devid when not provided by application")
> >
> > Before that, the devid set by `xl` was probably ignored. I think before,
> > the console devid would be taken from libxl__init_console_from_channel()
> > parametters, so the first devnum would be `0+1`, so never 0.
> >
> > Do you agree?
>
> I'm not sure I do. The use of ARRAY_EXTEND_INIT() in xl_parse.c predates
> commit 3a6679634766, so there is certainly more than one potential Fixes:
> candidate.

Of course, this was my first candidate as well, but that's part of the
original introduction of channel to the source code, so it didn't really
make sense to that the feature was commited with devid=0, surely it
would already been an issue at the time. This is why I start looking
in libxl on how devid was used.

> So at least for the xl case commit 3a6679634766 isn't relevant, and my patch
> is fixing the xl case only.

Last time I check, `xl` is using libxl, so any change to libxl can
impact xl.

Before 3a6679634766, channel#0 would be connected to console#1 because
libxl__init_console_from_channel() was called with dev_num=`channel#+1`,
and $dev_num was used to set console.devid.

After 3a6679634766, we have console.devid=channel.devid=dev_num if
channel.devid is -1, or console.devid=channel.devid.

Without 3a6679634766, having more than one channel with devid=-1 would
result in failing to start due to having more than one channel with the
same devid.

So the only good candidate is:
Fixes: 3a6679634766 ("libxl: set channel devid when not provided by application")


Also, I'm not sure channels are going to work properly if there's more
than one console, lots of code seems to assume
console.devid=channel.devid+1, and there's probably other issues.

Cheers,

--

Anthony Perard | Vates XCP-ng Developer

XCP-ng & Xen Orchestra - Vates solutions

web: https://vates.tech



  reply	other threads:[~2025-02-28 17:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-25  7:30 [PATCH v2] tools/xl: fix channel configuration setting Juergen Gross
2025-02-26 15:55 ` Anthony PERARD
2025-02-27 15:10   ` Jürgen Groß
2025-02-28 17:34     ` Anthony PERARD [this message]
2025-03-03 10:17       ` Jürgen Groß

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=Z8HzmC4evOxa6yPs@l14 \
    --to=anthony.perard@vates.tech \
    --cc=jgross@suse.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.