All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <hca@linux.ibm.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: linux390-list@tuxmaker.boeblingen.de.ibm.com, stable@vger.kernel.org
Subject: Re: [PATCH v2 1/3] s390/numa: set node distance to LOCAL_DISTANCE
Date: Wed, 5 Aug 2020 13:27:40 +0200	[thread overview]
Message-ID: <20200805112740.GD5275@osiris> (raw)
In-Reply-To: <c87c17b99a710d1752a189180582afb6ced9efeb.1596565862.git.agordeev@linux.ibm.com>

On Tue, Aug 04, 2020 at 08:35:49PM +0200, Alexander Gordeev wrote:
> The node distance is hardcoded to 0, which causes a trouble
> for some user-level applications. In particular, "libnuma"
> expects the distance of a node to itself as LOCAL_DISTANCE.
> This update removes the offending node distance override.
> 
> Cc: <stable@vger.kernel.org> # v5.6+
> Cc: Heiko Carstens <hca@linux.ibm.com>
> Fixes: 701dc81e7412 ("s390/mm: remove fake numa support")
> Signed-off-by: Alexander Gordeev <agordeev@linux.ibm.com>
> ---
>  arch/s390/include/asm/topology.h | 6 ------
>  1 file changed, 6 deletions(-)

It would have been nice if the Fixes tag would be correct, since then
there would be hardly any backport necessary. But unfortunately this
is broken since we support numa.

Older code had this:

int __node_distance(int a, int b)
{
	return mode->distance ? mode->distance(a, b) : 0;
}
EXPORT_SYMBOL(__node_distance);

And the distance function was only set for the emulation mode, but not
the default ("plain") mode.

I'll change that in the commit message.

      reply	other threads:[~2020-08-05 20:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1596565862.git.agordeev@linux.ibm.com>
2020-08-04 18:35 ` [PATCH v2 1/3] s390/numa: set node distance to LOCAL_DISTANCE Alexander Gordeev
2020-08-05 11:27   ` Heiko Carstens [this message]

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=20200805112740.GD5275@osiris \
    --to=hca@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=linux390-list@tuxmaker.boeblingen.de.ibm.com \
    --cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.