From: Feng Tang <feng.tang@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: kernel test robot <lkp@intel.com>, <oe-kbuild-all@lists.linux.dev>
Subject: Re: [lkp] [+64 bytes kernel size regression] [i386-tinyconfig] [78532abaf5] x86/tsc: Add option to force frequency recalibration with HW timer
Date: Sun, 8 Jan 2023 17:14:30 +0800 [thread overview]
Message-ID: <Y7qJdtnshG3vu95L@feng-clx> (raw)
In-Reply-To: <20230107160132.GY4028633@paulmck-ThinkPad-P17-Gen-1>
On Sat, Jan 07, 2023 at 08:01:32AM -0800, Paul E. McKenney wrote:
> On Sat, Jan 07, 2023 at 05:03:05PM +0800, kernel test robot wrote:
> >
> > FYI, we noticed a +64 bytes kernel size regression due to commit:
> >
> > commit: 78532abaf5f1c973c99680960ae22bd797951ddf (x86/tsc: Add option to force frequency recalibration with HW timer)
> > https://git.kernel.org/cgit/linux/kernel/git/paulmck/linux-rcu.git workqueue.2023.01.06a
> >
> >
> > Details as below (size data is obtained by `nm --size-sort vmlinux`):
> >
> > 8913f44d: clocksource: Permit limited-duration clocksource watchdogging
> > 78532aba: x86/tsc: Add option to force frequency recalibration with HW timer
>
> Perhaps there should be a Kconfig option to disable the clocksource
> watchdog? Not sure that a minimal kernel would worry about such things.
Yes, there is a CONFIG_CLOCKSOURCE_WATCHDOG option. For 78532aba, IMHO,
64 bytes is a relatively small cost comparing to its potential value.
Thanks,
Feng
>
> Thanx, Paul
>
> > +----------------------------------+----------+----------+-------+
> > | symbol | 8913f44d | 78532aba | delta |
> > +----------------------------------+----------+----------+-------+
> > | bzImage | 495904 | 495968 | 64 |
> > | nm.t.tsc_setup | 103 | 129 | 26 |
> > | nm.t.init_tsc_clocksource | 111 | 132 | 21 |
> > | nm.t.tsc_refine_calibration_work | 427 | 440 | 13 |
> > | nm.d.tsc_force_recalibrate | 0 | 4 | 4 |
> > +----------------------------------+----------+----------+-------+
> >
> >
> >
> > Thanks
> >
next prev parent reply other threads:[~2023-01-08 9:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 9:03 [lkp] [+64 bytes kernel size regression] [i386-tinyconfig] [78532abaf5] x86/tsc: Add option to force frequency recalibration with HW timer kernel test robot
2023-01-07 16:01 ` Paul E. McKenney
2023-01-08 9:14 ` Feng Tang [this message]
2023-01-08 17:05 ` Paul E. McKenney
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=Y7qJdtnshG3vu95L@feng-clx \
--to=feng.tang@intel.com \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paulmck@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.