On 02/20/2013 04:22 PM, Stuart Yoder wrote:
On Tue, Feb 19, 2013 at 1:47 PM, Scott Wood <scottw...@freescale.com> wrote:
This patch addresses boot-time invalidations only. How will you handle
hugetlb invalidations (or indirect entry invalidations, once that becomes
supported)?
We do envision that "direct guest TLB management" is an opt-in option
that a guest can enable.
If LRAT is on, with TLB management directly handled by guests, the only
mechanism we have to do TLB1 invalidates is tlbwe. That is our only option
as far as I know. So, hugetlb and indirect entries will each need to be
addressed separately. The kernel code that handles these either needs
to be A) modified to unconditionally do all invalidates by tlbwe or B)
conditionally
use tlbwe depending on whether this is a guest that has enabled direct
TLB management.
Stuart
In case of indirect entries I think we can configure tlbwe and tlbilx to
go to the hypervisor. The guest should not mix tlbwe (for TLB0) and
hardware page table walk, so we can support this scenario without
modifying the guest.
Diana
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
