Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] lib/ioctl_wrappers: Keep IGT working without pread/pwrite ioctls
Date: Tue, 16 Mar 2021 11:46:08 -0700	[thread overview]
Message-ID: <87a6r3hr7z.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <c1e0796a-6970-c535-2080-a8ce4dd34f4b@linux.intel.com>

On Tue, 16 Mar 2021 02:16:14 -0700, Tvrtko Ursulin wrote:
> On 15/03/2021 23:19, Dixit, Ashutosh wrote:
> > On Mon, 15 Mar 2021 09:51:04 -0700, Tvrtko Ursulin wrote:
> >>> @@ -324,6 +325,70 @@ void gem_close(int fd, uint32_t handle)
> >>>	do_ioctl(fd, DRM_IOCTL_GEM_CLOSE, &close_bo);
> >>>    }
> >>>    +static bool is_cache_coherent(int fd, uint32_t handle)
> >>> +{
> >>> +	return gem_get_caching(fd, handle) != I915_CACHING_NONE;
> >>> +}
> >>> +
> >>> +static void mmap_write(int fd, uint32_t handle, uint64_t offset,
> >>> +		       const void *buf, uint64_t length)
> >>> +{
> >>> +	void *map = NULL;
> >>> +
> >>> +	if (!length)
> >>> +		return;
> >>> +
> >>> +	if (is_cache_coherent(fd, handle)) {
> >>> +		/* offset arg for mmap functions must be 0 */
> >>
> >> Offset and lenght I think. So I guess none of the tests used non-aligned
> >> access? Might be worth putting those two as asserts at the top of
> >> mmap_write and mmap_read.
> >
> > Hi Tvrtko, sorry I think you missed the logic. offset and length coming
> > into mmap_write() and mmap_read() are non-zero (so tests are using
> > non-aligned access). However __gem_mmap_offset() (called from
> > __gem_mmap__cpu_coherent() etc.) has an assert that needs the offset to be
> > 0 (which is what the comment above refers to). Therefore instead of doing
> > mmap(offset, length) below we do mmap(0, offset + length).
>
> But is offset + length is guaranteed to be page aligned? I thought mmap(2)
> requires it. Well, if it works obviously I was thinking wrong..

Yes, seems to be working. Offset for mmap(2) needs to be page aligned (the
length is probably bumped up to be page aligned by the kernel) and in the
case of __gem_mmap_offset() the offset supplied to mmap is the page aligned
offset returned by DRM_IOCTL_I915_GEM_MMAP_OFFSET.
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2021-03-16 18:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21  8:37 [igt-dev] [PATCH i-g-t] lib/ioctl_wrappers: Keep IGT working without pread/pwrite ioctls Ashutosh Dixit
2021-01-21 10:00 ` [igt-dev] ✓ Fi.CI.BAT: success for lib/ioctl_wrappers: Keep IGT working without pread/pwrite ioctls (rev7) Patchwork
2021-01-21 11:33 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-03-15 16:25 ` [igt-dev] ✓ Fi.CI.BAT: success for lib/ioctl_wrappers: Keep IGT working without pread/pwrite ioctls (rev8) Patchwork
2021-03-15 16:51 ` [igt-dev] [PATCH i-g-t] lib/ioctl_wrappers: Keep IGT working without pread/pwrite ioctls Tvrtko Ursulin
2021-03-15 23:19   ` Dixit, Ashutosh
2021-03-16  9:16     ` Tvrtko Ursulin
2021-03-16 18:46       ` Dixit, Ashutosh [this message]
2021-03-15 17:33 ` [igt-dev] ✗ Fi.CI.IGT: failure for lib/ioctl_wrappers: Keep IGT working without pread/pwrite ioctls (rev8) Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2021-03-15 22:53 [igt-dev] [PATCH i-g-t] lib/ioctl_wrappers: Keep IGT working without pread/pwrite ioctls Ashutosh Dixit
2020-09-30  3:40 Ashutosh Dixit
2020-10-02  9:36 ` Chris Wilson
2020-10-02 19:34   ` Dixit, Ashutosh
2020-09-16 20:11 Ashutosh Dixit
2020-09-06 23:43 Ashutosh Dixit
2020-09-09  7:03 ` Zbigniew Kempczyński
2020-09-06 17:49 Ashutosh Dixit
2020-09-04 20:25 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=87a6r3hr7z.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=tvrtko.ursulin@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