Re: [Mesa-dev] [PATCH] i965: Don't tell the hardware about our UAV access.

2015-10-07 Thread Francisco Jerez
Emil Velikov writes: > On 26 September 2015 at 21:25, Francisco Jerez wrote: >> Emil Velikov writes: >> >>> Hi all, >>> >>> On 10 September 2015 at 00:30, Mark Janes wrote: Mark Janes writes: > Francisco Jerez writes: > >> Mark Janes writes: >> >>> When I teste

Re: [Mesa-dev] [PATCH] i965: Don't tell the hardware about our UAV access.

2015-10-07 Thread Emil Velikov
On 26 September 2015 at 21:25, Francisco Jerez wrote: > Emil Velikov writes: > >> Hi all, >> >> On 10 September 2015 at 00:30, Mark Janes wrote: >>> Mark Janes writes: >>> Francisco Jerez writes: > Mark Janes writes: > >> When I tested this, I saw an intermittent BSW gpu

Re: [Mesa-dev] [PATCH] i965: Don't tell the hardware about our UAV access.

2015-09-26 Thread Francisco Jerez
Emil Velikov writes: > Hi all, > > On 10 September 2015 at 00:30, Mark Janes wrote: >> Mark Janes writes: >> >>> Francisco Jerez writes: >>> Mark Janes writes: > When I tested this, I saw an intermittent BSW gpu hang. I haven't been > able to confirm that it is due to the h

Re: [Mesa-dev] [PATCH] i965: Don't tell the hardware about our UAV access.

2015-09-24 Thread Mark Janes
Emil Velikov writes: > Hi all, > > On 10 September 2015 at 00:30, Mark Janes wrote: >> Mark Janes writes: >> >>> Francisco Jerez writes: >>> Mark Janes writes: > When I tested this, I saw an intermittent BSW gpu hang. I haven't been > able to confirm that it is due to the h

Re: [Mesa-dev] [PATCH] i965: Don't tell the hardware about our UAV access.

2015-09-24 Thread Emil Velikov
Hi all, On 10 September 2015 at 00:30, Mark Janes wrote: > Mark Janes writes: > >> Francisco Jerez writes: >> >>> Mark Janes writes: >>> When I tested this, I saw an intermittent BSW gpu hang. I haven't been able to confirm that it is due to the host-mem-barrier test. >>> It wo

Re: [Mesa-dev] [PATCH] i965: Don't tell the hardware about our UAV access.

2015-09-09 Thread Mark Janes
Mark Janes writes: > Francisco Jerez writes: > >> Mark Janes writes: >> >>> When I tested this, I saw an intermittent BSW gpu hang. I haven't been >>> able to confirm that it is due to the host-mem-barrier test. >>> >> It would probably be useful to know if the hang is due to any of the >> ima

Re: [Mesa-dev] [PATCH] i965: Don't tell the hardware about our UAV access.

2015-09-09 Thread Roland Scheidegger
Am 09.09.2015 um 15:04 schrieb Roland Scheidegger: > Am 09.09.2015 um 05:56 schrieb Ian Romanick: >> On 08/15/2015 02:24 AM, Francisco Jerez wrote: >>> Roland Scheidegger writes: >>> I guess though you'd need these bits when implementing things like ARB_fragment_shader_ordering? (Thus st

Re: [Mesa-dev] [PATCH] i965: Don't tell the hardware about our UAV access.

2015-09-09 Thread Roland Scheidegger
Am 09.09.2015 um 05:56 schrieb Ian Romanick: > On 08/15/2015 02:24 AM, Francisco Jerez wrote: >> Roland Scheidegger writes: >> >>> I guess though you'd need these bits when implementing things like >>> ARB_fragment_shader_ordering? (Thus stuff actually looks useful but I >>> don't know if anybody

Re: [Mesa-dev] [PATCH] i965: Don't tell the hardware about our UAV access.

2015-09-09 Thread Francisco Jerez
Mark Janes writes: > Francisco Jerez writes: > >> Mark Janes writes: >> >>> When I tested this, I saw an intermittent BSW gpu hang. I haven't been >>> able to confirm that it is due to the host-mem-barrier test. >>> >> It would probably be useful to know if the hang is due to any of the >> ima

