From: Christoph Hellwig <hch@infradead.org>
To: "Duyck, Alexander H" <alexander.h.duyck@intel.com>
Cc: "Wang, Liang-min" <liang-min.wang@intel.com>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH] Enable SR-IOV instantiation through /sys file
Date: Sat, 28 Oct 2017 23:16:46 -0700 [thread overview]
Message-ID: <20171029061646.GA28105@infradead.org> (raw)
In-Reply-To: <1509146439.11655.60.camel@intel.com>
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?
next prev parent reply other threads:[~2017-10-29 6:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 20:04 [PATCH] Enable SR-IOV instantiation through /sys file Jeff Kirsher
2017-10-24 21:43 ` Alex Williamson
2017-10-24 21:49 ` Wang, Liang-min
2017-10-24 22:06 ` Alex Williamson
2017-10-24 22:29 ` Wang, Liang-min
2017-10-25 8:39 ` Alex Williamson
2017-10-27 21:50 ` Wang, Liang-min
2017-10-27 22:19 ` Alex Williamson
2017-10-27 22:30 ` Wang, Liang-min
2017-10-27 23:20 ` Duyck, Alexander H
2017-10-27 23:20 ` Duyck, Alexander H
2017-10-29 6:16 ` Christoph Hellwig [this message]
2017-10-29 21:12 ` Alexander Duyck
2017-10-30 12:39 ` David Woodhouse
2017-10-31 12:55 ` Wang, Liang-min
2017-10-31 12:55 ` Wang, Liang-min
2017-11-06 23:27 ` Alex Williamson
2017-11-06 23:47 ` Alexander Duyck
2017-11-07 16:59 ` Alex Williamson
2017-11-06 19:55 ` Bjorn Helgaas
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=20171029061646.GA28105@infradead.org \
--to=hch@infradead.org \
--cc=alex.williamson@redhat.com \
--cc=alexander.h.duyck@intel.com \
--cc=bhelgaas@google.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=kvm@vger.kernel.org \
--cc=liang-min.wang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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.