From: Ryan Harper <ryanh@us.ibm.com>
To: john cooper <john.cooper@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Marc Haber <mh+qemu-devel@zugschlus.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] Add virtio disk identification support
Date: Tue, 1 Jun 2010 20:46:52 -0500 [thread overview]
Message-ID: <20100602014652.GA16406@us.ibm.com> (raw)
In-Reply-To: <4BAAF541.4090605@redhat.com>
* john cooper <john.cooper@redhat.com> [2010-03-25 00:45]:
> This series adds the minimal support to qemu and virtio_blk
> to support passing of a virtio_blk serial id string from qemu
> through the guest driver and to the guest userland.
>
> This is derived in part from a patch set posted by Rusty some
> time ago, but has been minimized to remove support for prior
> versions which attempted to provide the same functionality via
> pci config/io space. This version rather uses a virtio request
> as proposed in Rusty's example.
>
> Also removed is the packaging of the serial/id string within
> the glorious bag of bits returned by the ATA_IDENTIFY command.
> Here we transfer only the 20 bytes of serial/id string from
> qemu to the guest userland. In the proposed interface, this
> is made available by an ioctl() into the virtio_blk driver
> however other interfaces (eg: /sys) have also been proposed.
> A code snippet is attached below as an example of ioctl usage.
>
> The resulting code is quite minimal and I believe it addresses
> all concerns raised in prior versions.
>
> -john
I've applied the qemu and kernel side of this patch series and tested
this out using the sample code below. I've also reworked this example
into a virtioblk_id tool to work with udev to generate /dev/disk/by-id
links; I'll be submitting a patch set to linux-hotplug with these
changes, (and update for path_id) and some udev rules to
persistent-storage script to autogenerate by-id and by-path symlinks for
virtio-blk devices.
I've also got a patch to apply ontop of the qemu patches to generate a
default serial number if one isn't specified (like we do for ide
devices).
Anthony, is this series in your queue yet?
Acked-by: Ryan Harper <ryanh@us.ibm.com>
>
>
>
> #include <stdio.h>
> #include <strings.h>
> #include <sys/types.h>
> #include <fcntl.h>
> #include <linux/hdreg.h>
>
> #define IOCTL_CMD 'VBID'
>
> main()
> {
> int fd, rv;
> char buf[512];
>
> bzero(buf, sizeof (buf));
> if ((fd = open("/dev/vda", O_RDONLY)) < 0)
> perror("open");
> else if (ioctl(fd, IOCTL_CMD, buf) < 0)
> perror("ioctl");
> else
> printf("[%s]\n", buf);
> }
>
> --
> john.cooper@redhat.com
>
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh@us.ibm.com
next prev parent reply other threads:[~2010-06-02 1:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 5:31 [Qemu-devel] [PATCH 0/4] Add virtio disk identification support john cooper
2010-05-28 13:16 ` Ryan Harper
2010-06-02 1:46 ` Ryan Harper [this message]
2010-06-02 2:56 ` john cooper
2010-06-03 8:22 ` john cooper
-- strict thread matches above, loose matches on Subject: below --
2010-07-02 5:50 john cooper
2010-07-02 6:39 ` Markus Armbruster
2010-07-02 6:27 ` john cooper
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=20100602014652.GA16406@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=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).