From: Ingo Molnar <mingo@kernel.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: kstewart@linuxfoundation.org, andrea.parri@amarulasolutions.com,
linux-efi@vger.kernel.org, brijesh.singh@amd.com,
jan.kiszka@siemens.com, jpoimboe@redhat.com, will.deacon@arm.com,
jarkko.sakkinen@linux.intel.com,
virtualization@lists.linux-foundation.org,
yamada.masahiro@socionext.com, manojgupta@google.com,
hpa@zytor.com, boris.ostrovsky@oracle.com, tweek@google.com,
mawilcox@microsoft.com, x86@kernel.org, akataria@vmware.com,
ghackmann@google.com, mingo@redhat.com, astrachan@google.com,
rientjes@google.com, geert@linux-m68k.org,
thomas.lendacky@amd.com, arnd@arndb.de,
linux-kbuild@vger.kernel.org, pombredanne@nexb.com,
rostedt@goodmis.org, acme@redhat.com, caoj.fnst@cn.fujitsu.com,
aryabinin@virtuozzo.com, sedat.dilek@gmail.com,
tglx@linutronix.de, jgross@suse.com, michal.lkml@markovi.net,
tstellar@redhat.com, gregkh@linuxfoundation.org,
mka@chromium.org, ard.bieshe
Subject: Re: [PATCH v6 3/3] x86: paravirt: make native_save_fl extern inline
Date: Fri, 22 Jun 2018 04:24:02 +0200 [thread overview]
Message-ID: <20180622022402.GA24194@gmail.com> (raw)
In-Reply-To: <20180621162324.36656-4-ndesaulniers@google.com>
* Nick Desaulniers <ndesaulniers@google.com> wrote:
> native_save_fl() is marked static inline, but by using it as
> a function pointer in arch/x86/kernel/paravirt.c, it MUST be outlined.
> --- a/arch/x86/include/asm/irqflags.h
> +++ b/arch/x86/include/asm/irqflags.h
> @@ -13,7 +13,7 @@
> * Interrupt control:
> */
>
> -static inline unsigned long native_save_fl(void)
> +extern inline unsigned long native_save_fl(void)
> {
> unsigned long flags;
>
What's the code generation effect of this on say a defconfig kernel vmlinux with
paravirt enabled?
Thanks,
Ingo
next parent reply other threads:[~2018-06-22 2:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180621162324.36656-1-ndesaulniers@google.com>
[not found] ` <20180621162324.36656-4-ndesaulniers@google.com>
2018-06-22 2:24 ` Ingo Molnar [this message]
[not found] ` <CAKwvOdn5gnB5cK=cy6weKyxAn4SNEdZTT_MtT_D_nHRG5EDZ4g@mail.gmail.com>
2018-06-26 7:13 ` [PATCH v6 3/3] x86: paravirt: make native_save_fl extern inline Ingo Molnar
[not found] ` <CAKwvOdnW9r=pgmodEL0VXCv=PZVt_WMCA+B5x4D5oKRM1y-0Ow@mail.gmail.com>
2018-07-03 7:21 ` Juergen Gross
2018-07-13 10:16 ` David Laight
[not found] ` <CAKwvOdmFVnSos71vAUnayuocBDhxLg76tvGF0y3sj+4+s7TCcw@mail.gmail.com>
2018-07-17 8:44 ` David Laight
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=20180622022402.GA24194@gmail.com \
--to=mingo@kernel.org \
--cc=acme@redhat.com \
--cc=akataria@vmware.com \
--cc=andrea.parri@amarulasolutions.com \
--cc=arnd@arndb.de \
--cc=aryabinin@virtuozzo.com \
--cc=astrachan@google.com \
--cc=boris.ostrovsky@oracle.com \
--cc=brijesh.singh@amd.com \
--cc=caoj.fnst@cn.fujitsu.com \
--cc=geert@linux-m68k.org \
--cc=ghackmann@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jan.kiszka@siemens.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgross@suse.com \
--cc=jpoimboe@redhat.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=manojgupta@google.com \
--cc=mawilcox@microsoft.com \
--cc=michal.lkml@markovi.net \
--cc=mingo@redhat.com \
--cc=mka@chromium.org \
--cc=ndesaulniers@google.com \
--cc=pombredanne@nexb.com \
--cc=rientjes@google.com \
--cc=rostedt@goodmis.org \
--cc=sedat.dilek@gmail.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tstellar@redhat.com \
--cc=tweek@google.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=will.deacon@arm.com \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.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).