From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Matthew Brost <matthew.brost@intel.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
intel-gfx@lists.freedesktop.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/guc: Remove usage of the deprecated ida_simple_xx() API
Date: Sun, 14 Apr 2024 10:26:35 +0200 [thread overview]
Message-ID: <a788ee2e-ee51-476f-8aee-aa344f221f9c@wanadoo.fr> (raw)
In-Reply-To: <ZbGlqD6zyyp4DsmH@DUT025-TGLU.fm.intel.com>
Le 25/01/2024 à 01:04, Matthew Brost a écrit :
> On Sun, Jan 14, 2024 at 04:15:34PM +0100, Christophe JAILLET wrote:
>> ida_alloc() and ida_free() should be preferred to the deprecated
>> ida_simple_get() and ida_simple_remove().
>>
>> Note that the upper limit of ida_simple_get() is exclusive, but the one of
>> ida_alloc_range() is inclusive. So a -1 has been added when needed.
>>
>> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
>
> Reviewed-by: Matthew Brost <matthew.brost@intel.com>
Hi,
polite reminder ;-)
CJ
>
>> ---
>> drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 13 ++++++-------
>> 1 file changed, 6 insertions(+), 7 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
>> index a259f1118c5a..73ce21ddf682 100644
>> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
>> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
>> @@ -2156,11 +2156,10 @@ static int new_guc_id(struct intel_guc *guc, struct intel_context *ce)
>> order_base_2(ce->parallel.number_children
>> + 1));
>> else
>> - ret = ida_simple_get(&guc->submission_state.guc_ids,
>> - NUMBER_MULTI_LRC_GUC_ID(guc),
>> - guc->submission_state.num_guc_ids,
>> - GFP_KERNEL | __GFP_RETRY_MAYFAIL |
>> - __GFP_NOWARN);
>> + ret = ida_alloc_range(&guc->submission_state.guc_ids,
>> + NUMBER_MULTI_LRC_GUC_ID(guc),
>> + guc->submission_state.num_guc_ids - 1,
>> + GFP_KERNEL | __GFP_RETRY_MAYFAIL | __GFP_NOWARN);
>> if (unlikely(ret < 0))
>> return ret;
>>
>> @@ -2183,8 +2182,8 @@ static void __release_guc_id(struct intel_guc *guc, struct intel_context *ce)
>> + 1));
>> } else {
>> --guc->submission_state.guc_ids_in_use;
>> - ida_simple_remove(&guc->submission_state.guc_ids,
>> - ce->guc_id.id);
>> + ida_free(&guc->submission_state.guc_ids,
>> + ce->guc_id.id);
>> }
>> clr_ctx_id_mapping(guc, ce->guc_id.id);
>> set_context_guc_id_invalid(ce);
>> --
>> 2.43.0
>>
>
>
next prev parent reply other threads:[~2024-04-14 8:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-14 15:15 Christophe JAILLET
2024-01-25 0:04 ` Matthew Brost
2024-04-14 8:26 ` Christophe JAILLET [this message]
2024-04-14 23:41 ` Matthew Brost
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=a788ee2e-ee51-476f-8aee-aa344f221f9c@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.brost@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@linux.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
all inboxes | Powered by JetHome®