[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH v2 0/1] xen/arm: Map mmio-sram nodes as cached memory
From: "Edgar E. Iglesias" <edgar.iglesias@xxxxxxxxxx> This patch changes the mapping from non-cached to cached for mmio-sram nodes that do not have the no-memory-wc property. This is a hang-over from 4.8 since the mmio-sram patches went in late in the cycle. I've explained the rationale in the commit message: Although on chip memories are relatively fast compared to off-chip memories, large on chip memories are still significantly slower than L1 caches. Depending on the memory, either cached or uncached may make most sense. Also, hardware domains may like to use the memory in a cache-coherent way to avoid SW managed coherency. By mapping it cached at S2, we let hardware domains select cacheability via S1 mappings. This was also discussed here: https://lists.xenproject.org/archives/html/xen-devel/2016-05/msg02412.html Were we reached the conclusion that we should be using the most relaxed attributes as long as we don't compromise security. Since mmio-sram DTS noders have a property (no-memory-wc) to describe srams with access restrictions, we can select the most relaxed mode for unrestricted ones. Cheers, Edgar ChangeLog: v1 -> v2: * Spell out On Chip Memories (OCMs) * Avoid dom0 in preference of hardware domains * Fix spelling of although Edgar E. Iglesias (1): xen/arm: Map mmio-sram nodes as cached memory xen/arch/arm/domain_build.c | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) -- 2.7.4 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |