From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 2/3] lib/i915/perf: Stop making copies of the registers
Date: Mon, 3 Apr 2023 20:47:59 +0300 [thread overview]
Message-ID: <20230403174800.19621-3-ville.syrjala@linux.intel.com> (raw)
In-Reply-To: <20230403174800.19621-1-ville.syrjala@linux.intel.com>
From: Ville Syrjälä <ville.syrjala@linux.intel.com>
Do these register things even need to be copied around like
this at all? Just make the pointers const and point them at
the static const data?
Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Cc: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
---
.../perf-configs/perf-registers-codegen.py | 19 +------------------
lib/i915/perf.h | 6 +++---
2 files changed, 4 insertions(+), 21 deletions(-)
diff --git a/lib/i915/perf-configs/perf-registers-codegen.py b/lib/i915/perf-configs/perf-registers-codegen.py
index bde3d14323d3..a2efb8a31440 100644
--- a/lib/i915/perf-configs/perf-registers-codegen.py
+++ b/lib/i915/perf-configs/perf-registers-codegen.py
@@ -44,20 +44,6 @@ def generate_register_configs(set):
c("{")
c.indent(4)
- # allocate memory
- total_n_registers = {}
- register_configs = set.findall('register_config')
- for register_config in register_configs:
- t = register_types[register_config.get('type')]
- if t not in total_n_registers:
- total_n_registers[t] = len(register_config.findall('register'))
- else:
- total_n_registers[t] += len(register_config.findall('register'))
-
- for reg in total_n_registers:
- c("metric_set->{0} = calloc({1}, sizeof(struct intel_perf_register_prog));".format(reg, total_n_registers[reg]))
- c("\n")
-
# fill in register/values
register_configs = set.findall('register_config')
for register_config in register_configs:
@@ -77,7 +63,7 @@ def generate_register_configs(set):
(register.get('address'), register.get('value')))
c.outdent(4)
c("};")
- c("memcpy(metric_set->%s, _%s, sizeof(_%s));" % (t, t, t))
+ c("metric_set->%s = _%s;" % (t, t))
c("metric_set->n_%s = sizeof(_%s) / sizeof(_%s[0]);" % (t, t, t))
c.outdent(4)
c("}")
@@ -155,9 +141,6 @@ def main():
c(copyright)
c("\n")
- c("#include <stdlib.h>")
- c("#include <string.h>")
- c("\n")
c("#include \"%s\"" % header_file)
c("#include \"i915/perf.h\"")
diff --git a/lib/i915/perf.h b/lib/i915/perf.h
index df5b6b96ef1d..6b139f687cca 100644
--- a/lib/i915/perf.h
+++ b/lib/i915/perf.h
@@ -256,13 +256,13 @@ struct intel_perf_metric_set {
int c_offset;
int perfcnt_offset;
- struct intel_perf_register_prog *b_counter_regs;
+ const struct intel_perf_register_prog *b_counter_regs;
uint32_t n_b_counter_regs;
- struct intel_perf_register_prog *mux_regs;
+ const struct intel_perf_register_prog *mux_regs;
uint32_t n_mux_regs;
- struct intel_perf_register_prog *flex_regs;
+ const struct intel_perf_register_prog *flex_regs;
uint32_t n_flex_regs;
struct igt_list_head link;
--
2.39.2
next prev parent reply other threads:[~2023-04-03 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 17:47 [igt-dev] [PATCH i-g-t 0/3] lib/i915/perf: Speed up the build Ville Syrjala
2023-04-03 17:47 ` [igt-dev] [PATCH i-g-t 1/3] lib/i915/perf: Stop generating silly C code Ville Syrjala
2023-04-03 17:47 ` Ville Syrjala [this message]
2023-04-03 17:48 ` [igt-dev] [PATCH i-g-t 3/3] lib/i915/perf: Convert the metric counters to an array as well Ville Syrjala
2023-04-03 19:07 ` [igt-dev] ✓ Fi.CI.BAT: success for lib/i915/perf: Speed up the build Patchwork
2023-04-04 1:27 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-04-04 7:59 ` [igt-dev] [PATCH i-g-t 0/3] " Lionel Landwerlin
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=20230403174800.19621-3-ville.syrjala@linux.intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=igt-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox