mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Isaac Manjarres <isaacmanjarres@google.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	John Ogness <john.ogness@linutronix.de>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	surenb@google.com, kernel-team@android.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] printk: Improve memory usage logging during boot
Date: Wed, 16 Oct 2024 12:24:35 +0200	[thread overview]
Message-ID: <Zw-USn7PUHwCIGfL@pathway.suse.cz> (raw)
In-Reply-To: <Zw5ke11y4TkRQJQ2@google.com>

On Tue 2024-10-15 05:47:55, Isaac Manjarres wrote:
> On Wed, Oct 02, 2024 at 11:04:48AM -0700, Isaac Manjarres wrote:
> > On Tue, Oct 01, 2024 at 05:46:31PM +0200, Petr Mladek wrote:
> > > On Mon 2024-09-30 11:48:24, Isaac J. Manjarres wrote:
> > > > With the new logs, it is much easier to see exactly why the memory
> > > > increased by 2304 KB:
> > > > 
> > > Note need to send v3. I could update the commit message when committing
> > > the patch.
> 
> I just wanted to follow up to see if there was anything else left
> for this patch? Otherwise, would it be possible to please merge this?

I am sorry for the delay and thanks for the reminder. Last weeks were
a bit hectic...

Anyway, I have just comitted the patch into printk/linux.git,
branch for-6.13.

Note:

I have updated the sample messages in the commit message as suggested
earlier.

Also I double checked the patch and simplified the comment
in the following hunk. The original one was a bit cryptic.

@@ -1185,20 +1196,25 @@ void __init setup_log_buf(int early)
 	if (!early && !new_log_buf_len)
 		log_buf_add_cpu();
 
-	if (!new_log_buf_len)
+	if (!new_log_buf_len) {
+		/* Show the memory stats only once. */
+		if (!early)
+			goto out;
+
 		return;
+	}

, see also
https://git.kernel.org/pub/scm/linux/kernel/git/printk/linux.git/commit/?h=for-6.13&id=a961ec4e2860af4933e8c1763fe4f038c2d6ac80

Best Regards,
Petr

  reply	other threads:[~2024-10-16 10:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-30 18:48 Isaac J. Manjarres
2024-10-01 15:46 ` Petr Mladek
2024-10-02 18:04   ` Isaac Manjarres
2024-10-15 12:47     ` Isaac Manjarres
2024-10-16 10:24       ` Petr Mladek [this message]
2024-10-16 16:38         ` Isaac Manjarres
2024-12-01 11:40   ` Geert Uytterhoeven
2024-12-03  9:42     ` Petr Mladek
2024-12-04 17:17       ` John Ogness

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=Zw-USn7PUHwCIGfL@pathway.suse.cz \
    --to=pmladek@suse.com \
    --cc=isaacmanjarres@google.com \
    --cc=john.ogness@linutronix.de \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=surenb@google.com \
    /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

all inboxes | Powered by JetHome®