qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <lvivier@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH] scripts: add a script to list virtio devices in a system
Date: Wed, 12 May 2021 09:44:45 +0200	[thread overview]
Message-ID: <b402ffd8-4f89-1b6c-f01d-67b4b31923d5@redhat.com> (raw)
In-Reply-To: <CAFEAcA8d6BQGHWUPp2cu-8eqYpXh5S6uV8va2A0KSq=f+9aWaw@mail.gmail.com>

On 11/05/2021 11:17, Peter Maydell wrote:
> On Thu, 6 May 2021 at 20:36, Laurent Vivier <lvivier@redhat.com> wrote:
>>
>> Add "lsvirtio" that lists all virtio devices in a system
>> the same way lspci does for the PCI cards.
> 
> This is cool, but it's not really QEMU specific -- it should
> work on any Linux guest running on some hypervisor or hardware
> that exposes virtio devices, right? So I'm not sure it really
> belongs in QEMU's source tree...
> 
> If you're a distro packager you'd probably want to have this be in its
> own package or at least not in the same package as the QEMU binaries,
> for instance, because this lives in the guest, not the host.
> 

Yes, I agree with that, but if it is in its own package I think it will never reach user
because no one will find it. I can try to push this into util-linux where we can find
tools like lscpu, lsblk ... but the competencies to review the code are in qemu-devel ML
not in util-linux ML.

Thanks,
Laurent



      reply	other threads:[~2021-05-12  7:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06 19:33 [PATCH] scripts: add a script to list virtio devices in a system Laurent Vivier
2021-05-06 19:50 ` Philippe Mathieu-Daudé
2021-05-07  6:17   ` Laurent Vivier
2021-05-11  8:33     ` Michael S. Tsirkin
2021-05-11  8:32 ` Michael S. Tsirkin
2021-05-11  9:17 ` Peter Maydell
2021-05-12  7:44   ` Laurent Vivier [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=b402ffd8-4f89-1b6c-f01d-67b4b31923d5@redhat.com \
    --to=lvivier@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).