mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Prarit Bhargava <prarit@redhat.com>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
	akpm@linux-foundation.org
Subject: Re: [PATCH] RFC: Introduce FW_INFO* functions
Date: Sat, 28 Sep 2013 14:00:04 -0400	[thread overview]
Message-ID: <52471924.40201@redhat.com> (raw)
In-Reply-To: <1380296451.17366.116.camel@joe-AO722>



On 09/27/2013 11:40 AM, Joe Perches wrote:
> On Fri, 2013-09-27 at 09:22 -0400, Prarit Bhargava wrote:
>> I'm proposing with this patch to do something similar to the WARN()
>> mechanism that is currently implemented in the kernel.  This
>> patchset introduces FW_INFO() and FW_INFO_DEV() which logs output
> 
> My first thought was "how ugly".
> There must be a better way than scraping dmesg output.

I am in no way married to this patch.  If anyone has a better idea I'd like to
hear it.  The dmesg log is the place that sysadmins are used to looking for it
-- it is the kernel that discovers and reports these issues.  AFAICT we've
always reported FW problems in the kernel log.

> 
>> diff --git a/kernel/panic.c b/kernel/panic.c
> []
>> @@ -445,6 +446,29 @@ void warn_slowpath_fmt_taint(const char *file, int line,
>>  }
>>  EXPORT_SYMBOL(warn_slowpath_fmt_taint);
>>  
>> +void warn_slowpath_fmt_dev(const char *file, int line,
>> +			   struct device *dev, const char *fmt, ...)
>> +{
>> +	struct slowpath_args args;
>> +
>> +	pr_info("[Firmware Info]: ");
>> +	if (dev)
>> +		pr_cont("%s %s: ",
>> +			dev_driver_string(dev), dev_name(dev));
>> +	pr_cont("at %s:%d ", file, line);
>> +
>> +	args.fmt = fmt;
>> +	va_start(args.args, fmt);
>> +	vprintk(args.fmt, args.args);
>> +	va_end(args.args);
>> +	if (dump_hardware_arch_desc())
>> +		pr_info("[Firmware Info]: %s\n", dump_hardware_arch_desc());
>> +	else
>> +		pr_info("[Firmware Info]: Hardware Unidentified\n");
>> +}
>> +EXPORT_SYMBOL(warn_slowpath_fmt_dev);
> 
> This bit should just use %pV and a single printk to
> avoid any possible message interleaving.
> 

Ah ... of course.  I'll definitely do that in a future patch.

Thanks for looking at this Joe.

P.

      reply	other threads:[~2013-09-28 18:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-27 13:22 Prarit Bhargava
2013-09-27 15:40 ` Joe Perches
2013-09-28 18:00   ` Prarit Bhargava [this message]

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=52471924.40201@redhat.com \
    --to=prarit@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome