From: Oleksii Kurochko <oleksii.kurochko@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Alistair Francis" <alistair.francis@wdc.com>,
"Bob Eshleman" <bobbyeshleman@gmail.com>,
"Connor Davis" <connojdavis@gmail.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Romain Caritey" <Romain.Caritey@microchip.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v1 12/14] xen/riscv: implement setup_irq()
Date: Thu, 17 Apr 2025 12:10:29 +0200 [thread overview]
Message-ID: <7b1f5d89-2be9-450f-a4db-381df42942e6@gmail.com> (raw)
In-Reply-To: <47492663-5832-49e7-af4d-ee536206e641@suse.com>
[-- Attachment #1: Type: text/plain, Size: 2573 bytes --]
On 4/15/25 5:55 PM, Jan Beulich wrote
>> +#ifdef CONFIG_IRQ_HAS_MULTIPLE_ACTION
>> + new->next = desc->action;
>> + smp_mb();
>> +#endif
>> +
>> + desc->action = new;
>> + smp_mb();
> Aren't smp_wmb() sufficient on both places? If not, I think comments
> want adding.
smp_wmb() will be sufficient but I think the barrier could be dropped at all
as __setup_irq() is called only in setup_irq() and __setup_irq() call is wrapped
by spinlock_{un}lock_irqsave() where spinlock_unlock_*() will put barrier.
>
>> + return 0;
>> +}
>> +
>> +void irq_set_affinity(struct irq_desc *desc, const cpumask_t *cpu_mask)
>> +{
>> + if ( desc != NULL )
> Can desc really be NULL here?
It can't as irq_desc[] isn't dynamically allocated.
> Isn't desc->lock required to be held?
It is and it is called in setup_irq() which calls spin_lock_irqsave().
Anyway, I think it could be dropped at all and use 'desc->handler->set_affinity(desc, cpu_mask);'
explicitly in setup_irq().
>> + spin_lock_irqsave(&desc->lock, flags);
>> +
>> + disabled = (desc->action == NULL);
>> +
>> + if ( test_bit(_IRQ_GUEST, &desc->status) )
>> + {
>> + spin_unlock_irqrestore(&desc->lock, flags);
>> + /*
>> + * TODO: would be nice to have functionality to print which domain owns
>> + * an IRQ.
>> + */
>> + printk(XENLOG_ERR "ERROR: IRQ %u is already in use by a domain\n", irq);
>> + return -EBUSY;
>> + }
>> +
>> + rc = __setup_irq(desc, irqflags, new);
>> + if ( rc )
>> + goto err;
>> +
>> + /* First time the IRQ is setup */
>> + if ( disabled )
>> + {
>> + /* disable irq by default */
>> + set_bit(_IRQ_DISABLED, &desc->status);
> Shouldn't this be set when we make it here?
It should be. I'll drop the setting of _IRQ_DISABLED.
>
>> + /* route interrupt to xen */
>> + intc_route_irq_to_xen(desc, IRQ_NO_PRIORITY);
>> +
>> + /*
>> + * we don't care for now which CPU will receive the
>> + * interrupt
>> + *
>> + * TODO: Handle case where IRQ is setup on different CPU than
>> + * the targeted CPU and the priority.
>> + */
>> + irq_set_affinity(desc, cpumask_of(smp_processor_id()));
>> + desc->handler->startup(desc);
>> + /* enable irq */
>> + clear_bit(_IRQ_DISABLED, &desc->status);
> Now it turns out this is really done twice: Once in aplic_irq_enable(),
> and once here.
Agree, this is a job of *_startup()->*_aplic_irq_enable(). I'll drop that too.
~ Oleksii
[-- Attachment #2: Type: text/html, Size: 4051 bytes --]
next prev parent reply other threads:[~2025-04-17 10:10 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 15:57 [PATCH v1 00/14] riscv: introduce basic UART support and interrupts for hypervisor mode Oleksii Kurochko
2025-04-08 15:57 ` [PATCH v1 01/14] xen/riscv: implement get_s_time() Oleksii Kurochko
2025-04-10 12:52 ` Jan Beulich
2025-04-14 14:50 ` Oleksii Kurochko
2025-04-08 15:57 ` [PATCH v1 02/14] xen/riscv: introduce smp_clear_cpu_maps() Oleksii Kurochko
2025-04-10 13:10 ` Jan Beulich
2025-04-14 15:05 ` Oleksii Kurochko
2025-04-14 15:13 ` Jan Beulich
2025-04-08 15:57 ` [PATCH v1 03/14] xen/riscv: introduce ioremap() Oleksii Kurochko
2025-04-10 15:13 ` Jan Beulich
2025-04-15 10:29 ` Oleksii Kurochko
2025-04-15 11:02 ` Jan Beulich
2025-04-17 14:20 ` Oleksii Kurochko
2025-04-17 14:24 ` Jan Beulich
2025-04-17 14:37 ` Oleksii Kurochko
2025-04-17 14:49 ` Jan Beulich
2025-04-22 8:40 ` Oleksii Kurochko
2025-04-22 9:14 ` Jan Beulich
2025-04-24 13:30 ` Oleksii Kurochko
2025-04-08 15:57 ` [PATCH v1 04/14] xen/riscv: introduce init_IRQ() Oleksii Kurochko
2025-04-10 15:25 ` Jan Beulich
2025-04-15 10:36 ` Oleksii Kurochko
2025-04-08 15:57 ` [PATCH v1 05/14] xen/riscv: introduce platform_get_irq() Oleksii Kurochko
2025-04-10 15:35 ` Jan Beulich
2025-04-15 11:11 ` Oleksii Kurochko
2025-04-15 11:23 ` Jan Beulich
2025-04-17 14:43 ` Oleksii Kurochko
2025-04-08 15:57 ` [PATCH v1 06/14] xen/riscv: riscv_of_processor_hartid() implementation Oleksii Kurochko
2025-04-10 15:53 ` Jan Beulich
2025-04-15 13:39 ` Oleksii Kurochko
2025-04-15 13:45 ` Jan Beulich
2025-04-25 17:07 ` Oleksii Kurochko
2025-04-28 6:31 ` Jan Beulich
2025-04-28 10:43 ` Oleksii Kurochko
2025-04-28 11:09 ` Jan Beulich
2025-04-08 15:57 ` [PATCH v1 07/14] xen/riscv: Introduce intc_hw_operations abstraction Oleksii Kurochko
2025-04-10 16:02 ` Jan Beulich
2025-04-15 15:01 ` Oleksii Kurochko
2025-04-08 15:57 ` [PATCH v1 08/14] xen/riscv: imsic_init() implementation Oleksii Kurochko
2025-04-14 9:32 ` Jan Beulich
2025-04-15 19:11 ` Oleksii Kurochko
[not found] ` <9a13c625-cd33-485d-a91f-9f005522b5a4@suse.com>
2025-04-23 11:44 ` Oleksii Kurochko
2025-04-29 8:24 ` Oleksii Kurochko
2025-04-08 15:57 ` [PATCH v1 09/14] xen/riscv: aplic_init() implementation Oleksii Kurochko
2025-04-14 10:04 ` Jan Beulich
2025-04-16 10:15 ` Oleksii Kurochko
2025-04-16 10:30 ` Jan Beulich
2025-04-17 15:21 ` Oleksii Kurochko
2025-04-17 15:30 ` Jan Beulich
2025-04-18 11:31 ` Oleksii Kurochko
2025-04-08 15:57 ` [PATCH v1 10/14] xen/riscv: implementation of aplic and imsic operations Oleksii Kurochko
2025-04-15 12:46 ` Jan Beulich
2025-04-16 19:05 ` Oleksii Kurochko
2025-04-17 6:25 ` Jan Beulich
2025-04-28 8:12 ` Oleksii Kurochko
2025-04-28 8:54 ` Jan Beulich
2025-04-30 16:07 ` Oleksii Kurochko
2025-04-15 14:53 ` Jan Beulich
2025-04-18 10:43 ` Oleksii Kurochko
2025-04-22 7:02 ` Jan Beulich
2025-04-25 19:31 ` Oleksii Kurochko
2025-04-28 6:35 ` Jan Beulich
2025-04-08 15:57 ` [PATCH v1 11/14] xen/riscv: add external interrupt handling for hypervisor mode Oleksii Kurochko
2025-04-15 14:42 ` Jan Beulich
2025-04-17 8:44 ` Oleksii Kurochko
2025-04-17 9:13 ` Oleksii Kurochko
2025-04-08 15:57 ` [PATCH v1 12/14] xen/riscv: implement setup_irq() Oleksii Kurochko
2025-04-15 15:55 ` Jan Beulich
2025-04-17 10:10 ` Oleksii Kurochko [this message]
2025-04-17 11:51 ` Jan Beulich
2025-04-08 15:57 ` [PATCH v1 13/14] xen/riscv: initialize interrupt controller Oleksii Kurochko
2025-04-15 15:59 ` Jan Beulich
2025-04-17 10:11 ` Oleksii Kurochko
2025-04-30 15:34 ` Oleksii Kurochko
2025-04-30 15:39 ` Jan Beulich
2025-04-08 15:57 ` [PATCH v1 14/14] xen/riscv: add basic UART support Oleksii Kurochko
2025-04-15 16:03 ` Jan Beulich
2025-04-17 10:31 ` Oleksii Kurochko
2025-04-17 11:52 ` 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=7b1f5d89-2be9-450f-a4db-381df42942e6@gmail.com \
--to=oleksii.kurochko@gmail.com \
--cc=Romain.Caritey@microchip.com \
--cc=alistair.francis@wdc.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=bobbyeshleman@gmail.com \
--cc=connojdavis@gmail.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--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.