linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Wagner <wagi@monom.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [ANNOUNCE] v5.9-rc2-rt1
Date: Thu, 27 Aug 2020 13:27:05 +0200	[thread overview]
Message-ID: <20200827112705.uleixtdmx3pacr5u@beryllium.lan> (raw)
In-Reply-To: <20200827102840.msv556nrah4h4vmq@linutronix.de>

On Thu, Aug 27, 2020 at 12:28:40PM +0200, Sebastian Andrzej Siewior wrote:
> On 2020-08-27 12:16:22 [+0200], Daniel Wagner wrote:
> > The -rt kernel is roughly 6MB larger. Just need to check the memory
> > ranges u-boot is using.
> 
> so that 6MiB sounded bad but then it is ~36MiB in total so….
> Is this full debug and so on?

I didn't really try to minimize the kernel. I haven't checked yet
if 5.6-rt is also showing this size increase. At least, our SUSE spin
off from v5.4-rt doesn't have this size increase with the same config.

Would be interesting to see the size numbers for v5.6-rt? Hmm, I'll
just start the compiler. It's all scripted anyway :)

Anyway, the config is:

  make defconfig

and

#
# Networking
#
CONFIG_PACKET=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y

# NFS
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFS_V4=y
CONFIG_NFS_V4_1=y
CONFIG_NFS_V4_2=y
CONFIG_ROOT_NFS=y

#
# Debugging
#
CONFIG_DEBUG_INFO=y
CONFIG_PRINTK_TIME=y
CONFIG_DEBUG_KERNEL=y
CONFIG_EARLY_PRINTK=y
CONFIG_MESSAGE_LOGLEVEL_DEFAULT=7

# Embedded config to kernel. /proc/config.gz
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y

CONFIG_KEXEC=y

# Default settings
#
# CONFIG_DEBUG_WW_MUTEX_SLOWPATH is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCKDEP is not set

CONFIG_DEBUG_ATOMIC_SLEEP=y

# CONFIG_CPU_FREQ is not set
# CONFIG_CPU_IDLE is not set

# CONFIG_NO_HZ is not set
CONFIG_HZ_PERIODIC=y

CONFIG_HZ_250=y
CONFIG_HZ=250

# CONFIG_SUSPEND is not set
# CONFIG_HIBERNATION is not set
# CONFIG_PM is not set

# cyclicdeadline dependency
CONFIG_SCHED_DEBUG=y

CONFIG_RCU_EXPERT=y
CONFIG_RCU_NOCB_CPU=y

# tracing
CONFIG_EMBEDDED=y
CONFIG_EXPERT=y
CONFIG_FTRACE=y
CONFIG_FUNCTION_TRACER=y
CONFIG_SCHED_TRACER=y

CONFIG_PREEMPT_RT=y

  reply	other threads:[~2020-08-27 15:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24 15:46 [ANNOUNCE] v5.9-rc2-rt1 Sebastian Andrzej Siewior
2020-08-26  8:08 ` Daniel Wagner
2020-08-26  8:12   ` Sebastian Andrzej Siewior
2020-08-26  9:05     ` Daniel Wagner
2020-08-26 10:43       ` Daniel Wagner
2020-08-27  9:19         ` Daniel Wagner
2020-08-27  9:27           ` Sebastian Andrzej Siewior
2020-08-27 10:16             ` Daniel Wagner
2020-08-27 10:28               ` Sebastian Andrzej Siewior
2020-08-27 11:27                 ` Daniel Wagner [this message]
2020-08-27 12:46                   ` Daniel Wagner
2020-08-27 15:50                     ` Daniel Vacek
2020-08-28  7:36                       ` Daniel Wagner
2020-08-28  8:13                         ` Sebastian Andrzej Siewior

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=20200827112705.uleixtdmx3pacr5u@beryllium.lan \
    --to=wagi@monom.org \
    --cc=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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).