From: Wei Wang <wei.w.wang@intel.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
virtio-dev@lists.oasis-open.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
mst@redhat.com, cohuck@redhat.com
Cc: pbonzini@redhat.com, dgilbert@redhat.com,
Halil Pasic <pasic@linux.ibm.com>
Subject: Re: [PATCH v1 0/2] Virtio: fix some vq allocation issues
Date: Thu, 03 Jan 2019 14:18:22 +0800 [thread overview]
Message-ID: <5C2DA92E.9090503@intel.com> (raw)
In-Reply-To: <c6746307-fae5-7652-af8d-19f560fc31d9@de.ibm.com>
On 12/28/2018 03:57 PM, Christian Borntraeger wrote:
>
> On 28.12.2018 03:26, Wei Wang wrote:
>> Some vqs don't need to be allocated when the related feature bits are
>> disabled. Callers notice the vq allocation layer by setting the related
>> names[i] to be NULL.
>>
>> This patch series fixes the find_vqs implementations to handle this case.
> So the random crashes during boot are gone.
> What still does not work is actually using the balloon.
>
> So in the qemu monitor using lets say "balloon 1000" will hang the guest.
> Seems to be a deadlock in the virtio-ccw code. We seem to call the
> config code in the interrupt handler.
Please try with applying both this series and the "virtio-balloon: tweak
config_changed"
series that I just sent.
This series fixes the ccw booting issue and that series tries to fix the
ccw deadlock issue.
Best,
Wei
prev parent reply other threads:[~2019-01-03 6:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-28 2:26 [PATCH v1 0/2] Virtio: fix some vq allocation issues Wei Wang
2018-12-28 2:26 ` [PATCH v1 1/2] virtio_pci: use queue idx instead of array idx to set up the vq Wei Wang
2019-01-03 9:57 ` Cornelia Huck
2019-01-09 16:29 ` Christian Borntraeger
2018-12-28 2:26 ` [PATCH v1 2/2] virtio: don't allocate vqs when names[i] = NULL Wei Wang
2019-01-03 9:59 ` Cornelia Huck
2019-01-09 16:30 ` Christian Borntraeger
2018-12-28 7:57 ` [PATCH v1 0/2] Virtio: fix some vq allocation issues Christian Borntraeger
2018-12-29 2:45 ` Wang, Wei W
2018-12-30 6:06 ` Halil Pasic
2018-12-31 6:03 ` Wang, Wei W
2018-12-31 23:40 ` Halil Pasic
2019-01-02 9:53 ` Cornelia Huck
2019-01-02 13:23 ` Cornelia Huck
2019-01-02 15:59 ` Halil Pasic
2019-01-02 18:02 ` Cornelia Huck
2019-01-02 19:13 ` Halil Pasic
2019-01-02 13:56 ` Halil Pasic
2019-01-03 6:18 ` Wei Wang [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=5C2DA92E.9090503@intel.com \
--to=wei.w.wang@intel.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=dgilbert@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.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