From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: [PATCH v3 0/4] Balloon inhibit enhancements, vfio restriction Date: Thu, 9 Aug 2018 12:20:23 +0300 Message-ID: <20180809121649-mutt-send-email-mst@kernel.org> References: <20180807193125.30378-1-alex.williamson@redhat.com> <20180807224033-mutt-send-email-mst@kernel.org> <20180807135303.3938b3a2@t450s.home> <20180808004929-mutt-send-email-mst@kernel.org> <20180808034543.GC24415@xz-mi> <20180808162304.42d3fecc@t450s.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Cornelia Huck , david@redhat.com, qemu-devel@nongnu.org, Peter Xu , kvm@vger.kernel.org To: Alex Williamson Return-path: Content-Disposition: inline In-Reply-To: <20180808162304.42d3fecc@t450s.home> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel2=m.gmane.org@nongnu.org Sender: "Qemu-devel" List-Id: kvm.vger.kernel.org On Wed, Aug 08, 2018 at 04:23:04PM -0600, Alex Williamson wrote: > So again, I think this comes down to new iommu driver support and new > iommu apis and new vfio apis to enable some sort of atomic update > interface, Oh absolutely. My point is some guest OS can start using atomic updates at any time since it's something IOMMU hardware supports. Adherence to a hardware spec would be preferable to adherence to an internal Linux API. I appreciate it's not an easy task involving host Linux and QEMU changes. -- MST