From: John Garry <john.garry@huawei.com>
To: Thomas Gleixner <tglx@linutronix.de>,
<gregkh@linuxfoundation.org>, <rafael@kernel.org>,
<martin.petersen@oracle.com>, <jejb@linux.ibm.com>
Cc: <linuxarm@huawei.com>, <linux-scsi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <maz@kernel.org>
Subject: Re: [PATCH v2 1/3] genirq/affinity: Add irq_update_affinity_desc()
Date: Wed, 18 Nov 2020 11:34:27 +0000 [thread overview]
Message-ID: <78356caa-57a0-b807-fe52-8f12d36c1789@huawei.com> (raw)
In-Reply-To: <87ft57r7v3.fsf@nanos.tec.linutronix.de>
Hi Thomas,
>
> Sorry for the delay.
No worries, Thanks for the effort.
> Supporting this truly on x86 needs some more
> thought and surgery, but for ARM it should not matter.
ok, as long as you are content not to support x86 atm.
> I made a few
> tweaks to your original code. See below.
I think maybe a few more tweaks, below. Apart from that, it looks to
work ok.
>
> Thanks,
>
> tglx
> ---
> From: John Garry <john.garry@huawei.com>
> Subject: genirq/affinity: Add irq_update_affinity_desc()
> Date: Wed, 28 Oct 2020 20:33:05 +0800
>
> From: John Garry <john.garry@huawei.com>
>
> Add a function to allow the affinity of an interrupt be switched to
> managed, such that interrupts allocated for platform devices may be
> managed.
>
> Suggested-by: Thomas Gleixner <tglx@linutronix.de>
> Signed-off-by: John Garry <john.garry@huawei.com>
> ---
> include/linux/interrupt.h | 8 ++++++
> kernel/irq/manage.c | 56 ++++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 64 insertions(+)
>
...
> +/**
> + * irq_update_affinity_desc - Update affinity management for an interrupt
> + * @irq: The interrupt number to update
> + * @affinity: Pointer to the affinity descriptor
> + *
> + * This interface can be used to configure the affinity management of
> + * interrupts which have been allocated already.
> + */
> +int irq_update_affinity_desc(unsigned int irq,
> + struct irq_affinity_desc *affinity)
Just a note on the return value, in the only current callsite -
platform_get_irqs_affinity() - we don't check the return value and
propagate the error. This is because we don't want to fail the interrupt
init just because of problems updating the affinity mask. So I could
print a message to inform the user of error (at the callsite).
> +{
> + struct irq_desc *desc;
> + unsigned long flags;
> + bool activated;
> +
> + /*
> + * Supporting this with the reservation scheme used by x86 needs
> + * some more thought. Fail it for now.
> + */
> + if (IS_ENABLED(CONFIG_GENERIC_IRQ_RESERVATION_MODE))
> + return -EOPNOTSUPP;
> +
> + desc = irq_get_desc_buslock(irq, &flags, 0);
> + if (!desc)
> + return -EINVAL;
> +
> + /* Requires the interrupt to be shut down */
> + if (irqd_is_started(&desc->irq_data))
We're missing the unlock here, right?
> + return -EBUSY;
> +
> + /* Interrupts which are already managed cannot be modified */
> + if (irqd_is_managed(&desc->irq_data))
And here, and I figure that this should be irqd_affinity_is_managed()
> + return -EBUSY;
> +
> + /*
> + * Deactivate the interrupt. That's required to undo
> + * anything an earlier activation has established.
> + */
> + activated = irqd_is_activated(&desc->irq_data);
> + if (activated)
> + irq_domain_deactivate_irq(&desc->irq_data);
> +
> + if (affinity->is_managed) {
> + irqd_set(&desc->irq_data, IRQD_AFFINITY_MANAGED);
> + irqd_set(&desc->irq_data, IRQD_MANAGED_SHUTDOWN);
> + }
> +
> + cpumask_copy(desc->irq_common_data.affinity, &affinity->mask);
> +
> + /* Restore the activation state */
> + if (activated)
> + irq_domain_deactivate_irq(&desc->irq_data);
> + irq_put_desc_busunlock(desc, flags);
> + return 0;
> +}
> +
> int __irq_set_affinity(unsigned int irq, const struct cpumask *mask, bool force)
> {
> struct irq_desc *desc = irq_to_desc(irq);
> .
>
Thanks,
John
next prev parent reply other threads:[~2020-11-18 11:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 12:33 [PATCH v2 0/3] Support managed interrupts for platform devices John Garry
2020-10-28 12:33 ` [PATCH v2 1/3] genirq/affinity: Add irq_update_affinity_desc() John Garry
2020-10-28 18:22 ` Thomas Gleixner
2020-11-02 17:32 ` John Garry
2020-11-02 20:35 ` Thomas Gleixner
2020-11-17 21:28 ` Thomas Gleixner
2020-11-18 11:34 ` John Garry [this message]
2020-11-18 20:38 ` Thomas Gleixner
2020-11-19 9:31 ` John Garry
2020-11-19 18:09 ` Thomas Gleixner
2020-11-19 19:56 ` John Garry
2020-11-19 21:03 ` Thomas Gleixner
2020-11-20 11:52 ` John Garry
2020-11-22 13:38 ` Marc Zyngier
2020-11-23 12:54 ` John Garry
2020-11-23 13:26 ` Marc Zyngier
2020-11-23 15:45 ` John Garry
2020-11-24 16:51 ` Marc Zyngier
2020-11-24 17:38 ` John Garry
2020-11-25 18:35 ` Marc Zyngier
2020-11-26 10:47 ` John Garry
2020-11-26 11:08 ` Marc Zyngier
2020-11-26 11:29 ` John Garry
2020-11-26 16:52 ` John Garry
2020-11-27 9:57 ` Marc Zyngier
2020-11-27 12:45 ` John Garry
2020-11-27 12:49 ` Marc Zyngier
2020-10-28 12:33 ` [PATCH v2 2/3] Driver core: platform: Add platform_get_irqs_affinity() John Garry
2020-10-28 12:33 ` [PATCH v2 3/3] scsi: hisi_sas: Expose HW queues for v2 hw John Garry
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=78356caa-57a0-b807-fe52-8f12d36c1789@huawei.com \
--to=john.garry@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=maz@kernel.org \
--cc=rafael@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).