All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Aravamudan <nacc@us.ibm.com>
To: sparclinux@vger.kernel.org
Subject: libhugetlbfs and sparc64 support
Date: Mon, 12 Mar 2007 18:39:20 +0000	[thread overview]
Message-ID: <20070312183920.GD29949@us.ibm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1980 bytes --]

***********************
Warning: Your file, libhugetlbfs-sparc64.tar.bz2, contains more than 32 files after decompression and cannot be scanned.
***********************


Hello all,

I'm currently trying to add (basic) support for sparc64 to libhugetlbfs.
If nothing else, this will ensure that sparc64 gets adequate testing. I
am finding, though, that using the attached tarball and running `make
func`, which should run through a series of quick functional tests, an
Ultra 60 I have access to hangs hard. To be clear, I'm not ruling out
general instability, but same box is able to build kernels and I'm more
prone to suspect hugepage support in the kernel.

What I'm seeing:

1) Running only the 32-bit tests (by specifying -b32 to
tests/run_test.sh), immediately after readpage finishes, the box hangs
hard, including serial console (has to be power cycled). No oops,
nothing.

2) Running only the 64-bit tests (-b64 to run_tests.sh), immediately
after unlinked_fd finishes, the box hangs similarly. Again, nothing on
the serial console to indicate a problem.

What I'm hoping to get is some help from folks that are sparc-savvy. Is
the box just busted, and maybe I should try to find another? Or are
people able to see similar problems running `make func`.

To reproduce:

Use 2.6.20.2, if possible, to avoid as many known hugepage bugs in
arch-generic code as possible. CONFIG_HUGETLBFS and CONFIG_HUGETLB_PAGE
set (the former selects the latter). Boot with hugepages=20 (or `echo 20
> /proc/sys/vm/nr_hugepages`). Using the attached tarball, run
`make func`. Tell me what happens :)

Note: I fully expect some test to fail, notably icache-hygeiene,
linkhuge and linkshare (the latter because the linker scripts in the
tarball are just dummy copies of the normal .x ones).

If someone could also verify my sparc assembly in elf32_sparc.S and
elf64_sparc.S, I would greatly appreciate it.

Thanks,
Nish

-- 
Nishanth Aravamudan <nacc@us.ibm.com>
IBM Linux Technology Center


[-- Attachment #2: libhugetlbfs-sparc64.tar.bz2 --]
[-- Type: application/octet-stream, Size: 58143 bytes --]

             reply	other threads:[~2007-03-12 18:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-12 18:39 Nishanth Aravamudan [this message]
2007-03-12 20:40 ` libhugetlbfs and sparc64 support David Miller
2007-03-12 21:12 ` Nishanth Aravamudan
2007-03-13  5:58 ` David Miller
2007-03-13 18:18 ` Bill Irwin

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=20070312183920.GD29949@us.ibm.com \
    --to=nacc@us.ibm.com \
    --cc=sparclinux@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.