From: Saul Wold <sgw@linux.intel.com>
To: Andre McCurdy <armccurdy@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/5] tuning support for 1st and 2nd generation Intel Atom CPUs
Date: Fri, 23 Oct 2015 08:59:39 -0700 [thread overview]
Message-ID: <562A596B.50300@linux.intel.com> (raw)
In-Reply-To: <1445281177-3309-1-git-send-email-armccurdy@gmail.com>
On 10/19/2015 11:59 AM, Andre McCurdy wrote:
> Andre McCurdy (5):
> tune-corei7.inc: fix PACKAGE_EXTRA_ARCHS_tune-corei7-32 typo
This change makes sense
> tune-bonnell.inc: support for first generation Intel Atom CPUs
> tune-silvermont.inc: support for second generation Intel Atom CPUs
> tune-atom.inc: include tune-bonnell.inc instead of tune-core2.inc
> tune-corei7.inc: update comments regarding Silvermont support
>
I am not sure these make sense, it adds additional complexity to an
already complex testing matrix.
Both the bonnell and silvermont tunes are fully part of their respective
core* tune settings, there is no real need to become more specific. We
know that newer code is starting to use intrinsics that can determine
the correct extensions based on the CPU type.
I know you replied partly to RP's query, but is there something specific
your trying to accomplish with these additional .incs that we don't
already do and if so what?
Sau!
meta-intel maintainer
> meta/conf/machine/include/tune-atom.inc | 4 +--
> meta/conf/machine/include/tune-bonnell.inc | 35 ++++++++++++++++++++++++++
> meta/conf/machine/include/tune-corei7.inc | 6 ++---
> meta/conf/machine/include/tune-silvermont.inc | 36 +++++++++++++++++++++++++++
> 4 files changed, 76 insertions(+), 5 deletions(-)
> create mode 100644 meta/conf/machine/include/tune-bonnell.inc
> create mode 100644 meta/conf/machine/include/tune-silvermont.inc
>
prev parent reply other threads:[~2015-10-23 15:59 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
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 [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=562A596B.50300@linux.intel.com \
--to=sgw@linux.intel.com \
--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