Which tree for paravirt related patches?

A recent patch modifying the core paravirt-ops functionality is highlighting some missing MAINTAINERS information for PARAVIRT_OPS: there is no information which tree is to be used for taking those patches per default. In the past this was mostly handled by the tip tree, and I think this is fine.

Re: [RFC PATCH v5 21/26] vhost: Add vhost_svq_valid_guest_features to shadow vq

On Wed, Nov 3, 2021 at 3:44 PM Eugenio Perez Martin wrote: > > On Wed, Nov 3, 2021 at 4:18 AM Jason Wang wrote: > > > > On Tue, Nov 2, 2021 at 4:10 PM Eugenio Perez Martin > > wrote: > > > > > > On Tue, Nov 2, 2021 at 6:26 AM Jason Wang wrote: > > > > > > > > On Sat, Oct 30, 2021 at 2:44 AM Eu

Re: [RFC PATCH v5 11/26] vhost: Handle host notifiers in SVQ

On Wed, Nov 3, 2021 at 3:40 PM Eugenio Perez Martin wrote: > > On Wed, Nov 3, 2021 at 3:56 AM Jason Wang wrote: > > > > On Tue, Nov 2, 2021 at 4:47 PM Eugenio Perez Martin > > wrote: > > > > > > On Tue, Nov 2, 2021 at 8:55 AM Jason Wang wrote: > > > > > > > > > > > > 在 2021/10/30 上午2:35, Eugen

Re: [GIT PULL] vhost,virtio,vhost: fixes,features

The pull request you sent on Wed, 3 Nov 2021 16:43:32 -0400: > https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/43e1b12927276cde8052122a24ff796649f09d60 Thank you! -- Deet-doot-dot, I am a bo

[GIT PULL] vhost,virtio,vhost: fixes,features

The following changes since commit 8bb7eca972ad531c9b149c0a51ab43a417385813: Linux 5.15 (2021-10-31 13:53:10 -0700) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus for you to fetch changes up to 540061ac79f0302ae91e44e6cd2

Re: [PATCH v2 05/12] x86/sev: Use GHCB protocol version 2 if supported

On Mon, Sep 13, 2021 at 05:55:56PM +0200, Joerg Roedel wrote: > From: Joerg Roedel > > Check whether the hypervisor supports GHCB version 2 and use it if > available. > > Signed-off-by: Joerg Roedel > --- > arch/x86/boot/compressed/sev.c | 10 -- > arch/x86/include/asm/sev.h | 4 +

Re: [PATCH 1/2] i2c: virtio: disable timeout handling

On Wed, Nov 03, 2021 at 07:37:45AM +0100, Viresh Kumar wrote: > On 03-11-21, 06:18, Chen, Conghui wrote: > > >>> Over the long term, I think the backend should provide that timeout > > >>> value and guarantee that its processing time should not exceed that > > >>> value. > > >> If you mean that the

Re: [PATCH v2 03/12] x86/sev: Save and print negotiated GHCB protocol version

On Mon, Sep 13, 2021 at 05:55:54PM +0200, Joerg Roedel wrote: > From: Joerg Roedel > > Save the results of the GHCB protocol negotiation into a data structure > and print information about versions supported and used to the kernel > log. Which is useful for? > +/* > + * struct sev_ghcb_protocol

Re: [RESEND PATCH 0/5] Cleanups for the nomodeset kernel command line parameter logic

Hi Am 03.11.21 um 13:28 schrieb Javier Martinez Canillas: [ resend with all relevant people as Cc now, sorry to others for the spam ] There is a lot of historical baggage on this parameter. It's defined in the vgacon driver as a "nomodeset" parameter, but it's handler function is called text_mo

Re: [RESEND PATCH 3/5] drm: Rename vgacon_text_force() function to drm_modeset_disabled()

Hi Am 03.11.21 um 13:28 schrieb Javier Martinez Canillas: This function is used by some DRM drivers to determine if the "nomodeset" kernel command line parameter was set and prevent these drivers to probe. But the function name is quite confusing and does not reflect what really the drivers are

Re: [RESEND PATCH 2/5] drm: Move nomodeset kernel parameter handler to the DRM subsystem

On Wed, 03 Nov 2021, Javier Martinez Canillas wrote: > The "nomodeset" kernel cmdline parameter is handled by the vgacon driver > but the exported vgacon_text_force() symbol is only used by DRM drivers. > > It makes much more sense for the parameter logic to be in the subsystem > of the drivers th

Re: [RESEND PATCH 2/5] drm: Move nomodeset kernel parameter handler to the DRM subsystem

Hi Am 03.11.21 um 13:28 schrieb Javier Martinez Canillas: The "nomodeset" kernel cmdline parameter is handled by the vgacon driver but the exported vgacon_text_force() symbol is only used by DRM drivers. It makes much more sense for the parameter logic to be in the subsystem of the drivers that

[PATCH 2/2] drm/virtio: introduce lazy pinning

From: mwezdeck Userspace can opt-in to not pin pages during resource create ioctl. In transfer_*_host and map ioctls check if memory is pinned. If pages are not pinned, pin it. Otherwise, do nothing. This change is transparent to userspace. --- drivers/gpu/drm/virtio/virtgpu_ioctl.c | 9

[PATCH 1/2] drm/virtio: introduce ioctl for pinning pages

From: mwezdeck Pinning pages happens in virtio_gpu_object_shmem_init() function. This ioctl allows to pin pages if it was not done earlier. Signed-off-by: mwezdeck --- drivers/gpu/drm/virtio/virtgpu_drv.h| 5 +++- drivers/gpu/drm/virtio/virtgpu_ioctl.c | 11 drivers/gpu/drm/vir

[PATCH] drm/virtio: new ioctl for pinning and lazy pinning

First patch implements new ioctl. If there are no pages pinned to bo object, then pin it. Second patch implements concepts of lazy pin. Userspace must opt-in for not pinning pages. I would like to record this work here and investigate another possibility. Mainly, problem statement for this two

[PATCH 3/4] drm/etnaviv: use dma_resv_describe

Instead of dumping the fence info manually. Signed-off-by: Christian König Reviewed-by: Rob Clark --- drivers/gpu/drm/etnaviv/etnaviv_gem.c | 26 +++--- 1 file changed, 7 insertions(+), 19 deletions(-) diff --git a/drivers/gpu/drm/etnaviv/etnaviv_gem.c b/drivers/gpu/drm/et

[PATCH 1/4] dma-buf: add dma_fence_describe and dma_resv_describe v2

Add functions to dump dma_fence and dma_resv objects into a seq_file and use them for printing the debugfs information. v2: fix missing include reported by test robot. Signed-off-by: Christian König Reviewed-by: Rob Clark --- drivers/dma-buf/dma-buf.c | 11 +-- drivers/dma-buf/dma-fe

DMA-buf debugfs cleanups

Hi guys, second round for those four patches adding some simple yet useful DMA-buf helper functions for debugfs prints. Fixed some missing includes and typos in commit messages. Please review and/or comment, Christian. ___ Virtualization mailing lis

[PATCH 2/4] drm/msm: use the new dma_resv_describe

Instead of hand rolling pretty much the same code. Signed-off-by: Christian König Reviewed-by: Rob Clark --- drivers/gpu/drm/msm/msm_gem.c | 20 +--- 1 file changed, 1 insertion(+), 19 deletions(-) diff --git a/drivers/gpu/drm/msm/msm_gem.c b/drivers/gpu/drm/msm/msm_gem.c index

[PATCH 4/4] drm/qxl: use iterator instead of dma_resv_shared_list

I'm not sure why it is useful to know the number of fences in the reservation object, but we try to avoid exposing the dma_resv_shared_list() function. So use the iterator instead. If more information is desired we could use dma_resv_describe() as well. Signed-off-by: Christian König --- driver

Re: [PATCH V9 7/9] vhost: introduce vDPA-based backend

On Tue, Nov 2, 2021 at 11:56 PM Jason Gunthorpe wrote: > > On Tue, Nov 02, 2021 at 11:52:20AM +0800, Jason Wang wrote: > > On Mon, Nov 1, 2021 at 10:11 PM Jason Gunthorpe wrote: > > > > > > On Thu, Mar 26, 2020 at 10:01:23PM +0800, Jason Wang wrote: > > > > From: Tiwei Bie > > > > > > > > This p

Re: [PATCH] drm/virtio: delay pinning the pages till first use

On Tue, Nov 02, 2021 at 08:58:55AM -0700, Chia-I Wu wrote: > On Tue, Nov 2, 2021 at 6:07 AM Gerd Hoffmann wrote: > > > > On Tue, Nov 02, 2021 at 12:31:39PM +0100, Maksym Wezdecki wrote: > > > From: mwezdeck > > > > > > The idea behind the commit: > > > 1. not pin the pages during resource_creat