From: Rob Landley <rob@landley.net>
To: Ollie Wild <aaw@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-kernel@vger.kernel.org,
parisc-linux@lists.parisc-linux.org, linux-mm@kvack.org,
linux-arch@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Andi Kleen <ak@suse.de>
Subject: Re: [patch] removes MAX_ARG_PAGES
Date: Thu, 10 May 2007 05:19:37 -0400 [thread overview]
Message-ID: <200705100519.38073.rob@landley.net> (raw)
In-Reply-To: <65dd6fd50705092106i15722e97g85f43191ceb5a3d7@mail.gmail.com>
On Thursday 10 May 2007 12:06 am, Ollie Wild wrote:
> On 5/9/07, Rob Landley <rob@landley.net> wrote:
> > Just FYI, a really really quick and dirty way of testing this sort of
thing on
> > more architectures and you're likely to physically have?
>
> Does this properly emulate caching? On parisc, cache coherency was
> the main issue we ran into. I suspect this might be the case with
> other architectures as well.
This is really a QEMU question. I've been focused on making cross-compilers
and using those to create kernels and a minimal native build environment I
could use to natively compile packages with. (The way I designed the thing
you could substitute real hardware for the qemu step, assuming you had it.
Or another emulator like armulator for a specific platform.)
I don't believe QEMU emulates parisc yet, although it adds new platforms all
the time. (It just grew an alpha emulation last month.) It's under very
active development.
Rob
next prev parent reply other threads:[~2007-05-10 9:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 8:51 [patch] removes MAX_ARG_PAGES Ollie Wild
2007-05-07 17:46 ` Luck, Tony
2007-05-07 19:01 ` William Lee Irwin III
2007-05-22 12:24 ` Peter Zijlstra
2007-05-09 20:48 ` Andrew Morton
2007-05-10 1:04 ` Rob Landley
2007-05-10 4:06 ` Ollie Wild
2007-05-10 9:19 ` Rob Landley [this message]
[not found] <617E1C2C70743745A92448908E030B2A0184DF88@scsmsx411.amr.corp.intel.com>
2007-05-24 15:20 ` Peter Zijlstra
2007-05-25 18:48 ` Luck, Tony
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=200705100519.38073.rob@landley.net \
--to=rob@landley.net \
--cc=a.p.zijlstra@chello.nl \
--cc=aaw@google.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=parisc-linux@lists.parisc-linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).