Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH] drm/xe: make compound literal initialization const
Date: Thu, 9 Mar 2023 17:18:56 -0500	[thread overview]
Message-ID: <ZApbUEobAF/ULC41@intel.com> (raw)
In-Reply-To: <20230309121746.479146-1-jani.nikula@intel.com>

On Thu, Mar 09, 2023 at 02:17:46PM +0200, Jani Nikula wrote:
> Be careful about having const in the compound literal initialization to
> keep the initializers in rodata. Here, the impact is 1.8k of mutable
> data moved to rodata.

is there any static tool/script that we could run along with checkpatch
to prevent these?

> 
> add/remove: 0/1 grow/shrink: 0/0 up/down: 0/-1804 (-1804)
> Data                                         old     new   delta
> __compound_literal                          1804       -   -1804
> Total: Before=42425, After=40621, chg -4.25%
> add/remove: 0/0 grow/shrink: 1/0 up/down: 1804/0 (1804)
> RO Data                                      old     new   delta
> __compound_literal                          7696    9500   +1804
> Total: Before=138535, After=140339, chg +1.30
> 
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>

Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>


> ---
>  drivers/gpu/drm/xe/xe_rtp.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_rtp.h b/drivers/gpu/drm/xe/xe_rtp.h
> index bd44fd8bbe05..8fc393ef7358 100644
> --- a/drivers/gpu/drm/xe/xe_rtp.h
> +++ b/drivers/gpu/drm/xe/xe_rtp.h
> @@ -363,7 +363,7 @@ struct xe_reg_sr;
>   */
>  #define XE_RTP_RULES(r1, ...)							\
>  	.n_rules = COUNT_ARGS(r1, ##__VA_ARGS__),				\
> -	.rules = (struct xe_rtp_rule[]) {					\
> +	.rules = (const struct xe_rtp_rule[]) {					\
>  		CALL_FOR_EACH(__ADD_XE_RTP_RULE_PREFIX, r1, ##__VA_ARGS__)	\
>  	}
>  
> @@ -390,7 +390,7 @@ struct xe_reg_sr;
>   */
>  #define XE_RTP_ACTIONS(a1, ...)							\
>  	.n_actions = COUNT_ARGS(a1, ##__VA_ARGS__),				\
> -	.actions = (struct xe_rtp_action[]) {					\
> +	.actions = (const struct xe_rtp_action[]) {				\
>  		CALL_FOR_EACH(__ADD_XE_RTP_ACTION_PREFIX, a1, ##__VA_ARGS__)	\
>  	}
>  
> -- 
> 2.39.1
> 

  reply	other threads:[~2023-03-09 22:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09 12:17 [Intel-xe] [PATCH] drm/xe: make compound literal initialization const Jani Nikula
2023-03-09 22:18 ` Rodrigo Vivi [this message]
2023-03-10 11:07   ` Jani Nikula
2023-03-13 16:10 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-03-13 16:11 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-03-13 16:15 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-03-13 20:46 ` [Intel-xe] [PATCH] " Lucas De Marchi

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=ZApbUEobAF/ULC41@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@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