OpenEmbedded runlevels empty?

2013-01-23 Thread Tim Northover
Hi again,

Sorry for spamming this list with what are essentially support questions, but
now that bug #1099896 has been fixed, I'm trying to build an OpenEmbedded
filesystem with it, following the instructions at
https://wiki.linaro.org/HowTo/ARMv8/OpenEmbedded.

What comes out seems amazingly close to a functional system, except that
nothing gets put into runlevel 5 so none of the actual programs get started on
boot (mainly sshd and a console login obviously, I could work around anything
else).

Has anyone seen this before or know where I should start looking? I've not
really used OpenEmbedded before.

Cheers.

Tim.

-- IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium.  Thank you.


___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


Re: OpenEmbedded runlevels empty?

2013-01-23 Thread Marcin Juszkiewicz
W dniu 23.01.2013 10:46, Tim Northover pisze:
 Hi again,
 
 Sorry for spamming this list with what are essentially support questions, but
 now that bug #1099896 has been fixed, I'm trying to build an OpenEmbedded
 filesystem with it, following the instructions at
 https://wiki.linaro.org/HowTo/ARMv8/OpenEmbedded.
 
 What comes out seems amazingly close to a functional system, except that
 nothing gets put into runlevel 5 so none of the actual programs get started on
 boot (mainly sshd and a console login obviously, I could work around anything
 else).
 
 Has anyone seen this before or know where I should start looking? I've not
 really used OpenEmbedded before.

I am working on it today.


___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


Re: OpenEmbedded runlevels empty?

2013-01-23 Thread Marcin Juszkiewicz
W dniu 23.01.2013 10:46, Tim Northover pisze:
 Hi again,
 
 Sorry for spamming this list with what are essentially support questions, but
 now that bug #1099896 has been fixed, I'm trying to build an OpenEmbedded
 filesystem with it, following the instructions at
 https://wiki.linaro.org/HowTo/ARMv8/OpenEmbedded.
 
 What comes out seems amazingly close to a functional system, except that
 nothing gets put into runlevel 5 so none of the actual programs get started on
 boot (mainly sshd and a console login obviously, I could work around anything
 else).

edit build/conf/site.conf and change DISTRO_FEATURES to this (in one line):

'DISTRO_FEATURES = x11 alsa argp ext2 largefile usbgadget usbhost xattr
nfs zeroconf ${DISTRO_FEATURES_LIBC} ${DISTRO_FEATURES_INITMAN}

Then it will work again.

___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


[GIT PULL]: big LITTLE MP master v14

2013-01-23 Thread Viresh Kumar
Hi Andrey,

I know you have already pulled in V14, but it has got changed now. So, please
repull it. (Branch: sched-pack-small-tasks-v2 is dropped now)

Updates:
---
- Rebased over 3.8-rc2
- per-task-load-average-v3-merged dropped as its already present in 3.8-rc2
- sched-pack-small-tasks-v1-fixed and
sched-pack-small-tasks-v1-arm dropped, as
  sched-pack-small-tasks-v2 contains all required patches. Even
  sched-pack-small-tasks-v2 is dropped at last moment due to some issues.
- Few patches from arm-multi_pmu_v2 dropped as they are already mainlined.
- Stats: Total distinct patches: 37
  - New Patches: cpufreq-fixes-v2 (5)


x-x

The following changes since commit d1c3ed669a2d452cacfb48c2d171a1f364dae2ed:

  Linux 3.8-rc2 (2013-01-02 18:13:21 -0800)

are available in the git repository at:

  git://git.linaro.org/arm/big.LITTLE/mp.git big-LITTLE-MP-master-v14

for you to fetch changes up to 56a331912166f0f618f0c0cf633c87967fe487c0:

  Merge branches 'arm-multi_pmu_v2', 'cpufreq-fixes-v2',
'hw-bkp-v7.1-debug-v2', 'task-placement-v2-sysfs', 'misc-patches' and
'config-fragments' into big-LITTLE-MP-master-v14 (2013-01-23 17:24:03
+0530)



Chris Redpath (2):
  ARM: Experimental Frequency-Invariant Load Scaling Patch
  ARM: Fix build breakage when big.LITTLE.conf is not used.

Dietmar Eggemann (2):
  ARM: hw_breakpoint: Check function for OS Save and Restore mechanism
  ARM: hw_breakpoint: Debug powerdown support for self-hosted debug

