mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Bjorn Helgaas <bhelgaas@google.com>,
	David Airlie <airlied@linux.ie>,
	Thierry Reding <treding@nvidia.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2] vgaarb: Use dev_printk() when possible
Date: Thu, 17 Nov 2016 14:20:59 -0600	[thread overview]
Message-ID: <20161117202059.GA22428@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <20161117185921.r3fcd4dhfdlahb6b@phenom.ffwll.local>

On Thu, Nov 17, 2016 at 07:59:21PM +0100, Daniel Vetter wrote:
> On Thu, Nov 17, 2016 at 11:47:58AM -0600, Bjorn Helgaas wrote:
> > Use dev_printk() when possible.  This makes messages more consistent with
> > other device-related messages and, in some cases, adds useful information.
> > This changes messages like this:
> > 
> >   vgaarb: failed to allocate pci device
> >   vgaarb: setting as boot device: PCI:0000:01:00.0
> >   vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
> >   vgaarb: bridge control possible 0000:01:00.0
> > 
> > to this:
> > 
> >   pci 0000:01:00.0: vgaarb: failed to allocate VGA arbiter data
> >   pci 0000:01:00.0: vgaarb: setting as boot VGA device
> >   pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
> >   pci 0000:01:00.0: vgaarb: bridge control possible
> > 
> > No functional change intended.
> 
> Found one more nit below where there was one relevant change that
> shouldn't be here.

> > @@ -1189,24 +1194,25 @@ static ssize_t vga_arb_write(struct file *file, const char __user *buf,
> >  				ret_val = -EPROTO;
> >  				goto done;
> >  			}
> > -			pr_debug("%s ==> %x:%x:%x.%x\n", curr_pos,
> > -				domain, bus, PCI_SLOT(devfn), PCI_FUNC(devfn));
> > -
> >  			pdev = pci_get_domain_bus_and_slot(domain, bus, devfn);
> > -			pr_debug("pdev %p\n", pdev);
> >  			if (!pdev) {
> > -				pr_err("invalid PCI address %x:%x:%x\n",
> > -					domain, bus, devfn);
> > +				pr_err("invalid PCI address %04x:%02x:%02x.%x\n",
> > +					domain, bus, PCI_SLOT(devfn),
> > +					PCI_FUNC(devfn));
> 
> Userspace-triggerable dmesg spam is imo not good, this needs to stay at
> debug level.

I did move these around slightly, but I don't *think* I changed
anything from debug to err level.  Previously:

  pr_debug("%s ==> %x:%x:%x.%x\n", ...);
  pdev = pci_get_domain_bus_and_slot(...);
  pr_debug("pdev %p\n", pdev);
  if (!pdev) {
    pr_err("invalid PCI address %x:%x:%x\n", ...);
  }

after my patch:

  pdev = pci_get_domain_bus_and_slot(...);
  if (!pdev) {
    pr_err("invalid PCI address %x:%x:%x\n", ...);
  }
  pr_debug("%s ==> %x:%x:%x.%x pdev %p\n", ...);

The pr_err() was there before.  I'd be glad to change that to a
pr_debug() if you prefer.

Bjorn

  reply	other threads:[~2016-11-17 20:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17 17:47 Bjorn Helgaas
2016-11-17 18:59 ` Daniel Vetter
2016-11-17 20:20   ` Bjorn Helgaas [this message]
2016-11-18  9:44     ` Daniel Vetter

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=20161117202059.GA22428@bhelgaas-glaptop.roam.corp.google.com \
    --to=helgaas@kernel.org \
    --cc=airlied@linux.ie \
    --cc=bhelgaas@google.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=treding@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 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®