[PATCH] drm/amdgpu:implement CONTEXT_CONTROL (v3)

[Liu, Monk]

Hi Bas & Christian

I'm not familiar with the policy of upstream kernel driver, so I cannot say if your proposal is doable or not,

I have questions:

1) Is that my patch must work with current MESA driver ? (even MESA doesn't change any bit of its logic) ?
2) is that my patch can let kmd go to a new path (using CONTEXT_CONTROL) with bump up the KMS version ?
3) will MESA change its logic (align with close OGL driver) and bump up its version so that new version MESA can work with new version KMS/kmd?

With above question addressed, we can together discuss how to modify CONTEXT_CONTROL patch

BR Monk




-----Original Message-----
From: Koenig, Christian 
Sent: Monday, September 05, 2016 7:57 PM
To: Liu, Monk <Monk.Liu at amd.com>
Cc: brahma_hybrid_dev <brahma_hybrid_dev at amd.com>
Subject: Re: [PATCH] drm/amdgpu:implement CONTEXT_CONTROL (v3)

Another possible solution which just came to my mind: Completely ignore the preamble flag on the IB on keep the existing preamble handling as it is.

Just insert a CONTEXT_CONTROL package at the beginning of the command submission controlled by if we have seen a context switch or not and then raise the driver version number.

Then we can fix Mesa to not emit the CONTEXT_CONTROL commands from the UMD any more and when SR-IOV comes out we add a handling to ignore the preamble flag in the kernel when it is activated.

Does that sounds like it should work?

Regards,
Christian.