linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Lynch <nathanl@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: srikar@linux.vnet.ibm.com, npiggin@gmail.com
Subject: [PATCH v2 0/2] powerpc/paravirt: vcpu_is_preempted() tweaks
Date: Tue, 28 Sep 2021 16:41:45 -0500	[thread overview]
Message-ID: <20210928214147.312412-1-nathanl@linux.ibm.com> (raw)

Minor changes arising from discovering that this code throws warnings with
DEBUG_PREEMPT kernels.

Changes since v1:
* Additional commentary to (1) distinguish hypervisor dispatch and preempt
  behavior from kernel scheduler preemption; and (2) more clearly justify
  the use of raw_smp_processor_id().
* Additional patch to update existing comments before making the functional
  change.

v1: https://lore.kernel.org/linuxppc-dev/20210921031213.2029824-1-nathanl@linux.ibm.com/

Nathan Lynch (2):
  powerpc/paravirt: vcpu_is_preempted() commentary
  powerpc/paravirt: correct preempt debug splat in vcpu_is_preempted()

 arch/powerpc/include/asm/paravirt.h | 40 +++++++++++++++++++++++++----
 1 file changed, 35 insertions(+), 5 deletions(-)

-- 
2.31.1


             reply	other threads:[~2021-09-28 21:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28 21:41 Nathan Lynch [this message]
2021-09-28 21:41 ` [PATCH v2 1/2] powerpc/paravirt: vcpu_is_preempted() commentary Nathan Lynch
2021-09-29  7:30   ` Srikar Dronamraju
2021-09-28 21:41 ` [PATCH v2 2/2] powerpc/paravirt: correct preempt debug splat in vcpu_is_preempted() Nathan Lynch
2021-09-29  7:30   ` Srikar Dronamraju
2021-10-11 12:06 ` [PATCH v2 0/2] powerpc/paravirt: vcpu_is_preempted() tweaks Michael Ellerman

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=20210928214147.312412-1-nathanl@linux.ibm.com \
    --to=nathanl@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=npiggin@gmail.com \
    --cc=srikar@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).