From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-185.mta1.migadu.com (out-185.mta1.migadu.com [95.215.58.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9D6E51494AD; Fri, 31 Jan 2025 23:21:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.185 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1738365683; cv=none; b=I+X1X0tACpFucVmKxA6ussMEwVamvX8X5p0TTln0J9wLrECw+biROAc5ndbQznj+Yhna/zYn1IWrC5jdjQZARiH6G7yGva5emXaihQAf0NOT2drC3mMuT8XoXKxMR3QHTs3nvWARqqTdxpBGUWefhPNGva91JbaKafco8m5tE78= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1738365683; c=relaxed/simple; bh=0jZgI8HjwW28cfb0yaKtcfeEFNmZ3ZmAE62YZbJw6ow=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=KnkmALsSESsTj9XLj8hMdk3v69B1d2WrV6jVfl/KOzouF0O2UxKgnI4PEPZAFelcmAUuRv4cxxOY8YtrGccSfEZa/s/mV4TydnjPAINLgWCzeq/7ARM8/hJPvjb0nMijE+S8RdrUjJX/AK09E8Gq0ntlU7mhb/QMpHQ1iN9U0AI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=OiydVhAd; arc=none smtp.client-ip=95.215.58.185 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="OiydVhAd" Message-ID: <7c7f3209-4259-44c2-8d13-94caa88e1468@linux.dev> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1738365679; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=0jZgI8HjwW28cfb0yaKtcfeEFNmZ3ZmAE62YZbJw6ow=; b=OiydVhAdi8bt1+1QlgtQB4phkxn784jjz/X9v3lxTEHiH/81D9LwnNMFYNNC0k7RT9raL6 HbaQRue5qD/cWqVOQcURfQwiUiwsmsTqx1vP3FDc7oT5CppxQhKlr1Y5JrNNijRiGZHfbi 9Z3uHUeWD0PK+omNuAQjOAsrh23JMVA= Date: Fri, 31 Jan 2025 15:21:12 -0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [PATCH v2 2/2] selftests/bpf: Select NUMA_NO_NODE to create map Content-Language: en-GB To: Saket Kumar Bhaskar , bpf@vger.kernel.org, linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org Cc: ast@kernel.org, hbathini@linux.ibm.com, andrii@kernel.org, daniel@iogearbox.net, davem@davemloft.net, kuba@kernel.org, hawk@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org, john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com, jolsa@kernel.org, mykolal@fb.com, shuah@kernel.org References: <7192d6aa9501115dc242435970df82b3d190f257.1738302337.git.skb99@linux.ibm.com> X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Yonghong Song In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT On 1/30/25 11:05 PM, Saket Kumar Bhaskar wrote: > On powerpc, a CPU does not necessarily originate from NUMA node 0. > This contrasts with architectures like x86, where CPU 0 is not > hot-pluggable, making NUMA node 0 a consistently valid node. > This discrepancy can lead to failures when creating a map on NUMA > node 0, which is initialized by default, if no CPUs are allocated > from NUMA node 0. > > This patch fixes the issue by setting NUMA_NO_NODE (-1) for map > creation for this selftest. > > Fixes: 96eabe7a40aa ("bpf: Allow selecting numa node during map creation") > Signed-off-by: Saket Kumar Bhaskar Acked-by: Yonghong Song