lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 16 May 2019 14:21:35 +0100
From:   Steven Price <>
To:     Robin Murphy <>,
        Rob Herring <>,
        Clément Péron <>
Cc:     Mark Rutland <>,
        devicetree <>,
        Neil Armstrong <>,
        David Airlie <>,
        linux-kernel <>,
        dri-devel <>,
        Maxime Ripard <>,
        linux-sunxi <>,
        Rob Herring <>, Chen-Yu Tsai <>,
        linux-arm-kernel <>
Subject: Re: [PATCH v4 0/8] Allwinner H6 Mali GPU support

On 16/05/2019 12:19, Robin Murphy wrote:
> I was expecting to see a similar behaviour to my T620 (which I now
> assume was down to 64-bit job descriptors sort-of-but-not-quite working)
> but this does look a bit more fundamental - the fact that it's a level 1
> fault with VA == head == tail suggests to me that the MMU can't see the
> page tables at all to translate anything. I really hope that the H6 GPU
> integration doesn't suffer from the same DMA offset as the Allwinner
> display pipeline stuff, because that would be a real pain to support in
> io-pgtable.

Assuming you mean the case where the physical address (as seen by the
CPU) is different from the dma address (as seen by the GPU), then I
highly doubt it because mali_kbase doesn't support it:

[from kbase_mem_pool_alloc_page() in mali_kbase_mem_pool.c]:

	dma_addr = dma_map_page(dev, p, 0, PAGE_SIZE, DMA_BIDIRECTIONAL);
	if (dma_mapping_error(dev, dma_addr)) {
		return NULL;

	WARN_ON(dma_addr != page_to_phys(p));

That being said it's quite possible there could be something in the bus
which needs configuring to make this work - in which case your best bet
is to look at the vendor kernel and see if anything extra is poked when
the Mali driver is loaded.


Powered by blists - more mailing lists