Jon Medhurst (1):
  ARM: sched: Avoid empty 'slow' HMP domain

Liviu Dudau (1):
  linaro/configs: big-LITTLE-MP: Enable the new tunable sysfs
interface by default.

Lorenzo Pieralisi (1):
  ARM: kernel: provide cluster to logical cpu mask mapping API

Morten Rasmussen (14):
  sched: entity load-tracking load_avg_ratio
  sched: Task placement for heterogeneous systems based on task
load-tracking
  sched: Forced task migration on heterogeneous systems
  sched: Introduce priority-based task migration filter
  ARM: Add HMP scheduling support for ARM architecture
  ARM: sched: Use device-tree to provide fast/slow CPU list for HMP
  ARM: sched: Setup SCHED_HMP domains
  sched: Add ftrace events for entity load-tracking
  sched: Add HMP task migration ftrace event
  sched: SCHED_HMP multi-domain task migration control
  sched: Enable HMP priority filter by default
  sched: Only down migrate low priority tasks if allowed by affinity mask
  linaro/configs: Enable HMP priority filter by default
  sched: Basic global balancing support for HMP

Olivier Cozette (1):
  ARM: Change load tracking scale using sysfs

Paul Turner (1):
  sched: implement usage tracking

Sudeep KarkadaNagesha (6):
  ARM: perf: replace global CPU PMU pointer with per-cpu pointers
  ARM: perf: register CPU PMUs with idr types
  ARM: perf: set cpu affinity to support multiple PMUs
  ARM: perf: set cpu affinity for the irqs correctly
  ARM: perf: remove spaces in CPU PMU names
  ARM: perf: save/restore pmu registers in pm notifier

Thomas Gleixner (1):
  genirq: Add default affinity mask command line option

Viresh Kumar (9):
  configs: Add config fragments for big LITTLE MP
  linaro/configs: Update big LITTLE MP fragment for task placement work
  config-frag/big-LITTLE: Use device-tree to provide fast/slow CPU
list for HMP
  cpufreq: Manage only online cpus
  cpufreq: Notify governors when cpus are hot-[un]plugged
  cpufreq: Don't use cpu removed during cpufreq_driver_unregister
  cpufreq: Simplify __cpufreq_remove_dev()
  cpufreq: Simplify cpufreq_add_dev()
  Merge branches 'arm-multi_pmu_v2', 'cpufreq-fixes-v2',
'hw-bkp-v7.1-debug-v2', 'task-placement-v2-sysfs', 'misc-patches' and
'config-fragments' into big-LITTLE-MP-master-v14

 Documentation/devicetree/bindings/arm/pmu.txt |3 +
 Documentation/kernel-parameters.txt   |9 +
 arch/arm/Kconfig  |   85 ++
 arch/arm/include/asm/hw_breakpoint.h  |3 +
 arch/arm/include/asm/pmu.h|   12 +
 arch/arm/include/asm/topology.h   |   34 +
 arch/arm/kernel/hw_breakpoint.c   |   56 +-
 arch/arm/kernel/perf_event.c  |   19 +
 arch/arm/kernel/perf_event_cpu.c  |  117 ++-
 arch/arm/kernel/perf_event_v7.c   |   57 +-
 arch/arm/kernel/topology.c|  120 +++
 drivers/cpufreq/cpufreq.c |  321 
 drivers/cpufreq/cpufreq_stats.c   |   27 +-
 drivers/cpufreq/freq_table.c  |9 +
 include/linux/cpufreq.h   |   14 +-
 include/linux/sched.h |   12 +
 include/trace/events/sched.h  |  153 
 kernel/irq/irqdesc.c

Re: [GIT PULL]: big LITTLE MP master v14

2013-01-23 Thread Viresh Kumar
On 23 January 2013 17:38, Viresh Kumar viresh.ku...@linaro.org wrote:
 Hi Andrey,

 I know you have already pulled in V14, but it has got changed now. So, please
 repull it. (Branch: sched-pack-small-tasks-v2 is dropped now)

BTW, the earlier v14 with sched-pack-small-tasks-v2 is preserved as
big-LITTLE-MP-master-v14-bkp

___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


Re: OpenEmbedded runlevels empty?

