From: Joby Poriyath <joby.poriyath@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
malcolm.crossley@citrix.com, xen-devel <xen-devel@lists.xen.org>
Subject: Re: (XEN) [2013-08-23 12:23:26] Assertion 'entry->pirq == pirq' failed at vmsi.c
Date: Fri, 23 Aug 2013 21:58:33 +0100 [thread overview]
Message-ID: <20130823205833.GA16674@citrix.com> (raw)
In-Reply-To: <521785F402000078000EE061@nat28.tlf.novell.com>
On Fri, Aug 23, 2013 at 02:55:32PM +0100, Jan Beulich wrote:
> >>> On 23.08.13 at 15:26, Sander Eikelenboom <linux@eikelenboom.it> wrote:
> > I have adjusted the debug patch, only letting it reuse the entry if ( pdev
> > == entry->pdev && entry->pirq == pirq){
> > so the assertion should be always true now, would this perhaps be the proper
> > fix or should it also check if it is also masked ?
>
> Yes, that might be a possible solution, albeit I don't like it - it points
> out that the original patch from Joby is - beyond the bug here - at
> least inefficient (in that we'd then allocate an entry per MSI-X table
> entry, i.e. per IRQ, instead of per device). I therefore think we
> rather ought to revert that change, and have him redo it properly.
Ok, we ought to revisit the original patch. Let us revert the code for now.
Thanks Sander for spotting this.
It's a certainly an oversight from my side.
A PCIe function can have multiple MSIx entries.
I'm on holidays. I'll be back on 29th Aug. I shall pick this up, then.
Thanks,
Joby
prev parent reply other threads:[~2013-08-23 20:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 12:34 (XEN) [2013-08-23 12:23:26] Assertion 'entry->pirq == pirq' failed at vmsi.c Sander Eikelenboom
2013-08-23 12:56 ` Jan Beulich
2013-08-23 13:26 ` Sander Eikelenboom
2013-08-23 13:55 ` Jan Beulich
2013-08-23 20:58 ` Joby Poriyath [this message]
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=20130823205833.GA16674@citrix.com \
--to=joby.poriyath@citrix.com \
--cc=JBeulich@suse.com \
--cc=linux@eikelenboom.it \
--cc=malcolm.crossley@citrix.com \
--cc=xen-devel@lists.xen.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.