From: Chris Lalancette <clalance@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: 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 14:51:17 +0200 [thread overview]
Message-ID: <48356C45.2020802@redhat.com> (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.
Ah, OK. Alternatively, we could do:
snprintf(bus_id, BUS_ID_SIZE, "virtio%d", index)
in register_virtio_device(), and just fix the one user who does it themselves
(kvm) to not duplicate the work.
Either way is fine with me.
Chris Lalancette
next prev parent reply other threads:[~2008-05-22 13:00 UTC|newest]
Thread overview: 11+ 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 12:51 ` Chris Lalancette [this message]
2008-05-22 13:38 ` Christian Borntraeger
2008-05-22 13:38 ` Christian Borntraeger
2008-05-22 21:58 ` Anthony Liguori
2008-05-22 21:58 ` Anthony Liguori
2008-05-23 2:43 ` Rusty Russell
2008-05-23 2:43 ` Rusty Russell
2008-05-22 12:38 ` 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=48356C45.2020802@redhat.com \
--to=clalance@redhat.com \
--cc=borntraeger@de.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.