Hello guys,
This reply will refer only to the first query (1):
1. Very bad performance from intel chipset on Thinkpad T540p
(2880x1620) (Marc MERLIN)
The solution here is switching to SNA mode on SandyBridge and newer
iterations of Intel HD Graphics core on Linux.
See the entry here for more detail:
https://gist.github.com/Brainiarc7/5e7d80753f81d27cb7c4
Regards,
Dennis.
On 24 April 2015 at 03:54, <intel-gfx-request@xxxxxxxxxxxxxxxxxxxxx> wrote:
> Send Intel-gfx mailing list submissions to
> intel-gfx@xxxxxxxxxxxxxxxxxxxxx
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> or, via email, send a message with subject or body 'help' to
> intel-gfx-request@xxxxxxxxxxxxxxxxxxxxx
>
> You can reach the person managing the list at
> intel-gfx-owner@xxxxxxxxxxxxxxxxxxxxx
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Intel-gfx digest..."
>
>
> Today's Topics:
>
> 1. Very bad performance from intel chipset on Thinkpad T540p
> (2880x1620) (Marc MERLIN)
> 2. Re: git pull] drm for v4.1-rc1 (Linus Torvalds)
> 3. Re: Very bad performance from intel chipset on Thinkpad T540p
> (2880x1620) (Chris Wilson)
> 4. Re: [PATCH -next] drm/i915/audio: remove duplicated include
> from intel_audio.c (John Hunter)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 23 Apr 2015 15:22:44 -0700
> From: Marc MERLIN <marc_xorg@xxxxxxxxxxx>
> To: intel-gfx@xxxxxxxxxxxxxxxxxxxxx
> Subject: Very bad performance from intel chipset on
> Thinkpad T540p (2880x1620)
> Message-ID: <20150423222244.GF20088@xxxxxxxxxxx>
> Content-Type: text/plain; charset=us-ascii
>
> Hi,
>
> My performance for normal work (2D, although many things like chrome use
> the GPU nowadays), and video (mplayer) is between just usable to
> horrible.
> Performance is bad enough that I'm about to replace the mainboard to get
> one with the Nvidia GeForce GT 730M 1GB. I have no idea how good or bad
> nouveau is on that, but I'm a bit desperate.
>
> Before I do that, can you let me know if I have my driver or Xorg tuned
> wrong somehow?
>
> Playing video with mplayer or youtube makes the whole UI very
> unresponsive.
> Playing a video with mplayer is mostly ok, but if I stretch the window
> just a bit, the rescalling is too slow to play real time and yet I have
> a quad core i7-4800MQ, so I doubt it's a CPU problem. Going to full
> screeen usually makes things better.
>
> I do use mplayer -vo gl since it's the only way to change
> colors/contrast/brightness.
>
> Kernel is 3.19, but problem has been there since I've had the laptop.
> X.Org X Server 1.16.4
>
> I do boot my kernel with these options I found recommended to save
> power, maybe I should remove some of them because they kill performance?
> pcie_aspm=force i915.i915_enable_rc6=7 i915.i915_enable_fbc=1 i915.semaphores=1 i915.lvds_downclock=1 acpi_backlight=vendor
>
> Relevant bits form Xorg.log:
> [ 48.720] (II) xfree86: Adding drm device (/dev/dri/card0)
> [ 49.096] (--) PCI:*(0:0:2:0) 8086:0416:17aa:2210 rev 6, Mem @ 0xf0000000/4194304, 0xe0000000/268435456, I/O @ 0x00004000/64
> [ 49.096] (II) "glx" will be loaded by default.
> [ 49.096] (II) LoadModule: "glx"
> [ 49.101] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
> [ 49.113] (II) Module glx: vendor="X.Org Foundation"
> [ 49.113] compiled for 1.16.4, module version = 1.0.0
> [ 49.113] ABI class: X.Org Server Extension, version 8.0
> [ 49.113] (**) AIGLX enabled
> [ 49.113] (II) LoadModule: "intel"
> [ 49.114] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
> [ 49.122] (II) Module intel: vendor="X.Org Foundation"
> [ 49.122] compiled for 1.15.99.904, module version = 2.21.15
> [ 49.122] Module class: X.Org Video Driver
> [ 49.122] ABI class: X.Org Video Driver, version 18.0
> [ 49.122] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
> i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
> 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
> Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
> GM45, 4 Series, G45/G43, Q45/Q43, G41, B43, HD Graphics,
> HD Graphics 2000, HD Graphics 3000, HD Graphics 2500,
> HD Graphics 4000, HD Graphics P4000, HD Graphics 4600,
> HD Graphics 5000, HD Graphics P4600/P4700, Iris(TM) Graphics 5100,
> HD Graphics 4400, HD Graphics 4200, Iris(TM) Pro Graphics 5200
> [ 49.122] (++) using VT number 7
>
> [ 49.133] (==) intel(0): Depth 24, (--) framebuffer bpp 32
> [ 49.133] (==) intel(0): RGB weight 888
> [ 49.133] (==) intel(0): Default visual is TrueColor
> [ 49.133] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 4600
> [ 49.133] (**) intel(0): Relaxed fencing enabled
> [ 49.133] (**) intel(0): Wait on SwapBuffers? enabled
> [ 49.133] (**) intel(0): Triple buffering? enabled
> [ 49.133] (**) intel(0): Framebuffer tiled
> [ 49.133] (**) intel(0): Pixmaps tiled
> [ 49.133] (**) intel(0): 3D buffers tiled
> [ 49.133] (**) intel(0): SwapBuffers wait enabled
> [ 49.133] (==) intel(0): video overlay key set to 0x101fe
> [ 49.133] (II) intel(0): Output eDP1 using monitor section Monitor0
> [ 49.133] (--) intel(0): found backlight control interface /sys/class/backlight/intel_backlight
> [ 49.134] (II) intel(0): Output VGA1 has no monitor section
> [ 49.134] (II) intel(0): Output DP1 has no monitor section
> [ 49.164] (II) intel(0): Output HDMI1 has no monitor section
> [ 49.164] (II) intel(0): Output DP2 has no monitor section
> [ 49.164] (II) intel(0): Output HDMI2 has no monitor section
> [ 49.164] (II) intel(0): EDID for output eDP1
> [ 49.164] (II) intel(0): Manufacturer: MEI Model: 96a2 Serial#: 0
> [ 49.164] (II) intel(0): Year: 2013 Week: 255
> [ 49.164] (II) intel(0): EDID Version: 1.4
> [ 49.164] (II) intel(0): Digital Display Input
> [ 49.164] (II) intel(0): 8 bits per channel
> [ 49.164] (II) intel(0): Digital interface is DisplayPort
> [ 49.164] (II) intel(0): Max Image Size [cm]: horiz.: 34 vert.: 19
>
> [ 49.201] (II) Loading sub module "dri2"
> [ 49.201] (II) LoadModule: "dri2"
> [ 49.201] (II) Module "dri2" already built-in
> [ 49.201] (==) Depth 24 pixmap format is 32 bpp
> [ 49.201] (II) intel(0): [DRI2] Setup complete
> [ 49.201] (II) intel(0): [DRI2] DRI driver: i965
> [ 49.201] (II) intel(0): Allocated new frame buffer 2880x1620 stride 11776, tiled
> [ 49.201] (II) UXA(0): Driver registered support for the following operations:
> [ 49.201] (II) solid
> [ 49.201] (II) copy
> [ 49.201] (II) composite (RENDER acceleration)
> [ 49.201] (II) put_image
> [ 49.201] (II) get_image
> [ 49.201] (==) intel(0): Backing store enabled
> [ 49.201] (==) intel(0): Silken mouse enabled
> [ 49.201] (II) intel(0): Initializing HW Cursor
> [ 49.201] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
> [ 49.201] (==) intel(0): DPMS enabled
> [ 49.201] (==) intel(0): Intel XvMC decoder enabled
> [ 49.202] (II) intel(0): Set up textured video
> [ 49.202] (II) intel(0): [XvMC] xvmc_vld driver initialized.
> [ 49.202] (II) intel(0): direct rendering: DRI2 Enabled
> [ 49.202] (==) intel(0): hotplug detection: "enabled"
> [ 49.220] (--) RandR disabled
> [ 49.223] (II) SELinux: Disabled on system
> [ 49.266] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
> [ 49.266] (II) AIGLX: enabled GLX_ARB_create_context
> [ 49.266] (II) AIGLX: enabled GLX_ARB_create_context_profile
> [ 49.266] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
> [ 49.266] (II) AIGLX: enabled GLX_INTEL_swap_event
> [ 49.266] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
> [ 49.266] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
> [ 49.266] (II) AIGLX: enabled GLX_ARB_fbconfig_float
> [ 49.266] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
> [ 49.266] (II) AIGLX: enabled GLX_ARB_create_context_robustness
> [ 49.267] (II) AIGLX: Loaded and initialized i965
> [ 49.267] (II) GLX: Initialized DRI2 GL provider for screen 0
> [ 49.267] (II) intel(0): Setting screen physical size to 762 x 428
>
> Thanks for any suggestions,
> Marc
> --
> "A mouse is a device used to point at the xterm you want to type in" - A.S.R.
> Microsoft is to operating systems ....
> .... what McDonalds is to gourmet cooking
> Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 23 Apr 2015 15:47:10 -0700
> From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
> To: Matthew Garrett <matthew.garrett@xxxxxxxxxx>
> Cc: Dave Airlie <airlied@xxxxxxxx>, "linux-pci@xxxxxxxxxxxxxxx"
> <linux-pci@xxxxxxxxxxxxxxx>, intel-gfx
> <intel-gfx@xxxxxxxxxxxxxxxxxxxxx>, Linux Kernel Mailing List
> <linux-kernel@xxxxxxxxxxxxxxx>, DRI mailing list
> <dri-devel@xxxxxxxxxxxxxxxxxxxxx>, Matthew Garrett <mjg59@xxxxxxxxxx>,
> Bjorn Helgaas <bhelgaas@xxxxxxxxxx>, Daniel Vetter
> <daniel.vetter@xxxxxxxxx>
> Subject: Re: git pull] drm for v4.1-rc1
> Message-ID:
> <CA+55aFwC+sH+62b4rDuy5PWAPEc9Xr3tWcCAQXOED+2Jk9C65A@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=UTF-8
>
> On Thu, Apr 23, 2015 at 2:56 PM, Matthew Garrett
> <matthew.garrett@xxxxxxxxxx> wrote:
>> On Thu, Apr 23, 2015 at 2:30 PM, Bjorn Helgaas <bhelgaas@xxxxxxxxxx> wrote:
>>>
>>> int pcibios_add_device(struct pci_dev *dev)
>>> {
>>> if (dev-is-default-vga-device) {
>>> dev->rom = 0xC0000;
>>> dev->romlen = 0x20000;
>>> }
>>
>> I don't know what we want to do here. This is, at some level,
>> fundamentally wrong - however, it also wouldn't surprise me if this is
>> also the only copy of the video ROM we have on some UEFI systems,
>> especially since I believe that Windows 7 still required that there be
>> a legacy ROM it could use for bootloader modesetting on UEFI
>> platforms. So simply making this conditional on BIOS may break
>> existing machines. But if there *is* a ROM there then we should be
>> able to id it from the usual video ROM signature?
>
> I'm not sure why we want that IORESOURCE_ROM_SHADOW thing at all, but
> yes, if what this is all about is the magic video ROM at 0xc0000, then
>
> (a) it should have nothing what-so-ever to do with the actual PCI
> BAR, since it's been *ages* since people actually had an expansion rom
> like that, and it's much more common that the video ROM comes as part
> of the system BIOS on laptops etc.
>
> (b) yes, the sane thing to do would be to just look for the ROM
> signature, 0x55 0xaa at 2kB incrementing headers (and checking the
> proper checksum too).
>
> There is no way to see that from the PCI device state, because as
> mentioned, quite often the "ROM" is entirely fake, and is not just
> some shadowed copy of a real underlying hardware ROM, but is
> fundamentally just a RAM image decompressed from some other source and
> then marked read-only.
>
> Linus
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 23 Apr 2015 23:49:24 +0100
> From: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>
> To: Marc MERLIN <marc_xorg@xxxxxxxxxxx>
> Cc: intel-gfx@xxxxxxxxxxxxxxxxxxxxx
> Subject: Re: Very bad performance from intel chipset on
> Thinkpad T540p (2880x1620)
> Message-ID: <20150423224924.GB5437@xxxxxxxxxxxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=us-ascii
>
> On Thu, Apr 23, 2015 at 03:22:44PM -0700, Marc MERLIN wrote:
>> I do boot my kernel with these options I found recommended to save
>> power, maybe I should remove some of them because they kill performance?
>> pcie_aspm=force i915.i915_enable_rc6=7 i915.i915_enable_fbc=1 i915.semaphores=1 i915.lvds_downclock=1 acpi_backlight=vendor
>
> Those options are broken.
>
>> Relevant bits form Xorg.log:
>> [ 49.114] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
>> [ 49.122] (II) Module intel: vendor="X.Org Foundation"
>> [ 49.122] compiled for 1.15.99.904, module version = 2.21.15
>
> Start by grabbing an updated xf86-video-intel.
> -Chris
>
> --
> Chris Wilson, Intel Open Source Technology Centre
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 24 Apr 2015 08:54:55 +0800
> From: John Hunter <zhjwpku@xxxxxxxxx>
> To: John Hunter <zhjwpku@xxxxxxxxx>, "yongjun_wei@xxxxxxxxxxxxxxxxx"
> <yongjun_wei@xxxxxxxxxxxxxxxxx>, "weiyj_lk@xxxxxxx"
> <weiyj_lk@xxxxxxx>, "intel-gfx@xxxxxxxxxxxxxxxxxxxxx"
> <intel-gfx@xxxxxxxxxxxxxxxxxxxxx>, "dri-devel@xxxxxxxxxxxxxxxxxxxxx"
> <dri-devel@xxxxxxxxxxxxxxxxxxxxx>, Daniel Vetter
> <daniel.vetter@xxxxxxxxx>
> Subject: Re: [PATCH -next] drm/i915/audio: remove
> duplicated include from intel_audio.c
> Message-ID:
> <CAEG8a3KhAaL6P2CT0FfzCY9CiTajESejJbtPFbGRCzX2gKCMzQ@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="utf-8"
>
> ok, let's keep it the the original way.
>
> On Fri, Apr 24, 2015 at 12:09 AM, Daniel Vetter <daniel@xxxxxxxx> wrote:
>
>> On Wed, Apr 22, 2015 at 10:50:55AM +0800, John Hunter wrote:
>> > Sure, but I need Daniel to admit that, because maybe include the two
>> header
>> > file make it easier to understand.
>> > And after checked other files in drm/i915, I found that a lot other file
>> do
>> > the
>> > same thing(include both header file). So I will just wait Daniel to wait
>> up
>> > and
>> > give me the order :-)
>>
>> drm/i915 headers are a bit a chaos anyway, so I'm not sure how useful that
>> would be really. And generally the trend in linux (and drm) is to have
>> split-up headers, so moving everyone to just include intel_drv.h would be
>> the "wrong" direction.
>>
>> tbh I just don't have an opinion really ;-)
>> -Daniel
>>
>> >
>> > On Wed, Apr 22, 2015 at 10:35 AM, yongjun_wei@xxxxxxxxxxxxxxxxx <
>> > yongjun_wei@xxxxxxxxxxxxxxxxx> wrote:
>> >
>> > > Hi John,
>> > >
>> > >
>> > >
>> > > Feel free to submit a new patch.
>> > >
>> > >
>> > >
>> > > Regards,
>> > >
>> > > Yongjun Wei
>> > >
>> > >
>> > >
>> > > *From:* John Hunter [mailto:zhjwpku@xxxxxxxxx]
>> > > *Sent:* 2015年4月22日 10:30
>> > > *To:* weiyj_lk@xxxxxxx; Daniel Vetter; Jani Nikula; David Airlie;
>> Yongjun
>> > > Wei (RD-CN); intel-gfx@xxxxxxxxxxxxxxxxxxxxx;
>> > > dri-devel@xxxxxxxxxxxxxxxxxxxxx; open list
>> > > *Subject:* Re: [PATCH -next] drm/i915/audio: remove
>> > > duplicated include from intel_audio.c
>> > >
>> > >
>> > >
>> > > Hi,
>> > >
>> > >
>> > >
>> > > I think maybe we should remove both of the two lines:
>> > >
>> > > #include "intel_drv.h"
>> > >
>> > > #include "i915_drv.h"
>> > >
>> > > Because we have* two* "intel_drv.h" and *one* "i915_drv.h", and
>> > >
>> > > "i915_drv.h" has already been included in the "intel_drv.h".
>> > >
>> > >
>> > >
>> > > I not sure whether i am right. If you need me to do the patch,
>> > >
>> > > let me know.
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > On Thu, Apr 16, 2015 at 10:30 PM, Daniel Vetter <daniel@xxxxxxxx>
>> wrote:
>> > >
>> > > On Thu, Apr 16, 2015 at 09:11:08PM +0800, weiyj_lk@xxxxxxx wrote:
>> > > > From: Wei Yongjun <yongjun_wei@xxxxxxxxxxxxxxxxx>
>> > > >
>> > > > Remove duplicated include.
>> > > >
>> > > > Signed-off-by: Wei Yongjun <yongjun_wei@xxxxxxxxxxxxxxxxx>
>> > >
>> > > Queued for -next, thanks for the patch.
>> > > -Daniel
>> > >
>> > > > ---
>> > > > drivers/gpu/drm/i915/intel_audio.c | 1 -
>> > > > 1 file changed, 1 deletion(-)
>> > > >
>> > > > diff --git a/drivers/gpu/drm/i915/intel_audio.c
>> > > b/drivers/gpu/drm/i915/intel_audio.c
>> > > > index 2396cc7..d00d488 100644
>> > > > --- a/drivers/gpu/drm/i915/intel_audio.c
>> > > > +++ b/drivers/gpu/drm/i915/intel_audio.c
>> > > > @@ -28,7 +28,6 @@
>> > > >
>> > > > #include <drm/drmP.h>
>> > > > #include <drm/drm_edid.h>
>> > > > -#include "intel_drv.h"
>> > > > #include "i915_drv.h"
>> > > >
>> > > > /**
>> > > >
>> > > > _______________________________________________
>> > > > Intel-gfx mailing list
>> > > > Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
>> > > > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>> > >
>> > > --
>> > > Daniel Vetter
>> > > Software Engineer, Intel Corporation
>> > > http://blog.ffwll.ch
>> > >
>> > > _______________________________________________
>> > > dri-devel mailing list
>> > > dri-devel@xxxxxxxxxxxxxxxxxxxxx
>> > > http://lists.freedesktop.org/mailman/listinfo/dri-devel
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > --
>> > >
>> > > Best regards
>> > >
>> > > Junwang Zhao
>> > >
>> > > Microprocessor Research and Develop Center
>> > >
>> > > Department of Computer Science &Technology
>> > >
>> > > Peking University
>> > >
>> > > Beijing, 100871, PRC
>> > >
>> > > =======================================================
>> > >
>> > > This message has been analyzed by Deep Discovery Email Inspector.
>> > >
>> > >
>> > >
>> > > TREND MICRO EMAIL NOTICE
>> > > The information contained in this email and any attachments is
>> confidential
>> > > and may be subject to copyright or other intellectual property
>> protection.
>> > > If you are not the intended recipient, you are not authorized to use or
>> > > disclose this information, and we request that you notify us by reply
>> mail or
>> > > telephone and delete the original message from your mail system.
>> > >
>> > >
>> >
>> >
>> > --
>> > Best regards
>> > Junwang Zhao
>> > Microprocessor Research and Develop Center
>> > Department of Computer Science &Technology
>> > Peking University
>> > Beijing, 100871, PRC
>>
>> > _______________________________________________
>> > dri-devel mailing list
>> > dri-devel@xxxxxxxxxxxxxxxxxxxxx
>> > http://lists.freedesktop.org/mailman/listinfo/dri-devel
>>
>>
>> --
>> Daniel Vetter
>> Software Engineer, Intel Corporation
>> http://blog.ffwll.ch
>>
>
>
>
> --
> Best regards
> Junwang Zhao
> Microprocessor Research and Develop Center
> Department of Computer Science &Technology
> Peking University
> Beijing, 100871, PRC
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.freedesktop.org/archives/intel-gfx/attachments/20150424/4fbb8764/attachment.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
>
> ------------------------------
>
> End of Intel-gfx Digest, Vol 87, Issue 314
> ******************************************
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
