From: "Luck, Tony" <tony.luck@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Jakub Kicinski <kuba@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Marco Elver <elver@google.com>, X86 ML <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 1/3] cpumask: Add a x86-specific cpumask_clear_cpu() helper
Date: Fri, 4 Feb 2022 16:46:24 +0000 [thread overview]
Message-ID: <547b5ccef6a54df49e556f596aafaa39@intel.com> (raw)
In-Reply-To: <20220204083015.17317-2-bp@alien8.de>
> Also, always inline two more cpumask generic helpers.
>
> allyesconfig:
>
> text data bss dec hex filename
> 190553143 159425889 32076404 382055436 16c5b40c vmlinux.before
> 190551812 159424945 32076404 382053161 16c5ab29 vmlinux.after
That looks odd. You added "always" to some inline functions, which I'd
have thought might cause *more* inlining, and thus an increase in text
size. But it actually went *down* by 1331 bytes.
-Tony
next prev parent reply other threads:[~2022-02-04 16:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 8:30 [PATCH 0/3] x86/mce: Fix more noinstr fun Borislav Petkov
2022-02-04 8:30 ` [PATCH 1/3] cpumask: Add a x86-specific cpumask_clear_cpu() helper Borislav Petkov
2022-02-04 16:46 ` Luck, Tony [this message]
2022-02-04 18:04 ` Borislav Petkov
2022-02-13 10:59 ` [tip: locking/core] " tip-bot2 for Borislav Petkov
2022-02-04 8:30 ` [PATCH 2/3] x86/ptrace: Always inline v8086_mode() for instrumentation Borislav Petkov
2022-02-13 10:59 ` [tip: locking/core] " tip-bot2 for Borislav Petkov
2022-02-04 8:30 ` [PATCH 3/3] x86/mce: Use arch atomic and bit helpers Borislav Petkov
2022-02-14 10:03 ` [tip: ras/core] " tip-bot2 for Borislav Petkov
2022-02-04 11:24 ` [PATCH 0/3] x86/mce: Fix more noinstr fun Marco Elver
2022-02-04 14:48 ` Borislav Petkov
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=547b5ccef6a54df49e556f596aafaa39@intel.com \
--to=tony.luck@intel.com \
--cc=bp@alien8.de \
--cc=elver@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.