All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ajay Kaher <ajay.kaher@broadcom.com>
To: stable@vger.kernel.org, gregkh@linuxfoundation.org
Cc: zack.rusin@broadcom.com, thomas.hellstrom@linux.intel.com,
	christian.koenig@amd.com, ray.huang@amd.com, airlied@gmail.com,
	daniel@ffwll.ch, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, ajay.kaher@broadcom.com,
	alexey.makhalov@broadcom.com, vasavi.sirnapalli@broadcom.com
Subject: [PATCH v6.1.y 0/2] drm/ttm: fixes for vmwgfx when SEV enabled
Date: Mon,  9 Dec 2024 09:49:02 +0000	[thread overview]
Message-ID: <20241209094904.2547579-1-ajay.kaher@broadcom.com> (raw)

drm/ttm patches for v6.1.y to fix vmwgfx when SEV enabled.

Zack Rusin (2):
  drm/ttm: Make sure the mapped tt pages are decrypted when needed
  drm/ttm: Print the memory decryption status just once

 drivers/gpu/drm/ttm/ttm_bo_util.c | 13 +++++++++++--
 drivers/gpu/drm/ttm/ttm_tt.c      | 12 ++++++++++++
 include/drm/ttm/ttm_tt.h          |  7 +++++++
 3 files changed, 30 insertions(+), 2 deletions(-)

-- 
2.39.4


             reply	other threads:[~2024-12-09  9:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-09  9:49 Ajay Kaher [this message]
2024-12-09  9:49 ` [PATCH v6.1.y 1/2] drm/ttm: Make sure the mapped tt pages are decrypted when needed Ajay Kaher
2024-12-09 14:35   ` Sasha Levin
2024-12-12 12:40   ` Patch "drm/ttm: Make sure the mapped tt pages are decrypted when needed" has been added to the 6.1-stable tree gregkh
2024-12-09  9:49 ` [PATCH v6.1.y 2/2] drm/ttm: Print the memory decryption status just once Ajay Kaher
2024-12-09 14:35   ` Sasha Levin
2024-12-12 12:40   ` Patch "drm/ttm: Print the memory decryption status just once" has been added to the 6.1-stable tree gregkh

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=20241209094904.2547579-1-ajay.kaher@broadcom.com \
    --to=ajay.kaher@broadcom.com \
    --cc=airlied@gmail.com \
    --cc=alexey.makhalov@broadcom.com \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ray.huang@amd.com \
    --cc=stable@vger.kernel.org \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=vasavi.sirnapalli@broadcom.com \
    --cc=zack.rusin@broadcom.com \
    /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.