From: john cooper <john.cooper@redhat.com>
To: Marc Haber <mh+qemu-devel@zugschlus.de>
Cc: john.cooper@redhat.com, Rusty Russell <rusty@rustcorp.com.au>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] virtio block device and sysfs
Date: Thu, 22 Apr 2010 16:48:26 -0400 [thread overview]
Message-ID: <4BD0B61A.4000800@redhat.com> (raw)
In-Reply-To: <20100422203055.GF5321@torres.zugschlus.de>
Marc Haber wrote:
> Hi,
>
> On Mon, Mar 22, 2010 at 10:22:14AM -0400, john cooper wrote:
>> Marc Haber wrote:
>>> It the serial "number" can be alphanumeric, that would be great to have.
>> It is simply a string of 20 characters, which AFAICT has
>> its roots in the ATA S/N convention along with many other
>> puzzling present day evils.
>
> That would be enough for my purposes, but more would be acceptable as
> well.
Internally the s/n string is currently limited to 20 bytes.
>> All that said, I like the alternate choice of adding a
>> special virtio request far better. It is actually simpler
>> (and more maintainable IMO) than going through the
>> gyrations of stuffing the S/N data through PCI config
>> space.
>
> Whatever is more easily implemented ;) How would a Windows
> installation see the label then?
Unknown at this point. That was part of my earlier motivation
to package up this information as an ATA_IDENTIFY command which
AFAIK is digestible by windows.
> Has my wish made its way on the official wishlist and/or roadmap?
I submitted a virtio-based patch a few weeks ago. I'd been
waiting for a reply from you concerning the /sys support
you'd mentioned. If that plan has fallen by the wayside
I'll forward a more robust ioctl patch to Rusty so we can
tie this off.
-john
--
john.cooper@redhat.com
next prev parent reply other threads:[~2010-04-22 20:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 22:42 [Qemu-devel] virtio block device and sysfs Marc Haber
2010-03-09 1:17 ` jvrao
2010-03-09 8:21 ` Marc Haber
2010-03-09 20:04 ` jvrao
2010-03-09 20:06 ` jvrao
2010-03-09 21:15 ` Marc Haber
2010-03-09 21:34 ` Anthony Liguori
2010-03-21 16:16 ` Jamie Lokier
2010-03-22 6:26 ` john cooper
2010-03-22 12:42 ` Marc Haber
2010-03-22 14:59 ` john cooper
2010-03-25 5:30 ` john cooper
2010-06-29 18:15 ` Marc Haber
2010-06-29 18:03 ` john cooper
2010-06-29 20:20 ` Marc Haber
2010-06-29 18:33 ` Ryan Harper
2010-06-29 18:36 ` Marc Haber
2010-06-29 18:36 ` Marc Haber
2010-06-30 7:01 ` Markus Armbruster
2010-09-13 8:55 ` Marc Haber
2010-09-13 14:34 ` Ryan Harper
2010-09-14 7:43 ` Marc Haber
2011-03-10 12:14 ` Marc Haber
2010-03-22 12:38 ` Marc Haber
2010-03-22 14:22 ` john cooper
2010-03-22 16:24 ` Jamie Lokier
2010-03-22 16:33 ` john cooper
2010-04-22 20:30 ` Marc Haber
2010-04-22 20:48 ` john cooper [this message]
2010-03-22 15:14 ` Paul Brook
2010-04-22 20:33 ` Marc Haber
2010-03-22 14:46 ` [Qemu-devel] " Michael S. Tsirkin
2010-03-22 14:52 ` Anthony Liguori
2010-03-20 18:32 ` [Qemu-devel] " Richard W.M. Jones
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=4BD0B61A.4000800@redhat.com \
--to=john.cooper@redhat.com \
--cc=mh+qemu-devel@zugschlus.de \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
/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).