From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Tom Rini <trini@konsulko.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
Joshua Watt <JPEWhacker@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core] [PATCH] qemux86-64: Allow higher tunes
Date: Thu, 11 Aug 2022 18:07:16 +0200 [thread overview]
Message-ID: <CANNYZj-O7y0O3v_NfFmpRR3LbLFGcFOtWT+i3HjfDdMzSE3WZg@mail.gmail.com> (raw)
In-Reply-To: <20220811160416.GW1146598@bill-the-cat>
On Thu, 11 Aug 2022 at 18:04, Tom Rini <trini@konsulko.com> wrote:
> > This is less useful than it may seem, and merely moves the supported
> > CPU from circa-2006 core 2 to circa-2008 core i7. You won't get AVX or
> > anything newer, which requires adding these instructions to qemu
> > usermode (a project I'd like to do if I had the time).
>
> True but it's also the case that tune-corei7.conf is the newest one in
> oe-core, yes? I had previously peeked in meta-intel which has a
> skylake tune, but bringing that in is something I'd leave to Intel/WR
> folks to take care of.
Yes, from making things consistent perspective this change is fine.
The skylake tune in meta-intel gives its users two less than great
choices: disable qemu usermode, or disable everything that qemu
doesn't support (AVX and up).
Alex
next prev parent reply other threads:[~2022-08-11 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 15:40 [PATCH] qemux86-64: Allow higher tunes Tom Rini
2022-08-11 15:51 ` [OE-core] " Alexander Kanavin
2022-08-11 16:04 ` Tom Rini
2022-08-11 16:07 ` Alexander Kanavin [this message]
2022-08-11 16:42 ` Mittal, Anuj
2022-12-09 22:23 ` Alexander Kanavin
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=CANNYZj-O7y0O3v_NfFmpRR3LbLFGcFOtWT+i3HjfDdMzSE3WZg@mail.gmail.com \
--to=alex.kanavin@gmail.com \
--cc=JPEWhacker@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=trini@konsulko.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;
as well as URLs for NNTP newsgroup(s).