From: Avi Kivity <avi@scylladb.com>
To: Alex Williamson <alex.williamson@redhat.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: avi@cloudius-systems.com, gleb@scylladb.com, corbet@lwn.net,
bruce.richardson@intel.com, mst@redhat.com,
linux-kernel@vger.kernel.org, alexander.duyck@gmail.com,
gleb@cloudius-systems.com, vladz@cloudius-systems.com,
iommu@lists.linux-foundation.org, hjk@hansjkoch.de,
gregkh@linuxfoundation.org
Subject: Re: [RFC PATCH 2/2] vfio: Include no-iommu mode
Date: Mon, 12 Oct 2015 19:31:10 +0300 [thread overview]
Message-ID: <561BE04E.4030108@scylladb.com> (raw)
In-Reply-To: <1444666999.4059.362.camel@redhat.com>
On 10/12/2015 07:23 PM, Alex Williamson wrote:
>> Also, although you think the long option will set the bar high
>> enough it probably will not satisfy anyone. It is annoying enough, that
>> I would just carry a patch to remove it the silly requirement.
>> And the the people who believe
>> all user mode DMA is evil won't be satisfied either.
> I find that many users blindly follow howtos and only sometimes do they
> question the options if they sound scary enough. So yeah, I would
> intend to make the option upstream sound scary enough for people to
> think twice about using it and maybe even read the description. That
> still doesn't prevent pasting it into modprobe.d and forgetting about
> it.
I think we need to allow for packages to work with this. I.e. drop
files into config directories rather than require editing of config
files. I think this is mostly workable via modprobe.d.
(for our own use case, we don't require the extreme performance of many
L2/L3 dpdk apps so we'll work with regular iommued vfio for bare-metal
installations and ship prebuilt virtual machine images for clouds, so it
doesn't matter that much to me).
next prev parent reply other threads:[~2015-10-12 16:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 18:40 [RFC PATCH 0/2] VFIO no-iommu Alex Williamson
2015-10-09 18:41 ` [RFC PATCH 1/2] vfio: Move vfio.c vfio_core.c Alex Williamson
2015-10-09 19:21 ` Greg KH
2015-10-09 18:41 ` [RFC PATCH 2/2] vfio: Include no-iommu mode Alex Williamson
2015-10-11 8:12 ` Avi Kivity
2015-10-11 8:57 ` Michael S. Tsirkin
2015-10-11 9:03 ` Avi Kivity
2015-10-11 9:19 ` Michael S. Tsirkin
2015-10-11 9:23 ` Gleb Natapov
2015-10-11 21:16 ` Alex Williamson
2015-10-12 15:56 ` Stephen Hemminger
2015-10-12 16:23 ` Alex Williamson
2015-10-12 16:31 ` Avi Kivity [this message]
2015-10-12 16:27 ` Michael S. Tsirkin
2015-10-12 17:46 ` Alex Williamson
2015-10-12 18:08 ` Alex Williamson
2015-10-11 17:29 ` [RFC PATCH 0/2] VFIO no-iommu Varun Sethi
2015-10-11 18:23 ` Alex Williamson
2015-10-11 18:28 ` Michael S. Tsirkin
2015-10-11 18:29 ` Michael S. Tsirkin
2015-10-11 19:25 ` Alex Williamson
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=561BE04E.4030108@scylladb.com \
--to=avi@scylladb.com \
--cc=alex.williamson@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=avi@cloudius-systems.com \
--cc=bruce.richardson@intel.com \
--cc=corbet@lwn.net \
--cc=gleb@cloudius-systems.com \
--cc=gleb@scylladb.com \
--cc=gregkh@linuxfoundation.org \
--cc=hjk@hansjkoch.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=stephen@networkplumber.org \
--cc=vladz@cloudius-systems.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox