From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Nick Hoath <nicholas.hoath@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [RFC] drm/i195: Add flag to enable virtual mappings above 4Gb
Date: Wed, 18 Mar 2015 17:08:23 +0000 [thread overview]
Message-ID: <5509B107.4040004@linux.intel.com> (raw)
In-Reply-To: <1426697873-14389-1-git-send-email-nicholas.hoath@intel.com>
On 03/18/2015 04:57 PM, Nick Hoath wrote:
> Wa32bitGeneralStateOffset & Wa32bitInstructionBaseOffset hardware
> workarounds require that GeneralStateOffset & InstructionBaseOffset
> are restricted to a 32 bit address space.
>
> This is a preparatory patch prior to supporting 64bit virtual memory
> allocations.
>
> Allow the user space to flag that a mapping can occur beyond
> the 32bit limit. This allows backward compatibility and user space
> drivers that haven't been enhanced to support these workarounds to
> function.
Just on the naming..
Maybe the whole thing would better be named "full mem", "full range" or
something like that?
"Hi mem", especially since the name is used in the userspace API has so
much historical baggage meaning it needs to be _only_ in the special
high memory range.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-03-18 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 16:57 [RFC] drm/i195: Add flag to enable virtual mappings above 4Gb Nick Hoath
2015-03-18 17:08 ` Tvrtko Ursulin [this message]
2015-03-19 16:29 ` Daniel Vetter
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=5509B107.4040004@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nicholas.hoath@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