All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Olšák" <maraeo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Deucher, Alexander" <Alexander.Deucher-5C7GfCeVMHo@public.gmane.org>
Cc: "Koenig,
	Christian" <Christian.Koenig-5C7GfCeVMHo@public.gmane.org>,
	amd-gfx mailing list
	<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: [PATCH] drm/amdgpu: reserve GDS resources statically
Date: Thu, 13 Sep 2018 15:04:35 -0400	[thread overview]
Message-ID: <CAAxE2A7Wd9wwQL-43eFi8wjs+oD6-cHWR95nM1U44_yJP6Q4YA@mail.gmail.com> (raw)
In-Reply-To: <BN6PR12MB180977B44E93B5357C5145B3F71A0-/b2+HYfkarSEx6ez0IUAagdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>

I was thinking about that too, but it would be too much trouble for
something we don't need.

Marek

On Thu, Sep 13, 2018 at 2:57 PM, Deucher, Alexander
<Alexander.Deucher@amd.com> wrote:
> Why don't we just fix up the current GDS code so it works the same as vram
> and then we can add a new CS or context flag to ignore the current static
> allocation for gfx.  We can ignore data persistence if it's too much
> trouble.  Assume you always have to init the memory before you use it.
> That's already the case.
>
>
> Alex
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  parent reply	other threads:[~2018-09-13 19:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-12 20:33 [PATCH] drm/amdgpu: reserve GDS resources statically Marek Olšák
     [not found] ` <20180912203358.2172-1-maraeo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-09-13  8:40   ` Christian König
     [not found]     ` <904d7dbb-eeec-03a0-92c8-5c5170a7b43c-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-09-13 15:27       ` Marek Olšák
     [not found]         ` <CAAxE2A44Brp==LORVMuKkU7o+O4wGiBEx7T8yYyMZd_b2uh6Tw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-09-13 17:26           ` Christian König
     [not found]             ` <7db280c8-e013-6865-aef7-7c1d5640b875-5C7GfCeVMHo@public.gmane.org>
2018-09-13 18:20               ` Marek Olšák
     [not found]                 ` <CAAxE2A64kojhUe+drdccAkSE4kTZP94OyMmG+xqH9wdDYgKATg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-09-13 18:57                   ` Deucher, Alexander
     [not found]                     ` <BN6PR12MB180977B44E93B5357C5145B3F71A0-/b2+HYfkarSEx6ez0IUAagdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2018-09-13 19:04                       ` Marek Olšák [this message]
     [not found]                         ` <CAAxE2A7Wd9wwQL-43eFi8wjs+oD6-cHWR95nM1U44_yJP6Q4YA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-09-13 21:01                           ` Marek Olšák
     [not found]                             ` <CAAxE2A5e6Rx_eZc40E=5ow+qwrkd2RoOFPbPBHBz3wCi3rusAg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-09-14  6:59                               ` Christian König

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=CAAxE2A7Wd9wwQL-43eFi8wjs+oD6-cHWR95nM1U44_yJP6Q4YA@mail.gmail.com \
    --to=maraeo-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=Alexander.Deucher-5C7GfCeVMHo@public.gmane.org \
    --cc=Christian.Koenig-5C7GfCeVMHo@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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.