From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Andi Kleen" <andi@firstfloor.org>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: the Linux kernel, testsuites, and maybe *you*
Date: Wed, 5 Sep 2007 13:51:10 -0400 [thread overview]
Message-ID: <8bd0f97a0709051051y1c0328ffx24068da775f8bad2@mail.gmail.com> (raw)
In-Reply-To: <8bd0f97a0709040805y233cf07yc60ec0fedadb706d@mail.gmail.com>
On 9/4/07, Mike Frysinger <vapier.adi@gmail.com> wrote:
> On 9/2/07, Andi Kleen <andi@firstfloor.org> wrote:
> > On Sun, Sep 02, 2007 at 11:15:23AM -0400, Mike Frysinger wrote:
> > > there is still the ABI issue ... code written in kernel space in pure
> > > asm cannot always be compiled in userspace and work properly/the same
> >
> > Is that a blackfin weirdness?
>
> yes, Blackfin is weird in this respect due to being a no-mmu and
> wanting ELF, but i was being sufficiently general to bolster my claims
> and to leave the door open for any other port out there i'm not
> familiar with and any port that comes along
actually, there was another case i was thinking of ... it isnt
uncommon for architectures to use compiler flags which affect the ABI
and thus make userland not a 1-to-1 test example for the kernel ...
consider the regparam stuff we use on i386
-mike
next prev parent reply other threads:[~2007-09-05 17:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 21:22 Mike Frysinger
2007-09-01 6:14 ` Robin Getz
2007-09-01 22:52 ` Mike Frysinger
2007-09-01 22:08 ` Andi Kleen
2007-09-01 22:50 ` Mike Frysinger
2007-09-02 6:59 ` Andi Kleen
2007-09-02 15:15 ` Mike Frysinger
2007-09-02 15:43 ` Andi Kleen
2007-09-04 15:05 ` Mike Frysinger
2007-09-05 17:51 ` Mike Frysinger [this message]
2007-09-02 18:20 ` Håvard Skinnemoen
2007-09-04 14:41 ` Robin Getz
2007-09-02 2:34 ` Bill Davidsen
2007-09-02 3:44 ` Mike Frysinger
2007-09-03 13:37 ` Bill Davidsen
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=8bd0f97a0709051051y1c0328ffx24068da775f8bad2@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=andi@firstfloor.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®