From: Juergen Gross <jgross@suse.com>
To: Jason Andryuk <jason.andryuk@amd.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Cc: stable@vger.kernel.org, xen-devel@lists.xenproject.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] xen/events: Return -EEXIST for bound VIRQs
Date: Tue, 2 Sep 2025 15:35:43 +0200 [thread overview]
Message-ID: <c8cf8f4b-b83a-4274-aeca-a443b2745a22@suse.com> (raw)
In-Reply-To: <20250828003604.8949-3-jason.andryuk@amd.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 904 bytes --]
On 28.08.25 02:36, 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.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Jason Andryuk <jason.andryuk@amd.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
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-09-02 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 0:36 [PATCH v3 0/3] xen/events: Fix Global and Domain VIRQ tracking Jason Andryuk
2025-08-28 0:36 ` [PATCH v3 1/3] xen/events: Cleanup find_virq() return codes Jason Andryuk
2025-08-28 0:36 ` [PATCH v3 2/3] xen/events: Return -EEXIST for bound VIRQs Jason Andryuk
2025-09-02 13:35 ` Juergen Gross [this message]
2025-08-28 0:36 ` [PATCH v3 3/3] xen/events: Update virq_to_irq on migration Jason Andryuk
2025-09-02 13:37 ` Juergen Gross
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=c8cf8f4b-b83a-4274-aeca-a443b2745a22@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=stable@vger.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®