All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Landon Clipp" <landonclipp@gmail.com>
To: "Alex Williamson" <alex.williamson@redhat.com>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Auger Eric" <eric.auger@redhat.com>,
	"Xiao Feng Ren" <renxiaof@linux.vnet.ibm.com>,
	"Arnd Bergmann" <arnd@arndb.de>, "Alexander Graf" <agraf@suse.de>,
	"Magnus Damm" <magnus.damm@gmail.com>,
	"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
	"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
	"Landon Clipp" <landonclipp@gmail.com>, <qemu-arm@nongnu.org>,
	<qemu-devel@nongnu.org>, <linux-renesas-soc@vger.kernel.org>
Subject: Re: [Qemu-arm] [PATCH/RFC 4/5] vfio: No-IOMMU mode support
Date: Fri, 20 Mar 2026 18:38:47 -0500	[thread overview]
Message-ID: <DH807PW5SQCW.3AA422QQRGVAH@gmail.com> (raw)
In-Reply-To: <20180209085024.004b6f9e@w520.home>

On Fri Feb 9, 2018 at 9:50 AM CST, Alex Williamson wrote:
> On Fri,  9 Feb 2018 16:17:35 +0100
> Geert Uytterhoeven <geert+renesas@glider.be> wrote:
>
>> From: Xiao Feng Ren <renxiaof@linux.vnet.ibm.com>
>> 
>> Add qemu support for the newly introduced VFIO No-IOMMU driver.
>> 
>> We need to add special handling for:
>> - Group character device is /dev/vfio/noiommu-$GROUP.
>> - No-IOMMU does not rely on a memory listener.
>> - No IOMMU will be set for its group, so no need to call
>>   vfio_kvm_device_add_group.
>> 
>> Signed-off-by: Xiao Feng Ren <renxiaof@linux.vnet.ibm.com>
>> [geert: Rebase]
>> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
>> ---
>>  hw/vfio/common.c              | 61 ++++++++++++++++++++++++++++++++++---------
>>  include/hw/vfio/vfio-common.h |  2 ++
>>  2 files changed, 50 insertions(+), 13 deletions(-)
>
> NAK.  I'm opposed to no-iommu support in QEMU in general, but accepting
> vfio devices with no-iommu (which provide no DMA translation!!!)
> transparently as if they might actually work like a regular vfio device
> is absolutely unacceptable.  Without DMA translation and isolation, you
> might want to think about another interface, I'm not keen on the idea
> of corrupting vfio support in order to blink some LEDs.  Thanks,
>
> Alex
>

8 years later, I was wondering if we could revisit this. I found myself in a
need to use enable_unsafe_noiommu_mode due to some systems I'm using not having
a usable IOMMU. QEMU is being used as part of a single-tenant workload
sandboxing environment, and given the specific circumstances, both the users and
the administrators understand that enabling the noiommu mode is unsafe and
cannot be used where security matters. Regardless, it's still something we want.

As the administrator of my system, it's under my control whether VFIO is put
into this mode, and if it is, I would expect the remaning software components
to respect that decision. As is, the system is unusable because of a lack of
support in QEMU.

I'm happy to elucidate more of my use-case if it is helpful, but I first wanted to
gauge your willingness to reconsider this under a different context.

