dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <deathsimple@vodafone.de>
To: "Zhou, David(ChunMing)" <David1.Zhou@amd.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: Fw: add find_bo_from_cpu_mapping interface
Date: Thu, 3 Dec 2015 20:01:41 +0100	[thread overview]
Message-ID: <56609195.1070006@vodafone.de> (raw)
In-Reply-To: <CY1PR12MB019921C7571E8CBD3165A646B40D0@CY1PR12MB0199.namprd12.prod.outlook.com>


[-- Attachment #1.1: Type: text/plain, Size: 730 bytes --]

Well a bit background would probably help here.

This is useful because certain applications are hopelessly braindead and 
pass a CPU which they got from the driver in the first place and which 
is a pointer to a memory mapped BO back to the driver.

With this IOCTL the driver is capable to handle this case gracefully and 
use the original BO for example as replacement for an userptr.

Regards,
Christian.

On 03.12.2015 14:02, Zhou, David(ChunMing) wrote:
>
>
> UMD can find the bo by the cpu address of BO. Any comments?
>
>
> Regards,
>
> David Zhou
>
>
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel


[-- Attachment #1.2: Type: text/html, Size: 2420 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2015-12-03 19:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CY1PR12MB019990978B7B487F0BD2A9BDB40D0@CY1PR12MB0199.namprd12.prod.outlook.com>
2015-12-03 13:02 ` Fw: add find_bo_from_cpu_mapping interface Zhou, David(ChunMing)
2015-12-03 19:01   ` Christian König [this message]

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=56609195.1070006@vodafone.de \
    --to=deathsimple@vodafone.de \
    --cc=David1.Zhou@amd.com \
    --cc=dri-devel@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