From: Petr Mladek <pmladek@suse.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH printk v5 6/8] printk: nbcon: Add sequence handling
Date: Mon, 18 Sep 2023 16:35:44 +0200 [thread overview]
Message-ID: <ZQhgQMqHzZ1WMvjo@alley> (raw)
In-Reply-To: <20230916192007.608398-7-john.ogness@linutronix.de>
On Sat 2023-09-16 21:26:05, John Ogness wrote:
> From: Thomas Gleixner <tglx@linutronix.de>
>
> Add an atomic_long_t field @nbcon_seq to the console struct to
> store the sequence number for nbcon consoles. For nbcon consoles
> this will be used instead of the non-atomic @seq field. The new
> field allows for safe atomic sequence number updates without
> requiring any locking.
>
> On 64bit systems the new field stores the full sequence number.
> On 32bit systems the new field stores the lower 32 bits of the
> sequence number, which are expanded to 64bit as needed by
> folding the values based on the sequence numbers available in
> the ringbuffer.
>
> For 32bit systems, having a 32bit representation in the console
> is sufficient. If a console ever gets more than 2^31 records
> behind the ringbuffer then this is the least of the problems.
>
> Co-developed-by: John Ogness <john.ogness@linutronix.de>
> Signed-off-by: John Ogness <john.ogness@linutronix.de>
> Signed-off-by: Thomas Gleixner (Intel) <tglx@linutronix.de>
Reviewed-by: Petr Mladek <pmladek@suse.com>
Best Regards,
Petr
next prev parent reply other threads:[~2023-09-18 16:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 19:19 [PATCH printk v5 0/8] provide nbcon base John Ogness
2023-09-16 19:20 ` [PATCH printk v5 1/8] printk: Add non-BKL (nbcon) console basic infrastructure John Ogness
2023-09-16 19:20 ` [PATCH printk v5 2/8] printk: nbcon: Add acquire/release logic John Ogness
2023-09-18 13:56 ` Petr Mladek
2023-09-16 19:20 ` [PATCH printk v5 3/8] printk: Make static printk buffers available to nbcon John Ogness
2023-09-16 19:20 ` [PATCH printk v5 4/8] printk: nbcon: Add buffer management John Ogness
2023-09-16 19:20 ` [PATCH printk v5 5/8] printk: nbcon: Add ownership state functions John Ogness
2023-09-16 19:20 ` [PATCH printk v5 6/8] printk: nbcon: Add sequence handling John Ogness
2023-09-18 14:35 ` Petr Mladek [this message]
2023-09-16 19:20 ` [PATCH printk v5 7/8] printk: nbcon: Add emit function and callback function for atomic printing John Ogness
2023-09-16 19:20 ` [PATCH printk v5 8/8] printk: nbcon: Allow drivers to mark unsafe regions and check state John Ogness
2023-09-18 14:54 ` [PATCH printk v5 0/8] provide nbcon base Petr Mladek
2023-09-19 12:08 ` Petr Mladek
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=ZQhgQMqHzZ1WMvjo@alley \
--to=pmladek@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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
all inboxes | Powered by JetHome®