All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: dri-devel@lists.freedesktop.org
Cc: christian.koenig@amd.com, Gerd Hoffmann <kraxel@redhat.com>,
	David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	virtualization@lists.linux-foundation.org (open list:VIRTIO GPU
	DRIVER), linux-kernel@vger.kernel.org (open list)
Subject: [PATCH v2 2/2] drm/virtio: set max_segment
Date: Tue, 18 Aug 2020 11:20:17 +0200	[thread overview]
Message-ID: <20200818092017.26290-3-kraxel@redhat.com> (raw)
In-Reply-To: <20200818092017.26290-1-kraxel@redhat.com>

When initializing call virtio_max_dma_size() to figure the scatter list
limit.  Needed to make virtio-gpu work properly with SEV.

v2: place max_segment in drm driver not gem object.

Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
 drivers/gpu/drm/virtio/virtgpu_kms.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/gpu/drm/virtio/virtgpu_kms.c b/drivers/gpu/drm/virtio/virtgpu_kms.c
index bf060c69850f..5a4364c00fae 100644
--- a/drivers/gpu/drm/virtio/virtgpu_kms.c
+++ b/drivers/gpu/drm/virtio/virtgpu_kms.c
@@ -114,6 +114,7 @@ int virtio_gpu_init(struct drm_device *dev)
 
 	vgdev->ddev = dev;
 	dev->dev_private = vgdev;
+	dev->max_segment = virtio_max_dma_size(vgdev->vdev);
 	vgdev->vdev = dev_to_virtio(dev->dev);
 	vgdev->dev = dev->dev;
 
-- 
2.18.4


WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel@redhat.com>
To: dri-devel@lists.freedesktop.org
Cc: David Airlie <airlied@linux.ie>,
	open list <linux-kernel@vger.kernel.org>,
	"open list:VIRTIO GPU DRIVER"
	<virtualization@lists.linux-foundation.org>,
	Daniel Vetter <daniel@ffwll.ch>,
	christian.koenig@amd.com
Subject: [PATCH v2 2/2] drm/virtio: set max_segment
Date: Tue, 18 Aug 2020 11:20:17 +0200	[thread overview]
Message-ID: <20200818092017.26290-3-kraxel@redhat.com> (raw)
In-Reply-To: <20200818092017.26290-1-kraxel@redhat.com>

When initializing call virtio_max_dma_size() to figure the scatter list
limit.  Needed to make virtio-gpu work properly with SEV.

v2: place max_segment in drm driver not gem object.

Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
 drivers/gpu/drm/virtio/virtgpu_kms.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/gpu/drm/virtio/virtgpu_kms.c b/drivers/gpu/drm/virtio/virtgpu_kms.c
index bf060c69850f..5a4364c00fae 100644
--- a/drivers/gpu/drm/virtio/virtgpu_kms.c
+++ b/drivers/gpu/drm/virtio/virtgpu_kms.c
@@ -114,6 +114,7 @@ int virtio_gpu_init(struct drm_device *dev)
 
 	vgdev->ddev = dev;
 	dev->dev_private = vgdev;
+	dev->max_segment = virtio_max_dma_size(vgdev->vdev);
 	vgdev->vdev = dev_to_virtio(dev->dev);
 	vgdev->dev = dev->dev;
 
-- 
2.18.4

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel@redhat.com>
To: dri-devel@lists.freedesktop.org
Cc: David Airlie <airlied@linux.ie>,
	open list <linux-kernel@vger.kernel.org>,
	"open list:VIRTIO GPU DRIVER"
	<virtualization@lists.linux-foundation.org>,
	Gerd Hoffmann <kraxel@redhat.com>,
	christian.koenig@amd.com
Subject: [PATCH v2 2/2] drm/virtio: set max_segment
Date: Tue, 18 Aug 2020 11:20:17 +0200	[thread overview]
Message-ID: <20200818092017.26290-3-kraxel@redhat.com> (raw)
In-Reply-To: <20200818092017.26290-1-kraxel@redhat.com>

When initializing call virtio_max_dma_size() to figure the scatter list
limit.  Needed to make virtio-gpu work properly with SEV.

v2: place max_segment in drm driver not gem object.

Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
 drivers/gpu/drm/virtio/virtgpu_kms.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/gpu/drm/virtio/virtgpu_kms.c b/drivers/gpu/drm/virtio/virtgpu_kms.c
index bf060c69850f..5a4364c00fae 100644
--- a/drivers/gpu/drm/virtio/virtgpu_kms.c
+++ b/drivers/gpu/drm/virtio/virtgpu_kms.c
@@ -114,6 +114,7 @@ int virtio_gpu_init(struct drm_device *dev)
 
 	vgdev->ddev = dev;
 	dev->dev_private = vgdev;
+	dev->max_segment = virtio_max_dma_size(vgdev->vdev);
 	vgdev->vdev = dev_to_virtio(dev->dev);
 	vgdev->dev = dev->dev;
 
-- 
2.18.4

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-08-18  9:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-18  9:20 [PATCH v2 0/2] drm: fix virtio-gpu + sev Gerd Hoffmann
2020-08-18  9:20 ` [PATCH v2 1/2] drm: allow limiting the scatter list size Gerd Hoffmann
2020-08-18  9:20   ` Gerd Hoffmann
2020-08-18  9:20   ` Gerd Hoffmann
2020-08-18  9:20   ` Gerd Hoffmann
2020-08-18  9:20   ` Gerd Hoffmann
2020-08-18  9:20   ` Gerd Hoffmann
2020-09-01  7:40   ` Daniel Vetter
2020-09-01  7:40     ` Daniel Vetter
2020-09-01  7:40     ` Daniel Vetter
2020-09-01  7:40     ` Daniel Vetter
2020-09-01  7:40     ` Daniel Vetter
2020-09-01  7:40     ` Daniel Vetter
     [not found]     ` <20200901074043.GT2352366-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2020-09-07  6:39       ` Gerd Hoffmann
2020-09-07  6:39     ` Gerd Hoffmann
2020-09-07  6:39       ` Gerd Hoffmann
2020-09-07  6:39       ` Gerd Hoffmann
2020-09-07  6:39       ` Gerd Hoffmann
2020-09-07  6:39       ` Gerd Hoffmann
2020-09-07  7:13       ` Daniel Vetter
2020-09-07  7:13         ` Daniel Vetter
2020-09-07  7:13         ` Daniel Vetter
2020-09-07  7:13         ` Daniel Vetter
2020-09-07  7:13         ` Daniel Vetter
2020-09-07  7:13         ` Daniel Vetter
2020-08-18  9:20 ` Gerd Hoffmann [this message]
2020-08-18  9:20   ` [PATCH v2 2/2] drm/virtio: set max_segment Gerd Hoffmann
2020-08-18  9:20   ` Gerd Hoffmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200818092017.26290-3-kraxel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=airlied@linux.ie \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.