2013-01-23 Thread Tim Northover
Hi Marcin,

On Wednesday 23 Jan 2013 11:08:16 Marcin Juszkiewicz wrote:
 edit build/conf/site.conf and change DISTRO_FEATURES to this (in one line):

 'DISTRO_FEATURES = x11 alsa argp ext2 largefile usbgadget usbhost xattr
 nfs zeroconf ${DISTRO_FEATURES_LIBC} ${DISTRO_FEATURES_INITMAN}

 Then it will work again.

Thanks for that suggestion (and your other help). It's working perfectly now.

There's just one other thing I had to do, which it might be worth either
documenting or automating. I had to switch eth0 over to dhcp for networking to
work.

Tim.

-- IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium.  Thank you.


___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


Re: sched: Consequences of integrating the Per Entity Load Tracking Metric into the Load Balancer

2013-01-23 Thread Alex Shi


 Maybe we can skip local group since it's a bottom-up search so we know
 there's no idle cpu in the lower domain from the prior iteration.

 
 I did this change but seems results are worse on my machines, guess start 
 seeking idle cpu bottom up is a bad idea.
 The following is full version with above change.
 

also tried to keep top-down seeking mode, and will return any idle cpu
instead of the first cpu in a idle group. But the result doesn't show
better on benchmark hackbench.

===
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 5eea870..fb85094 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -3169,6 +3169,7 @@ static int wake_affine(struct sched_domain *sd,
struct task_struct *p, int sync)
return 1;
}
+   /* bias toward prev cpu */
return 0;
 }
 @@ -3252,7 +3253,8 @@ find_idlest_cpu(struct sched_group *group, struct
task_struct *p, int this_cpu)
 /*
  * Try and locate an idle CPU in the sched_domain.
  */
