mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Andre Richter <andre.o.richter@gmail.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] virt/kvm/iommu.c: Add leading zeros to device's BDF notation in debug messages
Date: Wed, 02 Oct 2013 09:41:17 -0600	[thread overview]
Message-ID: <1380728477.14271.81.camel@ul30vt.home> (raw)
In-Reply-To: <20131002103508.GG17294@redhat.com>

On Wed, 2013-10-02 at 13:35 +0300, Gleb Natapov wrote:
> On Wed, Oct 02, 2013 at 12:23:26PM +0200, Andre Richter wrote:
> > When KVM (de)assigns PCI(e) devices to VMs, a debug message is printed
> > including the BDF notation of the respective device. Currently, the BDF
> > notation does not have the commonly used leading zeros. This produces
> > messages like "assign device 0:1:8.0", which look strange at first sight.
> > 
> > The patch fixes this by exchanging the printk(KERN_DEBUG ...) with dev_info()
> > and also inserts "kvm" into the debug message, so that it is obvious where
> > the message comes from. Also reduces LoC.
> Legacy assigned device is deprecated, but this looks nice enough to
> apply. Alex can you glance at it?

Seems ok to me, my only question would be why are we promoting this from
KERN_DEBUG to KERN_INFO.  We could use dev_dbg() to maintain the same
kernel log level.  A nice feature of either is that it prints out the
attached driver so we can see in dmesg whether the device is attached to
a host driver, nothing, or pci-stub.  Thanks,

Alex

> > 
> > Signed-off-by: Andre Richter <andre.o.richter@gmail.com>
> > ---
> >  virt/kvm/iommu.c | 12 ++----------
> >  1 file changed, 2 insertions(+), 10 deletions(-)
> > 
> > diff --git a/virt/kvm/iommu.c b/virt/kvm/iommu.c
> > index 72a130b..a3b1410 100644
> > --- a/virt/kvm/iommu.c
> > +++ b/virt/kvm/iommu.c
> > @@ -190,11 +190,7 @@ int kvm_assign_device(struct kvm *kvm,
> >  
> >  	pdev->dev_flags |= PCI_DEV_FLAGS_ASSIGNED;
> >  
> > -	printk(KERN_DEBUG "assign device %x:%x:%x.%x\n",
> > -		assigned_dev->host_segnr,
> > -		assigned_dev->host_busnr,
> > -		PCI_SLOT(assigned_dev->host_devfn),
> > -		PCI_FUNC(assigned_dev->host_devfn));
> > +	dev_info(&pdev->dev, "kvm assign device\n");
> >  
> >  	return 0;
> >  out_unmap:
> > @@ -220,11 +216,7 @@ int kvm_deassign_device(struct kvm *kvm,
> >  
> >  	pdev->dev_flags &= ~PCI_DEV_FLAGS_ASSIGNED;
> >  
> > -	printk(KERN_DEBUG "deassign device %x:%x:%x.%x\n",
> > -		assigned_dev->host_segnr,
> > -		assigned_dev->host_busnr,
> > -		PCI_SLOT(assigned_dev->host_devfn),
> > -		PCI_FUNC(assigned_dev->host_devfn));
> > +	dev_info(&pdev->dev, "kvm deassign device\n");
> >  
> >  	return 0;
> >  }
> > -- 
> > 1.8.1.2
> 
> --
> 			Gleb.




  reply	other threads:[~2013-10-02 15:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02 10:23 Andre Richter
2013-10-02 10:35 ` Gleb Natapov
2013-10-02 15:41   ` Alex Williamson [this message]
2013-10-02 19:08     ` Andre Richter
2013-10-02 19:58       ` Alex Williamson
2013-10-03  8:48 ` Gleb Natapov

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=1380728477.14271.81.camel@ul30vt.home \
    --to=alex.williamson@redhat.com \
    --cc=andre.o.richter@gmail.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.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®