From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/i915: Promote IS_BROADWELL to a simple macro
Date: Fri, 6 May 2016 17:29:18 +0300 [thread overview]
Message-ID: <20160506142918.GD4329@intel.com> (raw)
In-Reply-To: <572CA7A8.7010806@linux.intel.com>
On Fri, May 06, 2016 at 03:18:16PM +0100, Tvrtko Ursulin wrote:
>
> On 06/05/16 15:00, Ville Syrjälä wrote:
> > On Fri, May 06, 2016 at 02:43:50PM +0100, Tvrtko Ursulin wrote:
> >> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> >>
> >> If we allow it a dedicated flag in dev_priv we enable the
> >> compiler to nicely optimize conditions like IS_HASSWELL ||
> >> IS_BROADWELL.
> >>
> >> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> >> ---
> >> drivers/gpu/drm/i915/i915_drv.c | 4 ++++
> >> drivers/gpu/drm/i915/i915_drv.h | 3 ++-
> >> 2 files changed, 6 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
> >> index 9fd221c97275..da6532da44e3 100644
> >> --- a/drivers/gpu/drm/i915/i915_drv.c
> >> +++ b/drivers/gpu/drm/i915/i915_drv.c
> >> @@ -300,22 +300,26 @@ static const struct intel_device_info intel_haswell_m_info = {
> >> static const struct intel_device_info intel_broadwell_d_info = {
> >> BDW_FEATURES,
> >> .gen = 8,
> >> + .is_broadwell = 1,
> >> };
> >>
> >> static const struct intel_device_info intel_broadwell_m_info = {
> >> BDW_FEATURES,
> >> .gen = 8, .is_mobile = 1,
> >> + .is_broadwell = 1,
> >> };
> >>
> >> static const struct intel_device_info intel_broadwell_gt3d_info = {
> >> BDW_FEATURES,
> >> .gen = 8,
> >> + .is_broadwell = 1,
> >> .ring_mask = RENDER_RING | BSD_RING | BLT_RING | VEBOX_RING | BSD2_RING,
> >> };
> >>
> >> static const struct intel_device_info intel_broadwell_gt3m_info = {
> >> BDW_FEATURES,
> >> .gen = 8, .is_mobile = 1,
> >> + .is_broadwell = 1,
> >> .ring_mask = RENDER_RING | BSD_RING | BLT_RING | VEBOX_RING | BSD2_RING,
> >> };
> >>
> >> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> >> index c6351016eaf0..459561991081 100644
> >> --- a/drivers/gpu/drm/i915/i915_drv.h
> >> +++ b/drivers/gpu/drm/i915/i915_drv.h
> >> @@ -735,6 +735,7 @@ struct intel_csr {
> >> func(is_valleyview) sep \
> >> func(is_cherryview) sep \
> >> func(is_haswell) sep \
> >> + func(is_broadwell) sep \
> >> func(is_skylake) sep \
> >> func(is_broxton) sep \
> >> func(is_kabylake) sep \
> >
> > We could just replace all of these with a single enum and save a bunch
> > of space.
>
> Bitfield is really nice here because compiler can then merge tests like
> IS_HASWELL || IS_BROADWELL into a single test instruction.
Most if not all of those are in modeset code so I'm not entirely
convinced micro-optimizing that is all that useful.
Bunch of times I've just wished I could write 'whatever >= G4X' instead
of 'IS_G4X || gen >= 5' simply for readability.
>
> Regards,
>
> Tvrtko
>
> >
> >> @@ -2553,7 +2554,7 @@ struct drm_i915_cmd_table {
> >> #define IS_VALLEYVIEW(dev) (INTEL_INFO(dev)->is_valleyview)
> >> #define IS_CHERRYVIEW(dev) (INTEL_INFO(dev)->is_cherryview)
> >> #define IS_HASWELL(dev) (INTEL_INFO(dev)->is_haswell)
> >> -#define IS_BROADWELL(dev) (!INTEL_INFO(dev)->is_cherryview && IS_GEN8(dev))
> >> +#define IS_BROADWELL(dev) (INTEL_INFO(dev)->is_broadwell)
> >> #define IS_SKYLAKE(dev) (INTEL_INFO(dev)->is_skylake)
> >> #define IS_BROXTON(dev) (INTEL_INFO(dev)->is_broxton)
> >> #define IS_KABYLAKE(dev) (INTEL_INFO(dev)->is_kabylake)
> >> --
> >> 1.9.1
> >>
> >> _______________________________________________
> >> Intel-gfx mailing list
> >> Intel-gfx@lists.freedesktop.org
> >> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
> >
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-05-06 14:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 13:43 [PATCH 1/3] drm/i915: Make IS_GENx macros work on a mask Tvrtko Ursulin
2016-05-06 13:43 ` [PATCH 2/3] drm/i915: Promote IS_BROADWELL to a simple macro Tvrtko Ursulin
2016-05-06 14:00 ` Ville Syrjälä
2016-05-06 14:18 ` Tvrtko Ursulin
2016-05-06 14:29 ` Ville Syrjälä [this message]
2016-05-06 14:44 ` Tvrtko Ursulin
2016-05-06 14:51 ` Chris Wilson
2016-05-06 14:58 ` Ville Syrjälä
2016-05-06 13:43 ` [PATCH 3/3] drm/i915: Replace "INTEL_INFO->gen == x" checks with IS_GENx Tvrtko Ursulin
2016-05-06 13:59 ` Chris Wilson
2016-05-06 14:16 ` Tvrtko Ursulin
2016-05-06 14:20 ` Tvrtko Ursulin
2016-05-09 14:18 ` Dave Gordon
2016-05-10 7:47 ` Jani Nikula
2016-05-06 14:16 ` [PATCH 1/2] drm/i915: Introduce INTEL_GEN_RANGE macro Tvrtko Ursulin
2016-05-06 14:16 ` [PATCH 2/2] drm/i915: Do not use a bitfield for INTEL_INFO->num_pipes Tvrtko Ursulin
2016-05-06 19:21 ` Dave Gordon
2016-05-06 14:33 ` [PATCH 1/2] drm/i915: Introduce INTEL_GEN_RANGE macro Chris Wilson
2016-05-06 19:11 ` Dave Gordon
2016-05-09 12:32 ` Jani Nikula
2016-05-09 14:26 ` Dave Gordon
2016-05-09 14:40 ` Jani Nikula
2016-05-09 15:23 ` Chris Wilson
2016-05-10 7:54 ` Jani Nikula
2016-05-06 14:28 ` [PATCH 1/3] drm/i915: Make IS_GENx macros work on a mask Chris Wilson
2016-05-06 14:36 ` Tvrtko Ursulin
2016-05-06 14:43 ` 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=20160506142918.GD4329@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@linux.intel.com \
/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