 Messages in this thread SubjectRe: [PATCH 0/6] MSI portability
cleanups  .../... (enable/disable bits)  > Which are either
talking directly to the hardware, or are talking > to the
hypervisor, which is using hardware isolation so it is safe to >
talk directly to the hardware but isn't leting us? If we could
use > things to work around errata in card implementation
details it would > make some sense to me (although we don't seem
to have any cards with > that got the MSI registers wrong at
this point). Regardless these > operations clearly have a
different granularity than the other > operations, and should
have a different lookup method.  I'm not sure I undersdand the
point of your rant here. The hypervisor case hooks at alloc/free
and does everything from there. It doens't use an enable or a
diable hook.  The enable/disable ops are optional for that
reason. When not present, it's assumed that alloc/free do it
all.  When using a "direct" approach (what we call "raw"), we
expect backends to just plug the provi