From mboxrd@z Thu Jan 1 00:00:00 1970 From: pbonzini@redhat.com (Paolo Bonzini) Date: Thu, 05 Mar 2015 11:12:22 +0100 Subject: [RFC/RFT PATCH 0/3] arm64: KVM: work around incoherency with uncached guest mappings In-Reply-To: <20150304172855.GA28951@e104818-lin.cambridge.arm.com> References: <20150302163146.GB9686@lvm> <54F51A63.4060302@samsung.com> <20150304113505.GS28951@e104818-lin.cambridge.arm.com> <20150304122956.GT28951@e104818-lin.cambridge.arm.com> <20150304141212.GA5352@hawk.usersys.redhat.com> <20150304142943.GU28951@e104818-lin.cambridge.arm.com> <54F73ACF.1090605@redhat.com> <20150304172855.GA28951@e104818-lin.cambridge.arm.com> Message-ID: <54F82C06.2000701@redhat.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 04/03/2015 18:28, Catalin Marinas wrote: >> > >> > Can you add that property to the device tree for PCI devices too? > Yes but not with mainline yet: > > http://thread.gmane.org/gmane.linux.kernel.iommu/8935 > > We can add the property at the PCI host bridge level (with the drawback > that it covers all the PCI devices), like here: Even covering all PCI devices is not enough if we want to support device assignment of PCI host devices. I'd rather not spend effort on a solution that we know will only half-work a few months down the road. Paolo > Documentation/devicetree/bindings/pci/xgene-pci.txt