All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 202055] Failed to PCI passthrough SSD with SMI SM2262 controller.
Date: Mon, 08 Apr 2019 04:16:10 +0000	[thread overview]
Message-ID: <bug-202055-28872-0tjRpFdiZD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202055-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=202055

--- Comment #42 from Alex Williamson (alex.williamson@redhat.com) ---
It seems there's a partial workaround available since QEMU v2.12 hiding under
our noses.  That version adds support for relocating the MSI-X vector table on
vfio-pci devices, which recreates the MSI-X MMIO space elsewhere on the device.
 A side-effect of this is that the vector table and PBA are properly sized so
as not to collide.  The size of the tables remains wrong, but this only becomes
a problem if the nvme code attempts to allocate >16 vectors, which requires >15
vCPU (or host CPUs if the device is returned to host drivers after being
assigned)(nvme appears to allocate 1 admin queue, plus a queue per CPU, each
making use of an IRQ vector).  The QEMU vfio-pci device option is
x-msix-relocation= which allows specifying the bar to use for the MSI-X tables,
ex. bar0...bar5.  Since this device uses a 64bit bar0, we can either extend
that BAR or choose another, excluding bar1, which is consumed by the upper half
of bar0.  For instance, I tested with:

<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
...
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <source>
        <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
      </source>
      <alias name='ua-sm2262'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00'
function='0x0'/>
    </hostdev>
...
  <qemu:commandline>
    <qemu:arg value='-set'/>
    <qemu:arg value='device.ua-sm2262.x-msix-relocation=bar2'/>
  </qemu:commandline>


(NB: "ua-" is a required prefix when specifying an alias)

A new virtual BAR appears in the guest hosting the MSI-X table and QEMU starts
normally so long as the guest doesn't exceed 15 vCPUs.

The vCPU/pCPU count limitations are obviously not ideal, but hopefully this
provides some degree of workaround for typical configurations.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

       reply	other threads:[~2019-04-08  4:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-202055-28872@https.bugzilla.kernel.org/>
2019-04-08  4:16 ` bugzilla-daemon [this message]
2019-04-09 14:43 ` [Bug 202055] Failed to PCI passthrough SSD with SMI SM2262 controller bugzilla-daemon
2019-04-09 14:57 ` bugzilla-daemon
2020-07-28 15:41 ` bugzilla-daemon
2020-07-29 14:34 ` bugzilla-daemon
2020-12-29  1:00 ` bugzilla-daemon

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=bug-202055-28872-0tjRpFdiZD@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.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.