From: Dario Faggioli <dario.faggioli@citrix.com>
To: Julien Grall <julien.grall@arm.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Peng Fan <van.freenix@gmail.com>
Cc: Juergen Gross <jgross@suse.com>, Peng Fan <peng.fan@nxp.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [RFC 0/5] xen/arm: support big.little SoC
Date: Tue, 20 Sep 2016 19:24:14 +0200 [thread overview]
Message-ID: <1474392254.4393.220.camel@citrix.com> (raw)
In-Reply-To: <4c52141f-a6a4-a0b1-dced-f799b592481e@arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 2038 bytes --]
On Tue, 2016-09-20 at 17:34 +0200, Julien Grall wrote:
> On 20/09/2016 12:27, George Dunlap wrote:
> > I think we definitely need to have Xen have some kind of idea the
> > order between processors, so that the user doesn't need to figure
> > out
> > which class / pool is big and which pool is LITTLE. Whether this
> > sort
> > of enumeration is the best way to do that I'll let Julien and
> > Stefano
> > give their opinion.
>
> I don't think an hardcoded list of processor in Xen is the right
> solution. There are many existing processors and combinations for
> big.LITTLE so it will nearly be impossible to keep updated.
>
As far as either the scheduler or cpupools go, what's necessary would
be:
- in Xen, a function (or an array acting as a map, or whatever) to
call to know whether pcpu X is big or LITTLE;
- at toolstack level, an hypercal (or a field, bit, whatever in a
struct already returned by an existing hypercall) to know the same
thing, i.e., whether c pcpu is big or LITTLE.
Once we have this, we can do everything. We will probably want to
abstract things a bit, and make them as generic as practical, so that
the same interface can be used not only for ARM big.LITTLE, but for
whatever future heterogeneous cpu arch we'll support... but really, the
actual information that we need is "just" that.
I've absolutely no idea how such info could be achieved, and I have no
ARM big.LITTLE hardware to test on.
> I would expect the firmware table (device tree, ACPI) to provide
> relevant data for each processor and differentiate big from LITTLE
> core.
> Note that I haven't looked at it for now. A good place to start is
> looking at how Linux does.
>
Makes sense.
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-09-20 17:24 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 2:08 [RFC 0/5] xen/arm: support big.little SoC van.freenix
2016-09-19 2:08 ` [RFC 1/5] xen/arm: domain_build: setting opt_dom0_max_vcpus according to cpupool0 info van.freenix
2016-09-19 2:08 ` [RFC 2/5] xen: cpupool: introduce cpupool_arch_info van.freenix
2016-09-19 2:08 ` [RFC 3/5] xen: cpupool: add arch cpupool hook van.freenix
2016-09-19 2:08 ` [RFC 4/5] xen/arm: move vpidr from arch_domain to arch_vcpu van.freenix
2016-09-19 2:08 ` [RFC 5/5] xen/arm: cpupool: implement arch_domain_cpupool_compatible van.freenix
2016-09-19 8:09 ` [RFC 0/5] xen/arm: support big.little SoC Julien Grall
2016-09-19 8:36 ` Peng Fan
2016-09-19 8:53 ` Julien Grall
2016-09-19 9:38 ` Peng Fan
2016-09-19 9:59 ` Julien Grall
2016-09-19 13:15 ` Peng Fan
2016-09-19 20:56 ` Stefano Stabellini
2016-09-19 9:45 ` George Dunlap
2016-09-19 10:06 ` Julien Grall
2016-09-19 10:23 ` Juergen Gross
2016-09-19 17:18 ` Dario Faggioli
2016-09-19 21:03 ` Stefano Stabellini
2016-09-19 22:55 ` Dario Faggioli
2016-09-20 0:01 ` Stefano Stabellini
2016-09-20 0:54 ` Dario Faggioli
2016-09-20 10:03 ` Peng Fan
2016-09-20 10:27 ` George Dunlap
2016-09-20 15:34 ` Julien Grall
2016-09-20 17:24 ` Dario Faggioli [this message]
2016-09-20 19:09 ` Stefano Stabellini
2016-09-20 19:41 ` Julien Grall
2016-09-20 20:17 ` Stefano Stabellini
2016-09-21 8:38 ` Peng Fan
2016-09-21 9:22 ` George Dunlap
2016-09-21 12:35 ` Peng Fan
2016-09-21 15:00 ` Dario Faggioli
2016-09-21 10:15 ` Julien Grall
2016-09-21 12:28 ` Peng Fan
2016-09-21 15:06 ` Dario Faggioli
2016-09-22 9:45 ` Peng Fan
2016-09-22 11:21 ` Julien Grall
2016-09-23 2:38 ` Peng Fan
2016-09-21 10:09 ` Julien Grall
2016-09-21 10:22 ` George Dunlap
2016-09-21 13:06 ` Julien Grall
2016-09-21 15:45 ` Dario Faggioli
2016-09-21 19:28 ` Julien Grall
2016-09-22 6:16 ` Peng Fan
2016-09-22 8:43 ` Dario Faggioli
2016-09-22 11:24 ` Julien Grall
2016-09-22 16:31 ` Dario Faggioli
2016-09-23 13:56 ` Julien Grall
2016-09-21 18:13 ` Stefano Stabellini
2016-09-21 19:11 ` Julien Grall
2016-09-21 19:21 ` Julien Grall
2016-09-21 23:45 ` Stefano Stabellini
2016-09-22 6:49 ` Peng Fan
2016-09-22 8:50 ` Dario Faggioli
2016-09-22 9:27 ` Peng Fan
2016-09-22 9:51 ` George Dunlap
2016-09-22 10:09 ` Peng Fan
2016-09-22 10:39 ` Dario Faggioli
2016-09-22 10:13 ` Juergen Gross
2016-09-22 9:52 ` Dario Faggioli
2016-09-22 11:29 ` Julien Grall
2016-09-22 17:31 ` Stefano Stabellini
2016-09-22 18:54 ` Julien Grall
2016-09-23 2:14 ` Peng Fan
2016-09-23 9:24 ` Julien Grall
2016-09-23 10:05 ` Peng Fan
2016-09-23 10:15 ` Julien Grall
2016-09-23 13:36 ` Dario Faggioli
2016-09-24 1:57 ` Stefano Stabellini
2016-09-23 13:52 ` Dario Faggioli
2016-09-24 1:35 ` Stefano Stabellini
2016-09-23 2:03 ` Peng Fan
2016-09-22 10:05 ` Peng Fan
2016-09-22 16:26 ` Dario Faggioli
2016-09-22 17:33 ` Stefano Stabellini
2016-09-21 12:38 ` Peng Fan
2016-09-21 9:45 ` Dario Faggioli
2016-09-20 10:18 ` George Dunlap
2016-09-19 20:55 ` Stefano Stabellini
2016-09-19 10:33 ` George Dunlap
2016-09-19 13:33 ` Peng Fan
2016-09-20 0:11 ` Dario Faggioli
2016-09-20 6:18 ` Peng Fan
2016-09-19 16:43 ` Dario Faggioli
2016-09-19 13:08 ` Peng Fan
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=1474392254.4393.220.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=julien.grall@arm.com \
--cc=peng.fan@nxp.com \
--cc=sstabellini@kernel.org \
--cc=van.freenix@gmail.com \
--cc=xen-devel@lists.xen.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).