From: Paolo Bonzini <pbonzini@redhat.com>
To: Daniel Henrique Barboza <danielhb413@gmail.com>, qemu-devel@nongnu.org
Cc: famz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/3] VPD Block Limits emulation implementation
Date: Thu, 28 Jun 2018 12:03:40 +0200 [thread overview]
Message-ID: <2bc7533d-65f3-9b0e-00fd-b78d31b22065@redhat.com> (raw)
In-Reply-To: <20180627172432.11120-1-danielhb413@gmail.com>
On 27/06/2018 19:24, Daniel Henrique Barboza wrote:
> v2:
> - series overhauled - first 2 patches are cleanups (split in 2
> for easier review), patch 3 contains the whole logic
> - previous version link:
> https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg02289.html
>
>
> When using SCSI passthrough and running in Linux, QEMU edits the
> reply of the SCSI Inquiry VPD Block Limits message with the value
> of the /sys/bus/<dev>/queue/max_sectors_kb parameter the device
> has in the host. Doing so allows the Linux guest to proper setup
> the device.
>
> But the Block Limits message is optional, and its absence can cause
> the device to be unusable by the guest. An example can be seen
> at https://bugzilla.redhat.com/show_bug.cgi?id=1566195.
>
> This series implements an approach to solve it.
Queued, thanks.
Paolo
prev parent reply other threads:[~2018-06-28 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 17:24 [Qemu-devel] [PATCH v2 0/3] VPD Block Limits emulation implementation Daniel Henrique Barboza
2018-06-27 17:24 ` [Qemu-devel] [PATCH v2 1/3] hw/scsi: cleanups before VPD BL emulation Daniel Henrique Barboza
2018-06-27 17:24 ` [Qemu-devel] [PATCH v2 2/3] hw/scsi: centralize SG_IO calls into single function Daniel Henrique Barboza
2018-06-27 17:24 ` [Qemu-devel] [PATCH v2 3/3] hw/scsi: add VPD Block Limits emulation Daniel Henrique Barboza
2018-06-28 10:03 ` Paolo Bonzini [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=2bc7533d-65f3-9b0e-00fd-b78d31b22065@redhat.com \
--to=pbonzini@redhat.com \
--cc=danielhb413@gmail.com \
--cc=famz@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).