[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTil7ZIqfdYeNA1dkfIDoKPeWU-FIArR-n-1HjqEz@mail.gmail.com>
Date: Fri, 4 Jun 2010 10:43:07 +0800
From: Frank Pan <frankpzh@...il.com>
To: Chris Wright <chrisw@...s-sol.org>
Cc: "Williams, Mitch A" <mitch.a.williams@...el.com>,
Greg KH <greg@...ah.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
"David S. Miller" <davem@...emloft.net>,
Matt Carlson <mcarlson@...adcom.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Add a helper function in PCI IOV to get VF device
> VF is often loaded on the physical machine. There's also a networking
> specific mechanism for querying and configuring a VF via the PF.
? I don't really understand. What do you mean load? I don't think
physical machine is able to use it as a hardware device.
> While your patch is simple, it's unclear to me what your end goal is.
> The patch itself only adds a function. if you showed how you are
> planning to use it, that would really help.
Currently my hack is applied on 2.6.18 because of xen's limitation. As
Mitch says, igb driver is significantly different with recent ones. On
the other hand, my hack just exposes several PCI configuration and
MMIO registers to the sysfs, you will only understand the use case
when you also see the userspace hacks.
> It's especially confusing that you are comparing your patch with
> symlinks visible in sysfs.
That's my fault. The most recent reply explains it.
Thanks for reply.
--
Frank Pan
Computer Science and Technology
Tsinghua University
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists