Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/5] tune-atom.inc: include tune-bonnell.inc instead of tune-core2.inc
Date: Tue, 20 Oct 2015 10:16:38 +0100	[thread overview]
Message-ID: <1445332598.17974.142.camel@linuxfoundation.org> (raw)
In-Reply-To: <1445281177-3309-5-git-send-email-armccurdy@gmail.com>

On Mon, 2015-10-19 at 11:59 -0700, Andre McCurdy wrote:
> Use 'atom' as an alias for the first generation Intel Atom CPUs.
> ---
>  meta/conf/machine/include/tune-atom.inc | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/conf/machine/include/tune-atom.inc b/meta/conf/machine/include/tune-atom.inc
> index 5e1bb74..24cd676 100644
> --- a/meta/conf/machine/include/tune-atom.inc
> +++ b/meta/conf/machine/include/tune-atom.inc
> @@ -1,2 +1,2 @@
> -# Atom tunings are the same as core2 for now...
> -require conf/machine/include/tune-core2.inc
> +# Alias for the first generation of Intel Atom CPUs.
> +require conf/machine/include/tune-bonnell.inc

This is actually pretty nasty to anyone who uses package feeds or
packages since all of a sudden, the system rebuilds with a completely
different package architecture. Not sure we can take this change for
that reason.

I'd also like to understand how much of a difference these specific
tunes actually give. I know the Intel people have been trying to focus
on a smaller number of tunes that work well on the majority of platforms
rather than micro optimising the tunes.

Are there some benchmark numbers or other analysis which shows these
tunes as being more effective?

Cheers,

Richard





  parent reply	other threads:[~2015-10-20  9:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-19 18:59 [PATCH 0/5] tuning support for 1st and 2nd generation Intel Atom CPUs Andre McCurdy
2015-10-19 18:59 ` [PATCH 1/5] tune-corei7.inc: fix PACKAGE_EXTRA_ARCHS_tune-corei7-32 typo Andre McCurdy
2015-10-19 18:59 ` [PATCH 2/5] tune-bonnell.inc: support for first generation Intel Atom CPUs Andre McCurdy
2015-10-19 18:59 ` [PATCH 3/5] tune-silvermont.inc: support for second " Andre McCurdy
2015-10-19 18:59 ` [PATCH 4/5] tune-atom.inc: include tune-bonnell.inc instead of tune-core2.inc Andre McCurdy
2015-10-19 19:37   ` Khem Raj
2015-10-19 19:51     ` Andre McCurdy
2015-10-20  9:16   ` Richard Purdie [this message]
2015-10-20 20:55     ` Andre McCurdy
2015-10-19 18:59 ` [PATCH 5/5] tune-corei7.inc: update comments regarding Silvermont support Andre McCurdy
2015-10-22 18:57 ` [PATCH 0/5] tuning support for 1st and 2nd generation Intel Atom CPUs Saul Wold
2015-10-23 15:59 ` Saul Wold

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=1445332598.17974.142.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=armccurdy@gmail.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox