[RFC] hypercall-vsock: add a new vsock transport

Hi, We plan to add a new vsock transport based on hypercall (e.g. vmcall on Intel CPUs). It transports AF_VSOCK packets between the guest and host, which is similar to virtio-vsock, vmci-vsock and hyperv-vsock. Compared to the above listed vsock transports which are designed for high

Re: [PATCH 2/2] MAINTAINERS: Mark VMware mailing list entries as private

On Tue, 2021-11-09 at 00:58 +, Nadav Amit wrote: > > On Nov 8, 2021, at 4:37 PM, Joe Perches wrote: > > On Mon, 2021-11-08 at 16:22 -0800, Srivatsa S. Bhat wrote: > > > > So it's an exploder not an actual maintainer and it likely isn't > > publically archived with any normal list mechanism.

Re: [PATCH v2 7/9] drm/simpledrm: Enable FB_DAMAGE_CLIPS property

Den 09.11.2021 15.56, skrev Thomas Zimmermann: > Hi, > > thanks for looking through all this code. > > Am 09.11.21 um 14:04 schrieb Noralf Trønnes: >> >> >> Den 09.11.2021 13.38, skrev Thomas Zimmermann: >>> >>> >>> Am 08.11.21 um 21:55 schrieb Noralf Trønnes: Den 01.11.2021

Re: [PATCH v4 0/3] virtio support cache indirect desc

On Tue, 9 Nov 2021 08:03:18 -0500, Michael S. Tsirkin wrote: > On Mon, Nov 08, 2021 at 07:49:48PM +0800, Xuan Zhuo wrote: > > If the VIRTIO_RING_F_INDIRECT_DESC negotiation succeeds, and the number > > of sgs used for sending packets is greater than 1. We must constantly > > call __kmalloc/kfree

Re: [PATCH v4 1/3] virtio: cache indirect desc for split

On Tue, 9 Nov 2021 08:09:42 -0500, Michael S. Tsirkin wrote: > On Mon, Nov 08, 2021 at 07:49:49PM +0800, Xuan Zhuo wrote: > > In the case of using indirect, indirect desc must be allocated and > > released each time, which increases a lot of cpu overhead. > > > > Here, a cache is added for

Re: [PATCH v2 7/9] drm/simpledrm: Enable FB_DAMAGE_CLIPS property

Hi, thanks for looking through all this code. Am 09.11.21 um 14:04 schrieb Noralf Trønnes: Den 09.11.2021 13.38, skrev Thomas Zimmermann: Am 08.11.21 um 21:55 schrieb Noralf Trønnes: Den 01.11.2021 15.15, skrev Thomas Zimmermann: Enable the FB_DAMAGE_CLIPS property to reduce

Re: [PATCH] vdpa: add driver_override support

On Tue, Nov 09, 2021 at 08:10:58AM -0500, Michael S. Tsirkin wrote: On Mon, Nov 08, 2021 at 06:05:29PM +0100, Stefano Garzarella wrote: On Fri, Nov 5, 2021 at 4:01 AM Jason Wang wrote: > > On Fri, Nov 5, 2021 at 12:17 AM Stefano Garzarella wrote: > > > > `driver_override` allows to control

Re: [PATCH] vdpa: add driver_override support

On Mon, Nov 08, 2021 at 06:05:29PM +0100, Stefano Garzarella wrote: > On Fri, Nov 5, 2021 at 4:01 AM Jason Wang wrote: > > > > On Fri, Nov 5, 2021 at 12:17 AM Stefano Garzarella > > wrote: > > > > > > `driver_override` allows to control which of the vDPA bus drivers > > > binds to a vDPA

Re: [PATCH v4 1/3] virtio: cache indirect desc for split

On Mon, Nov 08, 2021 at 07:49:49PM +0800, Xuan Zhuo wrote: > In the case of using indirect, indirect desc must be allocated and > released each time, which increases a lot of cpu overhead. > > Here, a cache is added for indirect. If the number of indirect desc to be > applied for is less than

Re: [PATCH v2 8/9] drm/simpledrm: Support virtual screen sizes

Den 09.11.2021 10.06, skrev Thomas Zimmermann: > Hi > > Am 08.11.21 um 22:01 schrieb Noralf Trønnes: >> >> >> Den 01.11.2021 15.15, skrev Thomas Zimmermann: >>> Add constants for the maximum size of the shadow-plane surface >>> size. Useful for shadow planes with virtual screen sizes. The >>>

Re: [PATCH v2 7/9] drm/simpledrm: Enable FB_DAMAGE_CLIPS property

