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  linux-hardening  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:	Mon, 10 Nov 2014 16:20:34 -0500
From:	Alex Deucher <>
To:	Dave Airlie <>
Cc:	Oded Gabbay <>,
	Alex Deucher <>,
	dri-devel <>,
	LKML <>
Subject: Re: [PATCH v5 00/24] AMDKFD Kernel Driver

On Mon, Nov 10, 2014 at 4:16 PM, Dave Airlie <> wrote:
>>> How does amdkfd interfact with runtime pm on the radeon driver? I'd expect
>>> some calls to the runtime get/put functions in some places.
>>> Dave.
>> Hi Dave,
>> Per Jerome's request from the first time he saw the driver, we removed all
>> the "register bashing" code from amdkfd and moved them to the interface file
>> between amdkfd and radeon, which is part of the radeon driver.
>> See "[PATCH v5 05/24] drm/radeon: Add radeon <--> amdkfd interface" for the
>> implementation of that interface file.
> So in GPU offload mode, how does amdkfd wake the GPU up to execute
> stuff?
> GPU offload is where the radeon GPU is a secondary GPU and we power it
> down automatically.
> Granted I think our powerdown should probably check if the GPU is executing
> anything a bit more, but I don't think amdkfd can even wake it up to submit
> work at the moment.

Currently we never power down APUs (only dGPUs) and kfd only supports
APUs so they should always be available.  It will definitely need to
be handled properly if we eventually support dGPUs with the kfd.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists