Results 1 to 7 of 7

Thread: GLX_MESA_query_renderer Extension Published

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    13,398

    Default GLX_MESA_query_renderer Extension Published

    Phoronix: GLX_MESA_query_renderer Extension Published

    After talking about it for months with numerous software developers, game studios, and other stakeholders, Ian Romanick of Intel has published his initial specification on GLX_MESA_query_renderer, a new GLX extension (and coming to EGL too) for helping ISVs (and namely games) better understand the system they're running on...

    http://www.phoronix.com/vr.php?view=MTMxNTg

  2. #2
    Join Date
    Sep 2010
    Posts
    564

    Default

    Nice. However useless for another 6-12 moths unless mesa folks want to backport that extension to 9.0 and earlier. Hope its possible.

  3. #3
    Join Date
    Jan 2010
    Posts
    159

    Default

    Quote Originally Posted by przemoli View Post
    Nice. However useless for another 6-12 moths unless mesa folks want to backport that extension to 9.0 and earlier. Hope its possible.
    Won't happen. There are also no programs that use this extension yet, so there really is no reason to backport it.

  4. #4
    Join Date
    Sep 2010
    Posts
    564

    Default

    Quote Originally Posted by Ragas View Post
    Won't happen. There are also no programs that use this extension yet, so there really is no reason to backport it.
    Since it was created with input of actual app developer one can presume that at least some will start using it shortly.

    For example Valve may want to use it for their Steam client. (Also Valve release dev tool for their steam client integration for Win, and OSX, this extension nicely fit for Linux version!)
    Same probably goes for apitrace which could be updated to use it (as main discovery method or as verification that data obtained by other ways is correct and full).

  5. #5
    Join Date
    Sep 2010
    Posts
    419

    Default

    Some things about this.
    Don't call it GLX_(some specific driver or something that does not mean anything)_query_renderer.
    Give it something like GLX_query_graphics_renderer or something like that.
    It should be able to give me:
    - all GPU's
    - all active GPU's
    - all allowed to use GPU's
    - how much ram for each GPU, how much is dedicated and how much is shared with CPU or other processors.
    - if there are power saving limitations
    - what driver(s) there (are)is for each GPU
    - if a driver is cpu
    - what driver versions there is, are
    - what api the drivers support for each GPU.
    - ...

    do a seperate one for each api:
    GLX_OpenGL_query_capabilities
    - what profiles are supported
    - what versions are supported
    - ES versions supported
    - any things in non-hardware
    - ...

    GLX_EGL_query_capabilities
    ...

    ...

    The general GLX extension is for query what hardware there is and the api specific should concern themselves with how, what the api is supported. The api ones have a dependency on the general one.
    Last edited by plonoma; 03-02-2013 at 10:23 AM.

  6. #6
    Join Date
    Sep 2010
    Posts
    564

    Default

    Quote Originally Posted by plonoma View Post
    Some things about this.
    Don't call it GLX_(some specific driver or something that does not mean anything)_query_renderer.
    Give it something like GLX_query_graphics_renderer or something like that.
    It should be able to give me:
    - all GPU's
    - all active GPU's
    - all allowed to use GPU's
    - how much ram for each GPU, how much is dedicated and how much is shared with CPU or other processors.
    - if there are power saving limitations
    - what driver(s) there (are)is for each GPU
    - if a driver is cpu
    - what driver versions there is, are
    - what api the drivers support for each GPU.
    - ...

    do a seperate one for each api:
    GLX_OpenGL_query_capabilities
    - what profiles are supported
    - what versions are supported
    - ES versions supported
    - any things in non-hardware
    - ...

    GLX_EGL_query_capabilities
    ...

    ...

    The general GLX extension is for query what hardware there is and the api specific should concern themselves with how, what the api is supported. The api ones have a dependency on the general one.
    What is "query_renderer" ???

    And lets not forget that MESA is there because it IS driver specific extension. And nobody outside MESA use it. (Nvidia may soon add GLX_NV_query_renderer if they fancy, though)
    GLX is there to account for protocol against which extension was made.

    Now if somebody officially added GLX extendsion, then MESA can be dropped from official extension. Its called "promotion".

    And it work that way so standardization body can CHANGE original extension.

    All above is simple mimic of how OpenGL is being made. (NV/AMD/APPLE/MESA for driver specific extensions, EXT when some OEM's banch up and come with "unified" version, ARB for officially blessed one)

    Anyway GLX is dead. :P

    EGL is now THE way to do things. And EGL is managed by Khronos, not Mesa. So MESA is there to notify who is author of this extension.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •