From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/i915: Kill dev_priv->irq_received
Date: Mon, 20 Jan 2014 13:26:55 +0200 [thread overview]
Message-ID: <20140120112655.GU9454@intel.com> (raw)
In-Reply-To: <20140120111853.GG27650@nuc-i3427.alporthouse.com>
On Mon, Jan 20, 2014 at 11:18:53AM +0000, Chris Wilson wrote:
> On Fri, Jan 17, 2014 at 11:22:52AM +0000, Chris Wilson wrote:
> > On Fri, Jan 17, 2014 at 11:35:16AM +0200, ville.syrjala@linux.intel.com wrote:
> > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > >
> > > Not sure anyone cares about this information. I suppose most people
> > > would just look at /proc/interrupts instead.
> > >
> > > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Acked-by: Chris Wilson <chris@chris-wilson.co.uk>
>
> Darn. Should not have readily agreed, I actually do use in my pmu. Can I
> easily get at (from within i915.ko) the /proc/interrupts counter instead?
Not sure. irq_to_desc() maybe?
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2014-01-20 11:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 9:35 [PATCH 0/3] drm/i915: Random irq stuff ville.syrjala
2014-01-17 9:35 ` [PATCH 1/3] drm/i915: Cancel the hotplug re-enable timer on BDW ville.syrjala
2014-01-17 11:22 ` Chris Wilson
2014-01-17 11:43 ` [PATCH] drm/i915: Add intel_hpd_irq_uninstall() ville.syrjala
2014-01-17 12:13 ` Chris Wilson
2014-01-17 9:35 ` [PATCH 2/3] drm/i915: Make irq_received bool ville.syrjala
2014-01-17 11:23 ` Chris Wilson
2014-01-17 9:35 ` [PATCH 3/3] drm/i915: Kill dev_priv->irq_received ville.syrjala
2014-01-17 11:22 ` Chris Wilson
2014-01-17 17:13 ` Daniel Vetter
2014-01-20 11:18 ` Chris Wilson
2014-01-20 11:26 ` Ville Syrjälä [this message]
2014-01-20 13:28 ` Chris Wilson
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=20140120112655.GU9454@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.