Re: PING: [PATCH v4 0/5] virtio-crypto: Improve performance

2022-05-04 Thread Michael S. Tsirkin
On Thu, May 05, 2022 at 03:14:40AM +, Gonglei (Arei) wrote: > > > > -Original Message- > > From: zhenwei pi [mailto:pizhen...@bytedance.com] > > Sent: Thursday, May 5, 2022 10:35 AM > > To: Gonglei (Arei) ; m...@redhat.com; > > jasow...@redhat.com > > Cc: herb...@gondor.apana.org.au;

RE: PING: [PATCH v4 0/5] virtio-crypto: Improve performance

2022-05-04 Thread Gonglei (Arei) via Virtualization
> -Original Message- > From: zhenwei pi [mailto:pizhen...@bytedance.com] > Sent: Thursday, May 5, 2022 10:35 AM > To: Gonglei (Arei) ; m...@redhat.com; > jasow...@redhat.com > Cc: herb...@gondor.apana.org.au; linux-ker...@vger.kernel.org; > virtualization@lists.linux-foundation.org;

PING: [PATCH v4 0/5] virtio-crypto: Improve performance

2022-05-04 Thread zhenwei pi
Hi, Lei Jason replied in another patch: Still hundreds of lines of changes, I'd leave this change to other maintainers to decide. Quite frankly, the virtio crypto driver changed only a few in the past, and the performance of control queue is not good enough. I am in doubt about that this

Re: [PATCH net-next 2/2] net: move snowflake callers to netif_napi_add_tx_weight()

2022-05-04 Thread Xuan Zhuo
On Wed, 4 May 2022 09:37:25 -0700, Jakub Kicinski wrote: > Make the drivers with custom tx napi weight call netif_napi_add_tx_weight(). > > Signed-off-by: Jakub Kicinski > --- > CC: claudiu.man...@nxp.com > CC: bryan.whiteh...@microchip.com > CC: unglinuxdri...@microchip.com > CC:

[PATCH 5.17 054/225] virtio_net: fix wrong buf address calculation when using xdp

2022-05-04 Thread Greg Kroah-Hartman
From: Nikolay Aleksandrov commit acb16b395c3f3d7502443e0c799c2b42df645642 upstream. We received a report[1] of kernel crashes when Cilium is used in XDP mode with virtio_net after updating to newer kernels. After investigating the reason it turned out that when using mergeable bufs with an XDP

[PATCH 5.15 044/177] virtio_net: fix wrong buf address calculation when using xdp

2022-05-04 Thread Greg Kroah-Hartman
From: Nikolay Aleksandrov commit acb16b395c3f3d7502443e0c799c2b42df645642 upstream. We received a report[1] of kernel crashes when Cilium is used in XDP mode with virtio_net after updating to newer kernels. After investigating the reason it turned out that when using mergeable bufs with an XDP

[PATCH v3 0/2] kernel: add new infrastructure for platform_has() support

2022-05-04 Thread Juergen Gross via Virtualization
In another patch series [1] the need has come up to have support for a generic feature flag infrastructure. This patch series is introducing that infrastructure and adds the first use case. I have decided to use a similar interface as the already known x86 cpu_has() function. As the new

[PATCH v3 1/2] kernel: add platform_has() infrastructure

2022-05-04 Thread Juergen Gross via Virtualization
Add a simple infrastructure for setting, resetting and querying platform feature flags. Flags can be either global or architecture specific. Signed-off-by: Juergen Gross --- V2: - rename set/reset functions to platform_[set|clear]() (Boris Petkov, Heiko Carstens) - move function

[PATCH v3 2/2] virtio: replace arch_has_restricted_virtio_memory_access()

2022-05-04 Thread Juergen Gross via Virtualization
Instead of using arch_has_restricted_virtio_memory_access() together with CONFIG_ARCH_HAS_RESTRICTED_VIRTIO_MEMORY_ACCESS, replace those with platform_has() and a new platform feature PLATFORM_VIRTIO_RESTRICTED_MEM_ACCESS. Signed-off-by: Juergen Gross --- V2: - move setting of

Re: [PATCH v2] arm64: paravirt: Use RCU read locks to guard stolen_time

2022-05-04 Thread Will Deacon
On Wed, May 04, 2022 at 03:38:47PM +0200, Juergen Gross wrote: > On 04.05.22 11:45, Will Deacon wrote: > > On Thu, Apr 28, 2022 at 11:35:36AM -0700, Elliot Berman wrote: > > > diff --git a/arch/arm64/kernel/paravirt.c b/arch/arm64/kernel/paravirt.c > > > index 75fed4460407..e724ea3d86f0 100644 > >

Re: [PATCH v2] arm64: paravirt: Use RCU read locks to guard stolen_time

2022-05-04 Thread Juergen Gross via Virtualization
On 28.04.22 20:35, Elliot Berman wrote: From: Prakruthi Deepak Heragu During hotplug, the stolen time data structure is unmapped and memset. There is a possibility of the timer IRQ being triggered before memset and stolen time is getting updated as part of this timer IRQ handler. This causes

Re: [PATCH v2] arm64: paravirt: Use RCU read locks to guard stolen_time

2022-05-04 Thread Juergen Gross via Virtualization
On 04.05.22 11:45, Will Deacon wrote: On Thu, Apr 28, 2022 at 11:35:36AM -0700, Elliot Berman wrote: From: Prakruthi Deepak Heragu During hotplug, the stolen time data structure is unmapped and memset. There is a possibility of the timer IRQ being triggered before memset and stolen time is

Re: [PATCH v2] arm64: paravirt: Use RCU read locks to guard stolen_time

2022-05-04 Thread Will Deacon
On Thu, Apr 28, 2022 at 11:35:36AM -0700, Elliot Berman wrote: > From: Prakruthi Deepak Heragu > > During hotplug, the stolen time data structure is unmapped and memset. > There is a possibility of the timer IRQ being triggered before memset > and stolen time is getting updated as part of this

Re: [PATCH 4/4] drm/qxl: add drm_gem_plane_helper_prepare_fb

2022-05-04 Thread Daniel Vetter
On Fri, Apr 29, 2022 at 03:42:30PM +0200, Christian König wrote: > We could need to wait for the pin to complete here. > > Signed-off-by: Christian König > Cc: Dave Airlie > Cc: Gerd Hoffmann > Cc: virtualization@lists.linux-foundation.org > Cc: spice-de...@lists.freedesktop.org Reviewed-by:

Re: [PATCH v4 11/15] drm/shmem-helper: Add generic memory shrinker

2022-05-04 Thread Daniel Vetter
On Thu, Apr 28, 2022 at 09:20:15PM +0300, Dmitry Osipenko wrote: > 27.04.2022 18:03, Daniel Vetter wrote: > >> ... > @@ -172,6 +172,41 @@ struct drm_gem_object_funcs { >    * This is optional but necessary for mmap support. >    */ >   const struct

Re: [PATCH v4 10/15] drm/shmem-helper: Take reservation lock instead of drm_gem_shmem locks

2022-05-04 Thread Daniel Vetter
On Thu, Apr 28, 2022 at 09:31:00PM +0300, Dmitry Osipenko wrote: > Hello Daniel, > > 27.04.2022 17:50, Daniel Vetter пишет: > > On Mon, Apr 18, 2022 at 10:18:54PM +0300, Dmitry Osipenko wrote: > >> Hello, > >> > >> On 4/18/22 21:38, Thomas Zimmermann wrote: > >>> Hi > >>> > >>> Am 18.04.22 um