From: Dave Airlie
This is ported from the same code in the ati and intel drivers,
It uses the same option name as nvidia and the other DDXes to
disable tearing down outputs as it is hard to avoid racing with clients.
v2: address two issues with DeleteUnusedDP12 enabled, reported
by Daniel Marti
Dave Airlie writes:
> It uses the same option name as nvidia and the other DDXes to
> disable tearing down outputs as it is hard to avoid racing with
> clients.
I don't think having an option here is useful -- either we figure out
some way to make this reliable for clients, or we abandon the not
On 14 April 2015 at 00:51, Keith Packard wrote:
> Dave Airlie writes:
>
>> It uses the same option name as nvidia and the other DDXes to
>> disable tearing down outputs as it is hard to avoid racing with
>> clients.
>
> I don't think having an option here is useful -- either we figure out
> some
Dave Airlie writes:
> So we hot unplug, we remove the output XID from the server, in
> parallel the client does an operation with the output XID it has
> gotten already, and still believe is valid, and it gets BadMatch, and
> since hardly anyone handles X errors it falls over.
Yeah, I was curiou
On 14 April 2015 at 13:12, Keith Packard wrote:
> Dave Airlie writes:
>
>> So we hot unplug, we remove the output XID from the server, in
>> parallel the client does an operation with the output XID it has
>> gotten already, and still believe is valid, and it gets BadMatch, and
>> since hardly an
On 04/19/2015 08:52 PM, Dave Airlie wrote:
On 14 April 2015 at 13:12, Keith Packard wrote:
Dave Airlie writes:
So we hot unplug, we remove the output XID from the server, in
parallel the client does an operation with the output XID it has
gotten already, and still believe is valid, and it ge