Den 09.11.2021 13.38, skrev Thomas Zimmermann: > > > Am 08.11.21 um 21:55 schrieb Noralf Trønnes: >> >> >> Den 01.11.2021 15.15, skrev Thomas Zimmermann: >>> Enable the FB_DAMAGE_CLIPS property to reduce display-update >>> overhead. Also fixes a warning in the kernel log. >>> >>>   

Re: [PATCH v4 0/3] virtio support cache indirect desc

On Mon, Nov 08, 2021 at 07:49:48PM +0800, Xuan Zhuo wrote: > If the VIRTIO_RING_F_INDIRECT_DESC negotiation succeeds, and the number > of sgs used for sending packets is greater than 1. We must constantly > call __kmalloc/kfree to allocate/release desc. > > In the case of extremely fast package

Re: [PATCH v2 7/9] drm/simpledrm: Enable FB_DAMAGE_CLIPS property

Am 08.11.21 um 21:55 schrieb Noralf Trønnes: Den 01.11.2021 15.15, skrev Thomas Zimmermann: Enable the FB_DAMAGE_CLIPS property to reduce display-update overhead. Also fixes a warning in the kernel log. simple-framebuffer simple-framebuffer.0: [drm] drm_plane_enable_fb_damage_clips()

Re: [PATCH 2/2] MAINTAINERS: Mark VMware mailing list entries as private

On Mon, 2021-11-08 at 12:30 -0800, Srivatsa S. Bhat wrote: > From: Srivatsa S. Bhat (VMware) > > VMware mailing lists in the MAINTAINERS file are private lists meant > for VMware-internal review/notification for patches to the respective > subsystems. So, in an earlier discussion [1][2], it was

Re: [PATCH v2 7/9] drm/simpledrm: Enable FB_DAMAGE_CLIPS property

Hi Am 08.11.21 um 19:57 schrieb Noralf Trønnes: Den 01.11.2021 15.15, skrev Thomas Zimmermann: Enable the FB_DAMAGE_CLIPS property to reduce display-update overhead. Also fixes a warning in the kernel log. simple-framebuffer simple-framebuffer.0: [drm] drm_plane_enable_fb_damage_clips()

Re: [PATCH] drivers:gpio: Remove unneeded semicolon

On 09-11-21, 08:23, cgel@gmail.com wrote: > From: chiminghao > > Fix the following coccicheck REVIEW: > ./drivers/gpio/gpio-virtio.c:437:2-3 REVIEW Unneeded semicolon > > Reported-by: Zeal Robot > Signed-off-by: chiminghao > --- > drivers/gpio/gpio-virtio.c | 2 +- > 1 file changed, 1

Re: [PATCH v2 8/9] drm/simpledrm: Support virtual screen sizes

Hi Am 08.11.21 um 22:01 schrieb Noralf Trønnes: Den 01.11.2021 15.15, skrev Thomas Zimmermann: Add constants for the maximum size of the shadow-plane surface size. Useful for shadow planes with virtual screen sizes. The current sizes are 4096 scanlines with 4096 pixels each. This seems

[PATCH 27/29] dax: fix up some of the block device related ifdefs

The DAX device <-> block device association is only enabled if CONFIG_BLOCK is enabled. Update dax.h to account for that and use the right conditions for the fs_put_dax stub as well. Signed-off-by: Christoph Hellwig --- include/linux/dax.h | 41 - 1 file

[PATCH 28/29] iomap: build the block based code conditionally

Only build the block based iomap code if CONFIG_BLOCK is set. Currently that is always the case, but it will change soon. Signed-off-by: Christoph Hellwig --- fs/Kconfig| 4 ++-- fs/iomap/Makefile | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/fs/Kconfig

[PATCH 29/29] fsdax: don't require CONFIG_BLOCK

The file system DAX code now does not require the block code. So allow building a kernel with fuse DAX but not block layer. Signed-off-by: Christoph Hellwig --- fs/Kconfig | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/Kconfig b/fs/Kconfig index

[PATCH 26/29] fsdax: shift partition offset handling into the file systems

Remove the last user of ->bdev in dax.c by requiring the file system to pass in an address that already includes the DAX offset. As part of the only set ->bdev or ->daxdev when actually required in the ->iomap_begin methods. Signed-off-by: Christoph Hellwig --- fs/dax.c | 6

[PATCH 25/29] dax: return the partition offset from fs_dax_get_by_bdev

Prepare from removing the block_device from the DAX I/O path by returning the partition offset from fs_dax_get_by_bdev so that the file systems have it at hand for use during I/O. Signed-off-by: Christoph Hellwig --- drivers/dax/super.c | 9 ++--- drivers/md/dm.c | 4 ++--

