From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: shuah@kernel.org, luto@kernel.org, dave.hansen@intel.com,
tglx@linutronix.de, bp@suse.de, jun.miao@windriver.com,
chang.seok.bae@intel.com
Subject: [PATCH v1 2/4] selftests/x86/mov_ss_trap: Include processor-flags.h
Date: Sun, 2 Apr 2023 21:43:38 -0700 [thread overview]
Message-ID: <20230403044340.1312-3-chang.seok.bae@intel.com> (raw)
In-Reply-To: <20230403044340.1312-1-chang.seok.bae@intel.com>
Instead of defining X86_EFLAGS_RF, include the header file.
Signed-off-by: Chang S. Bae <chang.seok.bae@intel.com>
Cc: Shuah Khan <shuah@kernel.org>
Cc: linux-kselftest@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
Resolve here before including helper.h in the next patch which,
otherwise, has to remove the define there along with other changes.
---
tools/testing/selftests/x86/mov_ss_trap.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/tools/testing/selftests/x86/mov_ss_trap.c b/tools/testing/selftests/x86/mov_ss_trap.c
index 6b9bf8dc3b60..f8633aafc90c 100644
--- a/tools/testing/selftests/x86/mov_ss_trap.c
+++ b/tools/testing/selftests/x86/mov_ss_trap.c
@@ -35,8 +35,7 @@
#include <string.h>
#include <setjmp.h>
#include <sys/prctl.h>
-
-#define X86_EFLAGS_RF (1UL << 16)
+#include <asm/processor-flags.h>
#if __x86_64__
# define REG_IP REG_RIP
--
2.17.1
next prev parent reply other threads:[~2023-04-03 4:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 4:43 [PATCH v1 0/4] selftests/x86: Improve signal test code Chang S. Bae
2023-04-03 4:43 ` [PATCH v1 1/4] selftests/x86: Fix the altstack free Chang S. Bae
2023-04-03 4:43 ` Chang S. Bae [this message]
2023-04-03 4:43 ` [PATCH v1 3/4] selftests/x86: Consolidate signal handler helpers Chang S. Bae
2023-04-03 4:43 ` [PATCH v1 4/4] selftests/x86: Refactor altstack setup code Chang S. Bae
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=20230403044340.1312-3-chang.seok.bae@intel.com \
--to=chang.seok.bae@intel.com \
--cc=bp@suse.de \
--cc=dave.hansen@intel.com \
--cc=jun.miao@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@kernel.org \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
/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