From: Bill Irwin <bill.irwin@oracle.com>
To: Adam Litke <agl@us.ibm.com>
Cc: Bill Irwin <bill.irwin@oracle.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
akpm@linux-foundation.org
Subject: Re: Kernel Oops with shm namespace cleanups
Date: Fri, 2 Mar 2007 13:58:34 -0800 [thread overview]
Message-ID: <20070302215834.GM10643@holomorphy.com> (raw)
In-Reply-To: <1172852957.12220.4.camel@localhost.localdomain>
On Thu, 2007-03-01 at 16:08 -0800, Bill Irwin wrote:
>> Looks like I should grab these testcases for the sake of due diligence
>> (not to say I intend to alter maintenance style from primarily review,
>> approval, and bugfixing, not that I've been doing as much of any of those
>> as I should). To which architectures and/or distributions have the
>> userspace bits been ported, or otherwise run/tested on? A quick sniff
>> test on an Altix suggests SLES and/or ia64 may trip up the scripts:
On Fri, Mar 02, 2007 at 10:29:16AM -0600, Adam Litke wrote:
> Right now we support x86, powerpc, and x86_64. Segment remapping and
> hugetlb malloc won't work on ia64 until long format vhpt is supported (I
> suspect). But the test framework should be adaptable to other
> architectures.
Those patches have been around for a while. I'll ping Tony Luck et al
about that since I'm not entirely aware of what their issues might be.
I should probably get some testing in on sparc64 at some point, too.
-- wli
prev parent reply other threads:[~2007-03-02 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 20:13 Kernel Oops with shm namespace cleanups Adam Litke
2007-03-01 0:57 ` Eric W. Biederman
2007-03-02 0:08 ` Bill Irwin
2007-03-02 16:29 ` Adam Litke
2007-03-02 21:58 ` Bill Irwin [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=20070302215834.GM10643@holomorphy.com \
--to=bill.irwin@oracle.com \
--cc=agl@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@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.