Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Das, Nirmoy" <nirmoy.das@linux.intel.com>
To: Andrzej Hajda <andrzej.hajda@intel.com>,
	Nirmoy Das <nirmoy.das@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: matthew.auld@intel.com
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915: Use helper func to find out map type
Date: Tue, 20 Dec 2022 12:33:06 +0200	[thread overview]
Message-ID: <c88f147a-c4bd-c988-d3ec-8a53c6bf7acd@linux.intel.com> (raw)
In-Reply-To: <660fc517-82ad-1ecf-17c8-6f9017caaddd@intel.com>


On 12/19/2022 8:04 PM, Andrzej Hajda wrote:
> On 19.12.2022 12:29, Nirmoy Das wrote:
>> Use i915_coherent_map_type() function to find out
>> map_type of the shmem obj.
>>
>> v2: handle non-llc platform(Matt)
>>
>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
>> ---
>>   drivers/gpu/drm/i915/gt/shmem_utils.c | 7 +++++--
>>   1 file changed, 5 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/gt/shmem_utils.c 
>> b/drivers/gpu/drm/i915/gt/shmem_utils.c
>> index 402f085f3a02..449c9ed44382 100644
>> --- a/drivers/gpu/drm/i915/gt/shmem_utils.c
>> +++ b/drivers/gpu/drm/i915/gt/shmem_utils.c
>> @@ -8,6 +8,7 @@
>>   #include <linux/pagemap.h>
>>   #include <linux/shmem_fs.h>
>>   +#include "i915_drv.h"
>>   #include "gem/i915_gem_object.h"
>>   #include "gem/i915_gem_lmem.h"
>>   #include "shmem_utils.h"
>> @@ -32,6 +33,8 @@ struct file *shmem_create_from_data(const char 
>> *name, void *data, size_t len)
>>     struct file *shmem_create_from_object(struct drm_i915_gem_object 
>> *obj)
>>   {
>> +    struct drm_i915_private *i915 = to_i915(obj->base.dev);
>> +    enum i915_map_type map_type;
>>       struct file *file;
>>       void *ptr;
>>   @@ -41,8 +44,8 @@ struct file *shmem_create_from_object(struct 
>> drm_i915_gem_object *obj)
>>           return file;
>>       }
>>   -    ptr = i915_gem_object_pin_map_unlocked(obj, 
>> i915_gem_object_is_lmem(obj) ?
>> -                        I915_MAP_WC : I915_MAP_WB);
>> +    map_type = i915_coherent_map_type(i915, obj, true);
>> +    ptr = i915_gem_object_pin_map_unlocked(obj, map_type);
>
>
> More lines, but less branches, some gain :)
>

Yes and I am more behind the idea of unifying finding map_type with this 
helper.


> Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>


Thanks!

Nirmoy

>
> Regards
> Andrzej
>
>>       if (IS_ERR(ptr))
>>           return ERR_CAST(ptr);
>

  reply	other threads:[~2022-12-20 10:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 11:29 [Intel-gfx] [PATCH v2] drm/i915: Use helper func to find out map type Nirmoy Das
2022-12-19 16:26 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Use helper func to find out map type (rev2) Patchwork
2022-12-19 16:52 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-12-19 18:04 ` [Intel-gfx] [PATCH v2] drm/i915: Use helper func to find out map type Andrzej Hajda
2022-12-20 10:33   ` Das, Nirmoy [this message]
2022-12-20  4:08 ` [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Use helper func to find out map type (rev2) 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=c88f147a-c4bd-c988-d3ec-8a53c6bf7acd@linux.intel.com \
    --to=nirmoy.das@linux.intel.com \
    --cc=andrzej.hajda@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.auld@intel.com \
    --cc=nirmoy.das@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