From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 12/12] code_cov_parse_info: add support for filtering Xe driver data
Date: Tue, 17 Jan 2023 15:06:07 +0100 [thread overview]
Message-ID: <20230117140607.2759816-13-mauro.chehab@linux.intel.com> (raw)
In-Reply-To: <20230117140607.2759816-1-mauro.chehab@linux.intel.com>
From: Mauro Carvalho Chehab <mchehab@kernel.org>
Just like it does for i915, add an option to get code coverage
data from Xe driver.
For now, it won't be taking DRM core stuff into account; just
the Xe driver code itself.
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---
scripts/code_cov_parse_info | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
diff --git a/scripts/code_cov_parse_info b/scripts/code_cov_parse_info
index 2c3283cc1119..d133ef1a18d4 100755
--- a/scripts/code_cov_parse_info
+++ b/scripts/code_cov_parse_info
@@ -1387,6 +1387,7 @@ my $branch_filters;
my $show_files;
my $show_lines;
my $only_i915;
+my $only_xe;
my $only_drm;
my $check_branches;
@@ -1399,6 +1400,7 @@ GetOptions(
"verbose|v" => \$verbose,
"ignore-unused|ignore_unused" => \$ignore_unused,
"only-i915|only_i915" => \$only_i915,
+ "only-xe|only_xe" => \$only_xe,
"only-drm|only_drm" => \$only_drm,
"func-filters|f=s" => \$func_filters,
"include-func=s" => \@func_include_regexes,
@@ -1448,6 +1450,14 @@ if ($only_i915) {
push @src_include_regexes, "drm/vgem";
}
+if ($only_xe) {
+ # Please keep in sync with the documentation
+ push @src_exclude_regexes, "selftest";
+ push @src_include_regexes, "drm/xe";
+# push @src_include_regexes, "drm/ttm";
+# push @src_include_regexes, "drm/vgem";
+}
+
if ($only_drm) {
# Please keep in sync with the documentation
push @src_exclude_regexes, "trace.*\.h\$";
@@ -1493,7 +1503,9 @@ foreach my $f (@ARGV) {
if ($gen_report) {
$f =~ s,.*/,,;
+ $f =~ s/\.gz$//;
$f =~ s/\.info$//;
+ $f =~ s/\.json$//;
gen_stats();
@@ -1694,6 +1706,19 @@ Excluding files that match:
- selftest
+=item B<--only-xe> or B<--only_xe>
+
+Filters out C files and headers outside drm core and drm/i915.
+
+E. g. code coverage results will include only the files that that match
+the following regular expressions:
+
+ - drm/xe/
+
+Excluding files that match:
+
+ - selftest
+
=item B<--func-filters> B<[filter's file]> or B<-f> B<[filter's file]>
Use a file containing regular expressions (regex) to filter functions.
--
2.39.0
prev parent reply other threads:[~2023-01-17 14:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 14:05 [igt-dev] [PATCH i-g-t 00/12] Improve code coverage tool Mauro Carvalho Chehab
2023-01-17 14:05 ` [igt-dev] [PATCH i-g-t 01/12] code_cov_parse_info: silent some messages by default Mauro Carvalho Chehab
2023-01-17 14:05 ` [igt-dev] [PATCH i-g-t 02/12] code_cov_parse_info: do some renames to make it more coherent Mauro Carvalho Chehab
2023-01-17 14:05 ` [igt-dev] [PATCH i-g-t 03/12] code_cov_parse_info: use numberic sort for line numbers Mauro Carvalho Chehab
2023-01-17 14:05 ` [igt-dev] [PATCH i-g-t 04/12] code_cov_parse_info: better handle include regexes Mauro Carvalho Chehab
2023-01-17 14:06 ` [igt-dev] [PATCH i-g-t 05/12] code_cov_parse_info: add a tool to analyze branch coverage Mauro Carvalho Chehab
2023-01-17 14:06 ` [igt-dev] [PATCH i-g-t 06/12] code_cov_parse_info: add support for parsing JSON files Mauro Carvalho Chehab
2023-01-25 14:18 ` Kamil Konieczny
2023-01-17 14:06 ` [igt-dev] [PATCH i-g-t 07/12] code_cov_parse_info: add support for compressed files Mauro Carvalho Chehab
2023-01-17 14:06 ` [igt-dev] [PATCH i-g-t 08/12] code_cov_parse_info: allow specifying the source directory Mauro Carvalho Chehab
2023-01-17 14:06 ` [igt-dev] [PATCH i-g-t 09/12] code_cov_parse_info: better handle branch filtering Mauro Carvalho Chehab
2023-01-17 14:06 ` [igt-dev] [PATCH i-g-t 10/12] code_cov_parse_info: filter out branches from headers by default Mauro Carvalho Chehab
2023-01-17 14:06 ` [igt-dev] [PATCH i-g-t 11/12] code_cov_parse_info: add support for filtering branches Mauro Carvalho Chehab
2023-01-17 14:06 ` Mauro Carvalho Chehab [this message]
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=20230117140607.2759816-13-mauro.chehab@linux.intel.com \
--to=mauro.chehab@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