All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: dri-devel@lists.freedesktop.org
Cc: 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 2/2] drm/virtio: set max_segment
Date: Tue, 18 Aug 2020 09:48:28 +0200	[thread overview]
Message-ID: <20200818074828.9509-3-kraxel@redhat.com> (raw)
In-Reply-To: <20200818074828.9509-1-kraxel@redhat.com>

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

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

diff --git a/drivers/gpu/drm/virtio/virtgpu_object.c b/drivers/gpu/drm/virtio/virtgpu_object.c
index 1359eb8f1a02..26b608e2554e 100644
--- a/drivers/gpu/drm/virtio/virtgpu_object.c
+++ b/drivers/gpu/drm/virtio/virtgpu_object.c
@@ -214,6 +214,7 @@ int virtio_gpu_object_create(struct virtio_gpu_device *vgdev,
 		goto err_free_gem;
 
 	bo->dumb = params->dumb;
+	shmem_obj->base.max_segment = virtio_max_dma_size(vgdev->vdev);
 
 	if (fence) {
 		ret = -ENOMEM;
-- 
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>,
	Daniel Vetter <daniel@ffwll.ch>,
	"open list:VIRTIO GPU DRIVER"
	<virtualization@lists.linux-foundation.org>
Subject: [PATCH 2/2] drm/virtio: set max_segment
Date: Tue, 18 Aug 2020 09:48:28 +0200	[thread overview]
Message-ID: <20200818074828.9509-3-kraxel@redhat.com> (raw)
In-Reply-To: <20200818074828.9509-1-kraxel@redhat.com>

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

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

diff --git a/drivers/gpu/drm/virtio/virtgpu_object.c b/drivers/gpu/drm/virtio/virtgpu_object.c
index 1359eb8f1a02..26b608e2554e 100644
--- a/drivers/gpu/drm/virtio/virtgpu_object.c
+++ b/drivers/gpu/drm/virtio/virtgpu_object.c
@@ -214,6 +214,7 @@ int virtio_gpu_object_create(struct virtio_gpu_device *vgdev,
 		goto err_free_gem;
 
 	bo->dumb = params->dumb;
+	shmem_obj->base.max_segment = virtio_max_dma_size(vgdev->vdev);
 
 	if (fence) {
 		ret = -ENOMEM;
-- 
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>,
	Gerd Hoffmann <kraxel@redhat.com>,
	"open list:VIRTIO GPU DRIVER"
	<virtualization@lists.linux-foundation.org>
Subject: [PATCH 2/2] drm/virtio: set max_segment
Date: Tue, 18 Aug 2020 09:48:28 +0200	[thread overview]
Message-ID: <20200818074828.9509-3-kraxel@redhat.com> (raw)
In-Reply-To: <20200818074828.9509-1-kraxel@redhat.com>

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

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

diff --git a/drivers/gpu/drm/virtio/virtgpu_object.c b/drivers/gpu/drm/virtio/virtgpu_object.c
index 1359eb8f1a02..26b608e2554e 100644
--- a/drivers/gpu/drm/virtio/virtgpu_object.c
+++ b/drivers/gpu/drm/virtio/virtgpu_object.c
@@ -214,6 +214,7 @@ int virtio_gpu_object_create(struct virtio_gpu_device *vgdev,
 		goto err_free_gem;
 
 	bo->dumb = params->dumb;
+	shmem_obj->base.max_segment = virtio_max_dma_size(vgdev->vdev);
 
 	if (fence) {
 		ret = -ENOMEM;
-- 
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  7:48 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-18  7:48 [PATCH 0/2] drm: fix virtio-gpu + sev Gerd Hoffmann
2020-08-18  7:48 ` [PATCH 1/2] drm: allow limiting the scatter list size Gerd Hoffmann
2020-08-18  7:48   ` Gerd Hoffmann
2020-08-18  7:48   ` Gerd Hoffmann
2020-08-18  7:48   ` Gerd Hoffmann
2020-08-18  7:48   ` Gerd Hoffmann
2020-08-18  7:48   ` Gerd Hoffmann
2020-08-18  7:57   ` Christian König
2020-08-18  7:57     ` Christian König
2020-08-18  7:57     ` Christian König
2020-08-18  7:57     ` Christian König
2020-08-18  7:57     ` Christian König
2020-08-18  7:57     ` Christian König
2020-08-18  8:27     ` Gerd Hoffmann
2020-08-18  8:27       ` Gerd Hoffmann
2020-08-18  8:27       ` Gerd Hoffmann
2020-08-18  8:27       ` Gerd Hoffmann
2020-08-18  8:27       ` Gerd Hoffmann
2020-08-18  8:27       ` Gerd Hoffmann
2020-08-18  8:27       ` Gerd Hoffmann
2020-08-18  8:31       ` Christian König
2020-08-18  8:31         ` Christian König
2020-08-18  8:31         ` Christian König
2020-08-18  8:31         ` Christian König
2020-08-18  8:31         ` Christian König
2020-08-18  8:31         ` Christian König
2020-08-18  8:31         ` Christian König
2020-08-18  9:00         ` Gerd Hoffmann
2020-08-18  9:00           ` Gerd Hoffmann
2020-08-18  9:00           ` Gerd Hoffmann
2020-08-18  9:00           ` Gerd Hoffmann
2020-08-18  9:00           ` Gerd Hoffmann
2020-08-18  9:00           ` Gerd Hoffmann
2020-08-18  9:00           ` Gerd Hoffmann
2020-08-18  7:48 ` Gerd Hoffmann [this message]
2020-08-18  7:48   ` [PATCH 2/2] drm/virtio: set max_segment Gerd Hoffmann
2020-08-18  7:48   ` 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=20200818074828.9509-3-kraxel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=airlied@linux.ie \
    --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.