From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: Dealing with SIOV/IMS
Date: Fri, 2 Jan 2026 01:22:32 +0000 [thread overview]
Message-ID: <90681969-e7c1-40ce-88c9-a5639865c93c@citrix.com> (raw)
In-Reply-To: <aVb7jL52nkmSD-Gr@mail-itl>
On 01/01/2026 10:56 pm, Marek Marczykowski-Górecki wrote:
> Hi,
>
> I've got yet another report[1] of device failing because (I assume) the
> drivers reads MSI/MSI-X values (thinking it sees values actually set in
> the HW) and then pass them to the device via some alternative means.
Ath11k is known broken in this regard. It doesn't even work on native
systems. (It only works in Linux by dropping to a single interrupt and
tying it to CPU 0).
But, my understand is that this is specific to Ath11k and not to do with
IMS.
> IIUC this is what IMS does.
Not really. IMS moves the MSI-X table out of a BAR and into host memory.
It was a short-sighted design which is very hard for native to use and
impossible for virt to use.
AIUI, IMS has been abandoned as a technology, so I think we can simply
ignore it.
~Andrew
next prev parent reply other threads:[~2026-01-02 1:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-01 22:56 Dealing with SIOV/IMS Marek Marczykowski-Górecki
2026-01-02 1:01 ` Demi Marie Obenour
2026-01-02 1:22 ` Andrew Cooper [this message]
2026-01-02 3:52 ` Demi Marie Obenour
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=90681969-e7c1-40ce-88c9-a5639865c93c@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=marmarek@invisiblethingslab.com \
--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 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.