All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH] drm/i915: Drop platform_mask
Date: Fri, 15 Mar 2019 20:19:58 +0200	[thread overview]
Message-ID: <20190315181958.GE3888@intel.com> (raw)
In-Reply-To: <8cf151c2-dc27-fbf0-cf3d-16f71a5e3af1@linux.intel.com>

On Fri, Mar 15, 2019 at 07:13:49AM +0000, Tvrtko Ursulin wrote:
> 
> On 15/03/2019 06:56, Tvrtko Ursulin wrote:
> > 
> > On 15/03/2019 00:52, Chris Wilson wrote:
> >> Quoting José Roberto de Souza (2019-03-15 00:42:35)
> >>> We don't have any platform that is composed by 2 or more platforms so
> >>> we don't need a mask, lets drop it and remove the actual limit of 32
> >>> platforms.
> > 
> > Platform mask was a nifty trick to compile tests like IS_SKYLAKE || 
> > IS_BROADWELL etc into a single conditional.
> > 
> >> gcc doesn't entirely agree, this is a net loss here (i.e. code size
> >> increases).
> > 
> > Perhaps the size re-gain of dropping the platform mask could be checked 
> > against the size gain of making the mask 64 bit.
> 
> One possible alternative could be splitting the 64-bit platform mask 
> into two 32-bit dwords. Like:
> 
>    u32 platform_mask[2];
> 
>    #define IS_PLATFORM(p) (platform_mask[p / 32] & BIT(p % 32))

This is fast approaching nih bitmap.h territory.

-- 
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-03-15 18:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15  0:42 [PATCH] drm/i915: Drop platform_mask José Roberto de Souza
2019-03-15  0:52 ` Chris Wilson
2019-03-15  6:56   ` Tvrtko Ursulin
2019-03-15  7:13     ` Tvrtko Ursulin
2019-03-15  7:27       ` Lucas De Marchi
2019-03-15  8:23         ` Tvrtko Ursulin
2019-03-15 18:19       ` Ville Syrjälä [this message]
2019-03-15 18:43         ` Lucas De Marchi
2019-03-15 17:56     ` Paulo Zanoni
2019-03-15  1:21 ` ✓ Fi.CI.BAT: success for " Patchwork

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=20190315181958.GE3888@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --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 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.