From: Henning Schild <henning.schild@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH] charter: Introduce build chart generation tool
Date: Tue, 27 Apr 2021 20:07:20 +0200 [thread overview]
Message-ID: <20210427200720.3388d82b@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <f36cb66b-e65f-d763-6e48-bee508416571@ilbers.de>
Am Tue, 27 Apr 2021 20:28:28 +0300
schrieb Anton Mikanovich <amikan@ilbers.de>:
> 27.04.2021 20:01, Henning Schild wrote:
> > I think we should not parse those logs and do our own profiling.
> > bitbake has profiling support in several flavours. Last time i
> > checked isar was missing some library bits that are only in oe.
> >
> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.yoctoproject.org%2Fwiki%2FProfiling&data=04%7C01%7Cde173c00-e982-4fda-8644-47edf4671d63%40ad011.siemens.com%7Cc6c6d17c69c04eeaf7af08d909a1e352%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637551413172636476%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=hYyPIOO5TOCgZ%2B3kO7deFafAfhTi787HeXsgDqUTy1A%3D&reserved=0
> >
> > We should see what is the state of the art in yocto/OE and use
> > that, no own inventions. Then see how to get that into isar and
> > possibly massage it upstream to get it into isar without forking
> > oe/bitbake bits. Or we add "charter" to bitbake and take it from
> > there, in case we fill a gap that upstream might have.
> >
> > Am i correct that this charter is something that oe/bitbake does not
> > have?
> >
> > regards,
> > Henning
>
> Yes, this charter is our simple implementation of the same result as
> pybootchart+buildstats can produce in oe.
If it is "the same" i would like to question why we need that again and
can not use what is there.
> Buildstats-based solution is also not real-time and integration of
> the whole buildstats into Isar can be tricky.
We should look into why upstream can be tricky for us and solve those
tricky issues, or add that "charter" upstream if it fills a gap that
upstream might have.
Forking bitbake (and wic, probably not involved here) would be a really
bad idea. And even adding plugins might be bad.
For such central topics working together with oe and bitbake is the
only maintainable way ... IMHO. I already invested a lot on the wic
side and also on bitbake, and the projects seem to be open to the
isar-case from what i can tell.
regards,
Henning
prev parent reply other threads:[~2021-04-27 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 13:07 Anton Mikanovich
2021-04-22 10:22 ` Anton Mikanovich
2021-04-22 11:17 ` Jan Kiszka
2021-04-27 11:13 ` Anton Mikanovich
2021-04-27 17:01 ` Henning Schild
2021-04-27 17:28 ` Anton Mikanovich
2021-04-27 18:07 ` Henning Schild [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=20210427200720.3388d82b@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=amikan@ilbers.de \
--cc=isar-users@googlegroups.com \
/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