[PATCH 23/29] xfs: use IOMAP_DAX to check for DAX mappings

Use the explicit DAX flag instead of checking the inode flag in the iomap code. Signed-off-by: Christoph Hellwig --- fs/xfs/xfs_iomap.c | 7 --- fs/xfs/xfs_iomap.h | 3 ++- fs/xfs/xfs_pnfs.c | 2 +- 3 files changed, 7 insertions(+), 5 deletions(-) diff --git a/fs/xfs/xfs_iomap.c

[PATCH 24/29] xfs: use xfs_direct_write_iomap_ops for DAX zeroing

While the buffered write iomap ops do work due to the fact that zeroing never allocates blocks, the DAX zeroing should use the direct ops just like actual DAX I/O. Signed-off-by: Christoph Hellwig --- fs/xfs/xfs_iomap.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH 22/29] iomap: add a IOMAP_DAX flag

Add a flag so that the file system can easily detect DAX operations. Signed-off-by: Christoph Hellwig --- fs/dax.c | 7 --- include/linux/iomap.h | 1 + 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/fs/dax.c b/fs/dax.c index 5b52b878124ac..0bd6cdcbacfc4 100644

[PATCH 20/29] ext4: cleanup the dax handling in ext4_fill_super

Only call fs_dax_get_by_bdev once the sbi has been allocated and remove the need for the dax_dev local variable. Signed-off-by: Christoph Hellwig --- fs/ext4/super.c | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/fs/ext4/super.c b/fs/ext4/super.c index

[PATCH 21/29] xfs: move dax device handling into xfs_{alloc, free}_buftarg

Hide the DAX device lookup from the xfs_super.c code. Reviewed-by: Christoph Hellwig --- fs/xfs/xfs_buf.c | 8 fs/xfs/xfs_buf.h | 4 ++-- fs/xfs/xfs_super.c | 26 +- 3 files changed, 11 insertions(+), 27 deletions(-) diff --git a/fs/xfs/xfs_buf.c

[PATCH 19/29] ext2: cleanup the dax handling in ext2_fill_super

Only call fs_dax_get_by_bdev once the sbi has been allocated and remove the need for the dax_dev local variable. Signed-off-by: Christoph Hellwig --- fs/ext2/super.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/fs/ext2/super.c b/fs/ext2/super.c index

[PATCH 17/29] fsdax: factor out a dax_memzero helper

Factor out a helper for the "manual" zeroing of a DAX range to clean up dax_iomap_zero a lot. Signed-off-by: Christoph Hellwig --- fs/dax.c | 36 +++- 1 file changed, 19 insertions(+), 17 deletions(-) diff --git a/fs/dax.c b/fs/dax.c index

[PATCH 18/29] fsdax: decouple zeroing from the iomap buffered I/O code

Unshare the DAX and iomap buffered I/O page zeroing code. This code previously did a IS_DAX check deep inside the iomap code, which in fact was the only DAX check in the code. Instead move these checks into the callers. Most callers already have DAX special casing anyway and XFS will need it

[PATCH 14/29] fsdax: simplify the pgoff calculation

Replace the two steps of dax_iomap_sector and bdev_dax_pgoff with a single dax_iomap_pgoff helper that avoids lots of cumbersome sector conversions. Signed-off-by: Christoph Hellwig --- drivers/dax/super.c | 14 -- fs/dax.c| 35 ++-

[PATCH 15/29] xfs: add xfs_zero_range and xfs_truncate_page helpers

From: Shiyang Ruan Add helpers to prepare for using different DAX operations. Signed-off-by: Shiyang Ruan [hch: split from a larger patch + slight cleanups] Signed-off-by: Christoph Hellwig --- fs/xfs/xfs_bmap_util.c | 7 +++ fs/xfs/xfs_file.c | 3 +-- fs/xfs/xfs_iomap.c | 25

[PATCH 12/29] fsdax: remove a pointless __force cast in copy_cow_page_dax

Despite its name copy_user_page expected kernel addresses, which is what we already have. Signed-off-by: Christoph Hellwig --- fs/dax.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/dax.c b/fs/dax.c index 4e3e5a283a916..73bd1439d8089 100644 --- a/fs/dax.c +++ b/fs/dax.c

[PATCH 16/29] fsdax: simplify the offset check in dax_iomap_zero

The file relative offset must have the same alignment as the storage offset, so use that and get rid of the call to iomap_sector. Signed-off-by: Christoph Hellwig --- fs/dax.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/fs/dax.c b/fs/dax.c index

[PATCH 11/29] dm-stripe: add a stripe_dax_pgoff helper

Add a helper to perform the entire remapping for DAX accesses. This helper open codes bdev_dax_pgoff given that the alignment checks have already been done by the submitting file system and don't need to be repeated. Signed-off-by: Christoph Hellwig Acked-by: Mike Snitzer ---

[PATCH 09/29] dm-linear: add a linear_dax_pgoff helper

Add a helper to perform the entire remapping for DAX accesses. This helper open codes bdev_dax_pgoff given that the alignment checks have already been done by the submitting file system and don't need to be repeated. Signed-off-by: Christoph Hellwig Acked-by: Mike Snitzer ---

[PATCH 13/29] fsdax: use a saner calling convention for copy_cow_page_dax

Just pass the vm_fault and iomap_iter structures, and figure out the rest locally. Note that this requires moving dax_iomap_sector up in the file. Signed-off-by: Christoph Hellwig --- fs/dax.c | 29 + 1 file changed, 13 insertions(+), 16 deletions(-) diff --git

[PATCH 10/29] dm-log-writes: add a log_writes_dax_pgoff helper

Add a helper to perform the entire remapping for DAX accesses. This helper open codes bdev_dax_pgoff given that the alignment checks have already been done by the submitting file system and don't need to be repeated. Signed-off-by: Christoph Hellwig Acked-by: Mike Snitzer ---

[PATCH 07/29] xfs: factor out a xfs_setup_dax_always helper

Factor out another DAX setup helper to simplify future changes. Also move the experimental warning after the checks to not clutter the log too much if the setup failed. Signed-off-by: Christoph Hellwig --- fs/xfs/xfs_super.c | 47 +++--- 1 file changed,

[PATCH 04/29] dax: simplify the dax_device <-> gendisk association

Replace the dax_host_hash with an xarray indexed by the pointer value of the gendisk, and require explicitly calls from the block drivers that want to associate their gendisk with a dax_device. Signed-off-by: Christoph Hellwig Acked-by: Mike Snitzer --- drivers/dax/bus.c| 6 +-

[PATCH 08/29] dax: remove dax_capable

Just open code the block size and dax_dev == NULL checks in the callers. Signed-off-by: Christoph Hellwig Acked-by: Mike Snitzer --- drivers/dax/super.c | 36 drivers/md/dm-table.c| 22 +++--- drivers/md/dm.c |

[PATCH 01/29] nvdimm/pmem: move dax_attribute_group from dax to pmem

dax_attribute_group is only used by the pmem driver, and can avoid the completely pointless lookup by the disk name if moved there. This leaves just a single caller of dax_get_by_host, so move dax_get_by_host into the same ifdef block as that caller. Signed-off-by: Christoph Hellwig

[PATCH 02/29] dm: make the DAX support dependend on CONFIG_FS_DAX

The device mapper DAX support is all hanging off a block device and thus can't be used with device dax. Make it depend on CONFIG_FS_DAX instead of CONFIG_DAX_DRIVER. This also means that bdev_dax_pgoff only needs to be built under CONFIG_FS_DAX now. Signed-off-by: Christoph Hellwig ---

[PATCH 05/29] dax: remove the pgmap sanity checks in generic_fsdax_supported

Drivers that register a dax_dev should make sure it works, no need to double check from the file system. Signed-off-by: Christoph Hellwig --- drivers/dax/super.c | 49 + 1 file changed, 1 insertion(+), 48 deletions(-) diff --git a/drivers/dax/super.c

[PATCH 03/29] dax: remove CONFIG_DAX_DRIVER

CONFIG_DAX_DRIVER only selects CONFIG_DAX now, so remove it. Signed-off-by: Christoph Hellwig --- drivers/dax/Kconfig| 4 drivers/nvdimm/Kconfig | 2 +- drivers/s390/block/Kconfig | 2 +- fs/fuse/Kconfig| 2 +- 4 files changed, 3 insertions(+), 7 deletions(-) diff

[PATCH 06/29] dax: move the partition alignment check into fs_dax_get_by_bdev

fs_dax_get_by_bdev is the primary interface to find a dax device for a block device, so move the partition alignment check there instead of wiring it up through ->dax_supported. Signed-off-by: Christoph Hellwig --- drivers/dax/super.c | 23 ++- 1 file changed, 6

decouple DAX from block devices

Hi Dan, this series decouples the DAX from the block layer so that the block_device is not needed at all for the DAX I/O path. ___ Virtualization mailing list Virtualization@lists.linux-foundation.org