From: venkata.pyla@toshiba-tsip.com
To: jkacur@redhat.com
Cc: venkata pyla <venkata.pyla@toshiba-tsip.com>,
punit1.agrawal@toshiba.co.jp, daniel.sangorrin@toshiba.co.jp,
dinesh.kumar@toshiba-tsip.com, linux-rt-users@vger.kernel.org
Subject: [PATCH] rteval: kcompile.py: Relax the requirement for kernel tarball filename
Date: Wed, 22 Sep 2021 22:47:40 +0530 [thread overview]
Message-ID: <20210922171740.8939-1-venkata.pyla@toshiba-tsip.com> (raw)
From: venkata pyla <venkata.pyla@toshiba-tsip.com>
The kcompile module includes kernel version when looking for tarballs
or source folders. This necessitates periodically bumping the
kernel_prefix but also requires the user to provide particular version
of the kernel sources when using this workload. As the intent is to
generate a compile workload the source version used shouldn't matter.
To make life easier both for users and developers, relax the
requirement for specific version of kernel sources when using
kcompile.
Signed-off-by: venkata pyla <venkata.pyla@toshiba-tsip.com>
---
rteval/modules/loads/kcompile.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/rteval/modules/loads/kcompile.py b/rteval/modules/loads/kcompile.py
index 8d08a3d..be40a62 100644
--- a/rteval/modules/loads/kcompile.py
+++ b/rteval/modules/loads/kcompile.py
@@ -35,7 +35,7 @@ from rteval.Log import Log
from rteval.misc import expand_cpulist, compress_cpulist
from rteval.systopology import SysTopology
-kernel_prefix = "linux-5.13"
+kernel_prefix = "linux"
class KBuildJob:
'''Class to manage a build job bound to a particular node'''
--
2.20.1
next reply other threads:[~2021-09-22 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 17:17 venkata.pyla [this message]
2021-09-23 19:31 ` [PATCH] rteval: kcompile.py: Relax the requirement for kernel tarball filename John Kacur
2021-09-24 7:18 ` Venkata.Pyla
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=20210922171740.8939-1-venkata.pyla@toshiba-tsip.com \
--to=venkata.pyla@toshiba-tsip.com \
--cc=daniel.sangorrin@toshiba.co.jp \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=punit1.agrawal@toshiba.co.jp \
/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;
as well as URLs for NNTP newsgroup(s).