From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, John Snow <jsnow@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v1 1/2] scsi-disk: support reporting of rotation rate
Date: Wed, 4 Oct 2017 10:44:27 -0500 [thread overview]
Message-ID: <88a37718-54ab-82d1-a215-0ab87047131e@redhat.com> (raw)
In-Reply-To: <20171004114008.14849-2-berrange@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2129 bytes --]
On 10/04/2017 06:40 AM, Daniel P. Berrange wrote:
> The Linux kernel will query the SCSI "Block device characteristics"
> VPD to determine the rotations per minute of the disk. If this has
> the value 1, it is taken to be an SSD and so Linux sets the
> 'rotational' flag to 0 for the I/O queue and will stop using that
> disk as a source of random entropy. Other operating systems may
> also take into account rotation rate when setting up default
> behaviour.
>
> Mgmt apps should be able to set the rotation rate for virtualized
> block devices, based on characteristics of the host storage in use,
> so that the guest OS gets sensible behaviour out of the box. This
> patch thus adds a 'rotation-rate' parameter for 'scsi-hd' and
> 'scsi-block' device types. For the latter, this parameter will be
> ignored unless the host device has TYPE_DISK.
>
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> ---
> hw/scsi/scsi-disk.c | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
> bool tray_locked;
> + /*
> + * 0x0000 - rotation rate not reported
> + * 0x0001 - non-rotating medium (SSD)
> + * 0x0002-0x0400 - reserved
> + * 0x0401-0xffe - rotations per minute
s/0xffe/0xfffe/
> + * 0xffff - reserved
> + */
> + uint16_t rotation_rate;
> } SCSIDiskState;
>
> static bool scsi_handle_rw_error(SCSIDiskReq *r, int error, bool acct_failed);
> @@ -605,6 +613,7 @@ static int scsi_disk_emulate_inquiry(SCSIRequest *req, uint8_t *outbuf)
> outbuf[buflen++] = 0x83; // device identification
> if (s->qdev.type == TYPE_DISK) {
> outbuf[buflen++] = 0xb0; // block limits
> + outbuf[buflen++] = 0xb1; /* block device characteristics */
This function is awkward - it is a non-local audit to see whether we are
at risk of overflowing any buffers due to the new output. But from
what I can see, I think you're safe.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-10-04 15:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 11:40 [Qemu-devel] [PATCH v1 0/2] Reporting of rotation rate for disks Daniel P. Berrange
2017-10-04 11:40 ` [Qemu-devel] [PATCH v1 1/2] scsi-disk: support reporting of rotation rate Daniel P. Berrange
2017-10-04 15:44 ` Eric Blake [this message]
2017-10-04 16:49 ` Dr. David Alan Gilbert
2017-10-04 16:56 ` Daniel P. Berrange
2017-10-04 11:40 ` [Qemu-devel] [PATCH v1 2/2] ide: " Daniel P. Berrange
2017-10-04 15:45 ` Eric Blake
2017-10-04 15:57 ` John Snow
2017-10-20 8:42 ` Kevin Wolf
2017-10-20 9:02 ` Daniel P. Berrange
2017-10-23 17:17 ` John Snow
2017-10-04 12:19 ` [Qemu-devel] [PATCH v1 0/2] Reporting of rotation rate for disks Daniel P. Berrange
2017-10-10 10:18 ` Paolo Bonzini
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=88a37718-54ab-82d1-a215-0ab87047131e@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=jsnow@redhat.com \
--cc=pbonzini@redhat.com \
--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).