Thread (8 messages) 8 messages, 3 authors, 2020-01-27

Re: [PATCH v9 0/5] Add NUMA-awareness to qspinlock

From: "Paul E. McKenney" <paulmck@kernel.org>
Date: 2020-01-25 04:58:47
Also in: linux-arch, lkml

On Fri, Jan 24, 2020 at 09:17:05PM -0500, Waiman Long wrote:
On 1/24/20 8:59 PM, Waiman Long wrote:
quoted
quoted
You called it!  I will play with QEMU's -numa argument to see if I can get
CNA to run for me.  Please accept my apologies for the false alarm.

							Thanx, Paul
CNA is not currently supported in a VM guest simply because the numa
information is not reliable. You will have to run it on baremetal to
test it. Sorry for that.
Correction. There is a command line option to force CNA lock to be used
in a VM. Use the "numa_spinlock=on" boot command line parameter.
As I understand it, I need to use a series of -numa arguments to qemu
combined with the numa_spinlock=on (or =1) on the kernel command line.
If the kernel thinks that there is only one NUMA node, it appears to
avoid doing CNA.

Correct?

							Thanx, Paul

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help