Regards,
Landon (CoreWeave)

  parent reply	other threads:[~2026-03-20 23:38 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09 15:17 [PATCH/RFC 0/5] R-Car Gen3 GPIO Pass-Through Prototype (QEMU) Geert Uytterhoeven
2018-02-09 15:17 ` [Qemu-devel] " Geert Uytterhoeven
2018-02-09 15:17 ` [Qemu-arm] " Geert Uytterhoeven
2018-02-09 15:17 ` [PATCH/RFC 1/5] vfio/platform: make the vfio-platform device non abstract Geert Uytterhoeven
2018-02-09 15:17   ` [Qemu-devel] " Geert Uytterhoeven
2018-02-09 15:17   ` Geert Uytterhoeven
2018-02-09 15:17 ` [PATCH/RFC 2/5] hw/arm/sysbus-fdt: Allow device matching with compat string Geert Uytterhoeven
2018-02-09 15:17   ` [Qemu-devel] " Geert Uytterhoeven
2018-02-09 15:17   ` [Qemu-arm] " Geert Uytterhoeven
2018-02-09 15:17 ` [PATCH/RFC 3/5] hw/arm/virt: Allow dynamic sysbus devices again Geert Uytterhoeven
2018-02-09 15:17   ` [Qemu-devel] " Geert Uytterhoeven
2018-02-09 15:17   ` [Qemu-arm] " Geert Uytterhoeven
2018-02-09 15:27   ` Peter Maydell
2018-02-09 15:27     ` [Qemu-devel] " Peter Maydell
2018-02-09 15:27     ` [Qemu-arm] " Peter Maydell
2018-02-09 15:37     ` Geert Uytterhoeven
2018-02-09 15:37       ` [Qemu-devel] " Geert Uytterhoeven
2018-02-09 15:37       ` Geert Uytterhoeven
2018-02-09 15:46       ` Peter Maydell
2018-02-09 15:46         ` [Qemu-devel] " Peter Maydell
2018-02-09 15:46         ` [Qemu-arm] " Peter Maydell
2018-02-14 10:37   ` Auger Eric
2018-02-14 10:37     ` [Qemu-devel] " Auger Eric
2018-02-14 10:37     ` [Qemu-arm] " Auger Eric
2018-04-12 12:50     ` Geert Uytterhoeven
2018-04-12 12:50       ` [Qemu-devel] " Geert Uytterhoeven
2018-04-12 12:50       ` [Qemu-arm] " Geert Uytterhoeven
2018-02-09 15:17 ` [PATCH/RFC 4/5] vfio: No-IOMMU mode support Geert Uytterhoeven
2018-02-09 15:17   ` [Qemu-devel] " Geert Uytterhoeven
2018-02-09 15:17   ` [Qemu-arm] " Geert Uytterhoeven
2018-02-09 15:50   ` Alex Williamson
2018-02-09 15:50     ` [Qemu-devel] " Alex Williamson
2018-02-09 15:50     ` Alex Williamson
2018-02-09 16:06     ` Geert Uytterhoeven
2018-02-09 16:06       ` [Qemu-devel] " Geert Uytterhoeven
2018-02-09 16:06       ` Geert Uytterhoeven
2018-02-09 17:06       ` Alex Williamson
2018-02-09 17:06         ` [Qemu-devel] " Alex Williamson
2018-02-09 17:06         ` [Qemu-arm] " Alex Williamson
2026-03-20 23:38     ` Landon Clipp [this message]
2026-03-20 23:58       ` Landon Clipp
2026-03-21  5:50       ` Alex Williamson
2018-02-09 15:17 ` [PATCH/RFC 5/5] hw/arm/sysbus-fdt: Enable rcar-gen3-gpio dynamic instantiation Geert Uytterhoeven
2018-02-09 15:17   ` [Qemu-devel] " Geert Uytterhoeven
2018-02-09 15:17   ` Geert Uytterhoeven
2018-02-14 10:52   ` Auger Eric
2018-02-14 10:52     ` [Qemu-devel] " Auger Eric
2018-02-14 10:52     ` [Qemu-arm] " Auger Eric

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=DH807PW5SQCW.3AA422QQRGVAH@gmail.com \
    --to=landonclipp@gmail.com \
    --cc=agraf@suse.de \
    --cc=alex.williamson@redhat.com \
    --cc=arnd@arndb.de \
    --cc=eric.auger@redhat.com \
    --cc=geert+renesas@glider.be \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=renxiaof@linux.vnet.ibm.com \
    --cc=wsa+renesas@sang-engineering.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 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.