From: "Deucher, Alexander" <Alexander.Deucher-5C7GfCeVMHo@public.gmane.org>
To: "'Christian König'"
<deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>,
"amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Cc: "maraeo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
<maraeo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: RE: CPU mapping of split VRAM buffers
Date: Wed, 29 Mar 2017 15:36:41 +0000 [thread overview]
Message-ID: <BN6PR12MB1652DD0CE69D4972798E40DEF7350@BN6PR12MB1652.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1490792146-2218-1-git-send-email-deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
> -----Original Message-----
> From: amd-gfx [mailto:amd-gfx-bounces@lists.freedesktop.org] On Behalf
> Of Christian König
> Sent: Wednesday, March 29, 2017 8:56 AM
> To: amd-gfx@lists.freedesktop.org
> Cc: maraeo@gmail.com
> Subject: CPU mapping of split VRAM buffers
>
> Hi guys,
>
> this set implements CPU mapping of split VRAM buffers and could
> help with some performance issues regarding this.
>
> Please review and/or comment,
Should probably resend them to dri-devel as well since they touch core ttm.
Alex
> Christian.
>
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2017-03-29 15:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 12:55 CPU mapping of split VRAM buffers Christian König
[not found] ` <1490792146-2218-1-git-send-email-deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-03-29 12:55 ` [PATCH 1/6] drm/ttm: cleanup and optimize ttm_bo_mem_compat Christian König
2017-03-30 6:38 ` Michel Dänzer
[not found] ` <0aeb9046-86c6-f14f-490e-cbf74079e107-otUistvHUpPR7s880joybQ@public.gmane.org>
2017-03-30 8:41 ` Christian König
2017-03-29 12:55 ` [PATCH 2/6] drm/ttm: add io_mem_pfn callback Christian König
2017-03-30 6:39 ` Michel Dänzer
2017-03-29 12:55 ` [PATCH 3/6] drm/ttm: add TTM_PL_FLAG_CONTIGUOUS Christian König
[not found] ` <1490792146-2218-4-git-send-email-deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-03-30 6:39 ` Michel Dänzer
2017-03-29 12:55 ` [PATCH 4/6] drm/amdgpu: drop alpha support Christian König
2017-03-30 6:39 ` Michel Dänzer
2017-03-30 13:09 ` Alex Deucher
2017-03-30 13:22 ` Christian König
2017-03-31 1:07 ` Michel Dänzer
2017-03-31 7:09 ` Christian König
2017-03-31 7:19 ` Michel Dänzer
2017-03-29 12:55 ` [PATCH 5/6] drm/amdgpu: use TTM_PL_FLAG_CONTIGUOUS Christian König
2017-03-29 12:55 ` [PATCH 6/6] drm/amdgpu: handle CPU access for split VRAM buffers Christian König
2017-03-29 15:36 ` Deucher, Alexander [this message]
[not found] ` <BN6PR12MB1652DD0CE69D4972798E40DEF7350-/b2+HYfkarQqUD6E6FAiowdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-03-29 17:44 ` CPU mapping of " Christian König
2017-03-30 6:42 ` Michel Dänzer
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=BN6PR12MB1652DD0CE69D4972798E40DEF7350@BN6PR12MB1652.namprd12.prod.outlook.com \
--to=alexander.deucher-5c7gfcevmho@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org \
--cc=maraeo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.