From: Matthew Auld <matthew.auld@intel.com>
To: Arunpravin <Arunpravin.PaneerSelvam@amd.com>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
amd-gfx@lists.freedesktop.org
Cc: alexander.deucher@amd.com, tzimmermann@suse.de, christian.koenig@amd.com
Subject: Re: [Intel-gfx] [PATCH 4/7] drm/selftests: add drm buddy optimistic testcase
Date: Tue, 8 Feb 2022 10:12:07 +0000 [thread overview]
Message-ID: <b62abf9f-1e2a-b75f-1505-9f37024d2f8d@intel.com> (raw)
In-Reply-To: <20220203133234.3350-4-Arunpravin.PaneerSelvam@amd.com>
On 03/02/2022 13:32, Arunpravin wrote:
> create a mm with one block of each order available, and
> try to allocate them all.
>
> Signed-off-by: Arunpravin <Arunpravin.PaneerSelvam@amd.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
next prev parent reply other threads:[~2022-02-08 10:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 13:32 [Intel-gfx] [PATCH 1/7] drm/selftests: Move i915 buddy selftests into drm Arunpravin
2022-02-03 13:32 ` [Intel-gfx] [PATCH 2/7] drm/selftests: add drm buddy alloc limit testcase Arunpravin
2022-02-08 9:40 ` Matthew Auld
2022-02-22 19:07 ` Arunpravin
2022-02-03 13:32 ` [Intel-gfx] [PATCH 3/7] drm/selftests: add drm buddy alloc range testcase Arunpravin
2022-02-08 10:03 ` Matthew Auld
2022-02-03 13:32 ` [Intel-gfx] [PATCH 4/7] drm/selftests: add drm buddy optimistic testcase Arunpravin
2022-02-08 10:12 ` Matthew Auld [this message]
2022-02-03 13:32 ` [Intel-gfx] [PATCH 5/7] drm/selftests: add drm buddy pessimistic testcase Arunpravin
2022-02-08 10:17 ` Matthew Auld
2022-02-03 13:32 ` [Intel-gfx] [PATCH 6/7] drm/selftests: add drm buddy smoke testcase Arunpravin
2022-02-08 10:22 ` Matthew Auld
2022-02-03 13:32 ` [Intel-gfx] [PATCH 7/7] drm/selftests: add drm buddy pathological testcase Arunpravin
2022-02-08 10:26 ` Matthew Auld
2022-02-03 14:12 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [1/7] drm/selftests: Move i915 buddy selftests into drm Patchwork
2022-02-03 14:33 ` [Intel-gfx] [PATCH 1/7] " Christian König
2022-02-08 10:35 ` Matthew Auld
2022-02-22 18:35 ` Arunpravin
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=b62abf9f-1e2a-b75f-1505-9f37024d2f8d@intel.com \
--to=matthew.auld@intel.com \
--cc=Arunpravin.PaneerSelvam@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tzimmermann@suse.de \
/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