xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Weidong Han <weidong.han@intel.com>
To: mail ignored <0.bugs.only.0@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: follow up to a pciback "pv pci-passthrough co-assigned problem"
Date: Mon, 25 Jan 2010 09:44:58 +0800	[thread overview]
Message-ID: <4B5CF79A.6020002@intel.com> (raw)
In-Reply-To: <c67eed301001231015v2c572d2fxb4a221157f3f1bfd@mail.gmail.com>

mail ignored wrote:
> On Sat, Jan 23, 2010 at 9:58 AM, mail ignored <0.bugs.only.0@gmail.com> wrote:
>   
>> thanks.  i suppose i'll file a bug @ opensuse abt this, and see if
>> they'll put something into code so these changes will 'survive'
>> xen(-tools) updates ...
>>     
>
> cref -> https://bugzilla.novell.com/show_bug.cgi?id=573311
>   

I think this is not a bug. pls note that the devices behind 
PCIe-to-PCI/PCI-x bridge or Conventional PCI bridge can only be 
collectively assigned to a single domain, because the source-id in DMA 
requests is not device's bdf. Pls refer to section 3.6.1 in VT-d spec. 
What's more, FLR is required to make sure the device in a correct status 
before assignment, and some devices need to reset secondary bus to reset 
the device which results in all the devices behind same 
PCIe-to-PCI/PCI-x bridge or Conventional PCI bridge be reset. In your 
case, you need to hide all NICs (04:06.0 and 04:07.0) behind the same 
bridge, and assign them together to a guest. or you can set 
"pci-passthrough-strict-check no" in /etc/xen/xend-config.sxp and 
restart xend to loose the check in xend, but in this way you should be 
aware of potential issues (e.g. assigned device doesn't work).

Regards,
Weidong

  reply	other threads:[~2010-01-25  1:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-23  1:32 follow up to a pciback "pv pci-passthrough co-assigned problem" mail ignored
2010-01-23  4:09 ` mail ignored
2010-01-23 12:30   ` Pasi Kärkkäinen
2010-01-23 16:40     ` mail ignored
2010-01-23 16:48       ` Pasi Kärkkäinen
2010-01-23 17:36         ` mail ignored
2010-01-23 17:43           ` Pasi Kärkkäinen
2010-01-23 17:45             ` mail ignored
2010-01-23 17:54               ` mail ignored
2010-01-23 17:57                 ` Pasi Kärkkäinen
2010-01-23 17:58                   ` mail ignored
2010-01-23 18:15                     ` mail ignored
2010-01-25  1:44                       ` Weidong Han [this message]
2010-01-25 16:17                         ` 0bo0
2010-01-26  1:42                           ` Weidong Han
2010-01-26  7:02                             ` Pasi Kärkkäinen
2010-01-23 18:19             ` Keir Fraser
2010-01-26  6:50               ` 0bo0
2010-01-26  7:34                 ` Keir Fraser

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=4B5CF79A.6020002@intel.com \
    --to=weidong.han@intel.com \
    --cc=0.bugs.only.0@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).