From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: [RFC PATCH kernel] vfio-pci: Allow write combining Date: Mon, 16 Oct 2017 10:38:18 +0200 Message-ID: <1508143098.25065.277.camel@kernel.crashing.org> References: <20171009025000.39435-1-aik@ozlabs.ru> <20171010155515.39a0c5fe@t450s.home> <20171010204256.309715ce@t450s.home> <26fbe3b7-c54b-87a5-799d-22f4f043edd2@ozlabs.ru> <1507736107.25065.222.camel@kernel.crashing.org> <7ad2ee73-80dc-69ef-c98a-63b020f2f48b@ozlabs.ru> <20171016060043.GC2776@umbus.fritz.box> <67742d45-a267-0363-7448-7f8945f84c95@ozlabs.ru> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Alex Williamson , kvm@vger.kernel.org, Eric Auger To: Alexey Kardashevskiy , David Gibson Return-path: Received: from gate.crashing.org ([63.228.1.57]:34917 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751284AbdJPIib (ORCPT ); Mon, 16 Oct 2017 04:38:31 -0400 In-Reply-To: <67742d45-a267-0363-7448-7f8945f84c95@ozlabs.ru> Sender: kvm-owner@vger.kernel.org List-ID: On Mon, 2017-10-16 at 18:36 +1100, Alexey Kardashevskiy wrote: > > 1. Allow msix mapping to the userspace (to address non-64k-aligned msix bar) > > 2. Allow write combining in vfio for the userspace (kvm guest is kinda > special and may simply ignore mapping flags in some configs but PPC radix > guests still rely on this) Why ? The "G" bit is entirely under control of the guest afaik. This would only affect qemu itself. It's still useful for things like dpdk using vfio. > 3. what callback and where needs to be added to inform HV/PR KVM about VFIO > group, like IOMMUMR::add_vfio_group() proposal or something. Can you elaborate a bit ? I haven't followed this. Cheers, Ben.