[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 07/28] hw/vfio: mark all VFIO object classes as secure

To: Daniel P. Berrangé <berrange@xxxxxxxxxx>
From: marcandre.lureau@xxxxxxxxxx
Date: Fri, 02 Oct 2026 21:21:01 +0400
Authentication-results: eu.smtp.expurgate.cloud; dkim=pass header.s=mimecast20190719 header.d=redhat.com header.i="@redhat.com" header.h="From:Subject:Date:Message-Id:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding:In-Reply-To:References"
Cc: qemu-devel@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxx, qemu-riscv@xxxxxxxxxx, qemu-ppc@xxxxxxxxxx, qemu-block@xxxxxxxxxx, qemu-s390x@xxxxxxxxxx, qemu-arm@xxxxxxxxxx
Delivery-date: Fri, 02 Oct 2026 17:21:42 +0000
List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On Fri, 11 Sep 2026 15:36:06 +0100, Daniel P. Berrangé <berrange@xxxxxxxxxx> 
wrote:
> The VFIO subsystem is about securely passing host PCI devices
> to a guest, so all the classes should be presumed to be offering
> a security boundary.

Acked-by: Marc-André Lureau <marcandre.lureau@xxxxxxxxxx>

-- 
Marc-André Lureau <marcandre.lureau@xxxxxxxxxx>

Prev by Date: Re: [PATCH 06/28] hw: mark all remaining virtio object types as secure
Next by Date: Re: [PATCH 08/28] hw/xen: mark all Xen related object types as being secure
Previous by thread: Re: [PATCH 06/28] hw: mark all remaining virtio object types as secure
Next by thread: Re: [PATCH 07/28] hw/vfio: mark all VFIO object classes as secure
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.