dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <deathsimple@vodafone.de>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [drm-next] drm/radeon: use IBs for VM page table updates
Date: Fri, 01 Feb 2013 17:35:08 +0100	[thread overview]
Message-ID: <510BEEBC.9070901@vodafone.de> (raw)
In-Reply-To: <CADnq5_PjUXB-iLSx8Q9XTZ+uddViXg4oQX0bc17BJvvERR1NDw@mail.gmail.com>

Am 01.02.2013 15:04, schrieb Alex Deucher:
> On Fri, Feb 1, 2013 at 5:25 AM, Christian König <deathsimple@vodafone.de> wrote:
>> [SNAP]
>> Wouldn't it make sense to use the IB functions (ib_get, ib_schedule,
>> ib_free) here instead of filling the IB structure manually?
> I tried that initially, but ran into several problems and it ended up
> being easier to just allocate and schedule the IB directly.  The IB
> functions have self contained code to deal with semaphores and fences
> that I couldn't figure out how to make work cleanly with the vm
> semaphore and fence.  radeon_ib_schedule() takes the ring lock so if I
> needed to do any direct ring manipuation prior, I'd need to drop the
> lock before calling ib_schedule().  Let me know if you have any
> suggestions.

Just send out an updated version of the patch, which seems to look quite 
a bit cleaner and still works fine (at least on my SI board).

Christian.

>
> Alex
>
>
>> Apart from that it looks quite good.
>>
>> Christian.
>>

      reply	other threads:[~2013-02-01 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 21:37 [drm-next] drm/radeon: use IBs for VM page table updates alexdeucher
2013-02-01 10:25 ` Christian König
2013-02-01 14:04   ` Alex Deucher
2013-02-01 16:35     ` 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=510BEEBC.9070901@vodafone.de \
    --to=deathsimple@vodafone.de \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.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