LKML Archive on lore.kernel.org
 help / Atom feed
From: Song Liu <liu.song.a23@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Borislav Petkov <bp@alien8.de>,
	Dmitry Safonov <0x7f454c46@gmail.com>,
	Tariq Toukan <tariqt@mellanox.com>,
	Joerg Roedel <jroedel@suse.de>, Mike Travis <mike.travis@hpe.com>,
	stable@vger.kernel.org
Subject: Re: [patch 7/8] genirq/affinity: Defer affinity setting if irq chip is busy
Date: Tue, 5 Jun 2018 00:14:09 -0700
Message-ID: <CAPhsuW577-zethODoH2a_Z6PVZkhRPu+a7bgL2ZGpYiBNcEwpQ@mail.gmail.com> (raw)
In-Reply-To: <20180604162224.819273597@linutronix.de>

On Mon, Jun 4, 2018 at 8:33 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> The case that interrupt affinity setting fails with -EBUSY can be handled
> in the kernel completely by using the already available generic pending
> infrastructure.
>
> If a irq_chip::set_affinity() fails with -EBUSY, handle it like the
> interrupts for which irq_chip::set_affinity() can only be invoked from
> interrupt context. Copy the new affinity mask to irq_desc::pending_mask and
> set the affinity pending bit. The next raised interrupt for the affected
> irq will check the pending bit and try to set the new affinity from the
> handler. This avoids that -EBUSY is returned when an affinity change is
> requested from user space and the previous change has not been cleaned
> up. The new affinity will take effect when the next interrupt is raised
> from the device.
>
> Fixes: dccfe3147b42 ("x86/vector: Simplify vector move cleanup")
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Cc: stable@vger.kernel.org

Tested-by: Song Liu <songliubraving@fb.com>

> ---
>  kernel/irq/manage.c |   37 +++++++++++++++++++++++++++++++++++--
>  1 file changed, 35 insertions(+), 2 deletions(-)
>
> --- a/kernel/irq/manage.c
> +++ b/kernel/irq/manage.c
> @@ -204,6 +204,39 @@ int irq_do_set_affinity(struct irq_data
>         return ret;
>  }
>
> +#ifdef CONFIG_GENERIC_PENDING_IRQ
> +static inline int irq_set_affinity_pending(struct irq_data *data,
> +                                          const struct cpumask *dest)
> +{
> +       struct irq_desc *desc = irq_data_to_desc(data);
> +
> +       irqd_set_move_pending(data);
> +       irq_copy_pending(desc, dest);
> +       return 0;
> +}
> +#else
> +static inline int irq_set_affinity_pending(struct irq_data *data,
> +                                          const struct cpumask *dest)
> +{
> +       return -EBUSY;
> +}
> +#endif
> +
> +static int irq_try_set_affinity(struct irq_data *data,
> +                               const struct cpumask *dest, bool force)
> +{
> +       int ret = irq_do_set_affinity(data, dest, force);
> +
> +       /*
> +        * In case that the underlying vector management is busy and the
> +        * architecture supports the generic pending mechanism then utilize
> +        * this to avoid returning an error to user space.
> +        */
> +       if (ret == -EBUSY && !force)
> +               ret = irq_set_affinity_pending(data, dest);
> +       return ret;
> +}
> +
>  int irq_set_affinity_locked(struct irq_data *data, const struct cpumask *mask,
>                             bool force)
>  {
> @@ -214,8 +247,8 @@ int irq_set_affinity_locked(struct irq_d
>         if (!chip || !chip->irq_set_affinity)
>                 return -EINVAL;
>
> -       if (irq_can_move_pcntxt(data)) {
> -               ret = irq_do_set_affinity(data, mask, force);
> +       if (irq_can_move_pcntxt(data) && !irqd_is_setaffinity_pending(data)) {
> +               ret = irq_try_set_affinity(data, mask, force);
>         } else {
>                 irqd_set_move_pending(data);
>                 irq_copy_pending(desc, mask);
>
>

  reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-04 15:33 Thomas Gleixner
2018-06-05  7:14 ` Song Liu [this message]
2018-06-06 13:34 ` [tip:x86/urgent] " tip-bot for Thomas Gleixner

Reply instructions:

You may reply publically 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=CAPhsuW577-zethODoH2a_Z6PVZkhRPu+a7bgL2ZGpYiBNcEwpQ@mail.gmail.com \
    --to=liu.song.a23@gmail.com \
    --cc=0x7f454c46@gmail.com \
    --cc=bp@alien8.de \
    --cc=jroedel@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.travis@hpe.com \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=stable@vger.kernel.org \
    --cc=tariqt@mellanox.com \
    --cc=tglx@linutronix.de \
    /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

LKML Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/lkml/0 lkml/git/0.git
	git clone --mirror https://lore.kernel.org/lkml/1 lkml/git/1.git
	git clone --mirror https://lore.kernel.org/lkml/2 lkml/git/2.git
	git clone --mirror https://lore.kernel.org/lkml/3 lkml/git/3.git
	git clone --mirror https://lore.kernel.org/lkml/4 lkml/git/4.git
	git clone --mirror https://lore.kernel.org/lkml/5 lkml/git/5.git
	git clone --mirror https://lore.kernel.org/lkml/6 lkml/git/6.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 lkml lkml/ https://lore.kernel.org/lkml \
		linux-kernel@vger.kernel.org linux-kernel@archiver.kernel.org
	public-inbox-index lkml


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-kernel


AGPL code for this site: git clone https://public-inbox.org/ public-inbox