Re: [GIT PULL] vhost,vdpa,virtio: cleanups, fixes

2020-10-23 Thread pr-tracker-bot
The pull request you sent on Fri, 23 Oct 2020 11:38: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/9313f8026328d0309d093f6774be4b8f5340c0e5 Thank you! -- Deet-doot-dot, I am a

[PATCH] drm/: Constify struct drm_driver

2020-10-23 Thread Daniel Vetter
Only the following drivers aren't converted: - amdgpu, because of the driver_feature mangling due to virt support - nouveau, because DRIVER_ATOMIC uapi is still not the default on the platforms where it's supported (i.e. again driver_feature mangling) - vc4, again because of driver_feature

Re: [PATCH 04/16] vhost: prep vhost_dev_init users to handle failures

2020-10-23 Thread Michael S. Tsirkin
On Fri, Oct 09, 2020 at 02:41:26PM +0300, Dan Carpenter wrote: > Hi Mike, > > url: > https://github.com/0day-ci/linux/commits/Mike-Christie/vhost-fix-scsi-cmd-handling-and-IOPs/20201008-045802 > base: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git > linux-next > config:

Re: [PATCH] virtio_ring: use DMA when memory encryption is active

2020-10-23 Thread Michael S. Tsirkin
On Fri, Oct 23, 2020 at 11:00:54AM +0200, Sebastian Hofmann wrote: > > Michael S. Tsirkin hat am 22.10.2020 13:39 geschrieben: > > > > > > On Wed, Oct 21, 2020 at 05:14:25PM +0200, Sebastian Hofmann wrote: > > > virtio_ring does not work with active memory encryption because the host > > >

Re: [PATCH 00/16 V2] vhost: fix scsi cmd handling and IOPs

2020-10-23 Thread Michael S. Tsirkin
On Wed, Oct 07, 2020 at 03:54:45PM -0500, Mike Christie wrote: > The following patches were made over Michael's vhost branch here: > https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git/log/?h=vhost > > The patches also apply to Linus's or Martin's trees if you apply >

Re: [PATCH 14/16] vhost: poll support support multiple workers

