Bug 634200 - Content of $HOME/.drirc looks like ignored by i965 driver
Summary: Content of $HOME/.drirc looks like ignored by i965 driver
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-15 13:52 UTC by Zdenek Kabelac
Modified: 2018-04-11 12:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-18 15:37:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Zdenek Kabelac 2010-09-15 13:52:38 UTC
Description of problem:

I've been trying to check raw performance of glxgears and noticed, that now when vblank is default it's not so easy to disable it via 'suggested' way by using .drirc file in my home directory.

I've checked several various combinations in this file and never found a working version:

i.e.:
--
<driconf>
        <device screen="0" driver="i965">

                <application name="all">
                        <option name="vblank_mode" value="3" />
                </application>

                <application name="glxgears" executable="glxgears">        
                        <option name="vblank_mode" value="0"/>
                </application>

        </device>
</driconf>
--

However plain simple usage of   'vblank_mode=0 glxgears'  on command line seems to have desired effect and vblank is no longer slowing down FPS numbers.
And it give this output:

$ vblank_mode=0 glxgears
ATTENTION: default value of option vblank_mode overridden by environment.
ATTENTION: default value of option vblank_mode overridden by environment.
ATTENTION: option value of option vblank_mode ignored.
ATTENTION: option value of option vblank_mode ignored.


Version-Release number of selected component (if applicable):
mesa-dri-drivers-7.9-0.7.fc15.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Artem S. Tashkinov 2010-10-22 12:59:25 UTC
Confirming.

I have done the following:

$ xvattr -a XV_SYNC_TO_VBLANK -v 0
$ export vblank_mode=0

and installed .drirc

<driconf>
    <device screen="0" driver="dri2">
        <application name="Default">
            <option name="vblank_mode" value="0" />
        </application>
    </device>
</driconf>

and I still get:

$ glxgears
ATTENTION: default value of option vblank_mode overridden by environment.
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
301 frames in 5.0 seconds = 60.068 FPS

Comment 2 Artem S. Tashkinov 2010-11-03 21:52:30 UTC
It seems to be fixed in Fedora 14 at least for intel driver.

Comment 3 Matěj Cepl 2011-03-16 07:24:49 UTC
(In reply to comment #2)
> It seems to be fixed in Fedora 14 at least for intel driver.

??? This was reported against Rawhide (F16), which may mean the reporter actually uses F15.

Comment 4 Artem S. Tashkinov 2011-03-16 15:20:34 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > It seems to be fixed in Fedora 14 at least for intel driver.
> 
> ??? This was reported against Rawhide (F16), which may mean the reporter
> actually uses F15.

You are smoking something very weird.

First of all, this bug is no longer valid.

Secondly, this bug report was reported on 2010-09-15, even before F14 was out (2010–11-02).

Comment 5 Zdenek Kabelac 2011-03-16 16:03:08 UTC
I can confirm it currently does work on my rawhide mixture of F15/F16
currently using this package:

mesa-dri-drivers-7.10-0.27.fc15.x86_64

Comment 6 Artem S. Tashkinov 2011-03-16 18:22:27 UTC
(In reply to comment #5)
> I can confirm it currently does work on my rawhide mixture of F15/F16
> currently using this package:
> 
> mesa-dri-drivers-7.10-0.27.fc15.x86_64

Then do us a favour, please, close this bug report as RESOLVED/FIXED.

Thank you.


Note You need to log in before you can comment on or make changes to this bug.