From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 1/2] lib/ioctl_wrappers: Keep IGT working without pread/pwrite ioctls
Date: Fri, 04 Sep 2020 16:34:18 -0700 [thread overview]
Message-ID: <87zh655d6t.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20200904162026.10956-1-ashutosh.dixit@intel.com>
On Fri, 04 Sep 2020 09:20:25 -0700, Ashutosh Dixit wrote:
>
> The general direction at this time is to phase out pread/write ioctls
> and not support them in future products. This means IGT must be
> modified to handle the absence of pread/write ioctls. This patch does
> this as follows:
>
> * __gem_read, gem_read, __gem_write and gem_write calls which are
> wrappers around the pread/pwrite ioctls have been renamed to
> __gem_pread, gem_pread, __gem_pwrite and gem_pwrite. These will now
> only be used where the pread/pwrite ioctls must absolutely be used,
> such as tests which test these ioctls or must otherwise only use the
> pread/pwrite ioctl's.
It seemed to me that these new functions (__gem_pread, gem_pread,
__gem_pwrite and gem_pwrite) were not needed after all since the callers of
these functions would anyway have to call gem_require_pread_pwrite() to
skip when the pread/pwrite ioctls were unavailable. Therefore
gem_require_pread_pwrite() itself indicates that only the pread/pwrite
ioctls must be used. Therefore I have dropped __gem_pread, gem_pread,
__gem_pwrite and gem_pwrite in v2. This results in further simplification
and also the two previous patches have been squashed into a single patch in
v2.
> * The new gem_read and gem_write function calls are now treated as
> general purpose calls to read/write to a gem object. They now try
> doing the read/write using the pread/pwrite ioctls first but when
> these ioctls are unavailable they fall back to doing the read/write
> using a combination of mmap and memcpy.
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-09-04 23:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 16:20 [igt-dev] [PATCH i-g-t 1/2] lib/ioctl_wrappers: Keep IGT working without pread/pwrite ioctls Ashutosh Dixit
2020-09-04 16:20 ` [igt-dev] [PATCH i-g-t 2/2] tests/i915: Convert remaining sites to gem_pread/gem_pwrite Ashutosh Dixit
2020-09-04 19:55 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] lib/ioctl_wrappers: Keep IGT working without pread/pwrite ioctls Patchwork
2020-09-04 23:34 ` Dixit, Ashutosh [this message]
2020-09-05 4:20 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2020-09-02 0:40 [igt-dev] [PATCH i-g-t 1/2] " Ashutosh Dixit
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=87zh655d6t.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.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