All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	George Dunlap <george.dunlap@citrix.com>,
	Julien Grall <julien@xen.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 1/7] x86/smp: do not use shorthand IPI destinations in CPU hot{,un}plug contexts
Date: Wed, 12 Jun 2024 10:09:33 +0200	[thread overview]
Message-ID: <ZmlXve3rV2Vx9bH7@macbook> (raw)
In-Reply-To: <615582c8-c153-424d-bce4-eb0c903d28ad@suse.com>

On Tue, Jun 11, 2024 at 09:42:39AM +0200, Jan Beulich wrote:
> On 10.06.2024 16:20, Roger Pau Monne wrote:
> > Due to the current rwlock logic, if the CPU calling get_cpu_maps() does so from
> > a cpu_hotplug_{begin,done}() region the function will still return success,
> > because a CPU taking the rwlock in read mode after having taken it in write
> > mode is allowed.  Such behavior however defeats the purpose of get_cpu_maps(),
> 
> I'm not happy to see you still have this claim here. The behavior may (appear
> to) defeat the purpose here, but as expressed previously I don't view that as
> being a general pattern.

Right.  What about replacing the paragraph with:

"Due to the current rwlock logic, if the CPU calling get_cpu_maps() does so from
a cpu_hotplug_{begin,done}() region the function will still return success,
because a CPU taking the rwlock in read mode after having taken it in write
mode is allowed.  Such corner case makes using get_cpu_maps() alone
not enough to prevent using the shorthand in CPU hotplug regions."

I think the rest is of the commit message is not controversial.

> > as it should always return false when called with a CPU hot{,un}plug operation
> > is in progress.  Otherwise the logic in send_IPI_mask() is wrong, as it could
> > decide to use the shorthand even when a CPU operation is in progress.
> > 
> > Introduce a new helper to detect whether the current caller is between a
> > cpu_hotplug_{begin,done}() region and use it in send_IPI_mask() to restrict
> > shorthand usage.
> > 
> > Fixes: 5500d265a2a8 ('x86/smp: use APIC ALLBUT destination shorthand when possible')
> > Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> > ---
> > Changes since v1:
> >  - Modify send_IPI_mask() to detect CPU hotplug context.
> > ---
> >  xen/arch/x86/smp.c       |  2 +-
> >  xen/common/cpu.c         |  5 +++++
> >  xen/include/xen/cpu.h    | 10 ++++++++++
> >  xen/include/xen/rwlock.h |  2 ++
> >  4 files changed, 18 insertions(+), 1 deletion(-)
> > 
> > diff --git a/xen/arch/x86/smp.c b/xen/arch/x86/smp.c
> > index 7443ad20335e..04c6a0572319 100644
> > --- a/xen/arch/x86/smp.c
> > +++ b/xen/arch/x86/smp.c
> > @@ -88,7 +88,7 @@ void send_IPI_mask(const cpumask_t *mask, int vector)
> >       * the system have been accounted for.
> >       */
> >      if ( system_state > SYS_STATE_smp_boot &&
> > -         !unaccounted_cpus && !disabled_cpus &&
> > +         !unaccounted_cpus && !disabled_cpus && !cpu_in_hotplug_context() &&
> >           /* NB: get_cpu_maps lock requires enabled interrupts. */
> >           local_irq_is_enabled() && (cpus_locked = get_cpu_maps()) &&
> >           (park_offline_cpus ||
> 
> Along with changing the condition you also want to update the comment to
> reflect the code adjustment.

I've assumed the wording in the commet that says: "no CPU hotplug or
unplug operations are taking place" would already cover the addition
of the !cpu_in_hotplug_context() check.

Thanks, Roger.


  reply	other threads:[~2024-06-12  8:09 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-10 14:20 [PATCH v2 0/7] x86/irq: fixes for CPU hot{,un}plug Roger Pau Monne
2024-06-10 14:20 ` [PATCH v2 1/7] x86/smp: do not use shorthand IPI destinations in CPU hot{,un}plug contexts Roger Pau Monne
2024-06-11  7:42   ` Jan Beulich
2024-06-12  8:09     ` Roger Pau Monné [this message]
2024-06-12  8:56       ` Jan Beulich
2024-06-12 10:07         ` Oleksii K.
2024-06-10 14:20 ` [PATCH v2 2/7] x86/irq: describe how the interrupt CPU movement works Roger Pau Monne
2024-06-11  7:44   ` Jan Beulich
2024-06-12 10:08     ` Oleksii K.
2024-06-10 14:20 ` [PATCH v2 3/7] x86/irq: limit interrupt movement done by fixup_irqs() Roger Pau Monne
2024-06-11  9:59   ` Jan Beulich
2024-06-12  8:10     ` Roger Pau Monné
2024-06-12 10:13     ` Oleksii K.
2024-06-10 14:20 ` [PATCH v2 4/7] x86/irq: restrict CPU movement in set_desc_affinity() Roger Pau Monne
2024-06-11 10:20   ` Jan Beulich
2024-06-12  8:31     ` Roger Pau Monné
2024-06-10 14:20 ` [PATCH v2 5/7] x86/irq: deal with old_cpu_mask for interrupts in movement in fixup_irqs() Roger Pau Monne
2024-06-11 12:45   ` Jan Beulich
2024-06-12  8:47     ` Roger Pau Monné
2024-06-12  9:04       ` Jan Beulich
2024-06-12 10:41         ` Roger Pau Monné
2024-06-11 13:47   ` Jan Beulich
2024-06-12  8:36     ` Roger Pau Monné
2024-06-10 14:20 ` [PATCH v2 6/7] x86/irq: handle moving interrupts in _assign_irq_vector() Roger Pau Monne
2024-06-11 13:18   ` Jan Beulich
2024-06-12 10:39     ` Roger Pau Monné
2024-06-12 13:42       ` Jan Beulich
2024-06-12 15:36         ` Roger Pau Monné
2024-06-13  8:38           ` Jan Beulich
2024-06-13 11:31             ` Roger Pau Monné
2024-06-13 11:36               ` Jan Beulich
2024-06-13 12:55                 ` Roger Pau Monné
2024-06-13 13:07                   ` Jan Beulich
2024-06-10 14:20 ` [PATCH v2 7/7] x86/irq: forward pending interrupts to new destination in fixup_irqs() Roger Pau Monne
2024-06-11 13:50   ` Jan Beulich
2024-06-12 11:23     ` Roger Pau Monné
2024-06-12 13:47       ` 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=ZmlXve3rV2Vx9bH7@macbook \
    --to=roger.pau@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --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 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.