Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Nadav Amit <nadav.amit@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	kvm list <kvm@vger.kernel.org>,
	lkml@tlinx.org, Andrew Morton <akpm@linux-foundation.org>,
	Michal Marek <mmarek@suse.cz>,
	stable@vger.kernel.org
Subject: Re: [PATCH] compiler-gcc: disable -ftracer for __noclone functions
Date: Tue, 8 May 2018 11:12:30 -0700	[thread overview]
Message-ID: <6E5A36F3-F83E-4022-BE3A-88F1BADA3EEF@gmail.com> (raw)
In-Reply-To: <86f2fb42-b0eb-46d2-0aed-7efdb306bfe0@redhat.com>

Paolo Bonzini <pbonzini@redhat.com> wrote:

> On 05/05/2018 19:22, Nadav Amit wrote:
>> Paolo Bonzini <pbonzini@redhat.com> wrote:
>> 
>>> -ftracer can duplicate asm blocks causing compilation to fail in
>>> noclone functions.  For example, KVM declares a global variable
>>> in an asm like
>>> 
>>>   asm("2: ... \n
>>>        .pushsection data \n
>>>        .global vmx_return \n
>>>        vmx_return: .long 2b");
>>> 
>>> and -ftracer causes a double declaration.
>>> 
>>> Cc: Andrew Morton <akpm@linux-foundation.org>
>>> Cc: Michal Marek <mmarek@suse.cz>
>>> Cc: stable@vger.kernel.org
>>> Cc: kvm@vger.kernel.org
>>> Reported-by: Linda Walsh <lkml@tlinx.org>
>>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>>> ---
>>> include/linux/compiler-gcc.h | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>> 
>>> diff --git a/include/linux/compiler-gcc.h b/include/linux/compiler-gcc.h
>>> index 22ab246feed3..eeae401a2412 100644
>>> --- a/include/linux/compiler-gcc.h
>>> +++ b/include/linux/compiler-gcc.h
>>> @@ -199,7 +199,7 @@
>>> #define unreachable() __builtin_unreachable()
>>> 
>>> /* Mark a function definition as prohibited from being cloned. */
>>> -#define __noclone	__attribute__((__noclone__))
>>> +#define __noclone	__attribute__((__noclone__, __optimize__("no-tracer")))
>> 
>> [ Bringing the thread back from the dead for context ]
>> 
>> Setting different optimization attributes to certain functions apparently
>> prevents gcc from inlining functions with different “optimizations”. This
>> results in poor compilation - most notably of vmx_vcpu_run() - and causes
>> short functions such as to_vmx() not to be inlined.
> 
> Hmm, I suppose we need to disable -fno-tracer globally...  Has this
> changed in recent versions of GCC?

I don’t think so. I played with optimization attributes of gcc some time ago
and saw the same behavior. Unfortunately, I don’t easily find the place in
gcc that implements this behavior.

      reply	other threads:[~2018-05-08 18:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-31  7:44 [PATCH] compiler-gcc: disable -ftracer for __noclone functions Paolo Bonzini
2016-03-31  8:39 ` kbuild test robot
2018-05-05 17:22 ` Nadav Amit
2018-05-08 17:58   ` Paolo Bonzini
2018-05-08 18:12     ` Nadav Amit [this message]

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=6E5A36F3-F83E-4022-BE3A-88F1BADA3EEF@gmail.com \
    --to=nadav.amit@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@tlinx.org \
    --cc=mmarek@suse.cz \
    --cc=pbonzini@redhat.com \
    --cc=stable@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