Re: [Mesa-dev] [PATCH] i965: Don't tell the hardware about our UAV access.

2015-09-08 Thread Mark Janes
Francisco Jerez writes: > Mark Janes writes: > >> When I tested this, I saw an intermittent BSW gpu hang. I haven't been >> able to confirm that it is due to the host-mem-barrier test. >> > It would probably be useful to know if the hang is due to any of the > image load/store tests or if it's

Re: [Mesa-dev] [PATCH] i965: Don't tell the hardware about our UAV access.

2015-09-08 Thread Ian Romanick
On 08/15/2015 02:24 AM, Francisco Jerez wrote: > Roland Scheidegger writes: > >> I guess though you'd need these bits when implementing things like >> ARB_fragment_shader_ordering? (Thus stuff actually looks useful but I >> don't know if anybody wants to implement it in the near term.) >> > I bel

Re: [Mesa-dev] [PATCH] i965: Don't tell the hardware about our UAV access.

2015-09-08 Thread Francisco Jerez
Francisco Jerez writes: > Francisco Jerez writes: > >> Mark Janes writes: >> >>> When I tested this, I saw an intermittent BSW gpu hang. I haven't been >>> able to confirm that it is due to the host-mem-barrier test. >>> >> It would probably be useful to know if the hang is due to any of the >

Re: [Mesa-dev] [PATCH] i965: Don't tell the hardware about our UAV access.

2015-09-08 Thread Francisco Jerez
Francisco Jerez writes: > Mark Janes writes: > >> When I tested this, I saw an intermittent BSW gpu hang. I haven't been >> able to confirm that it is due to the host-mem-barrier test. >> > It would probably be useful to know if the hang is due to any of the > image load/store tests or if it's

Re: [Mesa-dev] [PATCH] i965: Don't tell the hardware about our UAV access.

2015-09-08 Thread Francisco Jerez
Mark Janes writes: > When I tested this, I saw an intermittent BSW gpu hang. I haven't been > able to confirm that it is due to the host-mem-barrier test. > It would probably be useful to know if the hang is due to any of the image load/store tests or if it's something unrelated. signature.asc

Re: [Mesa-dev] [PATCH] i965: Don't tell the hardware about our UAV access.

2015-09-08 Thread Mark Janes
When I tested this, I saw an intermittent BSW gpu hang. I haven't been able to confirm that it is due to the host-mem-barrier test. -Mark Francisco Jerez writes: > The hardware documentation relating to the UAV HW-assisted coherency > mechanism and UAV access enable bits is scarce and sometime

Re: [Mesa-dev] [PATCH] i965: Don't tell the hardware about our UAV access.

2015-09-01 Thread Francisco Jerez
Francisco Jerez writes: > The hardware documentation relating to the UAV HW-assisted coherency > mechanism and UAV access enable bits is scarce and sometimes > contradictory, and there's quite some guesswork behind this commit, so > let me summarize the background first: HSW and later hardware ha

Re: [Mesa-dev] [PATCH] i965: Don't tell the hardware about our UAV access.

2015-08-15 Thread Francisco Jerez
Roland Scheidegger writes: > I guess though you'd need these bits when implementing things like > ARB_fragment_shader_ordering? (Thus stuff actually looks useful but I > don't know if anybody wants to implement it in the near term.) > I believe that could be implemented using the thread dependenc

Re: [Mesa-dev] [PATCH] i965: Don't tell the hardware about our UAV access.

2015-08-14 Thread Roland Scheidegger
I guess though you'd need these bits when implementing things like ARB_fragment_shader_ordering? (Thus stuff actually looks useful but I don't know if anybody wants to implement it in the near term.) Roland Am 14.08.2015 um 18:27 schrieb Francisco Jerez: > The hardware documentation relating to

[Mesa-dev] [PATCH] i965: Don't tell the hardware about our UAV access.

2015-08-14 Thread Francisco Jerez
The hardware documentation relating to the UAV HW-assisted coherency mechanism and UAV access enable bits is scarce and sometimes contradictory, and there's quite some guesswork behind this commit, so let me summarize the background first: HSW and later hardware have infrastructure to support a str