On 11/13/2017 10:27 AM, Christian König wrote:
Am 13.11.2017 um 15:57 schrieb Andrey Grodzovsky:
On 11/13/2017 07:39 AM, Christian König wrote:
Am 13.11.2017 um 12:32 schrieb Michel Dänzer:
On 12/11/17 10:35 AM, Christian König wrote:
A few comments on the code:
+/* Validate bo size is b
Am 13.11.2017 um 15:57 schrieb Andrey Grodzovsky:
On 11/13/2017 07:39 AM, Christian König wrote:
Am 13.11.2017 um 12:32 schrieb Michel Dänzer:
On 12/11/17 10:35 AM, Christian König wrote:
A few comments on the code:
+/* Validate bo size is bit bigger then the request domain */
+static inlin
On 11/13/2017 07:39 AM, Christian König wrote:
Am 13.11.2017 um 12:32 schrieb Michel Dänzer:
On 12/11/17 10:35 AM, Christian König wrote:
A few comments on the code:
+/* Validate bo size is bit bigger then the request domain */
+static inline bool amdgpu_bo_validate_bo_size(struct amdgpu_dev
Am 13.11.2017 um 12:32 schrieb Michel Dänzer:
On 12/11/17 10:35 AM, Christian König wrote:
A few comments on the code:
+/* Validate bo size is bit bigger then the request domain */
+static inline bool amdgpu_bo_validate_bo_size(struct amdgpu_device
*adev,
+ unsigned long s
On 12/11/17 10:35 AM, Christian König wrote:
> A few comments on the code:
>
>> +/* Validate bo size is bit bigger then the request domain */
>> +static inline bool amdgpu_bo_validate_bo_size(struct amdgpu_device
>> *adev,
>> + unsigned long size, u32 domain)
> Drop the inline
A few comments on the code:
+/* Validate bo size is bit bigger then the request domain */
+static inline bool amdgpu_bo_validate_bo_size(struct amdgpu_device *adev,
+ unsigned long size, u32 domain)
Drop the inline keyword and the second _bo_ in the name here.
+{
+ str
On 11/10/2017 10:48 AM, Christian König wrote:
Am 10.11.2017 um 16:36 schrieb Andrey Grodzovsky:
On 11/10/2017 07:17 AM, Christian König wrote:
Series is Acked-by: Christian König .
Please note that I think your OOM killer test shows quite a bug we
currently have in the kernel driver.
A
Am 10.11.2017 um 16:36 schrieb Andrey Grodzovsky:
On 11/10/2017 07:17 AM, Christian König wrote:
Series is Acked-by: Christian König .
Please note that I think your OOM killer test shows quite a bug we
currently have in the kernel driver.
A single allocation of 1TB shouldn't trigger the OO
On 11/10/2017 07:17 AM, Christian König wrote:
Series is Acked-by: Christian König .
Please note that I think your OOM killer test shows quite a bug we
currently have in the kernel driver.
A single allocation of 1TB shouldn't trigger the OOM killer, but
rather be reacted immediately.
May
Am 10.11.2017 um 13:17 schrieb Christian König:
Series is Acked-by: Christian König .
Please note that I think your OOM killer test shows quite a bug we
currently have in the kernel driver.
A single allocation of 1TB shouldn't trigger the OOM killer, but
rather be reacted immediately.
Typo
Series is Acked-by: Christian König .
Please note that I think your OOM killer test shows quite a bug we
currently have in the kernel driver.
A single allocation of 1TB shouldn't trigger the OOM killer, but rather
be reacted immediately.
Instead I expected that we need to do multiple 1GB al
THe following patch series intoroduce dynamic tests dusabling/enabling
in amdgpu tester using Cunit API. Today test suits that
don't apply to specific HW just return success w/o executing while
single tests that can't be executed properly are commented out.
Suits are diasbled based on hooks the
12 matches
Mail list logo
