[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PCI pass-through problem for SN570 NVME SSD


  • To: "G.R." <firemeteor@xxxxxxxxxxxxxxxxxxxxx>
  • From: Jan Beulich <jbeulich@xxxxxxxx>
  • Date: Tue, 5 Jul 2022 13:59:00 +0200
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=suse.com; dmarc=pass action=none header.from=suse.com; dkim=pass header.d=suse.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=z69hHlsITH5q8CXok0Q2UKGeWhmtuhywEZWkEyPNaP8=; b=B4tWdzDbynmEpashzUpM65BsyjxbvdalslrJohMH8zKbeUDRokz8cWAeGtNaK4KdwzVGFwECj74oZ1OSPAz88P/6QOBwNyN87PZf0lEugh/UM25uBCe/7n0SjDAaWLb5ufziTxE6D6DTdOIWQDASqsFuMCUnNnYRNdJk12s2WQG6jKhVzPXUD1VZR+nY/3h0qw5zfTjhlE5LkrjvXkZlenpsKtoCqjVX3K/PgnLDvMaN/nW/e+vY0F2/eIS0+ZBcMu/pg5OjXgtpHd+F25hcsOWP9Hj+vCkkOfmzEMtRtYEdFagVVnLL00KzSQT1zREkhIK8H+Q6JIX08/NdwJJVhQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=EQlXatSYyAPUb8RcCXAl1TM/eIlVgASChECw7lfQIYU83ASK9dj2TlYbWCLfxtuEevruuihunEm5RN3nxzHnwKC5QMWaIbbtJm8cNKwDDHPdvPTvXwB/v/R+BBmf6CzbQKpCstBDW1rBSp4lVBff3MK4fcxD5ipTe7pDRvExpjkUl6bbXva6JT+4PDi6akXmY69du+lZsHEOX3boQidAQ4GUxjwpjr2F0OjIWXT9j2kEFsr+/gOUy7SeuvevcJOlDtvWRsIQT/rkMrnIEMgvuPGQ77doGG6z7Ihzbk8ciProUA4H88G5wzk6D1jeM3FFYsy86pZpBz3pM2zUCb4ZOA==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=suse.com;
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>
  • Delivery-date: Tue, 05 Jul 2022 11:59:27 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 05.07.2022 13:31, G.R. wrote:
> On Tue, Jul 5, 2022 at 5:04 PM Jan Beulich <jbeulich@xxxxxxxx> wrote:
>>
>> On 04.07.2022 18:31, G.R. wrote:
>>> On Tue, Jul 5, 2022 at 12:21 AM Roger Pau Monné <roger.pau@xxxxxxxxxx> 
>>> wrote:
>>>>> I retried with the following:
>>>>> pci=['05:00.0,permissive=1,msitranslate=1']
>>>>> Those extra options suppressed some error logging, but still didn't
>>>>> make the device usable to the domU.
>>>>> The nvmecontrol command still get ABORTED result from the kernel...
>>>>>
>>>>> The only thing remained in the QEMU file is this one:
>>>>> [00:05.0] msi_msix_setup: Error: Mapping of MSI-X (err: 61, vec: 0x30, 
>>>>> entry 0)
>>>>
>>>> Hm it seems like Xen doesn't find the position of the MSI-X table
>>>> correctly, given there's only one error path from msi.c returning
>>>> -ENODATA (61).
>>>>
>>>> Are there errors from pciback when this happens?  I would expect the
>>>> call to pci_prepare_msix() from pciback to fail and thus also report
>>>> some error?
>>>>
>>>> I think it's likely I will have to provide an additional debug patch
>>>> to Xen, maybe Jan has an idea of what could be going on.
>>>>
>>> pciback reports the same MSI-x related error.
>>> But even with DEBUG enabled, I didn't see more context reported.
>>> Please find details from the attachment.
>>
>> And nothing pertinent in "xl dmesg"? Looking back through the thread I
>> couldn't spot a complete hypervisor log (i.e. from boot to assignment
>> attempt). An issue with MSI-X table determination, as Roger suspects,
>> would typically be associated with a prominent warning emitted to the
>> log. But there are also further possible sources of -ENXIO, which
>> would go silently.
> Please find the xl dmesg in the attachment.
> It's with the two FreeBSD domU attempts so it should have captured
> some culprits if there is any...

Nothing useful in there. Yet independent of that I guess we need to
separate the issues you're seeing. Otherwise it'll be impossible to
know what piece of data belongs where.

Jan



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.