From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] i915: Handle the case where legacy mmap is not available
Date: Tue, 11 May 2021 09:19:34 -0700 [thread overview]
Message-ID: <871radw8dl.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20210511090000.1521342-1-maarten.lankhorst@linux.intel.com>
On Tue, 11 May 2021 02:00:00 -0700, Maarten Lankhorst wrote:
>
> We will remove support for the legacy mmap ioctl, so handle that
> case without rewriting all tests.
>
> When the gem_mmap ioctl is not available, transparently fallback to
> mmap_offset.
Unless we've done something in the kernel, with this we should expect to
see failures when object size approaches available system memory since as
we know the mmap_offset page fault handler tries to pin the entire object
which would fail for large objects. The old gem_mmap doesn't have this
limitation.
With pread/pwrite gone, the only option for large objects was to gem_mmap
and read/write but appears that will now go away too.
See e.g.
https://patchwork.freedesktop.org/patch/426749/?series=88561&rev=3
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2021-05-11 16:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 9:00 [igt-dev] [PATCH i-g-t] i915: Handle the case where legacy mmap is not available Maarten Lankhorst
2021-05-11 9:40 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-05-11 9:50 ` [igt-dev] [PATCH i-g-t] " Petri Latvala
2021-05-11 10:07 ` Maarten Lankhorst
2021-05-11 10:41 ` Petri Latvala
2021-05-11 10:48 ` [igt-dev] ✓ Fi.CI.IGT: success for " Patchwork
2021-05-11 16:19 ` Dixit, Ashutosh [this message]
2021-05-26 9:36 ` [igt-dev] [PATCH i-g-t] " Maarten Lankhorst
2021-05-18 15:08 ` [igt-dev] ✓ Fi.CI.BAT: success for i915: Handle the case where legacy mmap is not available (rev2) Patchwork
2021-05-19 3:52 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-06-18 13:45 ` [igt-dev] ✓ Fi.CI.BAT: success for i915: Handle the case where legacy mmap is not available (rev3) Patchwork
2021-06-18 15:02 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-06-24 1:30 ` [igt-dev] [PATCH i-g-t] i915: Handle the case where legacy mmap is not available Dixit, Ashutosh
2021-06-24 9:02 ` Maarten Lankhorst
2021-06-24 18:33 ` Dixit, Ashutosh
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=871radw8dl.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox