From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Cc: bitbake-dev <bitbake-dev@lists.berlios.de>
Subject: Re: Bitbake task logging
Date: Wed, 05 Jan 2011 00:45:12 +0000 [thread overview]
Message-ID: <1294188312.17519.22193.camel@rex> (raw)
In-Reply-To: <AANLkTinpcYFR8JaDHMtUcKW2YoaH6fG_+4An+Aq3mMoA@mail.gmail.com>
On Wed, 2011-01-05 at 00:40 +0300, Yury Bushmelev wrote:
> 2011/1/1 Richard Purdie <richard.purdie@linuxfoundation.org>:
> > I've been looking at the changes in bitbake master and those in Poky.
> > Both are trying to improve the logging situation but I think we need to
> > discuss/agree what we're trying to achieve.
>
> [skip]
>
> > Thoughts/Comments/Suggestions?
>
> I'm interested in build perfomance monitoring/analyze. It would be
> great to have some tool (may be like bootchart) to be able to look at
> CPU time/RAM/Disk bandwidth/network traffic per task.
You should already be able to do this with the addhandler functionality
in a bbclass file to tap into bitbake's event stream. If you find you
can't, we should enhance things so you can :).
Cheers,
Richard
next prev parent reply other threads:[~2011-01-05 0:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-01 18:14 Bitbake task logging Richard Purdie
2011-01-02 7:16 ` Esben Haabendal
2011-01-12 10:27 ` Aeschbacher, Fabrice
2011-01-12 12:35 ` Frans Meulenbroeks
2011-01-04 15:30 ` Chris Larson
2011-01-04 18:02 ` [Bitbake-dev] " Richard Purdie
2011-01-04 21:40 ` Yury Bushmelev
2011-01-05 0:45 ` Richard Purdie [this message]
2011-01-05 18:30 ` [Bitbake-dev] " Chris Larson
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=1294188312.17519.22193.camel@rex \
--to=rpurdie@rpsys.net \
--cc=bitbake-dev@lists.berlios.de \
--cc=openembedded-devel@lists.openembedded.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.