[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171029061646.GA28105@infradead.org>
Date: Sat, 28 Oct 2017 23:16:46 -0700
From: Christoph Hellwig <hch@...radead.org>
To: "Duyck, Alexander H" <alexander.h.duyck@...el.com>
Cc: "Wang, Liang-min" <liang-min.wang@...el.com>,
"alex.williamson@...hat.com" <alex.williamson@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
Subject: Re: [PATCH] Enable SR-IOV instantiation through /sys file
On Fri, Oct 27, 2017 at 11:20:41PM +0000, Duyck, Alexander H wrote:
> I don't see this so much as a security problem per-se. It all depends
> on the hardware setup. If I recall correctly, there are devices where
> the PF function doesn't really do much other than act as a bit more
> heavy-weight VF, and the actual logic is handled by a firmware engine
> on the device.
Can you cite an example? While those surely could exist in theory,
I can't think of a practical example.
Maybe we can start with the practical use case for this patch. That
is what device is this intended for?
Powered by blists - more mailing lists