search for: gvt

Hi. In the current state of gvt-g the user experience is suboptimal. So my question is what are the ETAs for following features: 1. Accelerated virt-manager console using gvt-g device 2. Custom resolutions or dynamic resolution 3. UEFI VMs support (Windows guest) Thanks.

Hello. All features are about usability and simple user experience. 1. Its about local display / dmabuf feature. Currently user needs to use virt-viewer tool. But virt-manager already incorporates graphical console. It would be nice if it could support accelerated gvt-g local display. Preferably with minimum performance overhead. Also virt-manager should allow to use mdev videocard alone, without requiring to use additional primary virtual adapter like QXL or Cirrus 2. Currently with gvt solution there few mdev devices each with fixed resolution. User should be...

Use the proper API instead. Fixes: f440c8a572d7 ("drm/i915/gvt/kvmgt: read/write GPA via KVM API") Signed-off-by: Christoph Hellwig <hch at lst.de> --- drivers/gpu/drm/i915/gvt/kvmgt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/gvt/kvmgt.c b/drivers/gpu/drm/i915/gvt/kvmgt.c index 074c4efb58eb..584840062...

So it looks like this solution is currently not very user friendly. Perhaps Intel could get Red Hat help to make first-class support of gvt feature in virt-manager? 09.05.2019, 10:28, "Gerd Hoffmann" <gerd@kraxel.org>: >   Hi, > >>  1. Its about local display / dmabuf feature. Currently user needs to >>  use virt-viewer tool. But virt-manager already incorporates graphical >>  console. It would...

Could you elaborate a bit more about the first two features? On UEFI VMs support (Windows guest), do you mean enabling Windows VM display on UEFI? Thanks. > -----Original Message----- > From: iGVT-g [mailto:igvt-g-bounces@lists.01.org] On Behalf Of Alex Ivanov > Sent: Friday, April 19, 2019 2:51 AM > To: libvirt-users@redhat.com; igvt-g@lists.01.org; virt-tools-list@redhat.com > Subject: [iGVT-g] GVT-g - suboptimal user experience > > Hi. > In the current state of gvt-g th...

> -----Original Message----- > From: Gerd Hoffmann [mailto:gerd@kraxel.org] > Sent: Thursday, May 9, 2019 3:28 PM > To: Alex Ivanov <gnidorah@ya.ru> > Cc: Yuan, Hang <hang.yuan@intel.com>; libvirt-users@redhat.com; igvt- > g@lists.01.org; virt-tools-list@redhat.com > Subject: Re: [iGVT-g] GVT-g - suboptimal user experience > > Hi, > > > 1. Its about local display / dmabuf feature. Currently user needs to > > use virt-viewer tool. But virt-manager already incorporates graphical > &...

.../masahiroy/linux-kbuild.git build-test Changes in v2: - fix up the new driver komeda - Add Sam's Reviewed-by drivers/gpu/drm/amd/amdgpu/Makefile | 2 +- drivers/gpu/drm/amd/lib/Makefile | 2 +- drivers/gpu/drm/arm/display/komeda/Makefile | 4 ++-- drivers/gpu/drm/i915/gvt/Makefile | 2 +- drivers/gpu/drm/msm/Makefile | 6 +++--- drivers/gpu/drm/nouveau/Kbuild | 8 ++++---- 6 files changed, 12 insertions(+), 12 deletions(-) diff --git a/drivers/gpu/drm/amd/amdgpu/Makefile b/drivers/gpu/drm/amd/amdgpu/Makefile index 466da59..62bf...

Hi, > 1. Its about local display / dmabuf feature. Currently user needs to > use virt-viewer tool. But virt-manager already incorporates graphical > console. It would be nice if it could support accelerated gvt-g local > display. virt-manager and virt-viewer essentially run the same code spice client code: both are using the spice-gtk widget. So, if that isn't working (didn't verify) it should be rather easy to wire up. > Also virt-manager should allow to use mdev videocard alone, without...

....masahiro at socionext.com> --- I put all gpu/drm changes into a single patch because they are trivial conversion. Please let me know if I need to split this into per-driver patches. drivers/gpu/drm/amd/amdgpu/Makefile | 2 +- drivers/gpu/drm/amd/lib/Makefile | 2 +- drivers/gpu/drm/i915/gvt/Makefile | 2 +- drivers/gpu/drm/msm/Makefile | 6 +++--- drivers/gpu/drm/nouveau/Kbuild | 8 ++++---- 5 files changed, 10 insertions(+), 10 deletions(-) diff --git a/drivers/gpu/drm/amd/amdgpu/Makefile b/drivers/gpu/drm/amd/amdgpu/Makefile index f76bcb9..b21ebb0 100644 --- a/drivers...

