From: Scott D Phillips <scott.d.phillips@intel.com>
To: Jordan Justen <jordan.l.justen@intel.com>,
IGT GPU Tools <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t 2/3] tools/aubdump: Add bitmap to track gtt pages that have been mapped
Date: Wed, 07 Mar 2018 08:20:04 -0800 [thread overview]
Message-ID: <87a7vjvowb.fsf@intel.com> (raw)
In-Reply-To: <20180307083121.2955-2-jordan.l.justen@intel.com>
Jordan Justen <jordan.l.justen@intel.com> writes:
> This will allow us to map ranges as they are used, but prevents
> remapping already mapped regions.
>
> By mapping ranges as they are used, we can support pinned pages
> without having to map all pages of the first 32-bits.
>
> v2:
> * Make bitmap manipulation functions independent from 4k page size.
> Maybe will be usable also for 1GB pages with PPGTT.
>
> Cc: Scott D Phillips <scott.d.phillips@intel.com>
> Signed-off-by: Jordan Justen <jordan.l.justen@intel.com>
lgtm
Reviewed-b: Scott D Phillips <scott.d.phillips@intel.com>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-03-07 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 8:31 [igt-dev] [PATCH i-g-t 1/3] tools/aubdump: Add gen8_map_range Jordan Justen
2018-03-07 8:31 ` [igt-dev] [PATCH i-g-t 2/3] tools/aubdump: Add bitmap to track gtt pages that have been mapped Jordan Justen
2018-03-07 16:20 ` Scott D Phillips [this message]
2018-03-07 8:31 ` [igt-dev] [PATCH i-g-t 3/3] tools/aubdump: For gen10+ support addresses up to 4GB Jordan Justen
2018-03-07 8:42 ` Jordan Justen
2018-03-07 16:21 ` Scott D Phillips
2018-03-07 8:43 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/3] tools/aubdump: Add gen8_map_range Patchwork
2018-03-07 16:09 ` [igt-dev] [PATCH i-g-t 1/3] " Scott D Phillips
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=87a7vjvowb.fsf@intel.com \
--to=scott.d.phillips@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jordan.l.justen@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