From: Roger Pau Monne <roger.pau@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Jan Beulich <jbeulich@suse.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: [PATCH v4 3/4] x86: fix indirect thunk usage of CONFIG_INDIRECT_THUNK
Date: Mon, 19 Feb 2018 14:16:19 +0000 [thread overview]
Message-ID: <20180219141620.20008-4-roger.pau@citrix.com> (raw)
In-Reply-To: <20180219141620.20008-1-roger.pau@citrix.com>
When indirect_thunk_asm.h is instantiated directly into assembly files
CONFIG_INDIRECT_THUNK might not be defined, and thus using .if against
it is wrong.
Add a check to define CONFIG_INDIRECT_THUNK to 0 if not defined, so
that using .if CONFIG_INDIRECT_THUNK is always correct.
This suppresses the following clang error:
<instantiation>:8:9: error: expected absolute expression
.if CONFIG_INDIRECT_THUNK == 1
^
<instantiation>:1:1: note: while in macro instantiation
INDIRECT_BRANCH call %rdx
^
entry.S:589:9: note: while in macro instantiation
INDIRECT_CALL %rdx
^
Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
---
Cc: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>
---
xen/include/asm-x86/indirect_thunk_asm.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/xen/include/asm-x86/indirect_thunk_asm.h b/xen/include/asm-x86/indirect_thunk_asm.h
index 96bcc25497..ad83986b2d 100644
--- a/xen/include/asm-x86/indirect_thunk_asm.h
+++ b/xen/include/asm-x86/indirect_thunk_asm.h
@@ -3,6 +3,10 @@
* usual #ifdef'ary to turn into comments.
*/
+.ifndef CONFIG_INDIRECT_THUNK
+ .equ CONFIG_INDIRECT_THUNK, 0
+.endif
+
.macro INDIRECT_BRANCH insn:req arg:req
/*
* Create an indirect branch. insn is one of call/jmp, arg is a single
--
2.16.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-02-19 14:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 14:16 [PATCH v4 0/4] clang fixes Roger Pau Monne
2018-02-19 14:16 ` [PATCH v4 1/4] build: filter out command line assembler arguments Roger Pau Monne
2018-02-19 15:43 ` Jan Beulich
2018-02-19 16:05 ` Roger Pau Monné
2018-02-19 16:14 ` Jan Beulich
2018-02-19 16:17 ` Roger Pau Monné
2018-02-19 14:16 ` [PATCH v4 2/4] x86/clang: restore integrated assembler usage with indirect thunks Roger Pau Monne
2018-02-19 15:57 ` Jan Beulich
2018-02-19 16:24 ` Roger Pau Monné
2018-02-19 17:09 ` Wei Liu
2018-02-19 14:16 ` Roger Pau Monne [this message]
2018-02-19 16:09 ` [PATCH v4 3/4] x86: fix indirect thunk usage of CONFIG_INDIRECT_THUNK Jan Beulich
2018-02-20 9:15 ` Jan Beulich
2018-02-20 10:19 ` Roger Pau Monné
2018-02-20 11:01 ` Roger Pau Monné
2018-02-20 11:13 ` Jan Beulich
2018-02-20 11:22 ` Roger Pau Monné
2018-02-20 12:32 ` Jan Beulich
2018-02-20 12:42 ` Roger Pau Monné
2018-02-20 12:53 ` Jan Beulich
2018-02-20 12:57 ` Roger Pau Monné
2018-02-19 14:16 ` [PATCH v4 4/4] build/clang: add a check whether the assembler supports .skip with labels Roger Pau Monne
2018-02-19 16:10 ` Jan Beulich
2018-02-19 16:16 ` Roger Pau Monné
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=20180219141620.20008-4-roger.pau@citrix.com \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).