public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jan Niggemann <jn@hz6.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Egbert Eich <eich@suse.com>, intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: i915 irq storm mitigation in 3.10
Date: Thu, 25 Jul 2013 23:23:24 +0200	[thread overview]
Message-ID: <a9eb123e84afe0bd3bfd4f169180a516@hz6.de> (raw)
In-Reply-To: <CAKMK7uGiFaAROx6Nm-MzbFW9Z76brD4cqwCBcTk8Z5f6YOh9HQ@mail.gmail.com>

Hi Daniel,

Am 25.07.2013 11:58, schrieb Daniel Vetter:
> Can you pls try the below
> patch (on top of Egbert's debug stuff)?
>
> diff --git a/drivers/gpu/drm/i915/i915_reg.h
> b/drivers/gpu/drm/i915/i915_reg.h
> index 6caa748..2d4c884 100644
> --- a/drivers/gpu/drm/i915/i915_reg.h
> +++ b/drivers/gpu/drm/i915/i915_reg.h
> @@ -1925,9 +1925,9 @@
>
>  #define PORT_HOTPLUG_STAT      (dev_priv->info->display_mmio_offset
> + 0x61114)
>  /* HDMI/DP bits are gen4+ */
> -#define   PORTB_HOTPLUG_LIVE_STATUS               (1 << 29)
> +#define   PORTD_HOTPLUG_LIVE_STATUS               (1 << 29)
>  #define   PORTC_HOTPLUG_LIVE_STATUS               (1 << 28)
> -#define   PORTD_HOTPLUG_LIVE_STATUS               (1 << 27)
> +#define   PORTB_HOTPLUG_LIVE_STATUS               (1 << 27)
>  #define   PORTD_HOTPLUG_INT_STATUS             (3 << 21)
>  #define   PORTC_HOTPLUG_INT_STATUS             (3 << 19)
>  #define   PORTB_HOTPLUG_INT_STATUS             (3 << 17)
I did, here are the logs:
364K http://files.hz6.de/kern_20130724_2.log
I don't understand what exactly this patch does, but I noticed:
- much less drm debug info, resulting in a much smaller log
- no more noticeable lag on my system (even though a storm was 
detected).
I double checked the latter and the lag seems indeed to be gone...

Jan

  parent reply	other threads:[~2013-07-25 21:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-06 21:41 i915 irq storm mitigation in 3.10 Jan Niggemann
2013-07-08 20:03 ` Daniel Vetter
2013-07-21 20:23   ` Jan Niggemann
2013-07-21 20:43     ` Daniel Vetter
2013-07-22  6:14       ` Jan Niggemann
2013-07-22  6:26         ` Daniel Vetter
2013-07-22  8:04       ` Egbert Eich
2013-07-22 19:28         ` Jan Niggemann
2013-07-22 20:36           ` Egbert Eich
2013-07-23  8:17             ` Daniel Vetter
2013-07-23 11:26           ` Egbert Eich
2013-07-24 20:52             ` Jan Niggemann
2013-07-25  7:50               ` Egbert Eich
2013-07-25  9:58                 ` Daniel Vetter
2013-07-25 11:18                   ` Egbert Eich
2013-07-25 21:23                   ` Jan Niggemann [this message]
2013-07-26  5:11                     ` Egbert Eich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a9eb123e84afe0bd3bfd4f169180a516@hz6.de \
    --to=jn@hz6.de \
    --cc=daniel@ffwll.ch \
    --cc=eich@suse.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox