HI Emil,
See below.
Thanks,
Alex
From: Emil Velikov
Sent: Friday, January 20, 2017 8:24 AM
To: Xie, AlexBin
Cc: amd-gfx mailing list
Subject: Re: [PATCH libdrm 2/3] amdgpu: A new option to choose which device to
run most tests
On
On 20 January 2017 at 19:14, Xie, AlexBin wrote:
> Hi Emil,
>
>
> Thanks for the comments.
>
>
> Please see below.
>
>
> Regards,
>
> Alex Bin Xie
>
>
>
>
> From: Emil Velikov
> Sent: Friday, January 20, 2017 8:18 AM
Hi Emil,
Thanks for the comments.
Please see below.
Regards,
Alex Bin Xie
From: Emil Velikov
Sent: Friday, January 20, 2017 8:18 AM
To: Xie, AlexBin
Cc: amd-gfx mailing list
Subject: Re: [PATCH libdrm 1/3] amdgpu: verify the
On 19 January 2017 at 22:53, Alex Xie wrote:
> This can be used to test multiple GPUs
>
> Signed-off-by: Alex Xie
> ---
> tests/amdgpu/amdgpu_test.c | 25 -
> 1 file changed, 20 insertions(+), 5 deletions(-)
>
> diff --git
On Fri, Jan 20, 2017 at 06:11:50PM +0900, Michel Dänzer wrote:
> On 20/01/17 04:44 PM, Nils Holland wrote:
> >
> > Sounds like a good idea! I was a bit heasitant because, to be honest,
> > I'm not at all an expert about the code in question and basically only
> > saw how you fixed the issue in
Yeah, thought about that possibility as well when we change the padding
to 256.
This happens every time our command submission uses more than 128 dw, in
this case you obviously have less than 128 padding.
But why doesn't this happen on Windows then?
Regards,
Christian.
Am 19.01.2017 um
Am 20.01.2017 um 04:45 schrieb zhoucm1:
some small nitpick...
On 2017年01月20日 06:53, Alex Xie wrote:
Verify the vender ID and driver name.
Open all AMDGPU devices.
Provide an option to open render node.
Tested as root: PASS
Tested as non-privileged user:
All tests failed as expected