From: Weidong Han <weidong.han@intel.com>
To: Alex Zeffertt <alex.zeffertt@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: pciback bug "secondary bus reset failed"
Date: Tue, 25 May 2010 09:03:33 +0800 [thread overview]
Message-ID: <4BFB21E5.5040905@intel.com> (raw)
In-Reply-To: <4BFAAEED.3050606@eu.citrix.com>
Alex Zeffertt wrote:
> Pasi Kärkkäinen wrote:
>
>> On Mon, May 24, 2010 at 04:53:01PM +0100, Alex Zeffertt wrote:
>>
>>> Hi,
>>>
>>> I'm trying to passthrough a PCI network card to a domU guest, but I'm
>>> hitting a bug that prevents the IRQ being unbound from dom0.
>>>
>>> Here are the steps I am taking:
>>>
>>> * configure Xen to pass $pci (0000:06:00.0) through to guest VM
>>> * unbind from current driver in dom0 and rebind to pciback:
>>>
>>> echo -n $pci > /sys/bus/pci/devices/$pci/driver/unbind
>>> modprobe pciback
>>> echo -n $pci > /sys/bus/pci/drivers/pciback/new_slot
>>> echo -n $pci > /sys/bus/pci/drivers/pciback/bind
>>>
>>> * start guest VM
>>>
>>> I then get the following on the dom0 console
>>>
>>> pciback 0000:06:00.0: secondary bus reset failed for device - all functions \
>>> need to be co-assigned - err: 6
>>> pciback 0000:06:00.0: FLR functionality not supported; attempts to use \
>>> secondary bus reset unsuccessful;
>>> pciback 0000:06:00.0: FLR not performed for device
>>>
>>>
>> Please check this wiki page:
>> http://wiki.xensource.com/xenwiki/XenPCIpassthrough
>>
>> It has a chapter about the "all functions need to be co-assigned" error..
>>
>> -- Pasi
>>
>
> Hi Pasi,
>
> Thanks for your reply. I think I understand what is happening now. My card is
> too old to have the Function Level Reset functionality. This leaves the
> following options:
>
>
> 1. Assign all the cards that share the PCI bus (0000:06) to the same guest.
> This enables the FLR functionality to be replaced by the bridge's "Secondary Bus
> Reset" functionality
>
> - or -
>
> 2. Apply the patch referred to on
> http://wiki.xensource.com/xenwiki/XenPCIpassthrough to bypass the FLR
>
>
> If I can't do number #1 because some cards are in use by dom0 then I guess #2 is
> the only option. But does #2 require that dom0 has never accessed the card?
>
No. Dom0 still can access the card. Dom0 just doesn't perform FLR on it
to avoid your issue.
> Also, what if you reboot the domU - does the fact that you can't do an FLR on
> the card mean that there will be unpredictable results the 2nd time domU tries
> to initialise it?
>
Yes. FLR is required by pci passthrough. your NIC only can be
co-assigned (#1). #2 is just a temporary workaround for your try.
Regards,
Weidong
> Thanks again,
>
> Alex
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2010-05-25 1:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 15:53 pciback bug "secondary bus reset failed" Alex Zeffertt
2010-05-24 16:30 ` Pasi Kärkkäinen
2010-05-24 16:53 ` Alex Zeffertt
2010-05-25 1:03 ` Weidong Han [this message]
2010-05-25 8:42 ` Alex Zeffertt
2010-05-25 8:50 ` Ian Campbell
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=4BFB21E5.5040905@intel.com \
--to=weidong.han@intel.com \
--cc=alex.zeffertt@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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.