On Tue, Dec 09, 2014 at 01:29:52PM +0100, Ard Biesheuvel wrote: > On 9 December 2014 at 12:26, Christoffer Dall > <christoffer.dall@xxxxxxxxxx> wrote: > > From: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> > > > > Instead of using kvm_is_mmio_pfn() to decide whether a host region > > should be stage 2 mapped with device attributes, add a new static > > function kvm_is_device_pfn() that disregards RAM pages with the > > reserved bit set, as those should usually not be mapped as device > > memory. > > > > Signed-off-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> > > Signed-off-by: Marc Zyngier <marc.zyngier@xxxxxxx> > > As I mentioned last week, this patch (and the next one) are already in > 3.18 so unless there is some policy I am unaware of, these do not have > to be submitted again. > They're in kvmarm/next, which is a stable branch (doesn't rebase) so our only choice would be to revert this commit specifically in kvmarm/next before sending the pull request. Since that would be more confusing than help anything, and Paolo said to just include the duplicate commit in the pull request, here it is. As we can see in linux-next, it's not really a problem. -Christoffer -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
