Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Dave Martin <Dave.Martin@arm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Hillf Danton <hdanton@sina.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [patch] arm64: assembler: Update the yield NEON comment
Date: Mon, 13 May 2019 17:38:13 +0100	[thread overview]
Message-ID: <20190513163813.GC10754@fuggles.cambridge.arm.com> (raw)
In-Reply-To: <20190513085624.GB28398@e103592.cambridge.arm.com>

On Mon, May 13, 2019 at 09:56:26AM +0100, Dave Martin wrote:
> On Sat, May 11, 2019 at 09:48:40AM +0100, Hillf Danton wrote:
> > > On Thu, May 09, 2019, Dave Martin wrote:
> > > > On Thu, May 09, 2019 at 03:01:43PM +0000, Hillf Danton wrote:
> > > 
> > [...]
> > 
> > > >   *
> > > > - * The yield itself consists of the following:
> > > > - * - Check whether the preempt count is exactly 1, in which case disabling
> > > > - *   preemption once will make the task preemptible. If this is not the case,
> > > > - *   yielding is pointless.
> > > > - * - Check whether TIF_NEED_RESCHED is set, and if so, disable and re-enable
> > > > - *   kernel mode NEON (which will trigger a reschedule), and branch to the
> > > > - *   yield fixup code.
> > > > + * The yield itself decrements the preempt count and if count hits zero, disable
> > > > + * and re-enable kernel mode NEON (which will trigger a reschedule), and branch
> > > > + * to the yield fixup code.
> > > 
> > > Good spot -- the original comment is definitely wrong: disabling
> > > preemption certainly shouldn't make the task preemptible!
> > > 
> > > So, I'm certainly in favour of fixing that.
> > > 
> > > Your new text doesn't look right, though: AFAICT commit 7faa313f05
> > > didn't intentionally change the behaviour here.  It looks to me like
> > > the preempt count (i.e., current_thread_info()->preempt) is not
> > > decremented by this code: the value is read and the subtraction is done
> > > for comparison purposes, but no value is stored back.
> > > 
> > Got it, thanks.
> > 
> > > This is intentional, because the the code needs to do some cleanup
> > > before preemption can be enabled for real: the call to kernel_neon_end
> > > does both of those jobs.
> > > 
> > > Or did I miss something?
> > > 
> > No, you didn't, Sir.
> > 
> > And I try again with log message updated and comment text corrected.
> > 
> > Hillf
> > ----------------->8-----------------------------------------------------------
> > From: Hillf Danton <hdanton@sina.com>
> > Subject: [patch] arm64: assembler: Update the yield NEON comment
> > 
> > The comment for specifying preempt count check was incorrect in commit
> > 24534b3511, and deserves a tiny tweak like the following for instance.
> > 
> > - * - Check whether the preempt count is exactly 1, in which case disabling
> > - *   preemption once will make the task preemptible. If this is not the case,
> > + * - Check whether the preempt count is exactly 1, in which case decrementing
> > + *   preempt count once will make the task preemptible. If this is not the case,
> > 
> > Then checking of TIF_NEED_RESCHED was removed in commit 7faa313f05, with the
> > comment left behind untouched.
> 
> Hmm, you're right here, I hadn't fully understood the context of that
> commit.
> 
> Will, Ard, can you comment on the rationale for that?  The commit
> message says nothing explicit about why the TIF_NEED_RESCHED check went
> away: it's now checked as part of the preempt count, right?

Yes. The value of !need_resched is stored adjacent to the preempt count,
which is why 7faa313f05ca ("arm64: preempt: Fix big-endian when checking
preempt count in assembly") can load both of the variables using a single
64-bit LDR instruction.

So we continue to check both the preempt count and the need_resched flag,
as before.

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-05-13 16:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <198595.152792649-sendEmail@laptop-0p1i5f25>
2019-05-13  8:56 ` [patch] arm64: assembler: Update the yield NEON comment Dave Martin
2019-05-13 16:38   ` Will Deacon [this message]
2019-05-09 15:01 Hillf Danton
2019-05-10 13:26 ` Dave Martin

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=20190513163813.GC10754@fuggles.cambridge.arm.com \
    --to=will.deacon@arm.com \
    --cc=Dave.Martin@arm.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=hdanton@sina.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=peterz@infradead.org \
    /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