From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Vasily Gorbik <gor@linux.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@suse.de>,
Miroslav Benes <mbenes@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] compiler.h: Avoid using inline asm operand modifiers
Date: Mon, 8 Nov 2021 08:50:16 -0800 [thread overview]
Message-ID: <20211108165016.kdehec32k3dw4334@treble> (raw)
In-Reply-To: <your-ad-here.call-01636386038-ext-6578@work.hours>
On Mon, Nov 08, 2021 at 04:40:38PM +0100, Vasily Gorbik wrote:
> > Does this work on s390?
> >
> > diff --git a/include/linux/compiler.h b/include/linux/compiler.h
> > index 3d5af56337bd..42935500a712 100644
> > --- a/include/linux/compiler.h
> > +++ b/include/linux/compiler.h
> > @@ -115,24 +115,18 @@ void ftrace_likely_update(struct ftrace_likely_data *f, int val,
> > * The __COUNTER__ based labels are a hack to make each instance of the macros
> > * unique, to convince GCC not to merge duplicate inline asm statements.
> > */
> > -#define __stringify_label(n) #n
> > -
> > -#define __annotate_reachable(c) ({ \
> > - asm volatile(__stringify_label(c) ":\n\t" \
> > +#define annotate_reachable() ({ \
> > + asm volatile("%c0:\n\t" \
> > ".pushsection .discard.reachable\n\t" \
> > - ".long " __stringify_label(c) "b - .\n\t" \
> > - ".popsection\n\t"); \
> > + ".long %c0b - .\n\t" \
> > + ".popsection\n\t" : : "i" (__COUNTER__ & 0x7f)); \
> > })
>
> hm, could we just add asm input back and not use it? and keep
> __stringify_label(c) as is? would that work as well?
Yeah, that seems to work:
diff --git a/include/linux/compiler.h b/include/linux/compiler.h
index 3d5af56337bd..429dcebe2b99 100644
--- a/include/linux/compiler.h
+++ b/include/linux/compiler.h
@@ -121,7 +121,7 @@ void ftrace_likely_update(struct ftrace_likely_data *f, int val,
asm volatile(__stringify_label(c) ":\n\t" \
".pushsection .discard.reachable\n\t" \
".long " __stringify_label(c) "b - .\n\t" \
- ".popsection\n\t"); \
+ ".popsection\n\t" : : "i" (c)); \
})
#define annotate_reachable() __annotate_reachable(__COUNTER__)
@@ -129,7 +129,7 @@ void ftrace_likely_update(struct ftrace_likely_data *f, int val,
asm volatile(__stringify_label(c) ":\n\t" \
".pushsection .discard.unreachable\n\t" \
".long " __stringify_label(c) "b - .\n\t" \
- ".popsection\n\t"); \
+ ".popsection\n\t" : : "i" (c)); \
})
#define annotate_unreachable() __annotate_unreachable(__COUNTER__)
diff --git a/include/linux/instrumentation.h b/include/linux/instrumentation.h
index fa2cd8c63dcc..24359b4a9605 100644
--- a/include/linux/instrumentation.h
+++ b/include/linux/instrumentation.h
@@ -11,7 +11,7 @@
asm volatile(__stringify(c) ": nop\n\t" \
".pushsection .discard.instr_begin\n\t" \
".long " __stringify(c) "b - .\n\t" \
- ".popsection\n\t"); \
+ ".popsection\n\t" : : "i" (c)); \
})
#define instrumentation_begin() __instrumentation_begin(__COUNTER__)
@@ -50,7 +50,7 @@
asm volatile(__stringify(c) ": nop\n\t" \
".pushsection .discard.instr_end\n\t" \
".long " __stringify(c) "b - .\n\t" \
- ".popsection\n\t"); \
+ ".popsection\n\t" : : "i" (c)); \
})
#define instrumentation_end() __instrumentation_end(__COUNTER__)
#else
next prev parent reply other threads:[~2021-11-08 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 13:03 [PATCH 0/2] objtool annotations: Avoid using inline asm operand modifiers Vasily Gorbik
2021-05-19 13:03 ` [PATCH 1/2] compiler.h: " Vasily Gorbik
2021-11-05 16:54 ` Josh Poimboeuf
2021-11-08 15:40 ` Vasily Gorbik
2021-11-08 16:50 ` Josh Poimboeuf [this message]
2021-11-10 10:39 ` David Laight
2021-05-19 13:03 ` [PATCH 2/2] instrumentation.h: " Vasily Gorbik
2021-05-19 20:52 ` [PATCH 0/2] objtool annotations: " Josh Poimboeuf
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=20211108165016.kdehec32k3dw4334@treble \
--to=jpoimboe@redhat.com \
--cc=bp@suse.de \
--cc=gor@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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