Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: gorcunov at gmail.com (Cyrill Gorcunov)
Subject: [PATCH] proc: fix and merge proc-self-map-file tests
Date: Fri, 9 Nov 2018 21:04:07 +0300	[thread overview]
Message-ID: <20181109180407.GO13195@uranus.lan> (raw)
In-Reply-To: <1541764873.3286172.1571234624.727F6284@webmail.messagingengine.com>

On Fri, Nov 09, 2018 at 10:01:13AM -0200, Rafael David Tinoco wrote:
> 
> Alright, I'm fixing membarrier_test before, so.. I guess we have a competition.. =o)

Rafael, Alexey, what about simply wrap the test code with x86 and extend later
with all archs which support zero address mapping?
---
 tools/testing/selftests/proc/proc-self-map-files-002.c |   14 ++++++++++++++
 1 file changed, 14 insertions(+)

Index: linux-ml.git/tools/testing/selftests/proc/proc-self-map-files-002.c
===================================================================
--- linux-ml.git.orig/tools/testing/selftests/proc/proc-self-map-files-002.c
+++ linux-ml.git/tools/testing/selftests/proc/proc-self-map-files-002.c
@@ -23,6 +23,11 @@
 #include <sys/mman.h>
 #include <stdlib.h>
 
+/*
+ * Should run on archs which support zero address mapping.
+ */
+#if defined(__i386) || defined(__x86_64)
+
 static void pass(const char *fmt, unsigned long a, unsigned long b)
 {
 	char name[64];
@@ -83,3 +88,12 @@ int main(void)
 
 	return 0;
 }
+
+#else
+
+int main(void)
+{
+	return 0;
+}
+
+#endif

WARNING: multiple messages have this Message-ID (diff)
From: gorcunov@gmail.com (Cyrill Gorcunov)
Subject: [PATCH] proc: fix and merge proc-self-map-file tests
Date: Fri, 9 Nov 2018 21:04:07 +0300	[thread overview]
Message-ID: <20181109180407.GO13195@uranus.lan> (raw)
Message-ID: <20181109180407.A20JUZiQ1BR3YH_OAhFJSm-p1_8cj6-Ccph4IJ9YMOc@z> (raw)
In-Reply-To: <1541764873.3286172.1571234624.727F6284@webmail.messagingengine.com>

On Fri, Nov 09, 2018@10:01:13AM -0200, Rafael David Tinoco wrote:
> 
> Alright, I'm fixing membarrier_test before, so.. I guess we have a competition.. =o)

Rafael, Alexey, what about simply wrap the test code with x86 and extend later
with all archs which support zero address mapping?
---
 tools/testing/selftests/proc/proc-self-map-files-002.c |   14 ++++++++++++++
 1 file changed, 14 insertions(+)

Index: linux-ml.git/tools/testing/selftests/proc/proc-self-map-files-002.c
===================================================================
--- linux-ml.git.orig/tools/testing/selftests/proc/proc-self-map-files-002.c
+++ linux-ml.git/tools/testing/selftests/proc/proc-self-map-files-002.c
@@ -23,6 +23,11 @@
 #include <sys/mman.h>
 #include <stdlib.h>
 
+/*
+ * Should run on archs which support zero address mapping.
+ */
+#if defined(__i386) || defined(__x86_64)
+
 static void pass(const char *fmt, unsigned long a, unsigned long b)
 {
 	char name[64];
@@ -83,3 +88,12 @@ int main(void)
 
 	return 0;
 }
+
+#else
+
+int main(void)
+{
+	return 0;
+}
+
+#endif

  parent reply	other threads:[~2018-11-09 18:04 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11 18:43 [PATCH] proc: fix proc-self-map-files selftest for arm rafael.tinoco
2018-10-11 18:43 ` Rafael David Tinoco
2018-10-11 19:42 ` gorcunov
2018-10-11 19:42   ` Cyrill Gorcunov
2018-10-11 20:56 ` adobriyan
2018-10-11 20:56   ` Alexey Dobriyan
2018-10-11 21:02   ` gorcunov
2018-10-11 21:02     ` Cyrill Gorcunov
2018-10-11 21:30     ` adobriyan
2018-10-11 21:30       ` Alexey Dobriyan
2018-10-11 22:00       ` gorcunov
2018-10-11 22:00         ` Cyrill Gorcunov
2018-10-15 16:55         ` rafael.tinoco
2018-10-15 16:55           ` Rafael David Tinoco
2018-10-15 17:21           ` gorcunov
2018-10-15 17:21             ` Cyrill Gorcunov
2018-11-08 10:41             ` rafael.tinoco
2018-11-08 10:41               ` Rafael David Tinoco
2018-11-08 11:11               ` gorcunov
2018-11-08 11:11                 ` Cyrill Gorcunov
2018-11-09 11:30                 ` [PATCH] proc: fix and merge proc-self-map-file tests rafael.tinoco
2018-11-09 11:30                   ` Rafael David Tinoco
2018-11-09 11:41                   ` gorcunov
2018-11-09 11:41                     ` Cyrill Gorcunov
2018-11-09 11:45                     ` rafael.tinoco
2018-11-09 11:45                       ` Rafael David Tinoco
2018-11-09 11:48                       ` gorcunov
2018-11-09 11:48                         ` Cyrill Gorcunov
2018-11-09 12:01                         ` rafael.tinoco
2018-11-09 12:01                           ` Rafael David Tinoco
2018-11-09 18:04                           ` gorcunov [this message]
2018-11-09 18:04                             ` Cyrill Gorcunov
2018-11-09 18:48                             ` rafael.tinoco
2018-11-09 18:48                               ` Rafael David Tinoco
2018-11-09 19:39                               ` gorcunov
2018-11-09 19:39                                 ` Cyrill Gorcunov
2018-11-10 17:47                   ` adobriyan
2018-11-10 17:47                     ` Alexey Dobriyan
2018-11-10 17:56                     ` rafael.tinoco
2018-11-10 17:56                       ` Rafael David Tinoco
2018-11-10 18:49                       ` adobriyan
2018-11-10 18:49                         ` Alexey Dobriyan
2018-11-11  2:50                         ` rafael.tinoco
2018-11-11  2:50                           ` Rafael David Tinoco

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=20181109180407.GO13195@uranus.lan \
    --to=linux-kselftest@vger.kernel.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