[apitrace] Regarding egl retrace

[Arun Sl]

Hello All,

Can anyone in this list help me with the issues described in the mails 
below?

Thanks & Regards
Arun S L



From:
Juha-Pekka Heikkilä <juha-pekka.heikkila at linux.intel.com>
To:
"Arun Sl" <arun.sl at tcs.com>
Date:
11/28/2013 05:21 PM
Subject:
Re: [apitrace] Regarding egl retrace



Hei Arun,

This problem is a bit beyond me without digging deeper with a debugger. I
think you would get good answers for this problem from the Apitrace list.
I can see where the error is emitted from inside Mesa but don't really
know what is causing it here.

/Juha-Pekka

On Thu, November 28, 2013 1:08 pm, Arun Sl wrote:
> Hello Juha,
>
> I got the following error now:
>
> $ glretrace --pgpu app_process.trace
> # call no gpu_start gpu_dura cpu_start cpu_dura vsize_start vsize_dura
> rss_start rss_dura pixels program name
> X Error of failed request:  GLXBadProfileARB
>   Major opcode of failed request:  153 (GLX)
>   Minor opcode of failed request:  34 ()
>   Serial number of failed request:  22
>   Current serial number in output stream:  20
>
> PS: changed the subject line as we are now discussing a different topic 
:)
>
> Thanks & Regards
> Arun S L
>
>
>
> From:
> Juha-Pekka Heikkilä <juha-pekka.heikkila at linux.intel.com>
> To:
> "Arun Sl" <arun.sl at tcs.com>
> Date:
> 11/28/2013 02:58 PM
> Subject:
> Re: [waffle] Compiling waffle against latest Android source tree
>
>
>
> Hi Arun,
>
> GL_EXT_timer_query is GL extension. You could try if glretracer works 
for
> you on the desktop for profiling, the code that will be executed is 
anyhow
> the same inside Mesa. I don't know how other's use this in Apitrace but
> you could ask on the Apitrace list, I am actually now also interested to
> know. :)
>
> Of course you have to remember the numbers you get from profiling on
> desktop are not comparable to numbers you get from your embedded device
> unless you are working with Intel GenX graphics also on the embedded
> device. Different HW accelerators and different drivers even for the 
same
> accelerator behave very differently.
>
> /Juha-Pekka
>
>
> On Thu, November 28, 2013 10:26 am, Arun Sl wrote:
>> Hello Juha,
>>
>> I do not have a device with me to test right away, we are in process of
>> procuring.
>>
>> I am not able to do gpu profiling for the traces taken on emulator on
>> emulator or on desktop.
>>
>> My display hardware details are as follows:
>>
>> *-display
>>              description: VGA compatible controller
>>              product: 2nd Generation Core Processor Family Integrated
>> Graphics Controller
>>              vendor: Intel Corporation
>>              physical id: 2
>>              bus info: pci at 0000:00:02.0
>>              version: 09
>>              width: 64 bits
>>              clock: 33MHz
>>              capabilities: msi pm vga_controller bus_master cap_list 
rom
>>              configuration: driver=i915 latency=0
>>              resources: irq:42 memory:fe000000-fe3fffff
>> memory:d0000000-dfffffff ioport:f000(size=64)
>>
>> My desktop version when run for gpu profiling, it gives the following
>> error (error is same when the binary is run for gpu profiling within
>> amdroid emulator):
>>
>> ~$ eglretrace --pgpu app_process.trace
>> libEGL warning: failed to create a pipe screen for i965
>> # call no gpu_start gpu_dura cpu_start cpu_dura vsize_start vsize_dura
>> rss_start rss_dura pixels program name
>> Error: Cannot run profile, GL_EXT_timer_query extension is not
> supported.
>>
>> I guess this means that the Mesa libraries for libEGL does not have the
>> GL_EXT_timer_query extention implemented. And since the same library is
>> used in emulator also (as we are making use of host gpu capabilities on
>> emulator) there also this fails. So to profile I will have to have a
> real
>> device. Is there any update you may know which will help get gpu
> profiling
>> info on desktop?
>>
>> PS: if I run native openGL applications (I guess they make use of libGL
>> library), the GPU profiling works on desktop.
>>
>> Thanks & Regards
>> Arun S L
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/apitrace/attachments/20131203/bea01026/attachment.html>