From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Oleksii Kurochko <oleksii.kurochko@gmail.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH for-4.19] xen/x86: limit interrupt movement done by fixup_irqs()
Date: Thu, 16 May 2024 18:23:53 +0200 [thread overview]
Message-ID: <ZkYzGZ3tDg9dRbnF@macbook> (raw)
In-Reply-To: <b77790c6-a5b5-40d9-9387-5101ace14a4c@suse.com>
On Thu, May 16, 2024 at 06:04:22PM +0200, Jan Beulich wrote:
> On 16.05.2024 17:56, Roger Pau Monné wrote:
> > On Thu, May 16, 2024 at 05:00:54PM +0200, Jan Beulich wrote:
> >> On 16.05.2024 15:22, Roger Pau Monne wrote:
> >>> @@ -2576,7 +2576,12 @@ void fixup_irqs(const cpumask_t *mask, bool verbose)
> >>> release_old_vec(desc);
> >>> }
> >>>
> >>> - if ( !desc->action || cpumask_subset(desc->affinity, mask) )
> >>> + /*
> >>> + * Avoid shuffling the interrupt around if it's assigned to a CPU set
> >>> + * that's all covered by the requested affinity mask.
> >>> + */
> >>> + cpumask_and(affinity, desc->arch.cpu_mask, &cpu_online_map);
> >>> + if ( !desc->action || cpumask_subset(affinity, mask) )
> >>> {
> >>> spin_unlock(&desc->lock);
> >>> continue;
> >>[...]
> >> In
> >> which case cpumask_subset() is going to always return true with your
> >> change in place, if I'm not mistaken. That seems to make your change
> >> questionable. Yet with that I guess I'm overlooking something.)
> >
> > I might we wrong, but I think you are missing that the to be offlined
> > CPU has been removed from cpu_online_map by the time it gets passed
> > to fixup_irqs().
>
> Just on this part (I'll need to take more time to reply to other parts):
> No, I've specifically paid attention to that fact. Yet for this particular
> observation of mine is doesn't matter. If mask == &cpu_online_map, then
> no matter what is in cpu_online_map
>
> cpumask_and(affinity, desc->arch.cpu_mask, &cpu_online_map);
>
> will mask things down to a subset of cpu_online_map, and hence
>
> if ( !desc->action || cpumask_subset(affinity, mask) )
>
> (effectively being
>
> if ( !desc->action || cpumask_subset(affinity, &cpu_online_map) )
>
> ) is nothing else than
>
> if ( !desc->action || true )
>
> . Yet that doesn't feel quite right.
Oh, I get it now. Ideally we would use cpu_online_map with the to be
removed CPU set, but that's complicated in this context.
For the purposes here we might as well avoid the AND of
->arch.cpu_mask with cpu_online_map and just check:
if ( !desc->action || cpumask_subset(desc->arch.cpu_mask, mask) )
As even if ->arch.cpu_mask has non-online CPUs set aside from the to
be offlined CPU, it would just mean that we might be shuffling more
than strictly necessary. Note this will only be an issue with cluster
mode, physical mode must always have a single online CPU set in
->arch.cpu_mask.
Thanks, Roger.
next prev parent reply other threads:[~2024-05-16 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 13:22 [PATCH for-4.19] xen/x86: limit interrupt movement done by fixup_irqs() Roger Pau Monne
2024-05-16 15:00 ` Jan Beulich
2024-05-16 15:56 ` Roger Pau Monné
2024-05-16 16:04 ` Jan Beulich
2024-05-16 16:23 ` Roger Pau Monné [this message]
2024-05-21 9:37 ` Jan Beulich
2024-05-21 9:46 ` Jan Beulich
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=ZkYzGZ3tDg9dRbnF@macbook \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=oleksii.kurochko@gmail.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.