From: Andi Shyti <andi.shyti@linux.intel.com>
To: "Mrozek, Michal" <michal.mrozek@intel.com>
Cc: Andi Shyti <andi.shyti@linux.intel.com>,
Nirmoy Das <nirmoy.das@linux.intel.com>,
"Landwerlin, Lionel G" <lionel.g.landwerlin@intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Andi Shyti <andi.shyti@kernel.org>,
"Hajda, Andrzej" <andrzej.hajda@intel.com>,
Chris Wilson <chris.p.wilson@linux.intel.com>,
"Das, Nirmoy" <nirmoy.das@intel.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] drm/i915/gt: Report full vm address range
Date: Wed, 20 Mar 2024 19:30:25 +0100 [thread overview]
Message-ID: <ZfsrQWNfzDGl8IVV@ashyti-mobl2.lan> (raw)
In-Reply-To: <BN9PR11MB527575D97CB63C5E4B1B0E7AE72D2@BN9PR11MB5275.namprd11.prod.outlook.com>
Hi Michal,
On Mon, Mar 18, 2024 at 05:21:54AM +0000, Mrozek, Michal wrote:
> > > Lionel, Michal, thoughts?
> Compute UMD needs to know exact GTT total size.
the problem is that we cannot apply the workaround without
reserving one page from the GTT total size and we need to apply
the workaround.
If we provide the total GTT size we will have one page that will
be contended between kernel and userspace and, if userspace is
unaware that the page belongs to the kernel, we might step on
each other toe.
The ask here from kernel side is to relax the check on the
maxNBitValue() in userspace and take what the kernel provides.
Thanks,
Andi
next prev parent reply other threads:[~2024-03-20 18:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 19:39 [PATCH] drm/i915/gt: Report full vm address range Andi Shyti
2024-03-14 2:40 ` ✗ Fi.CI.BAT: failure for " Patchwork
2024-03-14 5:21 ` [PATCH] " Mrozek, Michal
2024-03-14 14:04 ` Lionel Landwerlin
2024-03-14 16:05 ` Nirmoy Das
2024-03-15 17:08 ` Andi Shyti
2024-03-18 5:21 ` Mrozek, Michal
2024-03-20 18:30 ` Andi Shyti [this message]
2024-03-21 4:29 ` Mrozek, Michal
2024-03-14 20:13 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/gt: Report full vm address range (rev2) Patchwork
2024-03-14 20:33 ` ✗ Fi.CI.BAT: failure " Patchwork
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=ZfsrQWNfzDGl8IVV@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=andrzej.hajda@intel.com \
--cc=chris.p.wilson@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lionel.g.landwerlin@intel.com \
--cc=michal.mrozek@intel.com \
--cc=nirmoy.das@intel.com \
--cc=nirmoy.das@linux.intel.com \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox