[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8762567F-AF91-4D51-AEAD-4F4A18E59F8E@vmware.com>
Date: Mon, 8 Oct 2018 02:17:09 +0000
From: Nadav Amit <namit@...are.com>
To: Ingo Molnar <mingo@...nel.org>
CC: "hpa@...or.com" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Jan Beulich <JBeulich@...e.com>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Andy Lutomirski <luto@...nel.org>
Subject: Re: [PATCH v9 04/10] x86: refcount: prevent gcc distortions
at 2:31 AM, Ingo Molnar <mingo@...nel.org> wrote:
>
> * Nadav Amit <namit@...are.com> wrote:
>
>>> Are you using defconfig or a reasonable distro-config for your tests?
>>
>> I think it is best to take the kernel and run localyesconfig for testing.
>
> Ok, agreed - and this makes the numbers you provided pretty representative.
>
> Good - now that all of my concerns were addressed I'd like to merge the remaining 3 patches as
> well - but they are conflicting with ongoing x86 work in tip:x86/core. The extable conflict is
> trivial, the jump-label conflict a bit more involved.
>
> Could you please pick up the updated changelogs below and resolve the conflicts against
> tip:master or tip:x86/build and submit the remaining patches as well?
For the record, I summarized my analysis of the poor function inlining
decisions in Linux in the following blog-post:
https://nadav.amit.zone/blog/linux-inline
Regards,
Nadav
Powered by blists - more mailing lists