From: "Kalamarz, Lukasz" <lukasz.kalamarz@intel.com>
To: "Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t v3 3/4] lib/ioctl_wrapper: Implement __gem_mmap
Date: Mon, 14 Jan 2019 15:58:41 +0000 [thread overview]
Message-ID: <073882d119bba28aa05331d3b0c01ba89d64ccd2.camel@intel.com> (raw)
In-Reply-To: <a20400d9-4a2a-7d16-3be7-46d18aa897aa@intel.com>
On Fri, 2019-01-11 at 09:39 -0800, Daniele Ceraolo Spurio wrote:
>
> On 01/11/2019 08:15 AM, Lukasz Kalamarz wrote:
> > Previous implementation of __gem_mmap__cpu and __gem_mmap_wc only
> > differ with setting proper flag for caching. This patch implement
> > __gem_mmap, which merge those two functions into one.
> > v2: Reordered and splited this patch into two separete patches
>
> I think it make more sense for this to be a single patch together
> with
> the next one. Easier to review as well.
Will merge those tomorrow then :)
>
> > v3: Dropped unnecessary check
> >
> > Signed-off-by: Lukasz Kalamarz <lukasz.kalamarz@intel.com>
> > Cc: Michal Winiarski <michal.winiarski@intel.com>
> > Cc: Katarzyna Dec <katarzyna.dec@intel.com>
> > Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> > ---
> > lib/ioctl_wrappers.c | 36 ++++++++++++++++++++++++++++++++++++
> > 1 file changed, 36 insertions(+)
> >
> > diff --git a/lib/ioctl_wrappers.c b/lib/ioctl_wrappers.c
> > index f71f0e32..e9225da0 100644
> > --- a/lib/ioctl_wrappers.c
> > +++ b/lib/ioctl_wrappers.c
> > @@ -736,6 +736,42 @@ bool gem_mmap__has_wc(int fd)
> > return has_wc > 0;
> > }
> >
> > +/**
> > + * __gem_mmap:
> > + * @fd: open i915 drm file descriptor
> > + * @handle: gem buffer object handle
> > + * @offset: offset in the gem buffer of the mmap arena
> > + * @size: size of the mmap arena
> > + * @prot: memory protection bits as used by mmap()
> > + * @flags: flags used to determine caching
> > + *
> > + * This functions wraps up procedure to establish a memory mapping
> > through
> > + * direct cpu access, bypassing the gpu (valid for wc == false).
> > For wc == true
>
> This is a bit unclear IMO, as it sounds like the bypassing the GPU
> is
> only valid for wc == false, which isn't true since WC also bypasses
> the
> gpu caches.
Will change wording in description. My thought was that word 'also' in
second sentence will connect those two for a case, when wc == true.
----
Lukasz
>
> Also, instead of using wc == true/false I would say "wc mmappings"
> and
> "!wc mmappings" or something like that.
>
> Daniele
>
> > + * it also bypass cpu caches completely and GTT system agent (i.e.
> > there is no
> > + * automatic tiling of the mmapping through the fence registers).
> > + *
> > + * Returns: A pointer to the created memory mapping, NULL on
> > failure.
> > + */
> > +static void
> > +*__gem_mmap(int fd, uint32_t handle, uint64_t offset, uint64_t
> > size, unsigned int prot, uint64_t flags)
> > +{
> > + struct drm_i915_gem_mmap arg;
> > +
> > + memset(&arg, 0, sizeof(arg));
> > + arg.handle = handle;
> > + arg.offset = offset;
> > + arg.size = size;
> > + arg.flags = flags;
> > +
> > + if (igt_ioctl(fd, DRM_IOCTL_I915_GEM_MMAP, &arg))
> > + return NULL;
> > +
> > + VG(VALGRIND_MAKE_MEM_DEFINED(from_user_pointer(arg.addr_ptr),
> > arg.size));
> > +
> > + errno = 0;
> > + return from_user_pointer(arg.addr_ptr);
> > +}
> > +
> > /**
> > * __gem_mmap__wc:
> > * @fd: open i915 drm file descriptor
> >
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-01-14 15:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 16:15 [igt-dev] [PATCH i-g-t v3 1/4] lib/ioctl_wrapper: use defines for get_param instead of param number Lukasz Kalamarz
2019-01-11 16:15 ` [igt-dev] [PATCH i-g-t v3 2/4] lib/igt_dummyload: use gem_mmap__cpu and gem_mmap__wc when applicable Lukasz Kalamarz
2019-01-11 17:26 ` Daniele Ceraolo Spurio
2019-01-11 16:15 ` [igt-dev] [PATCH i-g-t v3 3/4] lib/ioctl_wrapper: Implement __gem_mmap Lukasz Kalamarz
2019-01-11 17:39 ` Daniele Ceraolo Spurio
2019-01-14 15:58 ` Kalamarz, Lukasz [this message]
2019-01-11 16:15 ` [igt-dev] [PATCH i-g-t v3 4/4] lib/ioctl_wrapper: Use __gem_mmap within __gem_mmap__cpu/wc Lukasz Kalamarz
2019-01-11 16:41 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,v3,1/4] lib/ioctl_wrapper: use defines for get_param instead of param number Patchwork
2019-01-11 17:54 ` [igt-dev] [PATCH i-g-t v3 1/4] " Daniele Ceraolo Spurio
2019-01-14 15:55 ` Kalamarz, Lukasz
2019-01-14 18:05 ` Daniele Ceraolo Spurio
2019-01-11 21:43 ` [igt-dev] ✓ Fi.CI.IGT: success for series starting with [i-g-t,v3,1/4] " 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=073882d119bba28aa05331d3b0c01ba89d64ccd2.camel@intel.com \
--to=lukasz.kalamarz@intel.com \
--cc=daniele.ceraolospurio@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