...;class id"? > > So this patch add id_table to mdev_driver and id for mdev parent, and > implement the match method for mdev bus. > > [1] https://lkml.org/lkml/2019/9/10/135 > > Signed-off-by: Jason Wang <jasowang at redhat.com> > --- > drivers/gpu/drm/i915/gvt/kvmgt.c | 2 +- > drivers/s390/cio/vfio_ccw_ops.c | 2 +- > drivers/s390/crypto/vfio_ap_ops.c | 3 ++- > drivers/vfio/mdev/mdev_core.c | 14 ++++++++++++-- > drivers/vfio/mdev/mdev_driver.c | 14 ++++++++++++++ > drivers/vfio/mdev/mdev_private.h | 1 + > drivers/vfio...

C7: lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Device 3185 (rev 03) grep Driver /var/log/Xorg.0.log [ 24.374] (**) | |-->Device "Intel Graphics" [ 24.610] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: [ 24.614] (II) intel: Driver for Intel(R) HD Graphics [ 24.614] (II) intel: Driver for Intel(R) Iris(TM) Graphics [ 24.614]

...izeof(T)) ) Signed-off-by: Jérémy Lefaure <jeremy.lefaure at lse.epita.fr> --- drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c | 9 +++++---- drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c | 9 +++++---- drivers/gpu/drm/gma500/psb_intel_sdvo.c | 9 ++++----- drivers/gpu/drm/i915/gvt/vgpu.c | 3 ++- drivers/gpu/drm/nouveau/nvkm/subdev/bios/init.c | 7 ++++--- drivers/gpu/drm/via/via_verifier.c | 10 ++++------ 6 files changed, 24 insertions(+), 23 deletions(-) diff --git a/drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c b/drivers/gpu/drm/amd/amdgpu/gfx_v8_...

Hi all, this series improves the use_mm / unuse_mm interface by better documenting the assumptions, and my taking the set_fs manipulations spread over the callers into the core API.

Hi all, this series improves the use_mm / unuse_mm interface by better documenting the assumptions, and my taking the set_fs manipulations spread over the callers into the core API.

> Linux migration document. > > * To: samba at sambadotorg, samba-technical at sambadotorg > * Subject: Linux migration document. > * From: Jeremy Allison <jra at sambadotorg> > * Date: Tue, 21 Oct 2003 23:20:58 +0000 > * Cc: jra at sambadotorg > > Hi all, > > If you're looking at a Windows server to Linux & Samba migration

On Wed, Apr 08, 2020 at 09:44:37AM +0800, Zhenyu Wang wrote: > On 2020.04.04 11:40:58 +0200, Christoph Hellwig wrote: > > No Xen support anywhere here. Remove a dead declaration and an unused > > include. > > > > Signed-off-by: Christoph Hellwig <hch at lst.de> > > --- > > We'll keep that off-tree. > > Acked-by: Zhenyu Wang <zhenyuw at

On Mon, Apr 06, 2020 at 11:08:46PM -0400, Yan Zhao wrote: > hi > we were removing this code. see > https://lore.kernel.org/kvm/20200313031109.7989-1-yan.y.zhao at intel.com/ This didn't make 5.7-rc1. > The implementation of vfio_dma_rw() has been in vfio next tree. > https://github.com/awilliam/linux-vfio/commit/8d46c0cca5f4dc0538173d62cd36b1119b5105bc This made 5.7-rc1, so

On Mon, Apr 13, 2020 at 08:04:10PM -0400, Yan Zhao wrote: > > I can't think of another way for a kernel thread to have a mm indeed. > for example, before calling to vfio_dma_rw(), a kernel thread has already > called use_mm(), then its current->mm is not null, and it has flag > PF_KTHREAD. > in this case, we just want to allow the copy_to_user() directly if >

..._driver and class_id for mdev > >> device with the match method for mdev bus. > >> > >> Signed-off-by: Jason Wang <jasowang at redhat.com> > >> --- > >> .../driver-api/vfio-mediated-device.rst | 5 +++++ > >> drivers/gpu/drm/i915/gvt/kvmgt.c | 1 + > >> drivers/s390/cio/vfio_ccw_ops.c | 1 + > >> drivers/s390/crypto/vfio_ap_ops.c | 1 + > >> drivers/vfio/mdev/mdev_core.c | 18 +++++++++++++++ > >> drivers/vfio/mdev/mdev_driver.c...

..._driver and class_id for mdev > >> device with the match method for mdev bus. > >> > >> Signed-off-by: Jason Wang <jasowang at redhat.com> > >> --- > >> .../driver-api/vfio-mediated-device.rst | 5 +++++ > >> drivers/gpu/drm/i915/gvt/kvmgt.c | 1 + > >> drivers/s390/cio/vfio_ccw_ops.c | 1 + > >> drivers/s390/crypto/vfio_ap_ops.c | 1 + > >> drivers/vfio/mdev/mdev_core.c | 18 +++++++++++++++ > >> drivers/vfio/mdev/mdev_driver.c...