From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] numa_helper: don't break is_numa() with TCONF
Date: Mon, 22 Feb 2016 14:25:22 +0100 [thread overview]
Message-ID: <20160222132522.GA6434@rei> (raw)
In-Reply-To: <283548158.25448265.1456145200825.JavaMail.zimbra@redhat.com>
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. 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. Or did I miss something?
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2016-02-22 13:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 15:02 [LTP] [PATCH] numa_helper: don't break is_numa() with TCONF Jan Stancek
2016-02-22 11:36 ` Cyril Hrubis
2016-02-22 12:46 ` Jan Stancek
2016-02-22 13:25 ` Cyril Hrubis [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-22 14:03 Jan Stancek
2016-02-22 14:26 ` Cyril Hrubis
2016-02-22 15:35 ` Jan Stancek
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=20160222132522.GA6434@rei \
--to=chrubis@suse.cz \
--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