From: Alexandra Yates <alexandra.yates at linux.intel.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] Complete build options for Pthread API
Date: Thu, 30 Oct 2014 20:35:27 -0700 [thread overview]
Message-ID: <50509.10.252.141.137.1414726527.squirrel@linux.intel.com> (raw)
In-Reply-To: CAG27Bk1t+2ZjJbrywNJYN+Hco+W+P-hGRsL9HsLcW7gyNXmVJA@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 2475 bytes --]
> On 25 October 2014 09:58, Sergey Senozhatsky
> <sergey.senozhatsky(a)gmail.com> wrote:
>> On (10/22/14 15:33), Sami Kerola wrote:
>>> On 22 October 2014 13:41, Sergey Senozhatsky
>>> <sergey.senozhatsky(a)gmail.com> wrote:
>>> > m4/* files are host-specific. they should never be part
>>> > of the source code or a package.
>>>
>>> I would not say it so strongly. There are plenty of projects that have
>>> files in m4 directory. Here's couple.
>>>
>>> http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=tree;f=m4
>>> https://github.com/karelzak/util-linux/tree/master/m4
>>
>> yes, but powertop does not use any optional m4 macros/libs that
>> are not basically available (afaik).
>
> Proposal to use AX_PTHREAD means that will change.
>
> Looking autoconf release notes
>
> http://lwn.net/Articles/531373/
>
> It might be possible to make m4 copies to go to AC_CONFIG_MACRO_DIR,
> while AC_CONFIG_MACRO_DIRS informs project specific m4 search patch.
> Assuming this sort of thing is tried it also looks like the autoconf
> version requirement will need to be pumped to 1.13 from 1.11.1. Please
> notice that I haven't ever tried to use multiple m4 directories, so
> this is reply is based on tons of assumptions without real experience
> or tests about topic. The minimum I need to make progress with
> separation is a decision what is the path for project local m4 files.
>
> That said autotools documentation
>
> http://www.gnu.org/software/automake/manual/html_node/Local-Macros.html
>
> is telling use of m4 directory is fine, and 'there is no consensus on
> the distribution of third-party macros'.
>
> Considering the above I'm 87.5% sure using m4/ directory initially to
> introduce AX_PTHREAD is OK. If needed/wanted/etc later changes can
> move the data around, set autoconf requirement higher, and so on what
> ever might come as aside effect.
>
>> https://lists.01.org/pipermail/powertop/2013-June/000855.html
>
> I do not understand how that message relates to m4 directories.
>
> --
> Sami Kerola
> http://www.iki.fi/kerolasa/
> _______________________________________________
> PowerTop mailing list
> PowerTop(a)lists.01.org
> https://lists.01.org/mailman/listinfo/powertop
>
What is the the return on investment for this feature in terms of
performance?
At the moment PowerTOP builds with in 40 seconds from source and building
the package takes ~15 seconds.
Thank you,
Alexandra.
next reply other threads:[~2014-10-31 3:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 3:35 Alexandra Yates [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-01 8:15 [Powertop] Complete build options for Pthread API SF Markus Elfring
2014-10-31 18:01 Alexandra Yates
2014-10-31 10:20 SF Markus Elfring
2014-10-31 10:01 Sami Kerola
2014-10-31 2:34 Alexandra Yates
2014-10-25 10:18 Sami Kerola
2014-10-25 8:58 Sergey Senozhatsky
2014-10-22 14:33 Sami Kerola
2014-10-22 12:41 Sergey Senozhatsky
2014-10-22 9:41 Sami Kerola
2014-10-20 4:44 SF Markus Elfring
2014-10-19 18:18 Sami Kerola
2014-10-19 11:30 SF Markus Elfring
2014-10-18 22:57 Sami Kerola
2014-10-18 19:20 SF Markus Elfring
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=50509.10.252.141.137.1414726527.squirrel@linux.intel.com \
--to=powertop@lists.01.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.