From: Juergen Gross <jgross@suse.com>
To: Stefano Stabellini <stefano.stabellini@amd.com>,
xen-devel@lists.xenproject.org
Cc: dfaggioli@suse.com, gwd@xenproject.org, jbeulich@suse.com
Subject: Re: [PATCH v2] xen/sched: Fix the sorted insertion in sched_domain_insert_unit()
Date: Tue, 27 Oct 2026 09:52:41 +0100 [thread overview]
Message-ID: <d162cea0-e682-4df9-b13a-82ccdd3a2c5b@suse.com> (raw)
In-Reply-To: <20261026233936.1330117-1-stefano.stabellini@amd.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 684 bytes --]
On 27.10.26 00:39, Stefano Stabellini wrote:
> The loop links the new unit in front of the unit whose successor has a
> higher unit_id, rather than after it: inserting 1 into {0, 2} gives
> {1, 0, 2}. Stop at the first unit with a higher unit_id instead.
>
> This goes unnoticed as long as units are inserted in unit_id order, as
> guest vCPUs typically are.
>
> Also rename prev_unit to next_unit: the new unit is linked in front of
> *next_unit, not after it.
>
> Fixes: 141db7fd4d2d ("xen/sched: build a linked list of struct sched_unit")
> Signed-off-by: Stefano Stabellini <stefano.stabellini@amd.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
prev parent reply other threads:[~2026-10-27 8:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 22:35 [PATCH] xen/sched: Fix the sorted insertion in sched_domain_insert_unit() Stefano Stabellini
2026-10-26 12:46 ` Jan Beulich
2026-10-26 13:15 ` Jürgen Groß
2026-10-26 23:39 ` [PATCH v2] " Stefano Stabellini
2026-10-27 8:52 ` Juergen Gross [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=d162cea0-e682-4df9-b13a-82ccdd3a2c5b@suse.com \
--to=jgross@suse.com \
--cc=dfaggioli@suse.com \
--cc=gwd@xenproject.org \
--cc=jbeulich@suse.com \
--cc=stefano.stabellini@amd.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.