From: Paolo Bonzini <pbonzini@redhat.com>
To: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>,
qemu-devel@nongnu.org
Cc: famz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 0/2] hw/scsi: support SCSI-2 passthrough without PI
Date: Fri, 6 Apr 2018 12:12:36 +0200 [thread overview]
Message-ID: <a94422e9-833f-db3a-fc38-39fab45f1850@redhat.com> (raw)
In-Reply-To: <5a3d6ece-e68b-5eae-3808-510c4eed4d68@linux.vnet.ibm.com>
On 06/04/2018 01:10, Daniel Henrique Barboza wrote:
> Yet another fix is to fully prohibit the user to set scsi_version
> scsi-block and scsi-generic cases, returning an error message right off
> the start. Not sure how hard this would be - perhaps the above
> alternatives are cleaner.
>
> Another fix is ... no fix. I am not sure how far the design philosophy
> of passthrough devices allows the user to overwrite device parameters in
> despite of their real values, but .... what if the user wants to
> enforce a scsi_version when using a scsi-block device? The device will
> surely behave badly, but the user explicitly enforced it via command
> line, so perhaps let him/her have at it?
Yeah, that was the idea. Removing it is as easy as dropping the
DEFINE_PROP_INT32 and initializing to -1 in scsi_block_realize (just
like for scsi_generic_realize), but for now we can keep it. My usecase
was more to downgrade scsi_version from newer to 2.
Paolo
next prev parent reply other threads:[~2018-04-06 10:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 16:23 [Qemu-devel] [PATCH v4 0/2] hw/scsi: support SCSI-2 passthrough without PI Paolo Bonzini
2018-04-05 16:23 ` [Qemu-devel] [PATCH 1/2] scsi-disk: allow customizing the SCSI version Paolo Bonzini
2018-04-05 22:49 ` Daniel Henrique Barboza
2018-04-05 16:23 ` [Qemu-devel] [PATCH 2/2] hw/scsi: support SCSI-2 passthrough without PI Paolo Bonzini
2018-04-05 23:10 ` [Qemu-devel] [PATCH v4 0/2] " Daniel Henrique Barboza
2018-04-06 10:12 ` Paolo Bonzini [this message]
2018-04-06 12:06 ` Daniel Henrique Barboza
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=a94422e9-833f-db3a-fc38-39fab45f1850@redhat.com \
--to=pbonzini@redhat.com \
--cc=danielhb@linux.vnet.ibm.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).