From: jsun@junsun.net (Jun Sun)
To: linux-arm-kernel@lists.infradead.org
Subject: Can cores have different CPU features in a SMP system?
Date: Fri, 29 Jul 2016 14:30:54 -0700 [thread overview]
Message-ID: <CAP5Nno430Jt3Ax2jUPP6ELpVBF-pK0Akxsa8sZ55f8GL7LQt=g@mail.gmail.com> (raw)
One specific example is that if a phone has two clusters. Cores in
one cluster has v8 crypto extension and cores in the other don't.
Will this work?
My gut feeling is no, since many apps query cpu features at run-time.
And process can migrate among cores. If an app starts on a core with
CE and migrates to another core without CE. Illegal instruction fault
will happen.
Just wanna confirm if this is indeed the case. Surprisingly google
search did not yield any meaningful answers.
Cheers.
Jun
next reply other threads:[~2016-07-29 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 21:30 Jun Sun [this message]
2016-08-01 19:08 ` Can cores have different CPU features in a SMP system? Jun Sun
2016-08-02 10:09 ` Suzuki K Poulose
2016-08-02 17:23 ` Jun Sun
2016-08-03 9:00 ` Suzuki K Poulose
2016-08-03 9:42 ` Suzuki K Poulose
2016-08-04 4:14 ` Jun Sun
2016-08-04 8:42 ` Suzuki K Poulose
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='CAP5Nno430Jt3Ax2jUPP6ELpVBF-pK0Akxsa8sZ55f8GL7LQt=g@mail.gmail.com' \
--to=jsun@junsun.net \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).