[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081217141542.GB19967@parisc-linux.org>
Date: Wed, 17 Dec 2008 07:15:43 -0700
From: Matthew Wilcox <matthew@....cx>
To: Jesse Barnes <jbarnes@...tuousgeek.org>
Cc: Yu Zhao <yu.zhao@...el.com>, linux-pci@...r.kernel.org,
achiang@...com, bjorn.helgaas@...com, grundler@...isc-linux.org,
greg@...ah.com, mingo@...e.hu, randy.dunlap@...cle.com,
rdreier@...co.com, horms@...ge.net.au, yinghai@...nel.org,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
virtualization@...ts.linux-foundation.org
Subject: Re: [PATCH 0/13 v7] PCI: Linux kernel SR-IOV support
On Tue, Dec 16, 2008 at 03:23:53PM -0800, Jesse Barnes wrote:
> I applied 1-9 to my linux-next branch; and at least patch #10 needs a respin,
I still object to #2. We should have the flexibility to have 'struct
resource's that are not in this array in the pci_dev. I would like to
see the SR-IOV resources _not_ in this array (and indeed, I'd like to
see PCI bridges keep their producer resources somewhere other than in
this array). I accept that there are still some problems with this, but
patch #2 moves us further from being able to achieve this goal, not
closer.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
--
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