From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: "Christian König" <christian.koenig@amd.com>,
dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, Matthew Auld <matthew.auld@intel.com>
Subject: Re: [Intel-gfx] [PATCH v2 3/7] drm/ttm: Use the BIT macro for the TTM_TT_FLAGs
Date: Thu, 9 Mar 2023 08:06:07 +0100 [thread overview]
Message-ID: <68a6a01a-6a98-0f9e-9d4b-ede48ac6665f@linux.intel.com> (raw)
In-Reply-To: <c1a9f255-9ee4-c020-9767-afb2591faaec@amd.com>
Hi, Christian,
Thanks for reviewing these.
Ack to merge reviewed patches through drm-misc-next?
Thanks,
Thomas
On 3/8/23 09:49, Christian König wrote:
> Am 07.03.23 um 15:46 schrieb Thomas Hellström:
>> New code is recommended to use the BIT macro instead of the explicit
>> shifts. Change the older defines so that we can keep the style
>> consistent
>> with upcoming changes.
>>
>> v2:
>> - Also change the value of the _PRIV_POPULATED bit (Christian König)
>>
>> Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
>
> Reviewed-by: Christian König <christian.koenig@amd.com>
>
>> ---
>> include/drm/ttm/ttm_tt.h | 10 +++++-----
>> 1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/include/drm/ttm/ttm_tt.h b/include/drm/ttm/ttm_tt.h
>> index b7d3f3843f1e..977ca195a536 100644
>> --- a/include/drm/ttm/ttm_tt.h
>> +++ b/include/drm/ttm/ttm_tt.h
>> @@ -83,12 +83,12 @@ struct ttm_tt {
>> * set by TTM after ttm_tt_populate() has successfully
>> returned, and is
>> * then unset when TTM calls ttm_tt_unpopulate().
>> */
>> -#define TTM_TT_FLAG_SWAPPED (1 << 0)
>> -#define TTM_TT_FLAG_ZERO_ALLOC (1 << 1)
>> -#define TTM_TT_FLAG_EXTERNAL (1 << 2)
>> -#define TTM_TT_FLAG_EXTERNAL_MAPPABLE (1 << 3)
>> +#define TTM_TT_FLAG_SWAPPED BIT(0)
>> +#define TTM_TT_FLAG_ZERO_ALLOC BIT(1)
>> +#define TTM_TT_FLAG_EXTERNAL BIT(2)
>> +#define TTM_TT_FLAG_EXTERNAL_MAPPABLE BIT(3)
>> -#define TTM_TT_FLAG_PRIV_POPULATED (1U << 31)
>> +#define TTM_TT_FLAG_PRIV_POPULATED BIT(4)
>> uint32_t page_flags;
>> /** @num_pages: Number of pages in the page array. */
>> uint32_t num_pages;
>
next prev parent reply other threads:[~2023-03-09 7:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 14:46 [Intel-gfx] [PATCH v2 0/7] drm/ttm: Small fixes / cleanups in prep for shrinking Thomas Hellström
2023-03-07 14:46 ` [Intel-gfx] [PATCH v2 1/7] drm/ttm: Fix a NULL pointer dereference Thomas Hellström
2023-03-07 16:55 ` Christian König
2023-03-07 17:46 ` Thomas Hellström
2023-03-07 14:46 ` [Intel-gfx] [PATCH v2 2/7] drm/ttm/pool: Fix ttm_pool_alloc error path Thomas Hellström
2023-03-08 8:48 ` Christian König
2023-03-08 8:58 ` Thomas Hellström
2023-03-07 14:46 ` [Intel-gfx] [PATCH v2 3/7] drm/ttm: Use the BIT macro for the TTM_TT_FLAGs Thomas Hellström
2023-03-08 8:49 ` Christian König
2023-03-09 7:06 ` Thomas Hellström [this message]
2023-03-09 8:06 ` Christian König
2023-03-07 14:46 ` [Intel-gfx] [PATCH v2 4/7] drm/ttm: Unexport ttm_global_swapout() Thomas Hellström
2023-03-08 8:49 ` Christian König
2023-03-07 14:46 ` [Intel-gfx] [PATCH v2 5/7] drm/ttm: Don't print error message if eviction was interrupted Thomas Hellström
2023-03-08 8:50 ` Christian König
2023-03-07 14:46 ` [Intel-gfx] [PATCH v2 6/7] drm/ttm: Reduce the number of used allocation orders for TTM pages Thomas Hellström
2023-03-07 19:42 ` kernel test robot
2023-03-08 9:15 ` Christian König
2023-03-08 9:22 ` Thomas Hellström
2023-03-07 14:46 ` [Intel-gfx] [PATCH v2 7/7] drm/ttm: Make the call to ttm_tt_populate() interruptible when faulting Thomas Hellström
2023-03-07 21:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/ttm: Small fixes / cleanups in prep for shrinking Patchwork
2023-03-09 12:09 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=68a6a01a-6a98-0f9e-9d4b-ede48ac6665f@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--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