From: Jambunathan K <jambunathan@netxen.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: PCI Passthru: fn0 exported but not fn1
Date: Fri, 24 Aug 2007 00:34:22 +0530 [thread overview]
Message-ID: <46CDDA36.4090508@netxen.com> (raw)
Given the following device list, I am exporting one of the functions to
Dom1 through PCI passthrough.
$ lspci | grep known
04:00.0 Ethernet controller: Unknown device 4040:0002 (rev 25)
04:00.1 Ethernet controller: Unknown device 4040:0002 (rev 25)
04:00.2 Ethernet controller: Unknown device 4040:0002 (rev 25)
04:00.3 Ethernet controller: Unknown device 4040:0002 (rev 25)
If I export just 04:00.0, it is visible ('lspci') in Dom1. However if I
export just 04:00.1 then it is no more visible in Dom1.
I am using Xen310. As an additional information, I am seeing this
behaviour on my 'new box'. Things were fine on my earlier box. It is
possible that this is a platform specific thing.
If it is a known issue, I would be happy to patch my tree. Otherwise I
can debug this further post some debug logs for your scrutiny.
Jambunathan K.
next reply other threads:[~2007-08-23 19:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 19:04 Jambunathan K [this message]
2007-08-24 14:42 ` PCI Passthru: fn0 exported but not fn1 Keir Fraser
2007-08-24 14:58 ` Jambunathan K
2007-08-24 15:01 ` Keir Fraser
2007-08-26 16:19 ` Jambunathan K
2007-08-27 14:08 ` Jambunathan K
2007-08-27 15:22 ` Keir Fraser
2007-08-27 15:27 ` Jambunathan K
2007-08-27 15:40 ` Keir Fraser
2007-08-27 15:58 ` Jambunathan K
2007-08-27 16:14 ` Keir Fraser
2007-08-27 16:34 ` Jambunathan K
2007-08-27 16:42 ` Keir Fraser
[not found] <C2FA6F3A.D05F%keir@xensource.com>
2007-08-29 14:18 ` Jambunathan K
2007-08-29 14:26 ` Keir Fraser
2007-08-30 10:11 ` Jambunathan K
2007-08-30 10:19 ` Keir Fraser
2007-08-30 14:45 ` Jambunathan K
2007-08-29 18:27 ` Stefan Neuwirth
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=46CDDA36.4090508@netxen.com \
--to=jambunathan@netxen.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.