linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@surriel.com>
To: Xie Yuanbin <qq570070308@gmail.com>,
	tglx@linutronix.de,  peterz@infradead.org,
	segher@kernel.crashing.org, david@kernel.org, hpa@zytor.com,
		arnd@arndb.de, acme@kernel.org, adrian.hunter@intel.com,
	agordeev@linux.ibm.com, 	akpm@linux-foundation.org,
	alex@ghiti.fr, alexander.shishkin@linux.intel.com,
		andreas@gaisler.com, anshuman.khandual@arm.com,
	aou@eecs.berkeley.edu,  borntraeger@linux.ibm.com, bp@alien8.de,
	bsegall@google.com,  dave.hansen@linux.intel.com,
	davem@davemloft.net, dietmar.eggemann@arm.com,
	frederic@kernel.org, gor@linux.ibm.com, hca@linux.ibm.com,
	irogers@google.com, 	james.clark@linaro.org, jolsa@kernel.org,
	juri.lelli@redhat.com, 	justinstitt@google.com,
	lorenzo.stoakes@oracle.com, luto@kernel.org,
		mark.rutland@arm.com, mathieu.desnoyers@efficios.com,
	max.kellermann@ionos.com, 	mgorman@suse.de, mingo@redhat.com,
	morbo@google.com, namhyung@kernel.org, 	nathan@kernel.org,
	nick.desaulniers+lkml@gmail.com, nysal@linux.ibm.com,
		palmer@dabbelt.com, paulmck@kernel.org, pjw@kernel.org,
	rostedt@goodmis.org,  ryan.roberts@arm.com, svens@linux.ibm.com,
	thuth@redhat.com, urezki@gmail.com, 	vincent.guittot@linaro.org,
	vschneid@redhat.com, linux@armlinux.org.uk
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	 linux-arm-kernel@lists.infradead.org,
	linux-riscv@lists.infradead.org,  linux-s390@vger.kernel.org,
	sparclinux@vger.kernel.org,  linux-perf-users@vger.kernel.org,
	llvm@lists.linux.dev
Subject: Re: [PATCH v5 2/3] sched: Make raw_spin_rq_unlock() inline
Date: Sun, 14 Dec 2025 18:39:56 -0500	[thread overview]
Message-ID: <ce226891413fe9c1d6f0c02697a32b646b4e0a0c.camel@surriel.com> (raw)
In-Reply-To: <20251214190907.184793-3-qq570070308@gmail.com>

On Mon, 2025-12-15 at 03:09 +0800, Xie Yuanbin wrote:
> raw_spin_rq_unlock() is short, and is called in some hot code paths
> such as finish_lock_switch.
> 
> Make raw_spin_rq_unlock() inline to optimize performance.
> 
> Signed-off-by: Xie Yuanbin <qq570070308@gmail.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Rik van Riel <riel@surriel.com>
> Cc: Segher Boessenkool <segher@kernel.crashing.org>
> Cc: David Hildenbrand (Red Hat) <david@kernel.org>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: H. Peter Anvin (Intel) <hpa@zytor.com>

Reviewed-by: Rik van Riel <riel@surriel.com>

-- 
All Rights Reversed.

  reply	other threads:[~2025-12-14 23:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-14 19:09 [PATCH v5 0/3] Optimize code generation during context switching Xie Yuanbin
2025-12-14 19:09 ` [PATCH v5 1/3] x86/mm/tlb: Make enter_lazy_tlb() always inline on x86 Xie Yuanbin
2025-12-15 15:42   ` Thomas Gleixner
2025-12-16 15:49     ` Xie Yuanbin
2025-12-14 19:09 ` [PATCH v5 2/3] sched: Make raw_spin_rq_unlock() inline Xie Yuanbin
2025-12-14 23:39   ` Rik van Riel [this message]
2025-12-14 19:13 ` [PATCH v5 3/3] sched/core: Make finish_task_switch() and its subfunctions always inline Xie Yuanbin
2025-12-15 13:10 ` [PATCH v5 0/3] Optimize code generation during context switching Xie Yuanbin

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=ce226891413fe9c1d6f0c02697a32b646b4e0a0c.camel@surriel.com \
    --to=riel@surriel.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=agordeev@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex@ghiti.fr \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=andreas@gaisler.com \
    --cc=anshuman.khandual@arm.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=arnd@arndb.de \
    --cc=borntraeger@linux.ibm.com \
    --cc=bp@alien8.de \
    --cc=bsegall@google.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=david@kernel.org \
    --cc=dietmar.eggemann@arm.com \
    --cc=frederic@kernel.org \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=hpa@zytor.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=juri.lelli@redhat.com \
    --cc=justinstitt@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=llvm@lists.linux.dev \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=luto@kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=max.kellermann@ionos.com \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=morbo@google.com \
    --cc=namhyung@kernel.org \
    --cc=nathan@kernel.org \
    --cc=nick.desaulniers+lkml@gmail.com \
    --cc=nysal@linux.ibm.com \
    --cc=palmer@dabbelt.com \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=pjw@kernel.org \
    --cc=qq570070308@gmail.com \
    --cc=rostedt@goodmis.org \
    --cc=ryan.roberts@arm.com \
    --cc=segher@kernel.crashing.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=svens@linux.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=thuth@redhat.com \
    --cc=urezki@gmail.com \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    --cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).