From: Eric Farman <farman@linux.vnet.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
"Richard W . M . Jones" <rjones@redhat.com>,
Felipe Franciosi <felipe@nutanix.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Dariusz Stojaczyk <dariuszx.stojaczyk@intel.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] vhost-scsi: add missing virtqueue_size parameter
Date: Tue, 5 Dec 2017 13:10:19 -0500 [thread overview]
Message-ID: <cac73ff5-1374-7ee6-34f8-6ea015b5722f@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAFEAcA_zY1rimg84UCoOo-d1x9t45gqyfxhKoYZR-0EW8fHa9A@mail.gmail.com>
On 12/05/2017 07:40 AM, Peter Maydell wrote:
> On 5 December 2017 at 00:59, Michael S. Tsirkin <mst@redhat.com> wrote:
>> On Mon, Dec 04, 2017 at 03:00:45PM -0500, Eric Farman wrote:
>>>
>>>
>>> On 12/04/2017 01:05 PM, Peter Maydell wrote:
>>>> On 4 December 2017 at 17:52, Eric Farman <farman@linux.vnet.ibm.com> wrote:
>>>>> On 12/01/2017 10:16 AM, Paolo Bonzini wrote:
>>>>>>
>>>>>> On 01/12/2017 16:15, Eric Farman wrote:
>>>>>>> diff --git a/hw/scsi/vhost-scsi.c b/hw/scsi/vhost-scsi.c
>>>>>>> index cd4ab05233..9c1bea8ff3 100644
>>>>>>> --- a/hw/scsi/vhost-scsi.c
>>>>>>> +++ b/hw/scsi/vhost-scsi.c
>>>>>>> @@ -233,6 +233,8 @@ static Property vhost_scsi_properties[] = {
>>>>>>> DEFINE_PROP_STRING("wwpn", VirtIOSCSICommon, conf.wwpn),
>>>>>>> DEFINE_PROP_UINT32("boot_tpgt", VirtIOSCSICommon, conf.boot_tpgt,
>>>>>>> 0),
>>>>>>> DEFINE_PROP_UINT32("num_queues", VirtIOSCSICommon, conf.num_queues,
>>>>>>> 1),
>>>>>>> + DEFINE_PROP_UINT32("virtqueue_size", VirtIOSCSICommon,
>>>>>>> conf.virtqueue_size,
>>>>>>> + 128),
>>>>>>> DEFINE_PROP_UINT32("max_sectors", VirtIOSCSICommon,
>>>>>>> conf.max_sectors,
>>>>>>> 0xFFFF),
>>>>>>> DEFINE_PROP_UINT32("cmd_per_lun", VirtIOSCSICommon,
>>>>>>> conf.cmd_per_lun, 128),
>>>>
>>>>> Wow, super quick, thank you! Seeing conversations today, is this queued for
>>>>> -rc4, or 2.12 and backport to qemu-stable?
>>>>
>>>> If people can come to a consensus on whether this is -rc4 material
>>>> by Tuesday 12:00 GMT that would be helpful.
>>>
>>> I'd vote for -rc4, since it's a new guest crash since 2.10.
>>
>> I think so too.
>
> Thanks; spoke also with Paolo on irc, and have pushed this to master
> for -rc4.
Cool! I just pulled master/rc4 and tested this scenario, and it works
great. Thanks everyone!
- Eric
next prev parent reply other threads:[~2017-12-05 18:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 15:15 [Qemu-devel] [PATCH for 2.11 0/1] Fix guest boot with vhost-scsi Eric Farman
2017-12-01 15:15 ` [Qemu-devel] [PATCH 1/1] vhost-scsi: add missing virtqueue_size parameter Eric Farman
2017-12-01 15:16 ` Paolo Bonzini
2017-12-04 17:52 ` Eric Farman
2017-12-04 18:05 ` Peter Maydell
2017-12-04 20:00 ` Eric Farman
2017-12-05 0:59 ` Michael S. Tsirkin
2017-12-05 12:40 ` Peter Maydell
2017-12-05 18:10 ` Eric Farman [this message]
2017-12-02 11:35 ` 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=cac73ff5-1374-7ee6-34f8-6ea015b5722f@linux.vnet.ibm.com \
--to=farman@linux.vnet.ibm.com \
--cc=dariuszx.stojaczyk@intel.com \
--cc=felipe@nutanix.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
/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).