From: Jan Beulich <jbeulich@suse.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: Manuel Bouyer <bouyer@antioche.eu.org>, xen-devel@lists.xenproject.org
Subject: Re: [PATCH] vpci/msix: exit early if MSI-X is disabled
Date: Wed, 2 Dec 2020 09:38:18 +0100 [thread overview]
Message-ID: <dfc96aa9-c39f-177c-c8f8-af18b80804de@suse.com> (raw)
In-Reply-To: <20201201174014.27878-1-roger.pau@citrix.com>
On 01.12.2020 18:40, Roger Pau Monne wrote:
> Do not attempt to mask an MSI-X entry if MSI-X is not enabled. Else it
> will lead to hitting the following assert on debug builds:
>
> (XEN) Panic on CPU 13:
> (XEN) Assertion 'entry->arch.pirq != INVALID_PIRQ' failed at vmsi.c:843
Since the line number is only of limited use, I'd like to see the
function name (vpci_msix_arch_mask_entry()) also added here; easily
done while committing, if the question further down can be resolved
without code change.
> --- a/xen/drivers/vpci/msix.c
> +++ b/xen/drivers/vpci/msix.c
> @@ -357,7 +357,11 @@ static int msix_write(struct vcpu *v, unsigned long addr, unsigned int len,
> * so that it picks the new state.
> */
> entry->masked = new_masked;
> - if ( !new_masked && msix->enabled && !msix->masked && entry->updated )
> +
> + if ( !msix->enabled )
> + break;
> +
> + if ( !new_masked && !msix->masked && entry->updated )
> {
> /*
> * If MSI-X is enabled, the function mask is not active, the entry
What about a "disabled" -> "enabled-but-masked" transition? This,
afaict, similarly won't trigger setting up of entries from
control_write(), and hence I'd expect the ASSERT() to similarly
trigger when subsequently an entry's mask bit gets altered.
I'd also be fine making this further adjustment, if you agree,
but the one thing I haven't been able to fully convince myself of
is that there's then still no need to set ->updated to true.
Jan
next prev parent reply other threads:[~2020-12-02 8:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 17:40 [PATCH] vpci/msix: exit early if MSI-X is disabled Roger Pau Monne
2020-12-02 8:38 ` Jan Beulich [this message]
2020-12-03 13:40 ` Jan Beulich
2020-12-06 11:15 ` Roger Pau Monné
2020-12-07 8:19 ` 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=dfc96aa9-c39f-177c-c8f8-af18b80804de@suse.com \
--to=jbeulich@suse.com \
--cc=bouyer@antioche.eu.org \
--cc=roger.pau@citrix.com \
--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;
as well as URLs for NNTP newsgroup(s).