-static int select_idle_sibling(struct task_struct *p, int target)
+static int select_idle_sibling(struct task_struct *p,
+   struct sched_domain *affine_sd, int sync)
 {
int cpu = smp_processor_id();
int prev_cpu = task_cpu(p);
@@ -3264,20 +3266,23 @@ static int select_idle_sibling(struct
task_struct *p, int target)
 * If the task is going to be woken-up on this cpu and if it is
 * already idle, then it is the right target.
 */
-   if (target == cpu  idle_cpu(cpu))
+   if (idle_cpu(cpu))
return cpu;
/*
 * If the task is going to be woken-up on the cpu where it previously
 * ran and if it is currently idle, then it the right target.
 */
-   if (target == prev_cpu  idle_cpu(prev_cpu))
+   if (cpu != prev_cpu  idle_cpu(prev_cpu))
return prev_cpu;
 +  if (cpu != prev_cpu  !wake_affine(affine_sd, p, sync))
+   cpu = prev_cpu;
+
/*
 * Otherwise, iterate the domains and find an elegible idle cpu.
 */
-   sd = rcu_dereference(per_cpu(sd_llc, target));
+   sd = rcu_dereference(per_cpu(sd_llc, cpu));
for_each_lower_domain(sd) {
sg = sd-groups;
do {
@@ -3290,7 +3295,7 @@ static int select_idle_sibling(struct task_struct
*p, int target)
goto next;
}
 -  target = cpumask_first_and(sched_group_cpus(sg),
+   cpu = cpumask_first_and(sched_group_cpus(sg),
tsk_cpus_allowed(p));
goto done;
 next:
@@ -3298,7 +3303,7 @@ next:
} while (sg != sd-groups);
}
 done:
-   return target;
+   return cpu;
 }
  /*
@@ -3351,10 +3356,7 @@ select_task_rq_fair(struct task_struct *p, int
sd_flag, int wake_flags)
}
if (affine_sd) {
-   if (cpu != prev_cpu  wake_affine(affine_sd, p, sync))
-   prev_cpu = cpu;
-
-   new_cpu = select_idle_sibling(p, prev_cpu);
+   new_cpu = select_idle_sibling(p, affine_sd, sync);
goto unlock;
}


___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


Re: [patch v4 0/18] sched: simplified fork, release load avg and power awareness scheduling

2013-01-23 Thread Viresh Kumar
On 24 January 2013 08:36, Alex Shi alex@intel.com wrote:
 Since the runnable info needs 345ms to accumulate, balancing
 doesn't do well for many tasks burst waking. After talking with Mike
 Galbraith, we are agree to just use runnable avg in power friendly
 scheduling and keep current instant load in performance scheduling for
 low latency.

 So the biggest change in this version is removing runnable load avg in
 balance and just using runnable data in power balance.

Pushed as power-aware-scheduling-v4 at:

http://git.linaro.org/gitweb?p=arm/big.LITTLE/mp.git;a=summary

___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


Re: [ RFC patch 0/4]: use runnable load avg in cfs balance instead of instant load

2013-01-23 Thread Viresh Kumar
On 24 January 2013 09:00, Alex Shi alex@intel.com wrote:
 This patchset can be used, but causes burst waking benchmark aim9 drop 5~7%
 on my 2 sockets machine. The reason is too light runnable load in early stage
 of waked tasks cause imbalance in balancing.

 So, it is immature and just a reference for guys who want to go gurther.

Pushed as runnable-load-avg-in-load-balance-v1-resent at:

http://git.linaro.org/gitweb?p=arm/big.LITTLE/mp.git;a=summary

___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


Re: [ RFC patch 0/4]: use runnable load avg in cfs balance instead of instant load

2013-01-23 Thread Alex Shi
On 01/24/2013 01:15 PM, Viresh Kumar wrote:
 On 24 January 2013 09:00, Alex Shi alex@intel.com wrote:
 This patchset can be used, but causes burst waking benchmark aim9 drop 5~7%
 on my 2 sockets machine. The reason is too light runnable load in early stage
 of waked tasks cause imbalance in balancing.

 So, it is immature and just a reference for guys who want to go gurther.
 
 Pushed as runnable-load-avg-in-load-balance-v1-resent at:
 
 http://git.linaro.org/gitweb?p=arm/big.LITTLE/mp.git;a=summary
 

Thanks!
For full usable version, you still need the patch 6~8 of
power-scheduling patchset.

-- 
Thanks Alex

___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


[RFC] Virtio-desktop: Virtio-based virtual desktop

2013-01-23 Thread Anup Patel
Hi All,

How about having a generic Virtio-based machine for emulating a virtual
desktop ?

I know folks have already thought about this and probably also tried
something or other on this front but, it will be good to know the downsides.

Virtio-desktop can be a separate specification describing a virtual
desktop.
Of-course we cannot avoid few architecture dependent virtual devices in but
the Virtio-desktop specification will try to keep minimum possible
architecture dependent devices.

As per our thoughts, a Virtio-desktop will have two kinds of devices:
1. Architecture dependent devices: This devices will be emulated in-kernel
by architecture specific code of KVM or Xen or Some other hypervisor.
   a) Virtualized CPU
   b) Virtualized PIC (i.e. in-kernel architecture specific emulation of
irqchip)
   c) Virtualized Timer (i.e. in-kernel architecture specific emulation of
timer chip)
2. Architecture independent devices: This are Virtio-based devices which
are usually required by a desktop virtual machine.
   a) Virtio-blk (storage)
  - Already available
   b) Virtio-net (network)
 - Already available
   c) Virtio-fb (display)
 - It seems some work has been already done for Virtio frame buffer but
I did not find drivers/fb/virtio-fb.c in latest kernel
   (http://thread.gmane.org/gmane.comp.emulators.kvm.devel/42720)
 - Is Virtio-fb work still in-progress ??
   d) Virtio-input (keyboard/mouse/multi-touch)
 - Currently not available
 - It will provide keyboard input events
 - It will provide mouse input events
 - It will provide multi-touch input events
   e) Virtio-power (reset/shutdown/enumeration)
 - It can provides info about the entire virtual machine including CPU,
PIC, Timer, available Virtio devices, etc.
 - It can also provide CPU and Virtio-device hot-plugging
 - Its primary purpose would be to provide reset and shutdown of CPU
and Virtio devices.
 - There will be only one instance of this device and its location will
be fixed for each architecture.

The Virtio-desktop specification may also describe a recommended memory map
of for each architecture.

Right now, only missing devices seems to be Virtio-fb, Virtio-input, and
Virtio-power, which some of us are willing to take-up.

IMHO, If we have something like Virtio-desktop specification then all
possible guest OSes can have support for it and different hypervisor can
emulate it without worrying about guest support.

Best Regards,
Anup
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev