Hello!
> > diff --git a/arch/arm/kvm/mmu.c b/arch/arm/kvm/mmu.c
> > index 7dace90..51ad98f 100644
> > --- a/arch/arm/kvm/mmu.c
> > +++ b/arch/arm/kvm/mmu.c
> > @@ -310,7 +310,8 @@ static void stage2_flush_ptes(struct kvm *kvm, pmd_t
> > *pmd,
> >
> > pte = pte_offset_kernel(pmd, addr);
> > do {
> > - if (!pte_none(*pte) &&
> > !kvm_is_device_pfn(__phys_to_pfn(addr)))
> > + if (!pte_none(*pte) &&
> > + (pte_val(*pte) & PAGE_S2_DEVICE) != PAGE_S2_DEVICE)
>
> I think your analysis is correct, but does that not apply to both instances?
No no, another one is correct, since it operates on real PFN (at least looks
like so). I have verified my fix against the original problem (crash on
Exynos5410 without generic timer), and it still works fine there.
> And instead of reverting, could we fix this properly instead?
Of course, i'm not against alternate approaches, feel free to. I've just
suggested what i could, to fix things quickly. I'm indeed no expert in KVM
memory management yet. After all, this is what mailing lists are for.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
