在 2022/3/10 下午4:20, Xuan Zhuo 写道:
On Wed, 9 Mar 2022 16:54:10 +0800, Jason Wang wrote:
在 2022/3/8 下午8:35, Xuan Zhuo 写道:
This patch implements virtio pci support for QUEUE RESET.
Performing reset on a queue is divided into these steps:
1. virtio_reset_vq() - notify the device
在 2022/3/9 下午5:32, Xuan Zhuo 写道:
On Wed, 9 Mar 2022 16:54:10 +0800, Jason Wang wrote:
在 2022/3/8 下午8:35, Xuan Zhuo 写道:
This patch implements virtio pci support for QUEUE RESET.
Performing reset on a queue is divided into these steps:
1. virtio_reset_vq() - notify the device
在 2022/3/10 下午12:46, Xuan Zhuo 写道:
On Wed, 9 Mar 2022 15:55:44 +0800, Jason Wang wrote:
在 2022/3/8 下午8:35, Xuan Zhuo 写道:
virtio ring supports reset.
Queue reset is divided into several stages.
1. notify device queue reset
2. vring release
3. attach new vring
4. notify device queue re-enable
Hi Jiyong,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on 3bf7edc84a9eb4007dd9a0cb8878a7e1d5ec6a3b]
url:
https://github.com/0day-ci/linux/commits/Jiyong-Park/vsock-cycle-only-on-its-own-socket/20220310-205638
base: 3bf7edc84a9eb4007dd9a0cb8878a7e1d5ec6a3b
Hi
Am 09.03.22 um 23:25 schrieb Dmitry Osipenko:
The reason for this work is to keep GEM shmem pages mapped and allocated
even while the BO is neither mapped nor pinned. As it is now, GEM SHMEM
creates and releases pages on each pin and unpin, and maps and unmaps
memory ranges on each vmap and
On Thu, Mar 10, 2022 at 03:14:20PM +0100, Stefano Garzarella wrote:
> On Thu, Mar 10, 2022 at 10:50:11PM +0900, Jiyong Park wrote:
> > When iterating over sockets using vsock_for_each_connected_socket, make
> > sure that a transport filters out sockets that don't belong to the
> > transport.
> >
>
On Thu, 10 Mar 2022 18:12:21 +0300, Dan Carpenter
wrote:
> Hello Xuan Zhuo,
>
> The patch 26ae35c46f93: "virtio_net: support rx/tx queue reset" from
> Mar 8, 2022, leads to the following Smatch static checker warning:
Yes, thanks to you, I also found this problem today.
>
> drivers/net
Hello Xuan Zhuo,
The patch 26ae35c46f93: "virtio_net: support rx/tx queue reset" from
Mar 8, 2022, leads to the following Smatch static checker warning:
drivers/net/virtio_net.c:1410 virtnet_napi_tx_disable()
warn: sleeping in atomic context
drivers/net/virtio_net.c
1829
On Thu, Mar 10, 2022 at 10:50:11PM +0900, Jiyong Park wrote:
When iterating over sockets using vsock_for_each_connected_socket, make
sure that a transport filters out sockets that don't belong to the
transport.
There actually was an issue caused by this; in a nested VM
configuration, destroying
On Thu, 10 Mar 2022 08:04:27 -0500, "Michael S. Tsirkin"
wrote:
> On Thu, Mar 10, 2022 at 08:33:30PM +0800, Xuan Zhuo wrote:
> > On Thu, 10 Mar 2022 07:17:09 -0500, "Michael S. Tsirkin"
> > wrote:
> > > On Thu, Mar 10, 2022 at 04:14:16PM +0800, Xuan Zhuo wrote:
> > > > On Thu, 10 Mar 2022 03:07
On Thu, Mar 10, 2022 at 10:28:29PM +0900, Jiyong Park wrote:
When iterating over sockets using vsock_for_each_connected_socket, make
sure that a transport filters out sockets that don't belong to the
transport.
There actually was an issue caused by this; in a nested VM
configuration, destroying
On Thu, Mar 10, 2022 at 08:01:53AM -0500, Michael S. Tsirkin wrote:
On Thu, Mar 10, 2022 at 09:54:24PM +0900, Jiyong Park wrote:
When iterating over sockets using vsock_for_each_connected_socket, make
sure that a transport filters out sockets that don't belong to the
transport.
There actually w
On Thu, Mar 10, 2022 at 10:11:32PM +0900, Jiyong Park wrote:
> Hi Michael,
>
> Thanks for looking into this.
>
> Would you mind if I ask what you mean by incomplete? Is it because non-updated
> modules will still have the issue? Please elaborate.
What stefano wrote:
I think there is the
On Thu, Mar 10, 2022 at 09:54:25PM +0900, Jiyong Park wrote:
> vsock_for_each_connected_socket now cycles over sockets of a specific
> transport only, rather than asking callers to do the filtering manually,
> which is error-prone.
>
> Signed-off-by: Jiyong Park
Pls just squash these two patches
On Thu, Mar 10, 2022 at 08:33:30PM +0800, Xuan Zhuo wrote:
> On Thu, 10 Mar 2022 07:17:09 -0500, "Michael S. Tsirkin"
> wrote:
> > On Thu, Mar 10, 2022 at 04:14:16PM +0800, Xuan Zhuo wrote:
> > > On Thu, 10 Mar 2022 03:07:22 -0500, "Michael S. Tsirkin"
> > > wrote:
> > > > On Thu, Mar 10, 2022
On Thu, Mar 10, 2022 at 09:54:24PM +0900, Jiyong Park wrote:
> When iterating over sockets using vsock_for_each_connected_socket, make
> sure that a transport filters out sockets that don't belong to the
> transport.
>
> There actually was an issue caused by this; in a nested VM
> configuration, d
On Thu, Mar 10, 2022 at 07:57:58AM -0500, Michael S. Tsirkin wrote:
> On Thu, Mar 10, 2022 at 09:54:23PM +0900, Jiyong Park wrote:
> > Hi Stefano,
> >
> > As suggested [1], I've made two patches for easier backporting without
> > breaking KMI.
> >
> > PATCH 1 fixes the very issue of cycling all v
On Thu, Mar 10, 2022 at 09:54:23PM +0900, Jiyong Park wrote:
> Hi Stefano,
>
> As suggested [1], I've made two patches for easier backporting without
> breaking KMI.
>
> PATCH 1 fixes the very issue of cycling all vsocks regardless of the
> transport and shall be backported.
>
> PATCH 2 is a ref
On Thu, Mar 10, 2022 at 07:53:25AM -0500, Michael S. Tsirkin wrote:
> This message had
> In-Reply-To: <20220310124936.4179591-1-jiy...@google.com>
> in its header but 20220310124936.4179591-2-jiy...@google.com was
> not sent to the list.
> Please don't do that. Instead, please write and send a pro
This message had
In-Reply-To: <20220310124936.4179591-1-jiy...@google.com>
in its header but 20220310124936.4179591-2-jiy...@google.com was
not sent to the list.
Please don't do that. Instead, please write and send a proper
cover letter. Thanks!
On Thu, Mar 10, 2022 at 09:49:35PM +0900, Jiyong P
On Thu, 10 Mar 2022 07:17:09 -0500, "Michael S. Tsirkin"
wrote:
> On Thu, Mar 10, 2022 at 04:14:16PM +0800, Xuan Zhuo wrote:
> > On Thu, 10 Mar 2022 03:07:22 -0500, "Michael S. Tsirkin"
> > wrote:
> > > On Thu, Mar 10, 2022 at 03:17:03PM +0800, Xuan Zhuo wrote:
> > > > On Thu, 10 Mar 2022 02:00
On Thu, Mar 10, 2022 at 04:14:16PM +0800, Xuan Zhuo wrote:
> On Thu, 10 Mar 2022 03:07:22 -0500, "Michael S. Tsirkin"
> wrote:
> > On Thu, Mar 10, 2022 at 03:17:03PM +0800, Xuan Zhuo wrote:
> > > On Thu, 10 Mar 2022 02:00:39 -0500, "Michael S. Tsirkin"
> > > wrote:
> > > > On Tue, Mar 08, 2022
On Thu, Mar 10, 2022 at 07:41:54PM +0900, Jiyong Park wrote:
Hi Stefano,
On Thu, Mar 10, 2022 at 5:59 PM Stefano Garzarella wrote:
Hi Jiyong,
On Thu, Mar 10, 2022 at 05:18:54PM +0900, Jiyong Park wrote:
>Filtering non-h2g connections out when determining orphaned connections.
>Otherwise, in
On Wed, Mar 09, 2022 at 10:24:56AM -0800, Vishnu Dasa wrote:
> notification_bitmap may not be released when VMCI_CAPS_DMA_DATAGRAM
> capability is missing from the device. Add missing
> 'err_free_notification_bitmap' label and use it instead of
> 'err_free_data_buffers' to avoid this.
>
> free_ir
Hi Jiyong,
On Thu, Mar 10, 2022 at 05:18:54PM +0900, Jiyong Park wrote:
Filtering non-h2g connections out when determining orphaned connections.
Otherwise, in a nested VM configuration, destroying the nested VM (which
often involves the closing of /dev/vhost-vsock if there was h2g
connections to
On Wed, 9 Mar 2022 16:54:10 +0800, Jason Wang wrote:
>
> 在 2022/3/8 下午8:35, Xuan Zhuo 写道:
> > This patch implements virtio pci support for QUEUE RESET.
> >
> > Performing reset on a queue is divided into these steps:
> >
> > 1. virtio_reset_vq() - notify the device to reset the queu
On Thu, 10 Mar 2022 03:07:22 -0500, "Michael S. Tsirkin"
wrote:
> On Thu, Mar 10, 2022 at 03:17:03PM +0800, Xuan Zhuo wrote:
> > On Thu, 10 Mar 2022 02:00:39 -0500, "Michael S. Tsirkin"
> > wrote:
> > > On Tue, Mar 08, 2022 at 08:35:01PM +0800, Xuan Zhuo wrote:
> > > > virtio ring supports rese
On Thu, Mar 10, 2022 at 03:17:03PM +0800, Xuan Zhuo wrote:
> On Thu, 10 Mar 2022 02:00:39 -0500, "Michael S. Tsirkin"
> wrote:
> > On Tue, Mar 08, 2022 at 08:35:01PM +0800, Xuan Zhuo wrote:
> > > virtio ring supports reset.
> > >
> > > Queue reset is divided into several stages.
> > >
> > > 1. no
28 matches
Mail list logo