From: John Hubbard <jhubbard@nvidia.com>
To: Timur Tabi <ttabi@nvidia.com>,
"gary@garyguo.net" <gary@garyguo.net>,
"rust-for-linux@vger.kernel.org" <rust-for-linux@vger.kernel.org>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
Joel Fernandes <joelagnelf@nvidia.com>,
"dakr@kernel.org" <dakr@kernel.org>,
"aliceryhl@google.com" <aliceryhl@google.com>,
Alexandre Courbot <acourbot@nvidia.com>,
"ojeda@kernel.org" <ojeda@kernel.org>
Subject: Re: [PATCH 2/2] gpu: nova-core: add missing newlines to several print strings
Date: Tue, 6 Jan 2026 18:39:05 -0800 [thread overview]
Message-ID: <f4d26971-bf10-4370-8994-13ad962becfd@nvidia.com> (raw)
In-Reply-To: <38a599e8cebb7209cd8e86135794f1d8755d7a7b.camel@nvidia.com>
On 1/6/26 6:21 PM, Timur Tabi wrote:
> On Tue, 2026-01-06 at 18:10 -0800, John Hubbard wrote:
>> nova-core (dev_*!) [after patch] 39 32 55%
>> nova-core (dev_*!) [before patch] 32 39 45%
>
> This can't be right, because I checked thoroughly to make sure that my patch fixed ALL dev_xx
> format strings.
Did you? haha :)
drivers/gpu/nova-core/fb.rs:81-85
dev_warn!(
&self.device,
"failed to unregister sysmem flush page: {:?}",
e
)
drivers/gpu/nova-core/gsp/boot.rs:83-87
dev_err!(
dev,
"FWSEC-FRTS returned with error code {:#x}",
frts_status
);
drivers/gpu/nova-core/gsp/cmdq.rs:616-620
dev_err!(
self.dev,
"GSP RPC: receive: Call {} - bad checksum",
header.sequence()
);
drivers/gpu/nova-core/gsp/sequencer.rs:391-395
dev_err!(
sequencer.dev,
"Error running command at index {}",
sequencer.seq_info.cmd_index
);
drivers/gpu/nova-core/gsp/sequencer.rs:401-404
dev_dbg!(
sequencer.dev,
"CPU Sequencer commands completed successfully"
);
However, you *are* correct about the "this can't be right". I had a bug
in my search script. Updated numbers do actually lean much more
toward using the \n on screen:
Codebase WITH \n WITHOUT \n % with \n
----------------------------------------------------------------
samples/rust (dev_*!) 39 1 98%
samples/rust (pr_*!) 29 6 83%
nova-core (dev_*!) 68 5 93%
nova (dev_*!) 0 0 --
tyr (dev_*!) 4 3 57%
pwm (dev_*!) 7 2 78%
binder (pr_*!) 22 57 28%
thanks,
--
John Hubbard
next prev parent reply other threads:[~2026-01-07 2:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 1:24 [PATCH 1/2] gpu: nova-core: check for overflow to DMATRFBASE1 Timur Tabi
2026-01-07 1:24 ` [PATCH 2/2] gpu: nova-core: add missing newlines to several print strings Timur Tabi
2026-01-07 2:10 ` John Hubbard
2026-01-07 2:21 ` Timur Tabi
2026-01-07 2:39 ` John Hubbard [this message]
2026-01-07 10:22 ` Miguel Ojeda
2026-01-07 10:22 ` Miguel Ojeda
2026-01-07 9:54 ` Miguel Ojeda
2026-01-07 9:54 ` Miguel Ojeda
2026-01-08 12:55 ` Gary Guo
2026-01-08 12:55 ` Gary Guo
2026-01-08 13:36 ` Danilo Krummrich
2026-01-08 13:36 ` Danilo Krummrich
2026-01-08 13:42 ` Alice Ryhl
2026-01-08 13:42 ` Alice Ryhl
2026-01-08 14:13 ` Gary Guo
2026-01-08 14:13 ` Gary Guo
2026-01-07 1:56 ` [PATCH 1/2] gpu: nova-core: check for overflow to DMATRFBASE1 John Hubbard
2026-01-07 2:04 ` Timur Tabi
2026-01-07 3:55 ` Joel Fernandes
2026-01-07 3:55 ` Joel Fernandes
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=f4d26971-bf10-4370-8994-13ad962becfd@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=joelagnelf@nvidia.com \
--cc=nouveau@lists.freedesktop.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=ttabi@nvidia.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 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.