Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Yury Norov <yury.norov@gmail.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Tvrtko Ursulin <tursulin@ursulin.net>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org,
	Andi Shyti <andi.shyti@linux.intel.com>,
	David Laight <David.Laight@aculab.com>,
	Jani Nikula <jani.nikula@intel.com>
Subject: Re: [PATCH v7 1/5] bits: introduce fixed-type GENMASK_U*()
Date: Mon, 24 Mar 2025 16:44:29 +0900	[thread overview]
Message-ID: <202c97b2-e99e-4b88-9ac5-171db244b7d0@wanadoo.fr> (raw)
In-Reply-To: <Z-EIHBCkUiBh63JE@smile.fi.intel.com>

On 24/03/2025 at 16:22, Andy Shevchenko wrote:
> On Sat, Mar 22, 2025 at 06:23:12PM +0900, Vincent Mailhol via B4 Relay wrote:
>>
>> Add GENMASK_TYPE() which generalizes __GENMASK() to support different
>> types, and implement fixed-types versions of GENMASK() based on it.
>> The fixed-type version allows more strict checks to the min/max values
>> accepted, which is useful for defining registers like implemented by
>> i915 and xe drivers with their REG_GENMASK*() macros.
>>
>> The strict checks rely on shift-count-overflow compiler check to fail
>> the build if a number outside of the range allowed is passed.
>> Example:
>>
>>   #define FOO_MASK GENMASK_U32(33, 4)
>>
>> will generate a warning like:
>>
>>   include/linux/bits.h:51:27: error: right shift count >= width of type [-Werror=shift-count-overflow]
>>      51 |               type_max(t) >> (BITS_PER_TYPE(t) - 1 - (h)))))
>>         |                           ^~
>>
>> While GENMASK_TYPE() is crafted to cover all variants, including the
>> already existing GENMASK(), GENMASK_ULL() and GENMASK_U128(), for the
>> moment, only use it for the newly introduced GENMASK_U*(). The
>> consolidation will be done in a separate change.
> 
> ...
> 
>>  #if !defined(__ASSEMBLY__)
>> +
> 
>> -#else
> 
>> +#else /* defined(__ASSEMBLY__) */
> 
>> -#endif
>> +
>> +#endif /* !defined(__ASSEMBLY__) */
> 
> Up to you, but if new version is needed or maintainer require, I would move the
> above changes either to a separate patch (prerequisite) or dropped them at all.
> These are not big but unneeded churn,

I do not want to drop this. After all the changes, there is a lot of
scrolling between the #if, #else and #endif, and the comments helps to
keep track of which context we are in.

As for putting this into another patch, OK but only if there is a need
for new version for other reasons.


Yours sincerely,
Vincent Mailhol


  reply	other threads:[~2025-03-24  7:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-22  9:23 [PATCH v7 0/5] bits: Fixed-type GENMASK_U*() and BIT_U*() Vincent Mailhol via B4 Relay
2025-03-22  9:23 ` [PATCH v7 1/5] bits: introduce fixed-type GENMASK_U*() Vincent Mailhol via B4 Relay
2025-03-24  7:22   ` Andy Shevchenko
2025-03-24  7:44     ` Vincent Mailhol [this message]
2025-03-22  9:23 ` [PATCH v7 2/5] bits: introduce fixed-type BIT_U*() Vincent Mailhol via B4 Relay
2025-03-24 13:41   ` Andy Shevchenko
2025-03-24 14:16     ` Vincent Mailhol
2025-03-24 14:32       ` Andy Shevchenko
2025-03-22  9:23 ` [PATCH v7 3/5] drm/i915: Convert REG_GENMASK*() to fixed-width GENMASK_U*() Vincent Mailhol via B4 Relay
2025-03-22  9:23 ` [PATCH v7 4/5] test_bits: add tests for GENMASK_U*() Vincent Mailhol via B4 Relay
2025-03-22  9:23 ` [PATCH v7 5/5] test_bits: add tests for BIT_U*() Vincent Mailhol via B4 Relay
2025-03-22 10:07 ` ✗ Fi.CI.CHECKPATCH: warning for bits: Fixed-type GENMASK_U*() and BIT_U*() (rev2) Patchwork
2025-03-22 10:07 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-03-22 16:19 ` ✓ i915.CI.BAT: success " Patchwork
2025-03-22 17:51 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-24 14:28 ` [PATCH v7 0/5] bits: Fixed-type GENMASK_U*() and BIT_U*() Yury Norov
2025-03-24 16:23   ` Vincent Mailhol
2025-03-25 15:23     ` Yury Norov
2025-03-25 16:13       ` Vincent Mailhol
2025-03-25 16:30         ` Yury Norov

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=202c97b2-e99e-4b88-9ac5-171db244b7d0@wanadoo.fr \
    --to=mailhol.vincent@wanadoo.fr \
    --cc=David.Laight@aculab.com \
    --cc=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi.shyti@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=lucas.demarchi@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=tursulin@ursulin.net \
    --cc=yury.norov@gmail.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