Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Antonino Maniscalco <antomani103@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Abhinav Kumar <quic_abhinavk@quicinc.com>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Marijn Suijten <marijn.suijten@somainline.org>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Jonathan Corbet <corbet@lwn.net>
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
	freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH v6 11/11] Documentation: document adreno preemption
Date: Tue, 1 Oct 2024 13:18:18 +0200	[thread overview]
Message-ID: <0aab9845-b960-477f-b869-e8d0759c4671@gmail.com> (raw)
In-Reply-To: <ZvtMB14Yx5m3TzFJ@archie.me>

On 10/1/24 3:10 AM, Bagas Sanjaya wrote:
> On Thu, Sep 26, 2024 at 11:16:53PM +0200, Antonino Maniscalco wrote:
>> +.. SPDX-License-Identifier: GPL-2.0
>> +
>> +:orphan:
> 
> Why don't this be added to toctree in Documentation/gpu/index.rst?

Yes so there is existing orphan documentation for msm so my intention 
was to add it as orphan then eventually send out a series to organize it 
properly (so creating an msm directory with an index which then points 
two files we currently have). Does that sound good to you?

> 
>> +
>> +=============
>> +MSM Preemtion
>> +=============
> s/Preemtion/Preemption/

Thanks for pointing out the typo!

> 
> 
>> +This mechanism can be used by the kernel to switch between rings. Whenever a
>> +submission occurs the kernel finds the highest priority ring which isn't empty
>> +and preempts to it if said ring is not the one being currently executed. This is
>> +also done whenever a submission completes to make sure execution resumes on a
>> +lower priority ring when a higher priority ring is done.
> 
> Do you mean that the kernel finds highest priority ring possible that is not
> empty? What if all these 4 rings are empty?
> 
> Confused...
> 

Yep, if all rings are empty we don't preempt, same as when the highest 
priority ring is the current one.

Best regards,
-- 
Antonino Maniscalco <antomani103@gmail.com>

      reply	other threads:[~2024-10-01 11:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-26 21:16 [PATCH v6 00/11] Preemption support for A7XX Antonino Maniscalco
2024-09-26 21:16 ` [PATCH v6 01/11] drm/msm: Fix bv_fence being used as bv_rptr Antonino Maniscalco
2024-09-26 21:16 ` [PATCH v6 02/11] drm/msm/a6xx: Track current_ctx_seqno per ring Antonino Maniscalco
2024-09-26 21:16 ` [PATCH v6 03/11] drm/msm: Add a `preempt_record_size` field Antonino Maniscalco
2024-09-26 21:16 ` [PATCH v6 04/11] drm/msm: Add CONTEXT_SWITCH_CNTL bitfields Antonino Maniscalco
2024-09-27 11:57   ` Connor Abbott
2024-09-27 15:01     ` Antonino Maniscalco
2024-09-26 21:16 ` [PATCH v6 05/11] drm/msm/a6xx: Implement preemption for a7xx targets Antonino Maniscalco
2024-09-27 16:13   ` Rob Clark
2024-09-27 16:29   ` Rob Clark
2024-09-27 20:15     ` Antonino Maniscalco
2024-09-26 21:16 ` [PATCH v6 06/11] drm/msm/a6xx: Sync relevant adreno_pm4.xml changes Antonino Maniscalco
2024-09-26 21:16 ` [PATCH v6 07/11] drm/msm/a6xx: Use posamble to reset counters on preemption Antonino Maniscalco
2024-09-26 21:16 ` [PATCH v6 08/11] drm/msm/a6xx: Add traces for preemption Antonino Maniscalco
2024-09-26 21:16 ` [PATCH v6 09/11] drm/msm/a6xx: Add a flag to allow preemption to submitqueue_create Antonino Maniscalco
2024-09-26 21:16 ` [PATCH v6 10/11] drm/msm/a6xx: Enable preemption for a750 Antonino Maniscalco
2024-09-26 21:16 ` [PATCH v6 11/11] Documentation: document adreno preemption Antonino Maniscalco
2024-10-01  1:10   ` Bagas Sanjaya
2024-10-01 11:18     ` Antonino Maniscalco [this message]

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=0aab9845-b960-477f-b869-e8d0759c4671@gmail.com \
    --to=antomani103@gmail.com \
    --cc=airlied@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=daniel@ffwll.ch \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=marijn.suijten@somainline.org \
    --cc=mripard@kernel.org \
    --cc=quic_abhinavk@quicinc.com \
    --cc=robdclark@gmail.com \
    --cc=sean@poorly.run \
    --cc=tzimmermann@suse.de \
    /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