All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Oscar Mateo <oscar.mateo@intel.com>
Cc: intel-gfx@lists.freedesktop.org, Ben Widawsky <ben@bwidawsk.net>
Subject: Re: [PATCH] drm/i915: Allow null render state batchbuffers bigger than one page
Date: Tue, 02 May 2017 12:17:04 +0300	[thread overview]
Message-ID: <8737cnd3e7.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20170428165313.GA20095@nuc-i3427.alporthouse.com>

Chris Wilson <chris@chris-wilson.co.uk> writes:

> On Fri, Apr 28, 2017 at 09:11:06AM +0000, Oscar Mateo wrote:
>> The new batchbuffer for CNL surpasses the 4096 byte mark.
>> 
>> Cc: Mika Kuoppala <mika.kuoppala@intel.com>
>> Cc: Ben Widawsky <ben@bwidawsk.net>
>> Signed-off-by: Oscar Mateo <oscar.mateo@intel.com>
>
> Evil, 4k+ of nothing-ness that userspace then has to configure for itself
> for correctness anyway.
>
> Patch looks ok, but still question the sanity.

Is there a requirement for CNL to init the renderstate?

I would like to drop the render state init from CNL if
we can't find evidence that it needs it. Bspec indicates
that it doesnt.

-Mika

> -Chris
>
> -- 
> Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-05-02  9:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-28  9:11 [PATCH] drm/i915: Allow null render state batchbuffers bigger than one page Oscar Mateo
2017-04-28 16:31 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-04-28 16:53 ` [PATCH] " Chris Wilson
2017-05-02  9:17   ` Mika Kuoppala [this message]
2017-05-02  9:31     ` Oscar Mateo
2017-05-03  8:52       ` Mika Kuoppala
2017-05-03  9:12         ` Oscar Mateo
2017-05-03 16:31           ` Chris Wilson
2017-07-13 22:28             ` Rodrigo Vivi
2017-07-14 14:52               ` Oscar Mateo
2017-07-14 15:08                 ` Chris Wilson
2017-07-18 15:15                   ` Oscar Mateo
2017-08-24  0:01                     ` Rodrigo Vivi
2017-08-24 22:39                       ` Oscar Mateo
2017-08-24 23:00                         ` Rodrigo Vivi
2017-10-05  4:34                           ` Rodrigo Vivi
2017-10-10 10:25                             ` Chris Wilson
2017-10-10 10:29                               ` Chris Wilson
2017-10-12 22:31                                 ` Rodrigo Vivi

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=8737cnd3e7.fsf@gaia.fi.intel.com \
    --to=mika.kuoppala@linux.intel.com \
    --cc=ben@bwidawsk.net \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=oscar.mateo@intel.com \
    /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.