[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <8eaba95f-5d3f-f225-31bf-65e6425330be@de.ibm.com>
Date: Mon, 7 Jan 2019 14:40:23 +0100
From: Christian Borntraeger <borntraeger@...ibm.com>
To: Wei Wang <wei.w.wang@...el.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 0/3] virtio-balloon: tweak config_changed
Can you please cc stable? Right now 4.20 does not work under KVM.
On 07.01.2019 08:01, Wei Wang wrote:
> Since virtio-ccw doesn't work with accessing to the config space
> inside an interrupt context, this patch series avoids that issue by
> moving the config register accesses to the related workqueue contexts.
>
> v2->v3 ChangeLog:
> - rename cmd_id_received to cmd_id_received_cache, and have call sites
> read the latest value via virtio_balloon_cmd_id_received. (Still
> kept Cornelia and Halil's reviewed-by as it's a minor change)
> - remove zeroing vb->num_free_page_blocks in probe since vb is
> allocated via kzalloc.
> v1->v2 ChangeLog:
> - add config_read_bitmap to indicate to the workqueue callbacks about
> the necessity of reading the related config fields.
>
> Wei Wang (3):
> virtio-balloon: tweak config_changed implementation
> virtio-balloon: improve update_balloon_size_func
> virtio_balloon: remove the unnecessary 0-initialization
>
> drivers/virtio/virtio_balloon.c | 104 ++++++++++++++++++++++++++--------------
> 1 file changed, 69 insertions(+), 35 deletions(-)
>
Powered by blists - more mailing lists