From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] proc01: handle EOPNOTSUPP if !hugepages_supported()
Date: Tue, 7 Jun 2016 12:49:32 -0400 (EDT) [thread overview]
Message-ID: <1669443228.4369795.1465318172517.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20160607161049.GB5810@rei>
----- Original Message -----
> From: "Cyril Hrubis" <chrubis@suse.cz>
> To: "Jan Stancek" <jstancek@redhat.com>
> Cc: ltp@lists.linux.it
> Sent: Tuesday, 7 June, 2016 6:10:50 PM
> Subject: Re: [LTP] [PATCH] proc01: handle EOPNOTSUPP if !hugepages_supported()
>
> Hi!
> > ---
> > testcases/kernel/fs/proc/proc01.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/testcases/kernel/fs/proc/proc01.c
> > b/testcases/kernel/fs/proc/proc01.c
> > index 2825b51dff95..409d6f9e32fe 100644
> > --- a/testcases/kernel/fs/proc/proc01.c
> > +++ b/testcases/kernel/fs/proc/proc01.c
> > @@ -108,6 +108,8 @@ static const struct mapping known_issues[] = {
> > {"read", "/proc/fs/nfsd/.getfd", EINVAL},
> > {"read", "/proc/self/net/rpc/use-gss-proxy", EAGAIN},
> > {"read", "/proc/sys/net/ipv6/conf/*/stable_secret", EIO},
> > + {"read", "/proc/sys/vm/nr_hugepages", EOPNOTSUPP},
> > + {"read", "/proc/sys/vm/nr_overcommit_hugepages", EOPNOTSUPP},
> > {"", "", 0}
>
> Looking at my bugzilla it suggests:
>
> + {"read", "/proc/sys/vm/nr_hugepages_mempolicy", EOPNOTSUPP}
>
> as well.
You're right. I didn't see this one on s390, because it's compiled
with CONFIG_NUMA=n. I added nr_hugepages_mempolicy as well and pushed.
Regards,
Jan
>
> --
> Cyril Hrubis
> chrubis@suse.cz
>
prev parent reply other threads:[~2016-06-07 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 14:54 [LTP] [PATCH] proc01: handle EOPNOTSUPP if !hugepages_supported() Jan Stancek
2016-06-07 16:09 ` Cyril Hrubis
2016-06-07 16:10 ` Cyril Hrubis
2016-06-07 16:49 ` Jan Stancek [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=1669443228.4369795.1465318172517.JavaMail.zimbra@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 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.