From: Jani Nikula <jani.nikula@intel.com>
To: "Christian König" <christian.koenig@amd.com>,
dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, Huang Rui <ray.huang@amd.com>
Subject: Re: [Intel-gfx] [PATCH] drm/ttm: let struct ttm_device_funcs be placed in rodata
Date: Thu, 09 Mar 2023 14:49:03 +0200 [thread overview]
Message-ID: <87bkl29jk0.fsf@intel.com> (raw)
In-Reply-To: <d844e8f4-dbfe-15a6-32db-4ab928fad77d@amd.com>
On Thu, 09 Mar 2023, Christian König <christian.koenig@amd.com> wrote:
> Am 09.03.23 um 13:37 schrieb Jani Nikula:
>> Make the struct ttm_device_funcs pointers const so the data can be placed in rodata.
>>
>> Cc: Christian Koenig <christian.koenig@amd.com>
>> Cc: Huang Rui <ray.huang@amd.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Good idea, Reviewed-by: Christian König <christian.koenig@amd.com>
Thanks!
> Should I push it to drm-misc-next or do you need it on some other branch?
Go ahead, I'm not urgently depending on it.
BR,
Jani.
>
> Christian.
>
>> ---
>> drivers/gpu/drm/ttm/ttm_device.c | 2 +-
>> include/drm/ttm/ttm_device.h | 4 ++--
>> 2 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/ttm/ttm_device.c b/drivers/gpu/drm/ttm/ttm_device.c
>> index ae2f19dc9f81..a71bb1362de4 100644
>> --- a/drivers/gpu/drm/ttm/ttm_device.c
>> +++ b/drivers/gpu/drm/ttm/ttm_device.c
>> @@ -190,7 +190,7 @@ EXPORT_SYMBOL(ttm_device_swapout);
>> * Returns:
>> * !0: Failure.
>> */
>> -int ttm_device_init(struct ttm_device *bdev, struct ttm_device_funcs *funcs,
>> +int ttm_device_init(struct ttm_device *bdev, const struct ttm_device_funcs *funcs,
>> struct device *dev, struct address_space *mapping,
>> struct drm_vma_offset_manager *vma_manager,
>> bool use_dma_alloc, bool use_dma32)
>> diff --git a/include/drm/ttm/ttm_device.h b/include/drm/ttm/ttm_device.h
>> index 56e82ba2d046..c22f30535c84 100644
>> --- a/include/drm/ttm/ttm_device.h
>> +++ b/include/drm/ttm/ttm_device.h
>> @@ -223,7 +223,7 @@ struct ttm_device {
>> * @funcs: Function table for the device.
>> * Constant after bo device init
>> */
>> - struct ttm_device_funcs *funcs;
>> + const struct ttm_device_funcs *funcs;
>>
>> /**
>> * @sysman: Resource manager for the system domain.
>> @@ -287,7 +287,7 @@ static inline void ttm_set_driver_manager(struct ttm_device *bdev, int type,
>> bdev->man_drv[type] = manager;
>> }
>>
>> -int ttm_device_init(struct ttm_device *bdev, struct ttm_device_funcs *funcs,
>> +int ttm_device_init(struct ttm_device *bdev, const struct ttm_device_funcs *funcs,
>> struct device *dev, struct address_space *mapping,
>> struct drm_vma_offset_manager *vma_manager,
>> bool use_dma_alloc, bool use_dma32);
>
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-03-09 12:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 12:37 [Intel-gfx] [PATCH] drm/ttm: let struct ttm_device_funcs be placed in rodata Jani Nikula
2023-03-09 12:45 ` Christian König
2023-03-09 12:49 ` Jani Nikula [this message]
2023-05-16 8:05 ` Jani Nikula
2023-05-16 16:11 ` Alex Deucher
2023-05-17 9:26 ` Jani Nikula
2023-03-09 12:52 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2023-03-09 13:15 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-03-11 2:42 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-05-16 16:08 ` [Intel-gfx] [PATCH] " Thomas Zimmermann
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=87bkl29jk0.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ray.huang@amd.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;
as well as URLs for NNTP newsgroup(s).