From: "Roger Pau Monné" <roger@xenproject.org>
To: Jan Beulich <jbeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Teddy Astie <teddy.astie@vates.tech>,
Julian Vetter <julian.vetter@vates.tech>
Subject: Re: [PATCH v2 1/5] x86/pass-through: alter locking around pt_irq_{create,destroy}_bind()
Date: Wed, 28 Oct 2026 16:36:45 +0100 [thread overview]
Message-ID: <auIWjQ9hXuHFHwJb@Mac.lan> (raw)
In-Reply-To: <3bd58966-9ca8-484f-acb8-cda56df565a6@suse.com>
On Wed, Oct 28, 2026 at 04:21:15PM +0100, Jan Beulich wrote:
> On 28.10.2026 15:33, Roger Pau Monné wrote:
> > On Wed, Sep 30, 2026 at 01:42:29PM +0200, Jan Beulich wrote:
> >> --- a/xen/arch/x86/hvm/vioapic.c
> >> +++ b/xen/arch/x86/hvm/vioapic.c
> >> @@ -197,8 +197,9 @@ static int vioapic_hwdom_map_gsi(unsigne
> >> return ret;
> >> }
> >>
> >> - pcidevs_lock();
> >> + read_lock(&currd->pci_lock);
> >> ret = pt_irq_create_bind(currd, &pt_irq_bind);
> >> + read_unlock(&currd->pci_lock);
> >
> > I think you need to extend the ->pci_lock'ed region so it also covers
> > unmap_domain_pirq(), otherwise the ASSERT_PDEV_LIST_IS_READ_LOCKED()
> > in there will trigger? IE: the read_unlock() needs to be where the
> > pcidevs_unlock() is?
>
> Oh, indeed. That would only be an issue if an error arose, so it's
> clear why I didn't hit that assertion.
>
> This being the only change (which I've made locally) necessary for
> the entire series - shall I re-send, or would you mind giving an ack
> for the patch with said adjustment made?
I'm happy for you do do the change locally and commit:
Reviewed-by: Roger Pau Monné <roger@xenproject.org>
Thanks, Roger.
next prev parent reply other threads:[~2026-10-28 15:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 11:40 [PATCH v2 0/5] x86: pass-through / {,v}PCI locking Jan Beulich
2026-09-30 11:42 ` [PATCH v2 1/5] x86/pass-through: alter locking around pt_irq_{create,destroy}_bind() Jan Beulich
2026-10-28 14:33 ` Roger Pau Monné
2026-10-28 15:21 ` Jan Beulich
2026-10-28 15:36 ` Roger Pau Monné [this message]
2026-09-30 11:42 ` [PATCH v2 2/5] x86/vPCI: tighten locking assertions Jan Beulich
2026-09-30 11:43 ` [PATCH v2 3/5] x86/pass-through: use simpler locking primitives in pt_irq_{create,destroy}_bind() Jan Beulich
2026-09-30 11:43 ` [PATCH v2 4/5] x86/vPCI: make better use of "pdev" in vpci_msix_arch_print() Jan Beulich
2026-10-28 14:38 ` Roger Pau Monné
2026-09-30 11:43 ` [PATCH v2 5/5] x86/vMSI: avoid "goto" in msixtbl_pt_unregister() Jan Beulich
2026-10-28 14:51 ` Roger Pau Monné
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=auIWjQ9hXuHFHwJb@Mac.lan \
--to=roger@xenproject.org \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=julian.vetter@vates.tech \
--cc=teddy.astie@vates.tech \
--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.