From: "Jürgen Groß" <jgross@suse.com>
To: Jason Andryuk <jason.andryuk@amd.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] xen/events: Return -EEXIST for bound VIRQs
Date: Wed, 27 Aug 2025 17:21:19 +0200 [thread overview]
Message-ID: <2d7bceff-d70f-4f17-b833-380ffc06577e@suse.com> (raw)
In-Reply-To: <20250826005517.41547-3-jason.andryuk@amd.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 2766 bytes --]
On 26.08.25 02:55, Jason Andryuk wrote:
> Change find_virq() to return -EEXIST when a VIRQ is bound to a
> different CPU than the one passed in. With that, remove the BUG_ON()
> from bind_virq_to_irq() to propogate the error upwards.
>
> Some VIRQs are per-cpu, but others are per-domain or global. Those must
> be bound to CPU0 and can then migrate elsewhere. The lookup for
> per-domain and global will probably fail when migrated off CPU 0,
> especially when the current CPU is tracked. This now returns -EEXIST
> instead of BUG_ON().
>
> A second call to bind a per-domain or global VIRQ is not expected, but
> make it non-fatal to avoid trying to look up the irq, since we don't
> know which per_cpu(virq_to_irq) it will be in.
>
> Signed-off-by: Jason Andryuk <jason.andryuk@amd.com>
> ---
> V2:
> New
> ---
> drivers/xen/events/events_base.c | 17 ++++++++++++-----
> 1 file changed, 12 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/xen/events/events_base.c b/drivers/xen/events/events_base.c
> index 199afe59f357..a85bc43f4344 100644
> --- a/drivers/xen/events/events_base.c
> +++ b/drivers/xen/events/events_base.c
> @@ -1314,10 +1314,12 @@ int bind_interdomain_evtchn_to_irq_lateeoi(struct xenbus_device *dev,
> }
> EXPORT_SYMBOL_GPL(bind_interdomain_evtchn_to_irq_lateeoi);
>
> -static int find_virq(unsigned int virq, unsigned int cpu, evtchn_port_t *evtchn)
> +static int find_virq(unsigned int virq, unsigned int cpu, evtchn_port_t *evtchn,
> + bool percpu)
> {
> struct evtchn_status status;
> evtchn_port_t port;
> + bool exists = false;
> int rc;
>
> memset(&status, 0, sizeof(status));
> @@ -1329,12 +1331,16 @@ static int find_virq(unsigned int virq, unsigned int cpu, evtchn_port_t *evtchn)
> continue;
> if (status.status != EVTCHNSTAT_virq)
> continue;
> - if (status.u.virq == virq && status.vcpu == xen_vcpu_nr(cpu)) {
> + if (status.u.virq != virq)
> + continue;
> + if (status.vcpu == xen_vcpu_nr(cpu)) {
> *evtchn = port;
> return 0;
> + } else if (!percpu) {
> + exists = true;
> }
> }
> - return -ENOENT;
> + return exists ? -EEXIST : -ENOENT;
> }
>
> /**
> @@ -1381,8 +1387,9 @@ int bind_virq_to_irq(unsigned int virq, unsigned int cpu, bool percpu)
> evtchn = bind_virq.port;
> else {
> if (ret == -EEXIST)
> - ret = find_virq(virq, cpu, &evtchn);
> - BUG_ON(ret < 0);
> + ret = find_virq(virq, cpu, &evtchn, percpu);
> + if (ret)
> + goto out;
I think you are leaking info here. I guess a call of __unbind_from_irq() is
wanted like in the error case below (note that the case of no valid evtchn is
handled there just fine).
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2025-08-27 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 0:55 [PATCH v2 0/3] xen/events: Fix Global and Domain VIRQ tracking Jason Andryuk
2025-08-26 0:55 ` [PATCH v2 1/3] xen/events: Cleanup find_virq() return codes Jason Andryuk
2025-08-26 7:22 ` Jan Beulich
2025-08-26 15:03 ` Jason Andryuk
2025-08-27 15:16 ` Jürgen Groß
2025-08-26 0:55 ` [PATCH v2 2/3] xen/events: Return -EEXIST for bound VIRQs Jason Andryuk
2025-08-27 15:21 ` Jürgen Groß [this message]
2025-08-27 22:11 ` Jason Andryuk
2025-08-26 0:55 ` [PATCH v2 3/3] xen/events: Update virq_to_irq on migration Jason Andryuk
2025-08-27 15:28 ` Jürgen Groß
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=2d7bceff-d70f-4f17-b833-380ffc06577e@suse.com \
--to=jgross@suse.com \
--cc=jason.andryuk@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr_tyshchenko@epam.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 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®