From: Keir Fraser <keir@xensource.com>
To: Jambunathan K <jambunathan@netxen.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Stefan Neuwirth <neuwirt-xen-devel@trillian.hd.shuttle.de>,
Sanjeev Jorapur <sanjeev@netxen.com>
Subject: Re: PCI Passthru: fn0 exported but not fn1
Date: Wed, 29 Aug 2007 15:26:41 +0100 [thread overview]
Message-ID: <C2FB40B1.14FF5%keir@xensource.com> (raw)
In-Reply-To: <46D58037.7010007@netxen.com>
On 29/8/07 15:18, "Jambunathan K" <jambunathan@netxen.com> wrote:
> Just to be sure I 'fixed'
> linux-2.6-xen-sparse/include/asm-x86_64/mach-xen/asm/pci.h and made a
> clean build from xen source tar. I ensured that BACKEND_PASS is set to yes.
>
> I am using the same vmlinuz both on Dom0 and Dom1. I am seeing that
> lspci in Dom1 *doesn't* report the exported non-zero function.
Very odd. The tracing you provide clearly shows that the kernel is *not*
scanning every fn. It is only scanning every fn==0.
The function of interest here is, I think,
linux/drivers/pci/probe.c:pci_scan_slot(). Notice how it iterates on every
fn but bails early if no device is found at fn 0 and !scan_all_fns. I
suggest you add some tracing to that function to check that:
A. It is being called; and
B. Exactly how it is bailing without checking fns != 0, if it ireally is
the case that scan_all_fns==1.
-- Keir
next prev parent reply other threads:[~2007-08-29 14:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C2FA6F3A.D05F%keir@xensource.com>
2007-08-29 14:18 ` PCI Passthru: fn0 exported but not fn1 Jambunathan K
2007-08-29 14:26 ` Keir Fraser [this message]
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
2007-08-23 19:04 Jambunathan K
2007-08-24 14:42 ` 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
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=C2FB40B1.14FF5%keir@xensource.com \
--to=keir@xensource.com \
--cc=jambunathan@netxen.com \
--cc=neuwirt-xen-devel@trillian.hd.shuttle.de \
--cc=sanjeev@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.