From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: "Zanoni, Paulo R" <paulo.r.zanoni@intel.com>,
"Vishwanathapura,
Niranjana" <niranjana.vishwanathapura@intel.com>
Cc: "Wilson, Chris P" <chris.p.wilson@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Hellstrom, Thomas" <thomas.hellstrom@intel.com>,
"Auld, Matthew" <matthew.auld@intel.com>,
"Vetter, Daniel" <daniel.vetter@intel.com>,
"christian.koenig@amd.com" <christian.koenig@amd.com>
Subject: Re: [Intel-gfx] [PATCH v6 3/3] drm/doc/rfc: VM_BIND uapi definition
Date: Mon, 4 Jul 2022 22:35:18 +0300 [thread overview]
Message-ID: <093da09a-7c75-b052-d789-04404be813a6@intel.com> (raw)
In-Reply-To: <d5fee715c3489b943f055f925935871fda3899e7.camel@intel.com>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
On 30/06/2022 20:12, Zanoni, Paulo R wrote:
>>>> Can you please explain what happens when we try to write to a range
>>>> that's bound as read-only?
>>>>
>>> It will be mapped as read-only in device page table. Hence any
>>> write access will fail. I would expect a CAT error reported.
>> What's a CAT error? Does this lead to machine freeze or a GPU hang?
>> Let's make sure we document this.
>>
> Catastrophic error.
>
Reading the documentation, it seems the behavior depends on the context
type.
With the Legacy 64bit context type, writes are ignored (BSpec 531) :
- "For legacy context, the access rights are not applicable and
should not be considered during page walk."
For Advanced 64bit context type, I think the HW will generate a pagefault.
-Lionel
[-- Attachment #2: Type: text/html, Size: 2378 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: "Zanoni, Paulo R" <paulo.r.zanoni@intel.com>,
"Vishwanathapura,
Niranjana" <niranjana.vishwanathapura@intel.com>
Cc: "Brost, Matthew" <matthew.brost@intel.com>,
"Wilson, Chris P" <chris.p.wilson@intel.com>,
"Ursulin, Tvrtko" <tvrtko.ursulin@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Hellstrom, Thomas" <thomas.hellstrom@intel.com>,
"Zeng, Oak" <oak.zeng@intel.com>,
"Auld, Matthew" <matthew.auld@intel.com>,
"jason@jlekstrand.net" <jason@jlekstrand.net>,
"Vetter, Daniel" <daniel.vetter@intel.com>,
"christian.koenig@amd.com" <christian.koenig@amd.com>
Subject: Re: [PATCH v6 3/3] drm/doc/rfc: VM_BIND uapi definition
Date: Mon, 4 Jul 2022 22:35:18 +0300 [thread overview]
Message-ID: <093da09a-7c75-b052-d789-04404be813a6@intel.com> (raw)
In-Reply-To: <d5fee715c3489b943f055f925935871fda3899e7.camel@intel.com>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
On 30/06/2022 20:12, Zanoni, Paulo R wrote:
>>>> Can you please explain what happens when we try to write to a range
>>>> that's bound as read-only?
>>>>
>>> It will be mapped as read-only in device page table. Hence any
>>> write access will fail. I would expect a CAT error reported.
>> What's a CAT error? Does this lead to machine freeze or a GPU hang?
>> Let's make sure we document this.
>>
> Catastrophic error.
>
Reading the documentation, it seems the behavior depends on the context
type.
With the Legacy 64bit context type, writes are ignored (BSpec 531) :
- "For legacy context, the access rights are not applicable and
should not be considered during page walk."
For Advanced 64bit context type, I think the HW will generate a pagefault.
-Lionel
[-- Attachment #2: Type: text/html, Size: 2378 bytes --]
next prev parent reply other threads:[~2022-07-04 19:35 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 1:49 [Intel-gfx] [PATCH v7 0/3] drm/doc/rfc: i915 VM_BIND feature design + uapi Niranjana Vishwanathapura
2022-06-26 1:49 ` Niranjana Vishwanathapura
2022-06-26 1:49 ` [Intel-gfx] [PATCH v6 1/3] drm/doc/rfc: VM_BIND feature design document Niranjana Vishwanathapura
2022-06-26 1:49 ` Niranjana Vishwanathapura
2022-06-27 16:12 ` [Intel-gfx] " Daniel Vetter
2022-06-30 0:38 ` Zanoni, Paulo R
2022-06-30 0:38 ` Zanoni, Paulo R
2022-06-30 5:39 ` [Intel-gfx] " Niranjana Vishwanathapura
2022-06-30 5:39 ` Niranjana Vishwanathapura
2022-06-26 1:49 ` [Intel-gfx] [PATCH v6 2/3] drm/i915: Update i915 uapi documentation Niranjana Vishwanathapura
2022-06-26 1:49 ` Niranjana Vishwanathapura
2022-06-26 1:49 ` [Intel-gfx] [PATCH v6 3/3] drm/doc/rfc: VM_BIND uapi definition Niranjana Vishwanathapura
2022-06-26 1:49 ` Niranjana Vishwanathapura
2022-06-30 0:33 ` [Intel-gfx] " Zanoni, Paulo R
2022-06-30 0:33 ` Zanoni, Paulo R
2022-06-30 6:08 ` [Intel-gfx] " Niranjana Vishwanathapura
2022-06-30 6:08 ` Niranjana Vishwanathapura
2022-06-30 6:39 ` [Intel-gfx] " Zanoni, Paulo R
2022-06-30 6:39 ` Zanoni, Paulo R
2022-06-30 16:18 ` [Intel-gfx] " Niranjana Vishwanathapura
2022-06-30 16:18 ` Niranjana Vishwanathapura
2022-06-30 17:12 ` [Intel-gfx] " Zanoni, Paulo R
2022-06-30 17:12 ` Zanoni, Paulo R
2022-06-30 18:30 ` [Intel-gfx] " Niranjana Vishwanathapura
2022-06-30 18:30 ` Niranjana Vishwanathapura
2022-07-04 19:35 ` Lionel Landwerlin [this message]
2022-07-04 19:35 ` Lionel Landwerlin
2022-06-30 7:59 ` [Intel-gfx] " Tvrtko Ursulin
2022-06-30 16:22 ` Niranjana Vishwanathapura
2022-07-01 8:11 ` Tvrtko Ursulin
2022-06-30 5:11 ` Jason Ekstrand
2022-06-30 5:11 ` Jason Ekstrand
2022-06-30 6:15 ` [Intel-gfx] " Niranjana Vishwanathapura
2022-06-30 6:15 ` Niranjana Vishwanathapura
2022-06-30 6:24 ` [Intel-gfx] " Niranjana Vishwanathapura
2022-06-30 15:14 ` Matthew Auld
2022-06-30 15:14 ` Matthew Auld
2022-06-30 15:34 ` [Intel-gfx] " Jason Ekstrand
2022-06-30 15:34 ` Jason Ekstrand
2022-06-30 16:23 ` [Intel-gfx] " Matthew Auld
2022-06-30 16:23 ` Matthew Auld
2022-07-01 8:45 ` [Intel-gfx] " Matthew Auld
2022-07-01 8:45 ` Matthew Auld
2022-06-30 15:45 ` [Intel-gfx] " Jason Ekstrand
2022-06-30 15:45 ` Jason Ekstrand
2022-06-30 18:32 ` [Intel-gfx] " Niranjana Vishwanathapura
2022-06-30 18:32 ` Niranjana Vishwanathapura
2022-06-26 2:03 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/doc/rfc: i915 VM_BIND feature design + uapi Patchwork
2022-06-26 2:03 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-06-26 2:25 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-06-27 21:34 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-06-24 17:49 [Intel-gfx] [PATCH v6 0/3] " Niranjana Vishwanathapura
2022-06-24 17:49 ` [Intel-gfx] [PATCH v6 3/3] drm/doc/rfc: VM_BIND uapi definition Niranjana Vishwanathapura
2022-06-24 20:07 ` Daniel Vetter
2022-06-25 19:02 ` Niranjana Vishwanathapura
2022-06-26 1:08 ` Niranjana Vishwanathapura
2022-06-27 9:07 ` Daniel Vetter
2022-06-27 8:55 ` Daniel Vetter
2022-06-30 6:21 ` Niranjana Vishwanathapura
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=093da09a-7c75-b052-d789-04404be813a6@intel.com \
--to=lionel.g.landwerlin@intel.com \
--cc=chris.p.wilson@intel.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=niranjana.vishwanathapura@intel.com \
--cc=paulo.r.zanoni@intel.com \
--cc=thomas.hellstrom@intel.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.