2020-10-23 Thread Michael S. Tsirkin
On Thu, Oct 08, 2020 at 08:46:42AM +0800, kernel test robot wrote: > Hi Mike, > > Thank you for the patch! Yet something to improve: > > [auto build test ERROR on vhost/linux-next] > [also build test ERROR on next-20201007] > [cannot apply to v5.9-rc8] > [If your patch is applied to the wrong

[GIT PULL] vhost,vdpa,virtio: cleanups, fixes

2020-10-23 Thread Michael S. Tsirkin
Was holding out for a couple of big new features including vop and rpmsg support for 1.0, but it looks like they won't make it in time. virtio i2c might be ready soon but that's a new driver so if it's ready soon it's probably ok to merge outside the merge window ... we'll see. The following

Re: [PATCH net] vhost_vdpa: Return -EFUALT if copy_from_user() fails

2020-10-23 Thread Michael S. Tsirkin
On Fri, Oct 23, 2020 at 03:08:53PM +0300, Dan Carpenter wrote: > The copy_to/from_user() functions return the number of bytes which we > weren't able to copy but the ioctl should return -EFAULT if they fail. > > Fixes: a127c5bbb6a8 ("vhost-vdpa: fix backend feature ioctls") > Signed-off-by: Dan

Re: [Intel-gfx] [PATCH 5/5] drm/: Constify struct drm_driver

2020-10-23 Thread kernel test robot
Hi Daniel, I love your patch! Perhaps something to improve: [auto build test WARNING on drm-tip/drm-tip] [cannot apply to drm-intel/for-linux-next drm-exynos/exynos-drm-next linus/master v5.9 next-20201023] [If your patch is applied to the wrong git tree, kindly drop us a note. And when

[PATCH 5/5] drm/: Constify struct drm_driver

2020-10-23 Thread Daniel Vetter
Only the following drivers aren't converted: - amdgpu, because of the driver_feature mangling due to virt support - nouveau, because DRIVER_ATOMIC uapi is still not the default on the platforms where it's supported (i.e. again driver_feature mangling) - vc4, again because of driver_feature

[PATCH net] vhost_vdpa: Return -EFUALT if copy_from_user() fails

2020-10-23 Thread Dan Carpenter
The copy_to/from_user() functions return the number of bytes which we weren't able to copy but the ioctl should return -EFAULT if they fail. Fixes: a127c5bbb6a8 ("vhost-vdpa: fix backend feature ioctls") Signed-off-by: Dan Carpenter --- drivers/vhost/vdpa.c | 10 +- 1 file changed, 5

Re: [PATCH] virtio_ring: use DMA when memory encryption is active

2020-10-23 Thread Sebastian Hofmann
> Jason Wang hat am 23.10.2020 11:10 geschrieben: > > > On 2020/10/23 下午5:00, Sebastian Hofmann wrote: > >> Michael S. Tsirkin hat am 22.10.2020 13:39 geschrieben: > >> > >> > >> On Wed, Oct 21, 2020 at 05:14:25PM +0200, Sebastian Hofmann wrote: > >>> virtio_ring does not work with active

Re: [PATCH] virtio_ring: use DMA when memory encryption is active

2020-10-23 Thread Jason Wang
On 2020/10/23 下午5:00, Sebastian Hofmann wrote: Michael S. Tsirkin hat am 22.10.2020 13:39 geschrieben: On Wed, Oct 21, 2020 at 05:14:25PM +0200, Sebastian Hofmann wrote: virtio_ring does not work with active memory encryption because the host cannot read it. Fix this by enforcing the use

Re: [PATCH] virtio_ring: use DMA when memory encryption is active

2020-10-23 Thread Sebastian Hofmann
> Michael S. Tsirkin hat am 22.10.2020 13:39 geschrieben: > > > On Wed, Oct 21, 2020 at 05:14:25PM +0200, Sebastian Hofmann wrote: > > virtio_ring does not work with active memory encryption because the host > > cannot read it. Fix this by enforcing the use of DMA which uses shared > >

[PATCH V4 3/3] vdpa_sim: implement get_iova_range()

2020-10-23 Thread Jason Wang
This implements a sample get_iova_range() for the simulator which advertise [0, ULLONG_MAX] as the valid range. Signed-off-by: Jason Wang --- drivers/vdpa/vdpa_sim/vdpa_sim.c | 12 1 file changed, 12 insertions(+) diff --git a/drivers/vdpa/vdpa_sim/vdpa_sim.c

[PATCH V4 1/3] vdpa: introduce config op to get valid iova range

2020-10-23 Thread Jason Wang
This patch introduce a config op to get valid iova range from the vDPA device. Signed-off-by: Jason Wang --- include/linux/vdpa.h | 15 +++ 1 file changed, 15 insertions(+) diff --git a/include/linux/vdpa.h b/include/linux/vdpa.h index eae0bfd87d91..30bc7a7223bb 100644 ---

[PATCH V4 2/3] vhost: vdpa: report iova range

2020-10-23 Thread Jason Wang
This patch introduces a new ioctl for vhost-vdpa device that can report the iova range by the device. For device that implements get_iova_range() method, we fetch it from the vDPA device. If device doesn't implement get_iova_range() but depends on platform IOMMU, we will query via

[PATCH V4 0/3] vDPA: API for reporting IOVA range

2020-10-23 Thread Jason Wang
Hi All: This series introduces API for reporing IOVA range. This is a must for userspace to work correclty: - for the process that uses vhost-vDPA directly, the IOVA must be allocated from this range. - for VM(qemu), when vIOMMU is not enabled, fail early if GPA is out of range - for

Re: [PATCH V3 2/3] vhost: vdpa: report iova range

2020-10-23 Thread Jason Wang
On 2020/10/23 下午1:28, kernel test robot wrote: Hi Jason, I love your patch! Perhaps something to improve: [auto build test WARNING on vhost/linux-next] [also build test WARNING on linus/master v5.9 next-20201023] [cannot apply to linux/master] [If your patch is applied to the wrong git tree

Re: [External] Re: [RFC 0/4] Introduce VDUSE - vDPA Device in Userspace

2020-10-23 Thread Jason Wang
On 2020/10/23 上午10:55, Yongji Xie wrote: On Tue, Oct 20, 2020 at 5:13 PM Jason Wang > wrote: On 2020/10/20 下午4:35, Yongji Xie wrote: > > > On Tue, Oct 20, 2020 at 4:01 PM Jason Wang mailto:jasow...@redhat.com> >