[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5C35CE55.6030200@intel.com>
Date: Wed, 09 Jan 2019 18:35:01 +0800
From: Wei Wang <wei.w.wang@...el.com>
To: Christian Borntraeger <borntraeger@...ibm.com>,
virtio-dev@...ts.oasis-open.org, linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org, kvm@...r.kernel.org,
mst@...hat.com, cohuck@...hat.com
CC: pbonzini@...hat.com, dgilbert@...hat.com, pasic@...ux.ibm.com
Subject: Re: [PATCH v3 1/3] virtio-balloon: tweak config_changed implementation
On 01/08/2019 04:46 PM, Christian Borntraeger wrote:
>
> On 08.01.2019 06:35, Wei Wang wrote:
>> On 01/07/2019 09:49 PM, Christian Borntraeger wrote:
>>> On 07.01.2019 08:01, Wei Wang wrote:
>>>> virtio-ccw has deadlock issues with reading the config space inside the
>>>> interrupt context, so we tweak the virtballoon_changed implementation
>>>> by moving the config read operations into the related workqueue contexts.
>>>> The config_read_bitmap is used as a flag to the workqueue callbacks
>>>> about the related config fields that need to be read.
>>>>
>>>> The cmd_id_received is also renamed to cmd_id_received_cache, and
>>>> the value should be obtained via virtio_balloon_cmd_id_received.
>>>>
>>>> Reported-by: Christian Borntraeger <borntraeger@...ibm.com>
>>>> Signed-off-by: Wei Wang <wei.w.wang@...el.com>
>>>> Reviewed-by: Cornelia Huck <cohuck@...hat.com>
>>>> Reviewed-by: Halil Pasic <pasic@...ux.ibm.com>
>>> Together with
>>> virtio_pci: use queue idx instead of array idx to set up the vq
>>> virtio: don't allocate vqs when names[i] = NULL
>>>
>>> Tested-by: Christian Borntraeger <borntraeger@...ibm.com>
>> OK. I don't plan to send a new version of the above patches as no changes needed so far.
>>
>> Michael, if the above two patches look good to you, please help add the related tested-by
>> and reviewed-by tags. Thanks.
> Can we also make sure that
>
> virtio_pci: use queue idx instead of array idx to set up the vq
> virtio: don't allocate vqs when names[i] = NULL
>
> also land in stable?
>
You could also send the request to stable after it gets merged to Linus'
tree.
The stable review committee will decide whether to take it.
Please see Option 2:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
Best,
Wei
Powered by blists - more mailing lists