From: Ramalingam C <ramalingam.c@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
Matthew Auld <matthew.auld@intel.com>
Subject: Re: [Intel-gfx] [PATCH v4 2/2] drm/i915: Create dumb buffer from LMEM
Date: Mon, 9 Dec 2019 17:27:01 +0530 [thread overview]
Message-ID: <20191209115701.GA22862@intel.com> (raw)
In-Reply-To: <157555148978.22727.11669212602896257587@skylake-alporthouse-com>
On 2019-12-05 at 13:11:29 +0000, Chris Wilson wrote:
> Quoting Ramalingam C (2019-12-05 13:02:40)
> > On 2019-12-05 at 12:20:12 +0000, Chris Wilson wrote:
> > > Quoting Matthew Auld (2019-12-05 12:12:19)
> > > > We would still need to clear the object(maybe I915_BO_ALLOC_CLEARED?)
> > > > in order to pass the IGTs. We also need to adjust dumb_buffer.c, since
> > > > that uses get_avail_ram_mb() for always_clear, but maybe we need the
> > > > query region uapi for that?
> > >
> > > Hmm. Questions over the maximum size for dumb buffer, maximum number of
> > > dumb buffers, etc, should be addressed to the dumb API. So some form of
> > > drmGetCap() ?
> > Chris, Is this suggestion to add this capability probing through a new IOCTL for
> > dumb APIs? Please clarify.
>
> I don't think we need a new ioctl, as drm_getcap already covers the dumb
> buffer API. We just need to expose the limits of the dumb buffer API
> through it.
>
> The 2 that spring to mind are maximum size of individual buffer and
> maximum size of total dumb buffers.
Will there be question for userspace for this extension or no?
AFAIK There is no consumer except IGT.
-Ram
> (The latter may be infinite for
> drivers that allow swapping of inactive buffers.) There was a request on
> irc for something like this as well, but I'm not aware of the context.
> -Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-12-09 11:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 6:54 [PATCH v4 1/2] drm/i915: lookup for mem_region of a mem_type Ramalingam C
2019-12-02 6:54 ` [Intel-gfx] " Ramalingam C
2019-12-02 6:54 ` [PATCH v4 2/2] drm/i915: Create dumb buffer from LMEM Ramalingam C
2019-12-02 6:54 ` [Intel-gfx] " Ramalingam C
2019-12-05 12:12 ` Matthew Auld
2019-12-05 12:20 ` Chris Wilson
2019-12-05 13:02 ` Ramalingam C
2019-12-05 13:11 ` Chris Wilson
2019-12-09 11:57 ` Ramalingam C [this message]
2019-12-09 12:03 ` Chris Wilson
2019-12-09 12:05 ` Ramalingam C
2019-12-05 12:59 ` Ramalingam C
2019-12-02 7:01 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [v4,1/2] drm/i915: lookup for mem_region of a mem_type Patchwork
2019-12-02 7:01 ` [Intel-gfx] " Patchwork
2019-12-02 7:31 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-12-02 7:31 ` [Intel-gfx] " Patchwork
2019-12-05 11:40 ` [Intel-gfx] [PATCH v4 1/2] " Matthew Auld
-- strict thread matches above, loose matches on Subject: below --
2019-11-06 16:08 Ramalingam C
2019-11-06 16:08 ` [PATCH v4 2/2] drm/i915: Create dumb buffer from LMEM Ramalingam C
2019-11-06 16:08 ` [Intel-gfx] " Ramalingam C
2019-11-07 9:45 ` Chris Wilson
2019-11-07 9:45 ` [Intel-gfx] " 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=20191209115701.GA22862@intel.com \
--to=ramalingam.c@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox