From: Ramalingam C <ramalingam.c@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [RFC 2/2] tests/dumb_duffer: extending for lmem coverage.
Date: Mon, 6 Jan 2020 12:13:04 +0530 [thread overview]
Message-ID: <20200106064302.GA29868@intel.com> (raw)
In-Reply-To: <157813602671.11773.15215167026114870941@skylake-alporthouse-com>
On 2020-01-04 at 11:07:06 +0000, Chris Wilson wrote:
> Quoting Ramalingam C (2020-01-04 10:08:26)
> > if lmem is available on intel platforms, dumb buffers are created out of
> > lmem. Hence tests are extended to cover the dumb buffers from lmem.
>
> Which has what to do with the dumb API?
Chris,
API is agnostic to memory region agnostic. But the page boundary that
needs to be considered for tests are different between LMEM and SMEM.
And also we need to get the total local memory available for the
create-clear test.
These changes were done in this patch.
-Ram
> -Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-01-06 6:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 10:08 [igt-dev] [RFC 1/2] lib/i915/intel_memory_region: wrappers for memory regions ops Ramalingam C
2020-01-04 10:08 ` [igt-dev] [RFC 2/2] tests/dumb_duffer: extending for lmem coverage Ramalingam C
2020-01-04 11:07 ` Chris Wilson
2020-01-06 6:43 ` Ramalingam C [this message]
2020-01-06 12:00 ` Chris Wilson
2020-01-04 10:42 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [RFC,1/2] lib/i915/intel_memory_region: wrappers for memory regions ops Patchwork
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=20200106064302.GA29868@intel.com \
--to=ramalingam.c@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@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