From: Marc Hartmayer <mhartmay@linux.ibm.com>
To: <kvm@vger.kernel.org>
Cc: Thomas Huth <thuth@redhat.com>,
David Hildenbrand <david@redhat.com>,
Janosch Frank <frankja@linux.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Andrew Jones <drjones@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
linux-s390@vger.kernel.org
Subject: [kvm-unit-tests PATCH 2/4] scripts: add support for architecture dependent functions
Date: Tue, 18 Aug 2020 15:04:22 +0200 [thread overview]
Message-ID: <20200818130424.20522-3-mhartmay@linux.ibm.com> (raw)
In-Reply-To: <20200818130424.20522-1-mhartmay@linux.ibm.com>
This is necessary to keep architecture dependent code separate from
common code.
Signed-off-by: Marc Hartmayer <mhartmay@linux.ibm.com>
---
README.md | 3 ++-
scripts/common.bash | 8 ++++++++
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/README.md b/README.md
index 48be206c6db1..24d4bdaaee0d 100644
--- a/README.md
+++ b/README.md
@@ -134,7 +134,8 @@ all unit tests.
## Directory structure
.: configure script, top-level Makefile, and run_tests.sh
- ./scripts: helper scripts for building and running tests
+ ./scripts: general architecture neutral helper scripts for building and running tests
+ ./scripts/<ARCH>: architecture dependent helper scripts for building and running tests
./lib: general architecture neutral services for the tests
./lib/<ARCH>: architecture dependent services for the tests
./<ARCH>: the sources of the tests and the created objects/images
diff --git a/scripts/common.bash b/scripts/common.bash
index 96655c9ffd1f..c7acdf14a835 100644
--- a/scripts/common.bash
+++ b/scripts/common.bash
@@ -1,3 +1,4 @@
+source config.mak
function for_each_unittest()
{
@@ -52,3 +53,10 @@ function for_each_unittest()
fi
exec {fd}<&-
}
+
+# The current file has to be the only file sourcing the arch helper
+# file
+ARCH_FUNC=scripts/${ARCH}/func.bash
+if [ -f "${ARCH_FUNC}" ]; then
+ source "${ARCH_FUNC}"
+fi
--
2.25.4
next prev parent reply other threads:[~2020-08-18 13:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 13:04 [kvm-unit-tests PATCH 0/4] s390x: Add Protected VM support Marc Hartmayer
2020-08-18 13:04 ` [kvm-unit-tests PATCH 1/4] common.bash: run `cmd` only if a test case was found Marc Hartmayer
2020-08-19 10:20 ` Cornelia Huck
2020-08-19 10:37 ` David Hildenbrand
2020-08-18 13:04 ` Marc Hartmayer [this message]
2020-08-18 14:31 ` [kvm-unit-tests PATCH 2/4] scripts: add support for architecture dependent functions Andrew Jones
2020-08-19 10:22 ` Cornelia Huck
2020-08-19 10:38 ` David Hildenbrand
2020-08-18 13:04 ` [kvm-unit-tests PATCH 3/4] run_tests/mkstandalone: add arch_cmd hook Marc Hartmayer
2020-08-18 14:32 ` Andrew Jones
2020-08-19 10:23 ` Cornelia Huck
2020-08-19 10:39 ` David Hildenbrand
2020-08-18 13:04 ` [kvm-unit-tests PATCH 4/4] s390x: add Protected VM support Marc Hartmayer
2020-08-18 13:20 ` Janosch Frank
2020-08-19 10:34 ` Cornelia Huck
2020-08-19 11:38 ` Marc Hartmayer
2020-08-19 10:42 ` David Hildenbrand
2020-08-19 11:49 ` Marc Hartmayer
2020-08-21 11:47 ` Marc Hartmayer
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=20200818130424.20522-3-mhartmay@linux.ibm.com \
--to=mhartmay@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=drjones@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).