From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Ira Weiny <ira.weiny@intel.com>, Sumitra Sharma <sumitraartsy@gmail.com>
Cc: Deepak R Varma <drv@mailo.com>, Fabio <fmdefrancesco@gmail.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, Daniel Vetter <daniel@ffwll.ch>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
David Airlie <airlied@gmail.com>
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915: Replace kmap() with kmap_local_page()
Date: Mon, 26 Jun 2023 10:02:18 +0100 [thread overview]
Message-ID: <d7a6f81e-94b8-1cb3-5fd6-ac944a052470@linux.intel.com> (raw)
In-Reply-To: <6491a85a37cc8_28e729425@iweiny-mobl.notmuch>
On 20/06/2023 14:23, Ira Weiny wrote:
> Sumitra Sharma wrote:
>> On Sun, Jun 18, 2023 at 11:11:08AM -0700, Ira Weiny wrote:
>>> Sumitra Sharma wrote:
>>>> kmap() has been deprecated in favor of the kmap_local_page()
>>>> due to high cost, restricted mapping space, the overhead of a
>>>> global lock for synchronization, and making the process sleep
>>>> in the absence of free slots.
>>>>
>>>> kmap_local_page() is faster than kmap() and offers thread-local
>>>> and CPU-local mappings, take pagefaults in a local kmap region
>>>> and preserves preemption by saving the mappings of outgoing tasks
>>>> and restoring those of the incoming one during a context switch.
>>>>
>>>> The mapping is kept thread local in the function
>>>> “i915_vma_coredump_create” in i915_gpu_error.c
>>>>
>>>> Therefore, replace kmap() with kmap_local_page().
>>>>
>>>> Suggested-by: Ira Weiny <ira.weiny@intel.com>
>>>>
>>>
>>> NIT: No need for the line break between Suggested-by and your signed off line.
>>>
>>
>> Hi Ira,
>>
>> What does NIT stand for?
>
> Shorthand for 'nitpicking'.
>
> "giving too much attention to details that are not important, especially
> as a way of criticizing: "
>
> - https://dictionary.cambridge.org/dictionary/english/nitpicking
>
> Via email this is a way for authors of an email to indicate something is
> technically wrong but while nicely acknowledging that it is not very
> significant and could be seen as overly critical.
>
> For this particular comment I'm showing something to pay attention to next
> time but that was not a big deal this time around.
>
>>
>> Thank you. I will take care about the line breaks.
>>
>>>> Signed-off-by: Sumitra Sharma <sumitraartsy@gmail.com>
>>>> ---
>>>>
>>>> Changes in v2:
>>>> - Replace kmap() with kmap_local_page().
>>>
>>> Generally it is customary to attribute a change like this to those who
>>> suggested it in a V1 review.
>>>
>>> For example:
>>>
>>> - Tvrtko/Thomas: Use kmap_local_page() instead of page_address()
>>>
>>> Also I don't see Thomas on the new email list. Since he took the time to
>>> review V1 he might want to check this version out. I've added him to the
>>> 'To:' list.
>>>
>>> Also a link to V1 is nice. B4 formats it like this:
>>>
>>> - Link to v1: https://lore.kernel.org/all/20230614123556.GA381200@sumitra.com/
>>>
>>> All that said the code looks good to me. So with the above changes.
>>>
>>> Reviewed-by: Ira Weiny <ira.weiny@intel.com>
>>>
>>
>> I have noted down the points mentioned above. Thank you again.
>>
>> I am not supposed to create another version of this patch for
>> adding the above mentions, as you and Thomas both gave this patch
>> a reviewed-by tag. Right?
>>
>
> Based on this response[*] from Tvrtko I think this version can move
> through without a v3.
>
> Thanks!
> Ira
>
> [*] https://lore.kernel.org/all/bcb0a1d2-cd4d-a56f-1ee6-7ccfdd2f7b38@linux.intel.com/
>
> <quote>
> Thanks all! I'll just re-send the patch for our CI, since it didn't get
> picked up automatically (stuck in moderation perhaps), with all r-b tags
> added and extra line space removed and merge it if results will be green.
>
> Regards,
>
> Tvrtko
> </quote>
Pushed to drm-intel-gt-next, thanks for the patch and reviews!
Regards,
Tvrtko
next prev parent reply other threads:[~2023-06-26 9:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 18:04 [Intel-gfx] [PATCH v2] drm/i915: Replace kmap() with kmap_local_page() Sumitra Sharma
2023-06-18 18:11 ` Ira Weiny
2023-06-19 7:59 ` Thomas Hellström (Intel)
2023-06-19 8:44 ` Tvrtko Ursulin
2023-06-19 15:45 ` Sumitra Sharma
2023-06-20 13:23 ` Ira Weiny
2023-06-20 18:07 ` Sumitra Sharma
2023-06-21 9:06 ` Thomas Hellström (Intel)
2023-06-21 13:24 ` Fabio M. De Francesco
2023-06-21 16:35 ` Ira Weiny
2023-06-21 18:51 ` Thomas Hellström (Intel)
2023-06-22 9:40 ` Tvrtko Ursulin
2023-06-26 9:02 ` Tvrtko Ursulin [this message]
2023-06-21 1:09 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Replace kmap() with kmap_local_page() (rev6) Patchwork
2023-06-21 22:30 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Replace kmap() with kmap_local_page() (rev7) Patchwork
2023-06-22 12:29 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-06-24 0:10 ` [Intel-gfx] [PATCH v2] drm/i915: Replace kmap() with kmap_local_page() Fabio M. De Francesco
-- strict thread matches above, loose matches on Subject: below --
2021-12-10 23:23 [Intel-gfx] [PATCH 1/7] " ira.weiny
2021-12-22 6:08 ` [Intel-gfx] [PATCH V2] " ira.weiny
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=d7a6f81e-94b8-1cb3-5fd6-ac944a052470@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=drv@mailo.com \
--cc=fmdefrancesco@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ira.weiny@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=sumitraartsy@gmail.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