From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: [RFC PATCH kernel] vfio-pci: Allow write combining Date: Wed, 11 Oct 2017 17:35:07 +0200 Message-ID: <1507736107.25065.222.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> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, David Gibson , Eric Auger To: Alexey Kardashevskiy , Alex Williamson Return-path: Received: from gate.crashing.org ([63.228.1.57]:42896 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751965AbdJKPfX (ORCPT ); Wed, 11 Oct 2017 11:35:23 -0400 In-Reply-To: <26fbe3b7-c54b-87a5-799d-22f4f043edd2@ozlabs.ru> Sender: kvm-owner@vger.kernel.org List-ID: On Wed, 2017-10-11 at 13:56 +1100, Alexey Kardashevskiy wrote: > Oopsie. This is because I overlooked it. Others do not use it. So I do need > a file. But in the current scheme where all BARs share one fd - it won't > work - I simply cannot allow WC on non-prefetchable BARs :-/ This is an oversight in the design of VFIO-PCI, it should have a way to specify write combine, either implicitely via such an arch hook, or explicitely via an ioctl prior to mapping the BARs for example. Alex, what do you reckon is the best approach here ? Cheers, Ben.