From: Joe Perches <joe@perches.com>
To: John Ogness <john.ogness@linutronix.de>,
Alexander Monakov <amonakov@ispras.ru>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
Joerg Roedel <jroedel@suse.de>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
iommu@lists.linux-foundation.org,
LKML <linux-kernel@vger.kernel.org>,
Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] iommu/amd: Fix extended features logging
Date: Sun, 11 Apr 2021 14:08:14 -0700 [thread overview]
Message-ID: <9a9246c417587f17009543f8048d5f9b7a2ed68f.camel@perches.com> (raw)
In-Reply-To: <87o8ekioo4.fsf@jogness.linutronix.de>
On Sun, 2021-04-11 at 21:52 +0200, John Ogness wrote:
> I'd rather fix dev_info callers to allow pr_cont and then fix any code
> that is using this workaround.
Assuming you mean all dev_<level>() uses, me too.
> And if the print maintainers agree it is OK to encourage
> pr_cont(LOGLEVEL "...") usage, then people should really start using
> that if the loglevel on those pieces is important.
I have no stong feeling about the use of pr_cont(<KERN_LEVEL>
as valuable or not. I think it's just a trivial bit that
could be somewhat useful when interleaving occurs.
A somewhat better mechanism would be to have an explicit
cookie use like:
cookie = printk_multipart_init(KERN_LEVEL, fmt, ...);
while (<condition>)
printk_multipart_cont(cookie, fmt, ...);
printk_multipark_end(cookie, fmt, ...);
And separately, there should be a pr_debug_cont or equivalent.
next prev parent reply other threads:[~2021-04-11 21:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 21:11 Alexander Monakov
2021-04-11 6:17 ` Paul Menzel
2021-04-11 11:22 ` Alexander Monakov
2021-04-11 19:52 ` John Ogness
2021-04-11 20:43 ` Alexander Monakov
2021-04-11 21:08 ` Joe Perches [this message]
2021-04-12 10:59 ` Petr Mladek
2021-04-12 10:49 ` Petr Mladek
2021-04-11 11:31 ` Joe Perches
2021-04-11 11:42 ` Alexander Monakov
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=9a9246c417587f17009543f8048d5f9b7a2ed68f.camel@perches.com \
--to=joe@perches.com \
--cc=amonakov@ispras.ru \
--cc=iommu@lists.linux-foundation.org \
--cc=john.ogness@linutronix.de \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=suravee.suthikulpanit@amd.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®