public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Chris Lalancette <clalance@redhat.com>,
	virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Carsten Otte <cotte@de.ibm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: [Fwd: [PATCH]: Fix silly output for virtio devices in /proc/interrupts]
Date: Thu, 22 May 2008 16:58:44 -0500	[thread overview]
Message-ID: <4835EC94.8080508@codemonkey.ws> (raw)
In-Reply-To: <200805222238.58166.rusty@rustcorp.com.au>

Rusty Russell wrote:
> On Wednesday 21 May 2008 23:13:05 Chris Lalancette wrote:
>   
>> Author: Chris Lalancette <clalance@redhat.com>
>> Date:   Thu May 15 09:04:55 2008 -0400
>>
>>     register_virtio_device was doing something silly, in that it was
>> overwriting what the calling driver stuck into .bus_id" for the name.  This
>> caused problems in the output of /proc/interrupts, since when you
>> request_irq(), it doesn't actually copy the devname you pass in but just
>> stores a pointer to the data.  The fix is to just not have
>> register_virtio_device do anything with the bus_id, and assume the higher
>> level driver set it up properly.
>>     
>
> OK, but only one higher-level driver will set it up properly: kvm.  Neither
> lguest nor s/390 do this, and as a result, they fail to register *any*
> devices.
>
> The following patch should fix it for s/390 (it's identical to the lguest
> patch), but would prefer testing (S/390-ers cc'd).
>   

It may actually be better for virtio to set this up.  The problem is 
that if you have multiple transports that are registering virtio 
devices, it's impossible at the transport level to guarantee uniqueness 
while still using the "virtio%d" naming.  Except the current scheme is 
no good, we'd have to push the dev_index into virtio too.

Regards,

Anthony Liguori

> ===
> virtio: S/390 set name of virtio devices directly.
>
> Chris has a patch 'Fix silly output for virtio devices in /proc/interrupts'
> which requires callers to the virtio driver infrastructure to set the bus_ids
> themselves.  This does that for s/390.
>
> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
> Cc: Christian Borntraeger <borntraeger@de.ibm.com>
> Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
> Cc: Carsten Otte <cotte@de.ibm.com>
> Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
> Cc: Chris Lalancette <clalance@redhat.com>
> ---
>  drivers/s390/kvm/kvm_virtio.c |    2 ++
>  1 file changed, 2 insertions(+)
>
> diff -r c903ef6b391f drivers/s390/kvm/kvm_virtio.c
> --- a/drivers/s390/kvm/kvm_virtio.c	Thu May 22 22:31:31 2008 +1000
> +++ b/drivers/s390/kvm/kvm_virtio.c	Thu May 22 22:32:55 2008 +1000
> @@ -265,6 +265,8 @@ static void add_kvm_device(struct kvm_de
>  
>  	kdev->vdev.dev.parent = &kvm_root;
>  	kdev->vdev.index = dev_index++;
> +	snprintf(kdev->vdev.dev.bus_id, BUS_ID_SIZE, "virtio%d",
> +		 kdev->vdev.index);
>  	kdev->vdev.id.device = d->type;
>  	kdev->vdev.config = &kvm_vq_configspace_ops;
>  	kdev->desc = d;
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   


  parent reply	other threads:[~2008-05-22 21:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21 13:13 [Fwd: [PATCH]: Fix silly output for virtio devices in /proc/interrupts] Chris Lalancette
2008-05-22 12:38 ` Rusty Russell
2008-05-22 12:51   ` Chris Lalancette
2008-05-22 13:38   ` Christian Borntraeger
2008-05-22 21:58   ` Anthony Liguori [this message]
2008-05-23  2:43     ` Rusty Russell

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=4835EC94.8080508@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=borntraeger@de.ibm.com \
    --cc=clalance@redhat.com \
    --cc=cotte@de.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=schwidefsky@de.ibm.com \
    --cc=virtualization@lists.linux-foundation.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