All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v4] drm/i915: clarify semaphore-ring interaction
Date: Mon, 21 May 2012 14:03:05 -0700	[thread overview]
Message-ID: <20120521140305.7421ef30@bwidawsk.net> (raw)
In-Reply-To: <1337589849_155240@CP5-2952>

On Mon, 21 May 2012 09:44:02 +0100
Chris Wilson <chris@chris-wilson.co.uk> wrote:

> On Sun, 20 May 2012 08:45:38 -0700, Ben Widawsky <ben@bwidawsk.net> wrote:
> > After Daniel split out this code, I think this makes more sense, and
> > looks nicer. Also added some comments to help the situation.
> > 
> > v2: Make signal_mbox be all rings for symmetric-ness.
> > v3: submitted the wrong version of the patch before.
> >   v2 had an issue with odd number of rings. The fix is to always emit an
> >   even number of instructions to the ring with mbox updates.
> > v4: I suck. The code should send out mbox updates for NUM_RINGS-1 *
> >   number of commands. Instead of NUM_RINGS * number of commands-1.
> > -ret = intel_ring_begin(ring, round_up((I915_NUM_RINGS) * 3, 2) + 4);
> > +ret = intel_ring_begin(ring, round_up((I915_NUM_RINGS-1) * 4, 2) + 4);
> 
> I'm honestly less enthralled about v4. I'd rather see that as a separate
> preparatory patch so that it is put into context.
> -Chris
> 

I can do that. Are you okay with the idea otherwise? This is really all
prep work for some HSW patches anyway.

-- 
Ben Widawsky, Intel Open Source Technology Center

  reply	other threads:[~2012-05-21 21:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-20 13:52 [PATCH v3] drm/i915: clarify semaphore-ring interaction Ben Widawsky
2012-05-20 15:45 ` [PATCH v4] " Ben Widawsky
2012-05-21  8:44   ` Chris Wilson
2012-05-21 21:03     ` Ben Widawsky [this message]
2012-05-21 21:40       ` Chris Wilson

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=20120521140305.7421ef30@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@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 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.