On 07.08.2012, at 23:01, Scott Wood scottw...@freescale.com wrote:
On 08/07/2012 05:57 AM, Alexander Graf wrote:
When we map a page that wasn't icache cleared before, do so when first
mapping it in KVM using the same information bits as the Linux mapping
logic. That way we are 100% sure
On 07.08.2012, at 23:01, Scott Wood scottw...@freescale.com wrote:
On 08/07/2012 05:57 AM, Alexander Graf wrote:
When we map a page that wasn't icache cleared before, do so when first
mapping it in KVM using the same information bits as the Linux mapping
logic. That way we are 100% sure
On 08/07/2012 05:57 AM, Alexander Graf wrote:
When we map a page that wasn't icache cleared before, do so when first
mapping it in KVM using the same information bits as the Linux mapping
logic. That way we are 100% sure that any page we map does not have stale
entries in the icache.
What
When we map a page that wasn't icache cleared before, do so when first
mapping it in KVM using the same information bits as the Linux mapping
logic. That way we are 100% sure that any page we map does not have stale
entries in the icache.
What we really would need is a method to flush the icache
When we map a page that wasn't icache cleared before, do so when first
mapping it in KVM using the same information bits as the Linux mapping
logic. That way we are 100% sure that any page we map does not have stale
entries in the icache.
What we really would need is a method to flush the icache
On 08/07/2012 05:57 AM, Alexander Graf wrote:
When we map a page that wasn't icache cleared before, do so when first
mapping it in KVM using the same information bits as the Linux mapping
logic. That way we are 100% sure that any page we map does not have stale
entries in the icache.
What
