Re: Reviewing big.LITTLE MP documentation
On Mon, Jul 23, 2012 at 1:14 AM, Vikram Dhillon wrote: > Hi all, > > I am in the process of documenting the major developments that have > occurred since last year in big.LITTLE processing and I will post a > formal RFC soon, before that I wanted to get some idea of whether I'm > going in the right direction. So following some wiki-pages and pull > requests, I'm going to document the following: Vikram, Thanks for volunteering to do this. I asume you're already aware of Viresh's integration tree[1]? > == > - Paul Turner's load tracking patchset (15) > - Thomas Gleixner's per-cpu-thread hotplugging (6) > - Vincent Guittot's topology patchset and the ARM topology definition > patchset: http://patches.linaro.org/2444/ (~6) > - Colin Cross's patchset removing the cpuidle patchset that removes > cpu0 power down restriction (4) > - Morten Rasmussen's forced HMP task migration patchset (5) > == That list seems to be ok for now, but we'll be adding more stuff to this soon. Please keep in touch with Viresh if you want to keep on top of this. > Please let me know if I missing out any important patch-sets? These > patches come with ample documentation but thus far I haven't seen a > single hub to get updates or information regarding them. Thanks for > your time! I started a skeleton wiki page[2] to keep track of the various patchsets, a short description of the features they enable, etc. It would be nice if you could contribute to this directly. Feel free to edit it. May I ask what you interest in b.L MP is? Regards, Amit [1] http://git.linaro.org/gitweb?p=arm/big.LITTLE/mp.git;a=summary [2] https://wiki.linaro.org/WorkingGroups/PowerManagement/Process/bigLittleMPTree ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Nexus 7/Jellybean Kernel Config
On Sun, Jul 08, 2012 at 09:40:46AM +0100, Dave Pigott wrote: > > > Shouldn't require a kernel change. Just a configuration with a really > > annoyingly low default. I am concerned with the explosion of the numbers > > mmc partitions in android though... > > > > > So am I. It means that, until the sd mux lands, we will have to have a > special kernel build of the lava master images to support more > partitions. We already ran out on imx53 and origen so we can't support > the userdata partition. What's the status of this fabled SD MUX thingamajig? -- Christian Robottom Reis, Engineering VP Brazil (GMT-3) | [+55] 16 9112 6430 | [+1] 612 216 4935 Linaro.org: Open Source Software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Nexus 7/Jellybean Kernel Config
+Zach +Andy Last I heard we were waiting on them to make the first batch and get them to us, but it had to be a decent sized run so it was going to be split with someone else. Zach or Andy may have more recent news though. On Jul 24, 2012 2:54 PM, "Christian Robottom Reis" wrote: > On Sun, Jul 08, 2012 at 09:40:46AM +0100, Dave Pigott wrote: > > > > > Shouldn't require a kernel change. Just a configuration with a really > annoyingly low default. I am concerned with the explosion of the numbers > mmc partitions in android though... > > > > > > > > So am I. It means that, until the sd mux lands, we will have to have a > > special kernel build of the lava master images to support more > > partitions. We already ran out on imx53 and origen so we can't support > > the userdata partition. > > What's the status of this fabled SD MUX thingamajig? > -- > Christian Robottom Reis, Engineering VP > Brazil (GMT-3) | [+55] 16 9112 6430 | [+1] 612 216 4935 > Linaro.org: Open Source Software for ARM SoCs > ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Nexus 7/Jellybean Kernel Config
Bero is working on it. We have some preliminary builds out: Go to: https://android-build.linaro.org/ search, jb Thing may change a bit (names, manifests, etc..) On 24 July 2012 15:19, Paul Larson wrote: > +Zach +Andy > Last I heard we were waiting on them to make the first batch and get them to > us, but it had to be a decent sized run so it was going to be split with > someone else. Zach or Andy may have more recent news though. > > On Jul 24, 2012 2:54 PM, "Christian Robottom Reis" wrote: >> >> On Sun, Jul 08, 2012 at 09:40:46AM +0100, Dave Pigott wrote: >> > >> > > Shouldn't require a kernel change. Just a configuration with a really >> > > annoyingly low default. I am concerned with the explosion of the numbers >> > > mmc partitions in android though... >> > > >> > > >> > So am I. It means that, until the sd mux lands, we will have to have a >> > special kernel build of the lava master images to support more >> > partitions. We already ran out on imx53 and origen so we can't support >> > the userdata partition. >> >> What's the status of this fabled SD MUX thingamajig? >> -- >> Christian Robottom Reis, Engineering VP >> Brazil (GMT-3) | [+55] 16 9112 6430 | [+1] 612 216 4935 >> Linaro.org: Open Source Software for ARM SoCs -- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[PATCH] acpi : remove power from acpi_processor_cx structure
Remove the power field as it is not used.
Signed-off-by: Daniel Lezcano
Cc: Konrad Rzeszutek Wilk
---
drivers/acpi/processor_idle.c|2 --
drivers/xen/xen-acpi-processor.c |1 -
include/acpi/processor.h |1 -
3 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
index e589c19..90582fb 100644
--- a/drivers/acpi/processor_idle.c
+++ b/drivers/acpi/processor_idle.c
@@ -483,8 +483,6 @@ static int acpi_processor_get_power_info_cst(struct
acpi_processor *pr)
if (obj->type != ACPI_TYPE_INTEGER)
continue;
- cx.power = obj->integer.value;
-
current_count++;
memcpy(&(pr->power.states[current_count]), &cx, sizeof(cx));
diff --git a/drivers/xen/xen-acpi-processor.c b/drivers/xen/xen-acpi-processor.c
index 7ff2569..7ef9c1d 100644
--- a/drivers/xen/xen-acpi-processor.c
+++ b/drivers/xen/xen-acpi-processor.c
@@ -98,7 +98,6 @@ static int push_cxx_to_hypervisor(struct acpi_processor *_pr)
dst_cx->type = cx->type;
dst_cx->latency = cx->latency;
- dst_cx->power = cx->power;
dst_cx->dpcnt = 0;
set_xen_guest_handle(dst_cx->dp, NULL);
diff --git a/include/acpi/processor.h b/include/acpi/processor.h
index 64ec644..db427fa 100644
--- a/include/acpi/processor.h
+++ b/include/acpi/processor.h
@@ -59,7 +59,6 @@ struct acpi_processor_cx {
u8 entry_method;
u8 index;
u32 latency;
- u32 power;
u8 bm_sts_skip;
char desc[ACPI_CX_DESC_LEN];
};
--
1.7.5.4
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Reviewing big.LITTLE MP documentation
On Tue, Jul 24, 2012 at 8:43 AM, Amit Kucheria wrote: > > I started a skeleton wiki page[2] to keep track of the various > patchsets, a short description of the features they enable, etc. It > would be nice if you could contribute to this directly. Feel free to > edit it. > > May I ask what you interest in b.L MP is? > > Regards, > Amit > > > [1] http://git.linaro.org/gitweb?p=arm/big.LITTLE/mp.git;a=summary > [2] > https://wiki.linaro.org/WorkingGroups/PowerManagement/Process/bigLittleMPTree Hi Amit, Yea, following Viresh's pull requests and your answer [1] I have been following big.LITTLE progress over the time. The wiki page would be a good help perhaps posting there might be a better idea. If I have covered enough ground over the time then I can post an RFC fairly soon. I'm mostly researching HMP for task placement and the big.LITTLE model seems perfect for that, earlier on I was working on an approach based on a restricted-type NUMA version where the CCI-400 can be used for lookups and based on remote-lookups some node_scan() can be used from NUMA-load balancers for task-placement, the NUMA load balancer patches that were recently posted to lkml by Andrea and Peter each following their own approach. That idea didn't seem to work so well, atm I'm reading Morten's patches to contribute code in that direction. [1] http://ask.linaro.org/questions/159/power-management-working-group-hmp-enhancements -- Regards, Vikram Dhillon ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
2012/7/25 Linaro Android Platform Team meeting agenda posted
Linaro Android platform team agenda posted to https://wiki.linaro.org/Platform/Android/Meetings/2012-07-25. 13:00 UTC in #linaro-meeting on irc.freenode.net on 2012/7/25. We’re going to present our JB upgrade plan (basically put the kernels we’re currently using into the builds and start fixing stuff). -- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Reviewing big.LITTLE MP documentation
On Wed, Jul 25, 2012 at 5:20 AM, Vikram Dhillon wrote: > On Tue, Jul 24, 2012 at 8:43 AM, Amit Kucheria > wrote: >> >> I started a skeleton wiki page[2] to keep track of the various >> patchsets, a short description of the features they enable, etc. It >> would be nice if you could contribute to this directly. Feel free to >> edit it. >> >> May I ask what you interest in b.L MP is? >> >> Regards, >> Amit >> >> >> [1] http://git.linaro.org/gitweb?p=arm/big.LITTLE/mp.git;a=summary >> [2] >> https://wiki.linaro.org/WorkingGroups/PowerManagement/Process/bigLittleMPTree > > Hi Amit, > > Yea, following Viresh's pull requests and your answer [1] I have been > following big.LITTLE progress over the time. The wiki page would be a > good help perhaps posting there might be a better idea. If I have > covered enough ground over the time then I can post an RFC fairly > soon. Looking forward to seeing it! > I'm mostly researching HMP for task placement and the big.LITTLE model > seems perfect for that, earlier on I was working on an approach based > on a restricted-type NUMA version where the CCI-400 can be used for > lookups and based on remote-lookups some node_scan() can be used from > NUMA-load balancers for task-placement, the NUMA load balancer patches > that were recently posted to lkml by Andrea and Peter each following > their own approach. That idea didn't seem to work so well, atm I'm > reading Morten's patches to contribute code in that direction. May I ask if you work for Broadcom then (since that question was asked by a Broadcom person)? > [1] > http://ask.linaro.org/questions/159/power-management-working-group-hmp-enhancements > > -- > Regards, > Vikram Dhillon ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
