Re: [PATCH] drm/amd/amdgpu: Allow broadcast on debugfs read (v2)

On 13/10/16 04:20 PM, Michel Dänzer wrote: > On 13/10/16 12:39 AM, StDenis, Tom wrote: >> It comes from amdgpu_query_gpu_info_init() >> >> >> for (i = 0; i < (int)dev->info.num_shader_engines; i++) { >> unsigned instance = (i << AMDGPU_INFO_MMR_SE_INDEX_SHIFT) | >>

[PATCH xf86-video-ati 1/2] Order unique chipsets according to first appearance in ati_pciids.csv

From: Michel Dänzer Instead of lexically. This makes it more likely for similar generations to be close to each other in the list of unique chipsets. Signed-off-by: Michel Dänzer --- src/pcidb/parse_pci_ids.pl | 9 +- src/radeon_chipset_gen.h

Re: [PATCH] drm/amdgpu/st: move ATC CG golden init from gfx to mc

Am 18.10.2016 um 06:34 schrieb Alex Deucher: It's technically an MC register so make sure we initialize it in the MC module rather than the gfx module. Since other bits in the same register are used to enable ATC CG features make sure we apply the golden setting first. Signed-off-by: Alex

Re: [PATCH 1/3] x86/pat: export io memory reserve/free api.

On 18 Oct. 2016 17:23, "Edward O'Callaghan" wrote: > > NACK, > > I think you want to use 'iomap_create_wc()' instead to avoid aliasing. Please explain what can alias here? Dave. > > Kind Regards, > Edward. > > On 10/18/2016 05:13 PM, Dave Airlie wrote: > > From:

Re: mm: fix cache mode tracking in vm_insert_mixed() breaks AMDGPU [was: Re: Latest testing with drm-next-4.9-wip and latest LLVM/mesa stack - Regression in PowerPlay/DPM on CIK?]

On Tue, Oct 18, 2016 at 08:01:01AM +1000, Dave Airlie wrote: > On 18 October 2016 at 07:25, Dan Williams wrote: > > On Sun, Oct 16, 2016 at 1:53 PM, Dave Airlie wrote: > >> On 17 October 2016 at 04:41, Marek Olšák wrote: > >>> On

Re: [PATCH 1/3] x86/pat: export io memory reserve/free api.

On 10/18/2016 07:29 PM, Dave Airlie wrote: > On 18 Oct. 2016 17:23, "Edward O'Callaghan" > wrote: >> >> NACK, >> >> I think you want to use 'iomap_create_wc()' instead to avoid aliasing. > > Please explain what can alias here?

[PATCH xf86-video-ati 2/2] Remove PCI IDs and bus type from ati_pciids.csv

From: Michel Dänzer This cleans up the list of unique chipsets a little further. Signed-off-by: Michel Dänzer --- src/pcidb/ati_pciids.csv | 282 - src/radeon_chipset_gen.h | 526

[PATCH 3/3] amdgpu: reserve VRAM ranges in PAT memtype tables.

From: Dave Airlie Signed-off-by: Dave Airlie --- drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c index 887483b..3142d70

[PATCH 2/3] drm/ttm: add API to reserve/free WC memory.

From: Dave Airlie These will be used by drivers to reserve/free WC memory in the PAT tracking tables, for VRAM BARs. Signed-off-by: Dave Airlie --- drivers/gpu/drm/ttm/ttm_bo_util.c | 24 include/drm/ttm/ttm_bo_driver.h | 2

[rfc] fix for regression in pat memory tracking in 4.9-rc1

Okay I spent some time looking into it, and this is the result. We have to manually insert the VRAM BAR into the pat memory tracking table as WC. The only other way things get inserted are via ioremap, which we never do for the whole VRAM BAR. We could in theory map the VRAM BAR using the iomap

[PATCH 1/3] x86/pat: export io memory reserve/free api.

From: Dave Airlie These functions are needed for gpu/ttm drivers to reserve the VRAM area as write combined. In a lot of places we don't ioremap but still need to insert pfn from it into a VMA using vm_insert_mixed, but a recent change in mixed insertion means we need to

Re: [PATCH 1/3] x86/pat: export io memory reserve/free api.

NACK, I think you want to use 'iomap_create_wc()' instead to avoid aliasing. Kind Regards, Edward. On 10/18/2016 05:13 PM, Dave Airlie wrote: > From: Dave Airlie > > These functions are needed for gpu/ttm drivers to reserve the > VRAM area as write combined. In a lot of

Re: [PATCH xf86-video-amdgpu] amdgpu_probe: Do not close server managed drm fds

[ Moving to the amd-gfx mailing list, where xf86-video-amdgpu (and -ati) patches are reviewed ] On 18/10/16 11:48 PM, Hans de Goede wrote: > This fixes the xserver only seeing AMD/ATI devices supported by the amdgpu > driver, as by the time xf86-video-ati gets a chance to probe them, the > fd