From: Ingo Molnar <mingo@kernel.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
David Ahern <dsahern@gmail.com>,
Pekka Enberg <penberg@kernel.org>,
Bernhard Rosenkraenzer <bernhard.rosenkranzer@linaro.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@infradead.org>
Subject: Re: [PATCHv2 1/1] perf: Port to Android
Date: Fri, 24 Aug 2012 20:02:01 +0200 [thread overview]
Message-ID: <20120824180201.GA32144@gmail.com> (raw)
In-Reply-To: <20120824133033.3d93cf5f@pyramind.ukuu.org.uk>
* Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Fri, 24 Aug 2012 05:08:45 +0100
> Matthew Garrett <mjg59@srcf.ucam.org> wrote:
>
> > On Thu, Aug 23, 2012 at 03:32:50PM -0600, David Ahern wrote:
> >
> > > Why not add support for the missing functions (on_exit, getsid,
> > > psignal and getline) to Bionic instead of perf?
> >
> > Many vendors need to target existing Android platforms and
> > don't have the luxury of waiting for code to get through
> > Google review and then land on devices between 6 months in
> > the future and never. The embedded world is dysfunctional in
> > a whole bunch of ways.
>
> So add a small library and link with -lstuffandroidforgot.
> That's basically how the FSF dealt with all the proprietary
> Unix library messes.
>
> Come to think of it call the library "integrated build runtime
> environment" and you can like with -libre ;)
>
> It's also going to be far more maintainable and generically
> useful for porting tools from GNU to 'droid userspace.
Well, you should see the uglies Git has to support Windows ;-)
Anyway, I'm not against making perf work on Android in
principle, it is Obviously Useful (tm).
Thanks,
Ingo
next prev parent reply other threads:[~2012-08-24 18:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 15:01 [PATCHv2 1/1] perf: Port to Android Bernhard Rosenkraenzer
2012-08-23 20:51 ` Pekka Enberg
2012-08-23 21:32 ` David Ahern
2012-08-24 4:08 ` Matthew Garrett
2012-08-24 8:35 ` Ingo Molnar
2012-08-24 12:30 ` Alan Cox
2012-08-24 18:02 ` Ingo Molnar [this message]
2012-08-24 9:02 ` Namhyung Kim
2012-08-24 9:09 ` Namhyung Kim
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=20120824180201.GA32144@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=acme@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bernhard.rosenkranzer@linaro.org \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mjg59@srcf.ucam.org \
--cc=penberg@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