From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] numa_helper: don't break is_numa() with TCONF
Date: Mon, 22 Feb 2016 15:03:05 +0100 [thread overview]
Message-ID: <56CB1519.4040902@redhat.com> (raw)
----- Original Message -----
> From: "Cyril Hrubis" <chrubis@suse.cz>
> To: "Jan Stancek" <jstancek@redhat.com>
> Cc: ltp@lists.linux.it
> Sent: Monday, 22 February, 2016 2:25:22 PM
> Subject: Re: [LTP] [PATCH] numa_helper: don't break is_numa() with TCONF
>
> Hi!
> > > And the same for is_numa(), it calls tst_brkm(TBROK | TERRNO, ...) in
> > > case that get_allowed_nodes_arr() returned non-zero.
> >
> > If get_allowed_nodes_arr() returned non-zero because of get_mempolicy,
> > that means get_mempolicy is implemented but failed. I think that
> > justifies TBROK.
>
> Now I'm confused. You said that the syscall can exit -1 and ENOSYS.
Correct, get_mempolicy is not implemented on aarch64.
> In that case the filter_nodemask_mem() returns -2 which is propagated from
> get_allowed_nodes_arr() to is_numa() where the test ends with TBROK
> rather than with TCONF.
It won't return -2 for ENOSYS, because of this line:
+ if (ret < 0 && errno != ENOSYS)
return -2;
> Or did I miss something?
I didn't make it clear in commit message that patch now silently ignores ENOSYS
from get_mempolicy. In this case get_allowed_nodes should return success, but
returned node set should be empty (I'll double check that this is the case on aarch64).
>
> --
> Cyril Hrubis
> chrubis@suse.cz
>
next reply other threads:[~2016-02-22 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 14:03 Jan Stancek [this message]
2016-02-22 14:26 ` [LTP] [PATCH] numa_helper: don't break is_numa() with TCONF Cyril Hrubis
2016-02-22 15:35 ` Jan Stancek
-- strict thread matches above, loose matches on Subject: below --
2016-02-19 15:02 Jan Stancek
2016-02-22 11:36 ` Cyril Hrubis
2016-02-22 12:46 ` Jan Stancek
2016-02-22 13:25 ` Cyril Hrubis
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=56CB1519.4040902@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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