Re: [PATCH] riscv: Support non-coherency memory model
From: Christoph Hellwig
Date: Mon Apr 22 2019 - 12:18:35 EST
On Mon, Apr 22, 2019 at 11:44:30PM +0800, guoren@xxxxxxxxxx wrote:
> - Add _PAGE_COHERENCY bit in current page table entry attributes. The bit
> designates a coherence for this page mapping. Software set the bit to
> tell the hardware that the region of the page's memory area must be
> coherent with IOs devices in SOC system by PMA settings.
> If IOs and CPU are already coherent in SOC system, CPU just ignore
> this bit.
> PTE format:
> | XLEN-1 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0
> PFN C RSW D A G U X W R V
> BIT(9): Coherence attribute bit
> 0: hardware needn't keep the page coherenct and software will
> maintain the coherence with cache clear/invalid operations.
> 1: hardware must keep the page coherenct and software needn't
> maintain the coherence.
> BIT(8): Reserved for software and now it's _PAGE_SPECIAL in linux
> Add a new hardware bit in PTE also need to modify Privileged
> Architecture Supervisor-Level ISA:
> - Add SBI_FENCE_DMA 9 in riscv-sbi.
> sbi_fence_dma(start, size, dir) could synchronize CPU cache data with
> DMA device in non-coherency memory model. The third param's definition
> is the same with linux's in include/linux/dma-direction.h:
Please don't make this an SBI call. We need a proper instruction
for cache flushing and invalidation. We'll also need that for pmem
support for example. I heard at least one other vendor already
had an instruction, and we really need to get this into the privileged
spec ASAP (yesterday in fact).
If you have your own instructions already we can probably binary
patch those in using the Linux alternatives mechanism once we have
a standardized way in the privileged spec.
We should probably start a working group for this ASAP unless we can
get another working group to help taking care of it.
> +#define pgprot_noncached pgprot_noncached
> +static inline pgprot_t pgprot_noncached(pgprot_t _prot)
> + unsigned long prot = pgprot_val(_prot);
> + prot |= _PAGE_COHERENCY;
> + return __pgprot(prot);
Nitpick: this can be shortened to
return __pgprot(pgprot_val(prot) | _PAGE_COHERENCY));
Also is this really a coherent flag, or an 'uncached' flag like in
many other architectures?
> +++ b/arch/riscv/mm/dma-mapping.c
This should probably be called dma-noncoherent.c
It should also have a user visible config option so that we don't
have to build it for fully coherent systems.
> +void arch_dma_prep_coherent(struct page *page, size_t size)
> + memset(page_address(page), 0, size);
No need for this memset, the caller takes care of it.
> diff --git a/arch/riscv/mm/ioremap.c b/arch/riscv/mm/ioremap.c
> index bd2f2db..f6aaf1e 100644
> --- a/arch/riscv/mm/ioremap.c
> +++ b/arch/riscv/mm/ioremap.c
> @@ -73,7 +73,7 @@ static void __iomem *__ioremap_caller(phys_addr_t addr, size_t size,
> void __iomem *ioremap(phys_addr_t offset, unsigned long size)
> - return __ioremap_caller(offset, size, PAGE_KERNEL,
> + return __ioremap_caller(offset, size, PAGE_KERNEL_COHERENCY,
I think ioremap is a different story, and should be a separate patch.