From: Peter Xu <peterx@redhat.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Juri Lelli <juri.lelli@redhat.com>, Ming Lei <minlei@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Kernel-managed IRQ affinity (cont)
Date: Mon, 23 Dec 2019 14:18:51 -0500 [thread overview]
Message-ID: <20191223191851.GA90172@xz-x1> (raw)
In-Reply-To: <20191219180917.GA7031@xz-x1>
On Thu, Dec 19, 2019 at 01:09:17PM -0500, Peter Xu wrote:
> On Fri, Dec 20, 2019 at 12:11:15AM +0800, Ming Lei wrote:
> > OK, please try the following patch:
> >
> >
> > diff --git a/include/linux/sched/isolation.h b/include/linux/sched/isolation.h
> > index 6c8512d3be88..0fbcbacd1b29 100644
> > --- a/include/linux/sched/isolation.h
> > +++ b/include/linux/sched/isolation.h
> > @@ -13,6 +13,7 @@ enum hk_flags {
> > HK_FLAG_TICK = (1 << 4),
> > HK_FLAG_DOMAIN = (1 << 5),
> > HK_FLAG_WQ = (1 << 6),
> > + HK_FLAG_MANAGED_IRQ = (1 << 7),
> > };
> >
> > #ifdef CONFIG_CPU_ISOLATION
> > diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
> > index 1753486b440c..0a75a09cc4e8 100644
> > --- a/kernel/irq/manage.c
> > +++ b/kernel/irq/manage.c
> > @@ -20,6 +20,7 @@
> > #include <linux/sched/task.h>
> > #include <uapi/linux/sched/types.h>
> > #include <linux/task_work.h>
> > +#include <linux/sched/isolation.h>
> >
> > #include "internals.h"
> >
> > @@ -212,12 +213,33 @@ int irq_do_set_affinity(struct irq_data *data, const struct cpumask *mask,
> > {
> > struct irq_desc *desc = irq_data_to_desc(data);
> > struct irq_chip *chip = irq_data_get_irq_chip(data);
> > + const struct cpumask *housekeeping_mask =
> > + housekeeping_cpumask(HK_FLAG_MANAGED_IRQ);
> > int ret;
> > + cpumask_var_t tmp_mask;
> >
> > if (!chip || !chip->irq_set_affinity)
> > return -EINVAL;
> >
> > - ret = chip->irq_set_affinity(data, mask, force);
> > + if (!zalloc_cpumask_var(&tmp_mask, GFP_KERNEL))
> > + return -EINVAL;
> > +
> > + /*
> > + * Userspace can't change managed irq's affinity, make sure
> > + * that isolated CPU won't be selected as the effective CPU
> > + * if this irq's affinity includes both isolated CPU and
> > + * housekeeping CPU.
> > + *
> > + * This way guarantees that isolated CPU won't be interrupted
> > + * by IO submitted from housekeeping CPU.
> > + */
> > + if (irqd_affinity_is_managed(data) &&
> > + cpumask_intersects(mask, housekeeping_mask))
> > + cpumask_and(tmp_mask, mask, housekeeping_mask);
> > + else
> > + cpumask_copy(tmp_mask, mask);
> > +
> > + ret = chip->irq_set_affinity(data, tmp_mask, force);
> > switch (ret) {
> > case IRQ_SET_MASK_OK:
> > case IRQ_SET_MASK_OK_DONE:
> > @@ -229,6 +251,8 @@ int irq_do_set_affinity(struct irq_data *data, const struct cpumask *mask,
> > ret = 0;
> > }
> >
> > + free_cpumask_var(tmp_mask);
> > +
> > return ret;
> > }
> >
> > diff --git a/kernel/sched/isolation.c b/kernel/sched/isolation.c
> > index 9fcb2a695a41..008d6ac2342b 100644
> > --- a/kernel/sched/isolation.c
> > +++ b/kernel/sched/isolation.c
> > @@ -163,6 +163,12 @@ static int __init housekeeping_isolcpus_setup(char *str)
> > continue;
> > }
> >
> > + if (!strncmp(str, "managed_irq,", 12)) {
> > + str += 12;
> > + flags |= HK_FLAG_MANAGED_IRQ;
> > + continue;
> > + }
> > +
> > pr_warn("isolcpus: Error, unknown flag\n");
> > return 0;
> > }
>
> Thanks for the quick patch. I'll test after my current round of tests
> finish and update. I'll probably believe this will work for us as
> long as it "functionally" works :) (after all it won't even need a RT
> environment because it's really about where to put some IRQs). So
> IMHO the more important thing is whether such a solution could be
> acceptable by the upstream.
I've tested this patch, it works for us. "isolcpus=managed_irq,2-9"
gives me:
[root@rt-vm 32]# pwd
/proc/irq/32
[root@rt-vm 32]# cat smp_affinity
003
[root@rt-vm 32]# cat effective_affinity
001
Thomas, do you think Ming's solution could be accepted?
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2019-12-23 19:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 19:57 Peter Xu
2019-12-19 8:28 ` Ming Lei
2019-12-19 14:32 ` Peter Xu
2019-12-19 16:11 ` Ming Lei
2019-12-19 18:09 ` Peter Xu
2019-12-23 19:18 ` Peter Xu [this message]
2020-01-09 20:02 ` Thomas Gleixner
2020-01-10 1:28 ` Ming Lei
2020-01-10 19:43 ` Thomas Gleixner
2020-01-11 2:48 ` Ming Lei
2020-01-14 13:45 ` Thomas Gleixner
2020-01-14 23:38 ` Ming Lei
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=20191223191851.GA90172@xz-x1 \
--to=peterx@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=minlei@redhat.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®