[ACTIVITY] Week 30

[Andrey Konovalov]

== Progress ==
* BB-29 ENG: Linux linaro baseline maintenance (80%):
  - added the updated Android topic back into linux-linaro-core-tracking tree, 
updated llct and ll to v4.2-rc3,
tagged the 15.07 linux-linaro kernel release
  - fixed vexpress64 linux-linaro CI builds by removing the step to build the 
boot wrapper (it no longer needed)
  - after the linux-linaro CI armv7 builds have been switched from utopic to 
vivid, the boards stopped booting
(/etc/machine-id is missing, and /etc is mounted ro). Added few kernel 
config option which are required by
systemd to distribution.conf fragment. This haven't made the 
/etc/machine-id error to disappear, but at least
the booting continued to the boot prompt, and the LAVA tests were executed.
  - noticed that enabling CONFIG_LOCALVERSION_AUTO in the config fragment 
doesn't result in git commit id being
added to the kernel version in the builds. The (two) reasons have been 
identified, the solution is TBD.
* PTO (20%):
  - July 24th - day off

== Plans ==
* BB-29 ENG: Linux linaro baseline maintenance (80%):
  - create separate Jira issues (stories) for the /etc/machine-id error, and the 
LOCALVERSION_AUTO issues.
  - update linux-linaro kernel trees to v4.2-rc4.
* PTO (20%):
  - July 31st - day off

== Issues ==
* none
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-dev

[ACTIVITY] Week 24

[Andrey Konovalov]

== Progress ==
* June 12th was a day off: local holiday (20%)
* CARD-788 EPIC: Linux linaro baseline maintenance (80%):
  - moved linux-linaro kernel tree to v4.1-rc7.
  - llct and ll CI jobs updated to use the rootfs with gator daemon version 
matching the kernel driver
  - old llct CI job is updated and its configuration is moved to 
ci/job/configs.git.
The corresponding build trigger created.
  - RE switching from board config fragments to corresponding defcconfigs:
Arndale boots OK when arndale.conf is replaced with exynos_defconfig. With 
multi_v7_defconfig it also
boots but w/o the onboard ethernet due to missing CONFIG_USB_HSIC_USB3503 
[1]

== Plans ==
* CARD-788 EPIC: Linux linaro baseline maintenance:
  - move linux-linaro kernel tree to v4.1-rc8, tag the tree for the 15.06 
release.
  - switch linux linaro builds in ci.l.o from board config fragments to 
relevant defconfigs
(small board specific config fragments could still be used if important 
options are missing
from the defconfigs)

== Issues ==
* none

[1] http://www.spinics.net/lists/linux-samsung-soc/msg42965.html
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-dev

[ACTIVITY] Week 23

[Andrey Konovalov]

== Progress ==
* CARD-788 EPIC: Linux linaro baseline maintenance (100%):
  - moved linux-linaro kernel tree to v4.1-rc6.
  - old llct CI job is updated and its configuration is moved to 
ci/job/configs.git.
The corresponding build trigger created.

== Plans ==
* CARD-788 EPIC: Linux linaro baseline maintenance:
  - move linux-linaro kernel tree to v4.1-rc7.
  - switch linux linaro builds in ci.l.o from board config fragments to 
relevant defconfigs
(small board specific config fragments could still be used if important 
options are missing
from the defconfigs)
* June 12th is a day off: local holiday

== Issues ==
* none
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-dev

[ACTIVITY] Week 14

[Andrey Konovalov]

== Progress ==
* DEVPLAT-321 clean up ILP32 build job (35%):
  - with Fathi's help the linux-linaro-tracking-ll-ilp32.yaml has been
fixed and added ci/job/configs.git. The jenkins job using this config is 
enabled.
* CARD-788 EPIC: Linux linaro baseline maintenance (50%):
  - moved llct and ll to v4.0-rc6. Later, on April 02, Amit P. merged the 
aosp/android-3.18 branch
into the Android topic for llct, and it caused some issues - Amit has 
addressed most of the numerous
merge conflicts, but few merge issues turned out to be unnoticed. For this 
reason ll is not
being updated to the most recent llct - waiting for the things in llct to 
settle down.
* DEVPLAT-345 ll-fold.sh script doesn't work correct with newer git versions 
(15%):
created. Drafted the test scripts to ensure that the ll-fold.sh changes to 
do under this card
don't introduce regressions (in particular - in re-creating the tree 
snapshots using the pinned
manifests).

== Plans ==
* CARD-788 EPIC: Linux linaro baseline maintenance:
  - resolve the android topic related issues in llct; update linux-linaro to 
v4.0-rc7
* DEVPLAT-321 clean up ILP32 build job:
  - close the card
* DEVPLAT-345 ll-fold.sh script doesn't work correct with newer git versions:
  - test llct and ll with the test scripts mentioned above. Proceed with fixes 
for
ll-fold.sh (review once more the set of patches received from ARM) if the 
testing is OK.

== Issues ==
* none
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-dev

[ACTIVITY] Week 15

[Andrey Konovalov]

== Progress ==
* DEVPLAT-321 clean up ILP32 build job (0%):
  - closed.
* CARD-788 EPIC: Linux linaro baseline maintenance (50%):
  - moved llct v4.0-rc7. A few issues in llct due to the android topic update 
to the aosp/android-3.18
resolved, but the others are arising. The last issue is Juno boot failure 
(kernel oops after starting
avahi-daemon) - still working on that. No updates for ll - still waiting 
for the things in llct to
settle down.
* DEVPLAT-345 ll-fold.sh script doesn't work correct with newer git versions 
(50%):
  - testing revealed that git rerere is more flexible in recognizing known 
conflicts than ll-fold.sh
implementation. The problem is that git rerere's known conflicts and 
their resolutions aren't saved
by ll-fold.sh (git saves them only locally), and they won't be available in 
a cloned repository. This
may result in failure to reconstruct the tree using pinned manifest if 
using e.g. a freshly cloned git
repo: ll-fold.sh itself may refuse to recognize a conflict to be known, and 
git rerere may not know this
conflict yet too. (The workaround could be to reconstruct earlier snapshots 
first - so that ll-fold.sh
applied the relevant solutions first time, and git rerere would care of 
applying them when reconstructing the
later snapshots).
The ARM's patches themselves look safe - they do address the types of the 
merge conflicts ever occurred during
the whole llct and ll lifesycles.

== Plans ==
* CARD-788 EPIC: Linux linaro baseline maintenance:
  - resolve the remaining issue(s?) in llct; update linux-linaro to v4.0.
* DEVPLAT-345 ll-fold.sh script doesn't work correct with newer git versions:
  - complete the card. Create a new one to address the issue with proper saving 
and sharing conflicts resolutions.

== Issues ==
* none
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-dev

[ACTIVITY] Week 13

[Andrey Konovalov]

== Progress ==
* mourning leave (60%)
* DEVPLAT-321 clean up ILP32 build job (15%):
  - updated the current ILP32 build job to use the standard QA's LTP test
case (it has got the 2 required fixes), and to pick up the latest
ILP32 and LP64 rootfs'es (vs the hardcoded ones). Submitted for review
the 1st draft of the job configuration in yaml - the job is being moved
to ci/job/configs.git
* CARD-788 EPIC: Linux linaro baseline maintenance (5%):
  - moved llct to v4.0-rc5

== Plans ==
* CARD-788 EPIC: Linux linaro baseline maintenance:
  - update linux-linaro to v4.0-rc6
* DEVPLAT-321 clean up ILP32 build job

== Issues ==
* none
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-dev

[ACTIVITY] Week 9

[Andrey Konovalov]

== Progress ==
* CARD-788 EPIC: Linux linaro baseline maintenance (5%):
  - linux-linaro schedule for 15.03 published on the wiki
  - tried moving llct to v4.0-rc1: 15 conflicts when merging the android topic.
They seem to be not hard to resolve though.
* CARD-1161 Add ILP32 support for ARM64 to Linaro engineering builds (75%):
  - added submission to LAVA to my existing ILP32 build job (Juno; both ILP32
and LP64 variants). Prepared the card for close-out. The remaining issues
will be resolved under card DEVPLAT-321 clean up ILP32 build job
* local holiday on Feb 23 (20%)

== Plans ==
* CARD-788 EPIC: Linux linaro baseline maintenance:
  - update linux-linaro to v4.0-rc2
* DEVPLAT-321 clean up ILP32 build job

== Issues ==
* none

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

[ACTIVITY]Week 5

[Andrey Konovalov]

== Progress ==
* CARD-788 EPIC: Linux linaro baseline maintenance (20%):
  - tagged the 15.01 kernel release in git;
  - linux-linaro CI: LAVA job templates for Juno corrected
  - linux-linaro schedule for 15.02 published
* CARD-1161 Add ILP32 support for ARM64 to Linaro engineering builds (80%):
  - booted a kernel built from 3.17-rc1 pinskia's tree with the rootfs image
by him in QEMU. The simple build and run Hello, world test passed OK.
  - found out that sshd crashes (ILP32 OE rootfs). Verified that booting
with armv8 rootfs, and chrooting into ILP32 rootfs makes it possible
to run ILP32 applications in LAVA interactively: made LTP syscalls
tests to complete by killing msgctl07 and msgrcv07; 300 test cases
failed (i.e. about 1/3 of the tests).
  - math LTP test fails on ILP32 userland (though some test cases pass), but
passes OK with armv8 rootfs. Seems to be due to libgcc_s.so.1 must be
installed for pthread_cancel to work.

== Plans ==
* CARD-788 EPIC: Linux linaro baseline maintenance:
  - update linux-linaro to v3.19-rc7
* CARD-1161 Add ILP32 support for ARM64 to Linaro engineering builds:
  - decide on how to get the current ILP32 kernel into CI the loop (atm the
build slaves don't have support for multilib gcc)
  - gather more information on LTP tests failures (using chroot to ilp32
userland in LAVA hacking session), and on sshd crash. File the bugs.
  - run LTP on the 3.17-rc1 kernel built from pinskia's tree with the rootfs
image by him in QEMU.

== Issues ==
* none


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

[ACTIVITY] Week 48

[Andrey Konovalov]

== Progress ==
* ILP32 support in linux-linaro: sanity tested with 64-bit userland (LTP syscall tests), 1 (out of 881) test failed on 
ILP32-enabled kernel only - regression (CARD-1161: 50%)

* llct updated to v3.18-rc6, the schedule for linux-linaro updates for 14.12 
published on the wiki (CARD-788: 30%)
* PTO (20 %)

== Plans ==
* PTO (20%)
* ILP32 support in linux-linaro
* usual linux-linaro updates for 14.12; fix the dependence on git version in 
ll-fold.sh script

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

[ACTIVITY] Week 37

[Andrey Konovalov]

== Progress ==
* vacations (20%)
* llct and linux-linaro trees have been updated to v3.17-rc4. The both are now using the Android topic by Amit P. 2014.09 
linux-linaro kernel release notes are done (CARD-788: 80%)


== Plans ==
* Linaro Connect

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

[ACTIVITY] Week 36

[Andrey Konovalov]

== Progress ==
* vacations (20%)
* linux-linaro tree has been updated to v3.17-rc3, and has got all the topics 
back (rebased the 2014.08's android
  and armv7 BE topics myself) (CARD-788: 65%)
* created bug 628 ifc6410: after moving from 3.16 to 3.17 kernel, ethernet is 
broken in linux-linaro-tracking CI builds to
  track one of the linux-linaro boot issues in LAVA; more to follow. (CARD-788: 
10%)
* updated the arndale.conf fragment to work around the boot failure. Kernel 
boots ok now, but the test results are worse then
  for 3.16 based kernels (LTP fails).  (CARD-788: 5%)

== Plans ==
* vacations (20%)
* move llct and linux-linaro trees to 3.17-rc4, switch to Android topic by Amit 
P. (CARD-788)
* create the bugs for the rest of linux-linaro boot/LAVA tests failures 
(CARD-788)
* linux-linaro CI: move to git based jenkins configuration (CARD-788)
* sanity check the ILP32 topic branch for ll using LTP and LP64 model,
  identify the missing components needed for testing in ILP32 (CARD-1161)

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

[ACTIVITY] Week 33

[Andrey Konovalov]

== Progress ==
* few more updates to linux-linaro-core-tracking and linux-linaro (CARD-788, 
20%)
* build failures for ifc6410 builds based on ll tree and multi_v7_defconfig: 
root cause found (CARD-788, 60%)
* created linux-linaro kernel CI job variant using git based job configuration. 
Added linux-linaro-tracking-ll.yaml
  to ci/job/configs.git, but jenkins is not using it yet (CARD-788, 20%)

== Plans ==
* 2014.08 ll kernel release (CARD-788)
* sanity check the ILP32 topic branch for ll using LTP and LP64 model,
  identify the missing components needed for testing in ILP32 (CARD-1161)


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

[ACTIVITY] Week 34

[Andrey Konovalov]

== Progress ==
* 2014.08 ll kernel release  (CARD-788, 50%)
* fixed the linux-linaro kernel CI job for ifc6410: CI builds boot OK now 
(CARD-788, 50%)

== Plans ==
* vacations
* move linux-linaro-core-tracking and linux-linaro trees to 3.17 (CARD-788)
* sanity check the ILP32 topic branch for ll using LTP and LP64 model,
  identify the missing components needed for testing in ILP32 (CARD-1161)


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

[ACTIVITY] week 28

[Andrey Konovalov]

== Progress ==
* moved linux-linaro-core-tracking and linux-linaro to v3.16-rc4, added big 
endian topic back to linux-linaro (CARD-788, 100%)

== Plans ==
* move linux-linaro-core-tracking and linux-linaro to v3.16-rc5 (CARD-788)
* add QCOM's ifc6410 board to linux-linaro CI loop (CARD-788)
* complete the ILP32 topic branch for ll, sanity check it with LTP in LP64,
  identify the missing components needed for testing in ILP32 (CARD-1161)
* follow up on:
  . DEVPLAT-210 upstream: fastboot in u-boot
  . bug 1189839 kernel crash on arndale while CPU hotplug
* update the wiki doc for DEVPLAT-204

== Issues ==
* none

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

[ACTIVITY] week 29

[Andrey Konovalov]

== Progress ==
* moved linux-linaro-core-tracking and linux-linaro to v3.16-rc5 (CARD-788, 40%)
* added Qualcomm's ifc6410 board to linux-linaro CI loop. Boot test only atm 
(CARD-788, 40%)
* ifc6410 doesn't boot in linux-linaro when building with gcc 4.8, but does boot when using the 4.6 from Ubuntu 12.04.4 LTS. 
Investigating that. Also the config fragment for ifc6410 might need updating (CARD-788, 20%)


== Plans ==
* move linux-linaro-core-tracking and linux-linaro to v3.16-rc6, 2014.07 ll 
kernel release (CARD-788)
* resolve ifc6410's boot issue (CARD-788)
* complete the ILP32 topic branch for ll, sanity check it with LTP in LP64,
  identify the missing components needed for testing in ILP32 (CARD-1161)
* finalize ifc6410's CI loop (clean up the jenkins job - move the scripts from jenkins to git etc; enable more tests in LAVA) 
(CARD-788)

* follow up on:
  . DEVPLAT-210 upstream: fastboot in u-boot
  . bug 1189839 kernel crash on arndale while CPU hotplug
* update the wiki doc for DEVPLAT-204

== Issues ==
* none

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

[ACTIVITY] week 27

[Andrey Konovalov]

== Progress ==
* moved linux-linaro-core-tracking and linux-linaro to v3.16-rc3, added llvm 
topic back to linux-linaro (CARD-788, 60%)
* added QCOM LT tree to linux-linaro, boot tested in LAVA (CARD-788, 40%)
* DEVPLAT-210 upstream: fastboot in u-boot: synced up with Dileep (0%)

== Plans ==
* move linux-linaro-core-tracking and linux-linaro to v3.16-rc4, make all the 
topics fixed for 3.16 (CARD-788)
* add QCOM's ifc6410 board to linux-linaro CI loop (CARD-788)
* complete the ILP32 topic branch for ll, sanity check it with LTP in LP64,
  identify the missing components needed for testing in ILP32 (CARD-1161)
* follow up on:
  . DEVPLAT-210 upstream: fastboot in u-boot
  . bug 1189839 kernel crash on arndale while CPU hotplug
* update the wiki doc for DEVPLAT-204

== Issues ==
* none

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

[ACTIVITY] week 26

[Andrey Konovalov]

== Progress ==
* linux-linaro-core-tracking tree updated to v3.16-rc2, linaro-android topic is 
back,
  the linux-linaro schedule for 2014.07 cycle created, the root cause for llct 
CI build
  failures since moving to 3.16 found (CARD-788, 75%)
* adding QCOM LT tree to linux-linaro is in progress: rebased the QCOM LT tree 
onto current llct,
  built the kernel, created the images to flash using fastboot using the QCOM 
LT's 3.14 jenkins
  jobs as the template, but the result failed to boot in LAVA (CARD-788, 25%)
* DEVPLAT-210 upstream: fastboot in u-boot: synced up with Dileep (0%)


== Plans ==
* fix the llct/ll CI builds (CARD-788)
* move linux-linaro-core-tracking and linux-linaro to v3.16-rc3 (CARD-788)
* add QCOM LT tree to linux-linaro (CARD-788)
* complete the ILP32 topic branch for ll, sanity check it with LTP in LP64,
  identify the missing components needed for testing in ILP32 (CARD-1161)
* follow up on:
  . DEVPLAT-210 upstream: fastboot in u-boot
  . bug 1189839 kernel crash on arndale while CPU hotplug
* update the wiki doc for DEVPLAT-204

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

[ACTIVITY] week 25

[Andrey Konovalov]

== Progress ==
* after a few more updates, linux-linaro kernel 14.06 release has been tagged, 
release notes are done (CARD-788, 45%)
* linux-linaro-core-tracking tree updated to v3.16-rc1 - w/o linaro-android, and samsung-boards-core-support topics yet 
(CARD-788, 40%)
* create a topic branch for ll with the recently posted v2 patch set for the Add ILP32 support for ARM64 to Linaro engineering 
builds card - in progress (CARD-1161, 15%)


== Plans ==
* create the linux-linaro schedule for 2014.07 cycle (CARD-788)
* move linux-linaro-core-tracking and linux-linaro to v3.16-rc2 (CARD-788)
* add QCOM LT tree to linux-linaro (CARD-788)
* complete the ILP32 topic branch for ll, sanity check it with LTP in LP64, identify the missing components needed for testing 
in ILP32 (CARD-1161)

* follow up on:
  . DEVPLAT-210 upstream: fastboot in u-boot
  . bug 1189839 kernel crash on arndale while CPU hotplug
* update the wiki doc for DEVPLAT-204

== Issues ==
* none

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

[ACTIVITY] week 24

[Andrey Konovalov]

== Progress ==
* bug 1328776 ll-20140607.0 - ftbfs on beaglebone (CARD-788, 15%)
* did the planned updates to llct, updated the schedule for ll updates in 
2014.06 (CARD-788, 5%)
* time off (80%)

== Plans ==
* linux-linaro kernel release week (CARD-788)
* follow up on:
  . DEVPLAT-210 upstream: fastboot in u-boot
  . bug 1189839 kernel crash on arndale while CPU hotplug
* create a topic branch for ll with the recently posted patch set for the Add ILP32 support for ARM64 to Linaro engineering 
builds card (CARD-1161)

* update the wiki doc for DEVPLAT-204

== Issues ==
* none

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

[ACTIVITY] week 23

[Andrey Konovalov]

== Progress ==
* upload the schedule for ll updates in 2014.06, did the updates to llct and ll 
trees (CARD-788, 50%)
* bug 1282076 - tried to narrow down the issue, but failed to reproduce it even using the 
older, known to fail Image.
  Maybe the kernel update on the host machine is the cause (bug 1282076, 10%)
* time off (40%)

== Plans ==
* time off 60%
* usual updates to ll / llct (CARD-788)
* try the recently posted patch set for the Add ILP32 support for ARM64 to Linaro 
engineering builds card (CARD-1161)
* update the wiki doc for DEVPLAT-204

== Issues ==
* None

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

[ACTIVITY] week 21

[Andrey Konovalov]

== Progress ==
* Final linux-linaro updates (BE topic) and sanity testing for 2014.05 
(CARD-788, 45%)
* systemtap test suite failed to build - root cause identified (bug 1319069, 
50%)
* moved llct to the next -rc (for 2014.06) (CARD-788, 5%)

== Plans ==
* follow up on 14.05 linux-linaro kernel release
* update the wiki doc for DEVPLAT-204

== Issues ==
* None

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

Re: Linaro 13.09 Very slow boot on Pandaboard

[Andrey Konovalov]

Hi Ola,

On 10/21/2013 05:26 PM, Ola Dahl wrote:

Hi,

I have downloaded the image for Pandaboard, from

http://releases.linaro.org/13.09/ubuntu/panda/panda-raring_developer_20130922-471.img.gz

I unpack it and copy it to a SD card using Windows Image writer.

When the Pandaboard boots, the boot hangs temporarily (circa one minute) after 
having printed

[6.891754] init: ureadahead main process (1106) terminated with status 5
[7.596893] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro

After the minute or so has passed, the printout resumes, and one sees

  * Setting sensors limits[ OK ]

  * Loading cpufreq kernel modules...

and then the login proceeds with success.

When I look in the dmesg printout I see

[6.143127] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. 
Opts: (null)
[6.891754] init: ureadahead main process (1106) terminated with status 5
[7.596893] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro
[8.069091] udevd[1193]: starting version 175
ing ok
[   10.653472] usb 1-1.1: link qh8-0001/eca3e3c0 start 2 [1/0 us]
[   10.653472] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[   10.655517] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   10.904968] init: udev-fallback-graphics main process (1398) terminated with 
status 1
[   11.121673] init: plymouth main process (1107) killed by ABRT signal
[   11.128204] init: plymouth-splash main process (1436) terminated with status 
2
[  131.484619] init: alsa-restore main process (1490) terminated with status 99
[  132.043243] init: plymouth-stop pre-start process (1601) terminated with 
status 1
[  132.072296] init: tty1 main process (1602) killed by TERM signal

Could it be that some  service is started that takes a lot of time?

Have you seen this before?


You don't have ethernet connected to the board, right?

I've given this image a try on a Panda ES board.

When the ethernet is available, I see no delays, and dmesg gives:

[   12.274230] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   12.340332] init: udev-fallback-graphics main process (1387) terminated with
status 1
[   12.931732] init: plymouth main process (1113) killed by ABRT signal
[   12.935455] init: plymouth-splash main process (1440) terminated with status 
2
[   13.937377] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   13.948211] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 
0x45E1
[   17.345123] init: failsafe main process (1396) killed by TERM signal
[   17.849884] init: alsa-restore main process (1535) terminated with status 99
[   18.483337] init: plymouth-stop pre-start process (1646) terminated with 
status 1
[   18.511535] init: tty1 main process (1647) killed by TERM signal

W/o ethernet (cable removed) there a delay of couple minutes after these lines 
are printed to the console:

Begin: Running /scripts/init-bottom ... done.
[7.031066] init: ureadahead main process (1105) terminated with status 5
[7.738800] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro

And dmesg is:

[   11.009429] init: udev-fallback-graphics main process (1397) terminated with
status 1
[   11.065185] usb 1-1.1: link qh8-0001/eca37480 start 2 [1/0 us]
[   11.065185] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[   11.067382] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   11.356414] hw-breakpoint: Failed to enable monitor mode on CPU 0.
[   11.726379] hw-breakpoint: CPU 0 failed to disable vector catch
[   12.011138] init: plymouth main process (1106) killed by ABRT signal
[   12.017639] init: plymouth-splash main process (1437) terminated with status 
2
[  132.446441] init: plymouth-stop pre-start process (1602) terminated with 
status 1
[  132.474243] init: tty1 main process (1603) killed by TERM signal

I.e. this is just how the prebuilt image is configured.


Thanks,
Andrey


Any hints are appreciated!

Best regards,

Ola



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




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

Re: LSK getting started

[Andrey Konovalov]

On 08/05/2013 11:34 PM, Mark Brown wrote:

On Mon, Aug 05, 2013 at 11:23:19PM +0400, Andrey Konovalov wrote:


# Misc fixes which don't belong to any particular topic:
ynk/llct-v3.10-misc-fixes
Add cross-build support to tools/lib/lk library


The 2nd chunk is still not in the mainline. I'll check with Wookey.


perf tools: make perf to build in 3.9 kernel tree again
ARM: crypto: sha1-armv4-large.S: fix SP handling


Right, v3.11 has the same changes in. Dropped these 2 commits from 
ynk/llct-v3.11-misc-fixes



These appear to be upstream anyway in one form or another.


KBuild: Allow scripts/* to be cross compiled


What's the upstreaming status on this?


Good question. There are no plans on upstreaming it atm


Thanks,
Andrey


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

Re: LSK getting started

[Andrey Konovalov]

On 08/08/2013 05:30 PM, Mark Brown wrote:

On Thu, Aug 08, 2013 at 05:20:46PM +0400, Andrey Konovalov wrote:

On 08/05/2013 11:34 PM, Mark Brown wrote:



These appear to be upstream anyway in one form or another.



KBuild: Allow scripts/* to be cross compiled



What's the upstreaming status on this?



Good question. There are no plans on upstreaming it atm


Any great reason why not?  It doesn't seem particularly controversial or
anything and definitely seems useful.


Just the patch author is not with Linaro any more. So I am not very 
clear who would submit the patch.



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

Re: LSK getting started

[Andrey Konovalov]

On 08/08/2013 06:04 PM, Mark Brown wrote:

On Thu, Aug 08, 2013 at 05:50:57PM +0400, Andrey Konovalov wrote:

On 08/08/2013 05:30 PM, Mark Brown wrote:



Any great reason why not?  It doesn't seem particularly controversial or
anything and definitely seems useful.



Just the patch author is not with Linaro any more. So I am not very
clear who would submit the patch.


Hrm, OK.  I'll try to take a look myself


Thanks!


- from a brief Google it looks
like nobody tried at all which is a shame.  We should really be pushing
people to upstream things so stuff like this doesn't happen.


Yes, the things would be much easier if the patch were sent upstream 
soon after it had been created and we started using it.



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

Re: LSK getting started

[Andrey Konovalov]

On 08/05/2013 03:37 PM, Andy Green wrote:

On 5 August 2013 18:59, Mark Brown broo...@kernel.org wrote:

On Mon, Aug 05, 2013 at 06:42:33PM +0800, Andy Green wrote:

On 5 August 2013 18:16, Mark Brown broo...@linaro.org wrote:



There may be other stuff lurking in linux-linaro that I'm not aware of,
everything is supposed to be individually selected for backport.



Literally linux-linaro I'm not sure is useful for anything, the tree
LTs are basing on is linux-linaro-core-tracking.



It's composed by rebase and then merges, so it's easy to see what's in
there from a quick git log.


That doesn't help with understanding why any of it is there or what it's
for.


Andrey is here hopefully he can do a Tixy-style breakdown.


Current linux-linaro-core-tracking topics:
==
(see the manifest for remote URLs)

configs/config-core-tracking
generic (board independent) config fragments

configs/config-boards-tracking
config fragments for the boards

android_jstultz/linaro-android-3.11-experimental-merge
AOSP tree rebased to a recent -rc, may also contain Linaro
patches being upstreamed

lt_arm/tracking-armlt-gator
gator driver (originally from DS-5) provided by ARM LT

lt_arm/tracking-armlt-multi_pmu_v2
This is the big.LITTLE PMU support that was in the MP branch.
(the MP branch has been dropped from llct)

lt_arm/tracking-armlt-iks
is a rebase of Nicolas's iks branch:
git://git.linaro.org/people/nico/linux.git iks
with the big.LITTLE MP config fragment added.

lt_arm/tracking-armlt-iks-cpufreq
is the cpufreq bits for IKS.

ynk/fixup_iks_linaro-android-3.11
is a fixup which doesn't show up as a conflict when
lt_arm/tracking-armlt-iks and Android are merged because both
topics increase NR_IPI to 7.

b_L_mp/ll-interactive-gov-updates
The patches to the Android interactive governor.
These changes are important for ARM big LITTLE platforms which
want multiple instances of a governor to be available for a
multi package system. Have been sent for inclusion into AOSP.

ynk/binder-3.8-rebase
Just these 2 patches:
Android: Add support for 32-bit Binder calls in a 64-bit kernel
binder: fix printk() format specifier to match userptr32_t type

# Basic boards enablement:
lt_samsung/llct/arndale-core-support
basic Arndale support
lt_broadcom/llct/capri-support
basic support for Capri board

# Packaging:
ynk/linaro-builddeb-tweaks
a few patches to support kernel cross build with deb-pkg and
to put the dtb files into the kernel image deb package
according to linaro-hwpack-* tools expectations.

# Misc fixes which don't belong to any particular topic:
ynk/llct-v3.10-misc-fixes
Add cross-build support to tools/lib/lk library
perf tools: make perf to build in 3.9 kernel tree again
ARM: crypto: sha1-armv4-large.S: fix SP handling
KBuild: Allow scripts/* to be cross compiled


Current linux-linaro topics:


lt_arm/integration-linaro-vexpress
ARM LT's integration branch to support Versatile Express

ynk/samsung-lt-tracking
Samsung LT's integration branch with full Arndale support
(the copy of Samsung LT's tag samsung-lt-v3.11-rc3)

configs/config-core-tracking
and
configs/config-boards-tracking
- the same llct topics


Thanks,
Andrey


Sounds reasonable attached is our current patch for your
consideration.  There's a permanent #warning about an unwind tables
TODO this also knocks out the others are actual problems.


Please split this up into proper patches, and of course you should be
submitting any fixes upstream if they're still present - if you're doing
this sort of warning cleanup work it's going to be useful upstream too.
I had a quick glance through and:


These are only applied on lsk and llct, I don't actually know where
the code patched came from but I think they're all mainline.  I'll
check it out later.


  - Things like just assigning a value to variables at declaration are
worrying since that just shuts up the flow analysis warnings even if
they're actually pointing out a genuine missed code path.


In this case it's okay, that var is written via a pointer arg to
another call, but the call either returns an err or fills it in.  The
value is only used on non-error path.  It's just keeping the compiler
happy.


  - The regmap change isn't something that I've seen upstream...


If you mean where did the original come from

commit 5a08d15602987bbdff3407d7645f95b7a70f1a6f
Author: Stephen Warren swar...@nvidia.com
Date:   Wed Mar 20 17:02:02 2013 -0600

 regmap: don't corrupt work buffer in _regmap_raw_write()


  - For printf() warnings consider changing the printf() format specifier
to be accurate rather than casting.


Yes fair enough.

-Andy

Re: ux500 not booting

[Andrey Konovalov]

Greetings,

I see a similar problem with my snowball, and I was under impression is 
that something is wrong with microSD interface (eMMC works ok) on this 
particular board (SDK-00840 V11, 905-00024-B11, 100-00103-B13).
Moreover, to my knowledge QA has no problems with SD when testing the 
recent release images.


But after reading this email thread, I tried booting my snowball board 
using the 12.05 release image [1], and the 13.05 release image [2] - 
just in case. The [1] booted ok, on the snowball I've downloaded the [1] 
from releases.l.o to the rootfs on the SD and checked it with 'bzip2 -t' 
- no errors. With [2] written to the same microSD card I got numerous 
errors, most with error -84 (different from what Daniel reported):


[4.654144] mmci-pl18x sdi0: error during DMA transfer!
[4.659515] mmcblk0: response CRC error sending r/w cmd command, card 
status 0x800b00

done.
[5.305755] mmcblk0: error -84 sending stop command, original cmd 
response 0x900, card status 0x900
[5.316741] mmcblk0: error -84 sending stop command, original cmd 
response 0x900, card status 0x900

[5.328430] mmci-pl18x sdi0: error during DMA transfer!
[5.334106] mmcblk0: error -84 sending status command, retrying
[5.340087] mmcblk0: error -84 sending status command, retrying
[5.346099] mmcblk0: error -84 transferring data, sector 107296, nr 
216, cmd response 0x900, card status 0xb00


Just FYI.

Thanks,
Andrey

[1] 
https://releases.linaro.org/12.05/ubuntu/leb-snowball/lt-snowball-x11-base-precise_ubuntu-desktop_20120525-89.img.bz2
[2] 
https://releases.linaro.org/13.05/ubuntu/snowball/snowball-raring_developer_20130526-344.img.gz


On 06/07/2013 12:30 PM, Daniel Lezcano wrote:

On 06/07/2013 09:34 AM, Linus Walleij wrote:

On Thu, Jun 6, 2013 at 6:15 PM, Daniel Lezcano
daniel.lezc...@linaro.org wrote:


I tried to boot my ux500


Is this an HREF (black plastic box) or the Snowball board?


It is the snowball board.


  with the 3.10-rc4 kernel but it hangs at boot
time with the following messages:


Hm, looks like some very real corruption, Ulf what do you say?

Linus







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

Re: [ANNOUNCE] linux-linaro kernel schedule / llct age

[Andrey Konovalov]

On 06/04/2013 03:22 AM, Andy Green wrote:

On 22/05/13 02:48, the mail apparently from Andrey Konovalov included:


The next steps are:
May 22: ll rebuild based on llct-20130521.0
May 23: ll rebuild based on llct-20130521.0, linux-linaro release
candidate, code freeze


The last llct update for this cycle is scheduled on May 21,
The last linux-linaro update for this cycle is scheduled on May 23.
May 23 is the linux-linaro code freeze for 13.05 (only bug fixes allowed
after this date).


This happened, which is good, but llct has not updated for 3.10-rc3 or
3.10-rc4 yet, which is not good; llct is two weeks old.  Something
similar happened last month.


Agreed. This is not good. And I've pushed the llct updates to fix that.

On the other side, I am considering dropping llct as an intermediate 
step when creating the ll tree. The linux-linaro-stable work done in 
13.05 shown that topic dependencies may be more complex, and could not 
be met by just creating one intermediate tree. The more generic approach 
seems to add explicit topic dependencies into the manifest, so that the 
tool to merge the topic together would use this information.


Another point to mention, is the proposal to merge the board enablement 
topics first, and the generic features next (the LSK case). This would 
assume the generic topics to enable their features for all the linaro 
supported boards, or adding separate topic to enable the features for 
particular boards. This also breaks the current 2-level llct/ll model.


Also I am going to more actively use rebasing the topic to their most 
recent base w/o topic owners intervention (e.g. like I did for one month 
for the Samsung LT's integration topic few cycles ago).
For the topic owners this would mean something like that if their topic 
C is based on topics A and B, the topic C must be based on the A and B 
tip when submitted to for inclusion into linux-linaro(-whatever) tree, 
and after that it will be automatically rebased onto the most recent 
version of topic A and B unless there are conflicts requiring the topic 
owner's help. This is a very rough idea at the moment - I am not quite 
sure if it could even work.



I realize this isn't the case for everyone but actually the literal
schedule for 13.05 holds zero interest for me.


In long term this should evolve into change log / release notes.
(I do use it for writing the release notes)


Timely updates on llct for each mainline -rc are very interesting
though, in fact we depend on them.


OK. Could you use ll instead of llct, if ll were updated frequently 
enough (soon after every -rc at least)?



Is it possible things have gotten a little unbalanced with all the
excitement of code freezes, releases, schedules that make the
choo-choo noises for the monthly release train set, we're not giving the
llct tracking activity enough love?


Seems so. I just don't think that releases and schedules is a lot of 
excitement. In the last week of a cycle it is rather a head ache :)



Thanks,
Andrey


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

Re: [GIT PULL]: ll-interactive-gov-updates : Per policy governor instance

[Andrey Konovalov]

Hi Viresh,

On 05/21/2013 10:20 AM, Viresh Kumar wrote:

Hi Andrey,

I have got some important updates for Android's Interactive Governor.
These are already sent to Todd Poyner for inclusion into AOSP and
we are awaiting a response.

These changes are important for ARM big LITTLE platforms which
want multiple instances of a governor to be available for a multi
package system.

Until then, we want these patches to land into linux-linaro release via
my tree.

Below is what I did to generate this branch:

- Checked out: 
https://git.linaro.org/gitweb?p=people/jstultz/android.git;a=shortlog;h=refs/heads/linaro-android-3.10-experimental-merge
- Merged v3.10-rc2 into it (As I had some cpufreq core patches included here)
- Applied my patches (8) over it

I am not able to generate a formal PULL request using 'git request-pull'
as 3.10-rc2 is not yet there in your tree.

Please pull git://git.linaro.org/arm/big.LITTLE/mp.git
ll-interactive-gov-updates
into linux-linaro.


Merged into v3.10-rc2 based llct-20130521.0.

Thanks,
Andrey


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

Re: [ANNOUNCE] linux-linaro kernel schedule for 13.05 published

[Andrey Konovalov]

Greetings,

On 05/20/2013 01:28 AM, Andrey Konovalov wrote:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule



The 13.05 linux-linaro release will be v3.10-rc2 based


May 20: ll rebuild based on llct-20130518.0
 * Done: the tag is ll-20130520.1
 * Changes:
   . Snowball build is fixed (the fix propagated from llct)
   . Snowball: ethernet works ok with the kernel config built from the 
config fragments (linaro-base + ubuntu-minimal + u8500)


May 21: v3.10-rc2 based linux-linaro-core-tracking (llct) rebuild
 * Done: the tag is llct-20130521.0
 * Changes:
   . interactive-gov-updates topic from Viresh Kumar added
   . arndale-core-support topic from Samsung LT added

No more llct updates are planned for 13.05 unless critical issues would 
be found in llct-20130521.0


The next steps are:
May 22: ll rebuild based on llct-20130521.0
May 23: ll rebuild based on llct-20130521.0, linux-linaro release 
candidate, code freeze



The last llct update for this cycle is scheduled on May 21,
The last linux-linaro update for this cycle is scheduled on May 23.
May 23 is the linux-linaro code freeze for 13.05 (only bug fixes allowed
after this date).


Thanks,
Andrey


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

Re: [ANNOUNCE] linux-linaro kernel schedule for 13.05 published

[Andrey Konovalov]

On 05/17/2013 10:13 AM, Fathi Boudra wrote:

On 17 May 2013 09:06, Fathi Boudra fathi.bou...@linaro.org wrote:

On 16 May 2013 22:11, Andrey Konovalov andrey.konova...@linaro.org wrote:

On 05/15/2013 10:59 PM, Andrey Konovalov wrote:


On 05/15/2013 12:04 AM, Andrey Konovalov wrote:


https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule


The 13.05 linux-linaro release will be v3.10-rc2 based,



May 16: ll rebuild based on llct-20130515.1
* Done: the tag is ll-20130516.0
* Changes:
   . based on v3.10-rc1
   . IKS included into integration-linaro-vexpress topic
* Known issues:
   . the Samsung topic hasn't moved to v3.10 yet
   . panda isn't supported as is (omap4.conf is to be fixed; USB needs
verification)


U8500 (Snowball) fails to build:
fatal error: mach/irqs.h: No such file or directory
  #include mach/irqs.h
^

Issue known upstream and raised already a couple of times.


Linus provided a patch:
http://marc.info/?l=linux-kernelm=136567139910888w=2


Thanks!
The fix is added to linux-linaro-core-tracking, and will made it into 
linux-linaro this Monday.



The next step is:
May 17: v3.10-rc1 based linux-linaro-core-tracking (llct) rebuild
* Expected: config fragments updates



The last llct update for this cycle is scheduled on May 21,
The last linux-linaro update for this cycle is scheduled on May 23.
May 23 is the linux-linaro code freeze for 13.05 (only bug fixes allowed
after this date).



Thanks,
Andrey



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

Re: [ANNOUNCE] linux-linaro kernel schedule for 13.05 published

[Andrey Konovalov]

On 05/15/2013 10:59 PM, Andrey Konovalov wrote:

On 05/15/2013 12:04 AM, Andrey Konovalov wrote:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

The 13.05 linux-linaro release will be v3.10-rc2 based,


May 16: ll rebuild based on llct-20130515.1
* Done: the tag is ll-20130516.0
* Changes:
  . based on v3.10-rc1
  . IKS included into integration-linaro-vexpress topic
* Known issues:
  . the Samsung topic hasn't moved to v3.10 yet
  . panda isn't supported as is (omap4.conf is to be fixed; USB needs 
verification)


The next step is:
May 17: v3.10-rc1 based linux-linaro-core-tracking (llct) rebuild
* Expected: config fragments updates


The last llct update for this cycle is scheduled on May 21,
The last linux-linaro update for this cycle is scheduled on May 23.
May 23 is the linux-linaro code freeze for 13.05 (only bug fixes allowed
after this date).


Thanks,
Andrey


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

Re: [PATCH] configs: linaro-base: Enable CRYPTO_[AES|SHA1]_ARM

[Andrey Konovalov]

On 05/15/2013 05:02 PM, Jon Medhurst (Tixy) wrote:

On Wed, 2013-05-15 at 14:41 +0200, Ard Biesheuvel wrote:

On 15 May 2013 14:38, Jon Medhurst (Tixy) t...@linaro.org wrote:

I see that the ARM version is following the pattern of SPARC64 and X86
SSSE3 in how it is configured, so for fear of opening a can of worms,
perhaps it's simpler if we just go with the linaro-base.conf patch which
started this thread? :-)



Yes please!


I've just spotted that you have posted a fix to the ARM SHA1 code [1] so
perhaps we shouldn't enable it until that fix works its way into the
Linaro tree? (If it's important for Linaro work the perhaps you could
ask Andrey to add the patch to the Linaro tree early.)


- added the ARM: crypto: sha1-armv4-large.S: fix SP handling patch to 
linux-linaro-core-tracking tree starting from tag llct-20130515.1


Thanks,
Andrey


[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2013-May/168374.html




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

Re: [ANNOUNCE] linux-linaro kernel schedule for 13.05 published

[Andrey Konovalov]

On 05/15/2013 12:04 AM, Andrey Konovalov wrote:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

The 13.05 linux-linaro release will be v3.10-rc2 based,


May 15: v3.10-rc1 based linux-linaro-core-tracking (llct) rebuild
* Done: the tag is llct-20130515.1
* Changes:
 . the 3.8-based binder topic re-added
 . kernel/printk.c: build error in CONFIG_DEBUG_LL=y case fixed
 . ARM: crypto: sha1-armv4-large.S: fix SP handling patch needed to 
enable CONFIG_CRYPTO_SHA1_ARM


The next step is:
May 16: ll rebuild based on llct-20130515.1


The last llct update for this cycle is scheduled on May 21,
The last linux-linaro update for this cycle is scheduled on May 23.
May 23 is the linux-linaro code freeze for 13.05 (only bug fixes allowed
after this date).


Thanks,
Andrey


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

Re: [ANNOUNCE] linux-linaro kernel schedule for 13.05 published

[Andrey Konovalov]

On 05/08/2013 10:53 PM, Andrey Konovalov wrote:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

The 13.05 linux-linaro release will be v3.10-rc2 based,


May 13: v3.10-rc1 based linux-linaro-core-tracking (llct) rebuild
Done: the tag is llct-20130514.0
Changes:
new Android and numa/huge pages topics
ashmem/binder topics are not included, and will be added early 
next week (after the topics are updated for 3.10)

snowball topic temporary removed
Known issues:
panda doesn't boot with kernel config made from the config 
fragments (stops after Starting kernel ...). omap2plus_defconfig works 
much better, but still has problems (the console output *looks* like 
serial interrupts are partially lost)


The next step is:
May 15: ll rebuild based on llct-20130514.0


The last llct update for this cycle is scheduled on May 21,
The last linux-linaro update for this cycle is scheduled on May 23.
May 23 is the linux-linaro code freeze for 13.05 (only bug fixes allowed
after this date).


Thanks,
Andrey



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

Re: [ANNOUNCE] linux-linaro kernel schedule for 13.05 published

[Andrey Konovalov]

On 05/06/2013 11:06 PM, Andrey Konovalov wrote:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

The 13.05 linux-linaro release will be v3.10-rc2 based,


May 08: ll rebuild based on llct-20130506.0
 * Skipped: make dtbs broken in llct-20130506.0

May 08: v3.9 based linux-linaro-core-tracking (llct) rebuild (if there 
are changes to the topics)

 * Done: the tag is llct-20130508.0
 * Changes:
   - linaro-android-3.9-experimental-fixes topic added to revert commit 
5e94686 ARM: convert build of appended dtb zImage to list of dtbs

   - linux-3.9.y topic added to pull the v3.9.1 stable tree updates

The next step is:
May 10: ll rebuild based on llct-20130508.0


The last llct update for this cycle is scheduled on May 21,
The last linux-linaro update for this cycle is scheduled on May 23.
May 23 is the linux-linaro code freeze for 13.05 (only bug fixes allowed
after this date).


Thanks,
Andrey


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

Re: [ANNOUNCE] linux-linaro kernel schedule for 13.05 published

[Andrey Konovalov]

On 05/03/2013 11:20 PM, Andrey Konovalov wrote:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

The 13.05 linux-linaro release will be v3.10-rc2 based,


linux-linaro and linux-linaro-core-tracking trees have been updated.
The tags are ll-20130506.0 and llct-20130506.0.

The next step is:
May 08: ll rebuild based on llct-20130506.0 (v3.9 based)


The last llct update for this cycle is scheduled on May 21,
The last linux-linaro update for this cycle is scheduled on May 23.
May 23 is the linux-linaro code freeze for 13.05 (only bug fixes allowed
after this date).


Thanks,
Andrey


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

Re: [ANNOUNCE] linux-linaro kernel schedule for 13.05 published

[Andrey Konovalov]

On 05/03/2013 12:47 PM, Jon Medhurst (Tixy) wrote:

On Thu, 2013-05-02 at 22:40 +0400, Andrey Konovalov wrote:

Greetings,

This wiki page:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

- is now tracking the linux-linaro kernel rebuilds for 13.05.

v3.9 release based linux-linaro-core-tracking (llct) rebuild has been
published, the tag is llct-20130502.0 . The 13.05 linux-linaro release
will be v3.10-rc3 based,


I think you may have miscalculated. Isn't the merge window 2 weeks long?
In which case, as 3.9 was released this past Monday, we shouldn't expect
-rc1 until May 13th and -rc3 will be in June.


Tixy, yes, you are right. I've corrected the LinuxLinaroKernelSchedule.

The 13.05 linux-linaro release will be v3.10-rc2 based,
The next step is:
May 06: ll rebuild based on llct-20130502.0.

Please let me know if sticking to v3.9 until v3.10-rc1 is out (May 13th) 
is an issue for the topics.


The last llct update for this cycle is scheduled on May 21,
The last linux-linaro update for this cycle is scheduled on May 23.
May 23 is the linux-linaro code freeze for 13.05 (only bug fixes allowed 
after this date).


Thanks,
Andrey


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

[ANNOUNCE] linux-linaro kernel schedule for 13.05 published

[Andrey Konovalov]

Greetings,

This wiki page:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

- is now tracking the linux-linaro kernel rebuilds for 13.05.

v3.9 release based linux-linaro-core-tracking (llct) rebuild has been 
published, the tag is llct-20130502.0 . The 13.05 linux-linaro release 
will be v3.10-rc3 based, but let's do one more v3.9 based kernel not to 
miss the v3.9 release.


The next step is:
May 06: ll rebuild based on llct-20130502.0.

The last llct update for this cycle is scheduled on May 21,
The last linux-linaro update for this cycle is scheduled on May 23.
May 23 is the linux-linaro code freeze for 13.05 (only bug fixes allowed 
after this date).


Thanks,
Andrey

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

[ANNOUNCE] [linux-linaro kernel] Start maintaining the list of the current topic owners in git.l.o

[Andrey Konovalov]

Greetings,

I've been asked to have the list of the linux-linaro and 
linux-linaro-core-tracking topic owners in git.l.o. I longer term this 
information would be a part of the manifest. For now it would be a text 
file in [1], the linux-linaro and linux-linaro-core-tracking branches.


Dear topic owners,
please check if this information is correct (attached). The current list 
reflects the 13.04 release state, e.g. the two Snowball related topics 
would be reworked for the next cycle (by myself, using Lee's assistance 
when needed). So feel free to make corrections, and don't worry too much 
if the currently listed topics would change in 13.05 (but let me know if 
this is the case). The topic names correspond to the ones in the 
manifests (see the [1]).



Thanks,
Andrey

[1] git://git.linaro.org/kernel/linux-linaro-manifest.git
From abc291a2c91c33d2dc65b80ab30d67162c1b88ab Mon Sep 17 00:00:00 2001
From: Andrey Konovalov andrey.konova...@linaro.org
Date: Thu, 25 Apr 2013 22:32:23 +0400
Subject: [PATCH] ll: create the list of topic owners

This is a short-term solution. In longer term this information would be
moved into the manifest.

Signed-off-by: Andrey Konovalov andrey.konova...@linaro.org
---
 topic-owners |8 
 1 file changed, 8 insertions(+)
 create mode 100644 topic-owners

diff --git a/topic-owners b/topic-owners
new file mode 100644
index 000..3a0baa9
--- /dev/null
+++ b/topic-owners
@@ -0,0 +1,8 @@
+topicowner
+##
+samslt-all			Tushar Behera tushar.beh...@linaro.org
+integration-linaro-vexpress	Jon Medhurst (Tixy) t...@linaro.org
+perf-android			Dmitry Pervushin dmitry.pervus...@linaro.org
+panda-fix-usb			Andrey Konovalov andrey.konova...@linaro.org
+ll-misc-fixes-13.04		Andrey Konovalov andrey.konova...@linaro.org
+snowball-fixes-13.03		Andrey Konovalov andrey.konova...@linaro.org
-- 
1.7.9.5

From ec8dbca60a8d855986429c381d388df7c7c6af09 Mon Sep 17 00:00:00 2001
From: Andrey Konovalov andrey.konova...@linaro.org
Date: Thu, 25 Apr 2013 22:32:23 +0400
Subject: [PATCH] llct: create the list of topic owners

This is a short-term solution. In longer term this information would be
moved into the manifest.

Signed-off-by: Andrey Konovalov andrey.konova...@linaro.org
---
 topic-owners |   18 ++
 1 file changed, 18 insertions(+)
 create mode 100644 topic-owners

diff --git a/topic-owners b/topic-owners
new file mode 100644
index 000..2ffcbe1
--- /dev/null
+++ b/topic-owners
@@ -0,0 +1,18 @@
+topicowner
+##
+core-configs			Andrey Konovalov andrey.konova...@linaro.org
+Jon Medhurst (Tixy) t...@linaro.org
+basic-board-configs		Andrey Konovalov andrey.konova...@linaro.org
+Jon Medhurst (Tixy) t...@linaro.org
+linaro-android-3.9		John Stultz john.stu...@linaro.org
+gatorJon Medhurst (Tixy) t...@linaro.org
+big-LITTLE-MP-master-v16	Viresh Kumar viresh.ku...@linaro.org
+kvm-arm-configs			Riku Voipio riku.voi...@linaro.org
+hugetlbSteve Capper steve.cap...@linaro.org
+numaSteve Capper steve.cap...@linaro.org
+irqchip-reorg			Jon Medhurst (Tixy) t...@linaro.org
+armdroid-ashmem			Serban Constantinescu serban.constantine...@arm.com
+armdroid-binder			Serban Constantinescu serban.constantine...@arm.com
+ste-tb-ethernet			Lee Jones lee.jo...@linaro.org
+linaro-builddeb-tweaks		Andrey Konovalov andrey.konova...@linaro.org
+llct-v3.9-misc-fixes		Andrey Konovalov andrey.konova...@linaro.org
-- 
1.7.9.5

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

[ANNOUNCE] linux-linaro kernel schedule for 13.04 updated

[Andrey Konovalov]

Greetings,

On 04/15/2013 11:42 AM, Andrey Konovalov wrote:

11.04.2013 23:20, Andrey Konovalov пишет:

Greetings,

This is a reminder that this wiki page:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

- is now tracking the linux-linaro kernel rebuilds for 13.04.


v3.9-rc7 is out. So the next two steps are:

April 15: v3.9-rc7 based linux-linaro-core-tracking (llct) rebuild

- done

April 16: ll rebuild based on llct-20130415

- done

April 16: v3.9-rc7 based linux-linaro-core-tracking (llct) rebuild
- done: the tag is llct-20130417.0
Changes:
numa topic added
linaro/configs/kvm-host.conf updated

Next step:

April 18: ll rebuild based on llct-20130417.0, linux-linaro release 
candidate.


April 18 is the linux-linaro code freeze for 13.04 (only bug fixes
allowed after this date).

Thanks,
Andrey


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

[ANNOUNCE] linux-linaro kernel schedule for 13.04 updated

[Andrey Konovalov]

Greetings,

11.04.2013 23:20, Andrey Konovalov пишет:

Greetings,

This is a reminder that this wiki page:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

- is now tracking the linux-linaro kernel rebuilds for 13.04.

v3.9-rc6 based linux-linaro-core-tracking (llct) rebuild has just been
published, the tag is llct-20130411.0.

The next step is:
April 12: ll rebuild based on llct-20130411.0.

- done

v3.9-rc7 is out. So the next two steps are:

April 15: v3.9-rc7 based linux-linaro-core-tracking (llct) rebuild
April 16: ll rebuild based on llct-20130415

The last llct update for this cycle is scheduled on April 16,
The last linux-linaro update for this cycle is scheduled on April 18.
April 18 is the linux-linaro code freeze for 13.04 (only bug fixes
allowed after this date).

Thanks,
Andrey


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

[ANNOUNCE] linux-linaro kernel schedule for 13.04 updated

[Andrey Konovalov]

Greetings,

This is a reminder that this wiki page:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

- is now tracking the linux-linaro kernel rebuilds for 13.04.

v3.9-rc6 based linux-linaro-core-tracking (llct) rebuild has just been 
published, the tag is llct-20130411.0.


The next step is:
April 12: ll rebuild based on llct-20130411.0.

The last llct update for this cycle is scheduled on April 16,
The last linux-linaro update for this cycle is scheduled on April 18.
April 18 is the linux-linaro code freeze for 13.04 (only bug fixes 
allowed after this date).


Thanks,
Andrey

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

[ANNOUNCE] linux-linaro kernel schedule for 13.03

[Andrey Konovalov]

Greetings,

The current 13.03 schedule has been published on wiki:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

llct rebuild is planned later today.

The 13.03 release would be v3.9-rc3 based (tentative).

Please make sure that requests to add new topics (with the git branch to 
pull from) have been sent to me, or will be sent as soon as the topic is 
ready. I would appreciate a heads up like information on the new 
topics which are more complex than a couple patches on top of mainline. 
For the moment I am aware of the kvm topic only. Anything else?



Thanks,
Andrey

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

Re: [ANNOUNCE] linux-linaro kernel schedule for 13.02

[Andrey Konovalov]

Hi Liviu,

On 02/28/2013 02:18 PM, Liviu Dudau wrote:

Hi Andrey,

Do you have any plans to do another respin of the ll tree before final 13.02?


I do plan to update the ll tree later today to pull a fix from one of 
the ll topics. But this update won't get into 13.02 release: the 
linux-linaro kernel is released one week before the whole release. So 
the 13.02 linux-linaro kernel release happened last Friday, Feb 22.


Thanks,
Andrey


Regards,
Liviu

On Sun, Feb 10, 2013 at 06:03:49PM +, Andrey Konovalov wrote:

Greetings,

llct has been moved to v3.8-rc7 (tag llct-20130210.0).
If the ll topics would be ready, on Feb 11, in the evening GMT there
will be the ll rebuild based on llct-20130210.0.

Thanks,
Andrey

On 02/04/2013 09:51 PM, Andrey Konovalov wrote:

Greetings,

The current 13.02 schedule has been published on wiki:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

llct rebuild is planned later today.

The 13.02 release would be v3.8-rc8 based (tentative).

Please make sure that requests to add new topics (with the git branch to
pull from) have been sent to me, or will be sent as soon as the topic is
ready. I would appreciate a heads up like information on the new
topics which are more complex than a couple patches on top of mainline.
For the moment I am aware of the kvm topic only. Anything else?


Thanks,
Andrey



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






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

Re: [GIT PULL] big LITTLE MP - v15

[Andrey Konovalov]

On 02/15/2013 09:27 PM, Viresh Kumar wrote:

Hi Andrey,

big LITTLE MP v15 is ready for you to pull.


Merged into llct-20130217.0

Thanks,
Andrey


Its 11:00 PM at my side
and am feeling
really sleepy, please forgive any stupid mistakes of mine.

 Updates:
 ---
 - Rebased over 3.8-rc7
 - Stats: Total distinct patches: 36
   - Dropped Patches: Two patches from cpufreq-fixes-v2 (3): causing some
   failures.


-x---x

The following changes since commit 836dc9e3fbbab0c30aa6e664417225f5c1fb1c39:

   Linux 3.8-rc7 (2013-02-09 08:20:39 +1100)

are available in the git repository at:

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

for you to fetch changes up to 6ab7c9986cf271abd3564ec8e90ad48a4ff1d8b7:

   Merge branches 'arm-multi_pmu_v2', 'cpufreq-fixes-v3',
'hw-bkp-v7.1-debug-v2', 'task-placement-v2',
'task-placement-v2-sysfs', 'misc-patches' and 'config-fragments' into
big-LITTLE-MP-master-v15 (2013-02-15 22:44:07 +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 (7):
   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
   sched: fix arch_get_fast_and_slow_cpus to get logical cpumask correctly

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

Viresh Kumar (7):
   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
   Merge branches 'arm-multi_pmu_v2', 'cpufreq-fixes-v3',
'hw-bkp-v7.1-debug-v2', 'task-placement-v2',
'task-placement-v2-sysfs', 'misc-patches' and 'config-fragments' into
big-LITTLE-MP-master-v15

  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|  132 
  drivers/cpufreq/cpufreq.c |   25 +-
  include/linux/sched.h |   12 +
  include/trace/events/sched.h  |  153 
  kernel/irq/irqdesc.c  |   21 +-
  kernel/sched/core.c   |4 +
  kernel/sched/debug.c  |3 +
  kernel/sched/fair.c   | 1021 -
  kernel/sched/sched.h  |   13 +-
  linaro/configs/big-LITTLE-MP.conf 

Re: [ANNOUNCE] linux-linaro kernel schedule for 13.02

[Andrey Konovalov]

Greetings,

llct has been moved to v3.8-rc7 (tag llct-20130210.0).
If the ll topics would be ready, on Feb 11, in the evening GMT there 
will be the ll rebuild based on llct-20130210.0.


Thanks,
Andrey

On 02/04/2013 09:51 PM, Andrey Konovalov wrote:

Greetings,

The current 13.02 schedule has been published on wiki:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

llct rebuild is planned later today.

The 13.02 release would be v3.8-rc8 based (tentative).

Please make sure that requests to add new topics (with the git branch to
pull from) have been sent to me, or will be sent as soon as the topic is
ready. I would appreciate a heads up like information on the new
topics which are more complex than a couple patches on top of mainline.
For the moment I am aware of the kvm topic only. Anything else?


Thanks,
Andrey



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

[ANNOUNCE] linux-linaro kernel schedule for 13.02

[Andrey Konovalov]

Greetings,

The current 13.02 schedule has been published on wiki:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

llct rebuild is planned later today.

The 13.02 release would be v3.8-rc8 based (tentative).

Please make sure that requests to add new topics (with the git branch to 
pull from) have been sent to me, or will be sent as soon as the topic is 
ready. I would appreciate a heads up like information on the new 
topics which are more complex than a couple patches on top of mainline. 
For the moment I am aware of the kvm topic only. Anything else?



Thanks,
Andrey

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

Re: [ANNOUNCE] linux-linaro kernel schedule for 13.01

[Andrey Konovalov]

Greetings,

The llct and ll have been updated to v3.8-rc4.
The tags are llct-20130121.1 and ll-20130122.0 respectively.
Some more details are here:
http://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

Unless there would be a strong reason, for the 13.01 ll will remain on 
llct-20130121.1 as the base. No more llct updates are scheduled for 13.01.


ll code freeze is this Thursday. No new topic and massive changes would 
be allowed for ll after Jan 24 and until 13.01 is out, only bug fixes 
would be added.


Thanks,
Andrey

18.01.2013 20:10, Andrey Konovalov пишет:

Greetings,

Due to the commit 54b956b903607f8f8878754dd4352da6a54a1da2 Remove
__dev* markings from init.h changes in v3.8-rc4, there will be no
updated llct today (the LinuxLinaroKernelSchedule wiki page updated):
the android topic needs some rework to account for this change.

The llct / ll topic owners,
Please ensure that your topics are ready for llct and then ll to move to
v3.8-rc4!
This can be done by e.g.:
   git checkout -B bbb v3.8-rc4
   git merge your topic branch
   grep __devinit -r *
   grep __devexit -r *
There should be no __devinit/__devexit added vs v3.8-rc4.

Thanks,
Andrey


On 01/15/2013 01:29 PM, Andrey Konovalov wrote:

Greetings,

The current 13.01 schedule has been published on wiki:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

Initial versions of llct and ll trees has been pushed to g.l.o,
kernel/linux-linaro-tracking.git yesterday.

The 13.01 release would be v3.8-rc4 based (tentative).

Some changes vs 12.12:
  * new topic in ll for better Snowball support.
Currently this is device tree, serial console, emmc, ethernet.
  * the perf-android patch(es) would be a separate ll topic.


Thanks,
Andrey





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

Re: [ANNOUNCE] linux-linaro kernel schedule for 13.01

[Andrey Konovalov]

Greetings,

Due to the commit 54b956b903607f8f8878754dd4352da6a54a1da2 Remove 
__dev* markings from init.h changes in v3.8-rc4, there will be no 
updated llct today (the LinuxLinaroKernelSchedule wiki page updated):

the android topic needs some rework to account for this change.

The llct / ll topic owners,
Please ensure that your topics are ready for llct and then ll to move to 
v3.8-rc4!

This can be done by e.g.:
  git checkout -B bbb v3.8-rc4
  git merge your topic branch
  grep __devinit -r *
  grep __devexit -r *
There should be no __devinit/__devexit added vs v3.8-rc4.

Thanks,
Andrey


On 01/15/2013 01:29 PM, Andrey Konovalov wrote:

Greetings,

The current 13.01 schedule has been published on wiki:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

Initial versions of llct and ll trees has been pushed to g.l.o,
kernel/linux-linaro-tracking.git yesterday.

The 13.01 release would be v3.8-rc4 based (tentative).

Some changes vs 12.12:
  * new topic in ll for better Snowball support.
Currently this is device tree, serial console, emmc, ethernet.
  * the perf-android patch(es) would be a separate ll topic.


Thanks,
Andrey



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

[ANNOUNCE] linux-linaro kernel schedule for 13.01

[Andrey Konovalov]

Greetings,

The current 13.01 schedule has been published on wiki:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

Initial versions of llct and ll trees has been pushed to g.l.o, 
kernel/linux-linaro-tracking.git yesterday.


The 13.01 release would be v3.8-rc4 based (tentative).

Some changes vs 12.12:
 * new topic in ll for better Snowball support.
   Currently this is device tree, serial console, emmc, ethernet.
 * the perf-android patch(es) would be a separate ll topic.


Thanks,
Andrey

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

Re: [ANNOUNCE] linux-linaro kernel schedule for 13.01

[Andrey Konovalov]

On 01/15/2013 03:59 PM, Tushar Behera wrote:

On 01/15/2013 02:59 PM, Andrey Konovalov wrote:

Greetings,

The current 13.01 schedule has been published on wiki:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

Initial versions of llct and ll trees has been pushed to g.l.o,
kernel/linux-linaro-tracking.git yesterday.

The 13.01 release would be v3.8-rc4 based (tentative).

Some changes vs 12.12:
  * new topic in ll for better Snowball support.
Currently this is device tree, serial console, emmc, ethernet.
  * the perf-android patch(es) would be a separate ll topic.


Thanks,
Andrey

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


Samsung LT tree supporting Origen board on v3.8-rc3 has been pushed to glo.


Included into ll-20130115.0. Thanks!

-- Andrey


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

Re: [ANNOUNCE] linux-linaro kernel schedule for 13.01

[Andrey Konovalov]

On 01/15/2013 01:55 PM, Viresh Kumar wrote:

On 15 January 2013 14:59, Andrey Konovalov andrey.konova...@linaro.org wrote:

The current 13.01 schedule has been published on wiki:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

Initial versions of llct and ll trees has been pushed to g.l.o,
kernel/linux-linaro-tracking.git yesterday.

The 13.01 release would be v3.8-rc4 based (tentative).

Some changes vs 12.12:
  * new topic in ll for better Snowball support.
Currently this is device tree, serial console, emmc, ethernet.
  * the perf-android patch(es) would be a separate ll topic.


You can pull in b.L-MP-v14 branch for this.


It is already in llct (starting from llct-20130114.0).

Thanks,
Andrey

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

Re: When do we plan to move to Linux 3.8?

[Andrey Konovalov]

On 01/04/2013 02:28 PM, Jon Medhurst (Tixy) wrote:

On Fri, 2013-01-04 at 15:14 +0530, Viresh Kumar wrote:

On 4 January 2013 15:09, Jon Medhurst (Tixy) t...@linaro.org wrote:

I assume we'll be moving to Linux 3.8 for the January release cycle?


For the 13.01 my plan was to stay at 3.7 plus the stable 3.7.y updates 
(as by the time of code freeze the mainline would be at v3.8-rc4 or so - 
not sure if -rc4 would be stable enough).


But if the topic owners fill comfortable with moving to 3.8, we can go 
that way. Just would like to get confirmations from the owners of the 
heaviest topics.



For my part I have prepared a 3.8 branch for vexpress [1] which doesn't
yet contain Android patches or bit.LITTLE MP as their respective
branches aren't on 3.8 yet.


big.LITTLE MP is 3.8 based now :)


I take it as the vexpress topic (for the ll tree) and the big.LITTLE 
topic (for the llct tree) are ready to switch to 3.8, correct?


This leaves the Android topic for llct (John?) and Samsung LT topic for 
ll (Tushar?).


If anyone has another topic branch to include into 13.01 release, and 
moving to 3.8 or staying at 3.7.y is critical for that topic, please 
chime in!



:-) I've now included that in my integration-next branch and Android
boots on this, even though we don't have any of the Android patches?!
(I'm sure that never used to be possible.) Of course, we're missing
important things like the interactive governor...

If we're definitely moving to 3.8 then I may soon drop my temporary
'next' branches and move 'tracking' branches to 3.8, so if anyone can't
see integration-next in my tree, use
integration-{linux,android}-vexpress


Yes, definitely moving to 3.8 would make my life a bit easier too: 
llct could be moved to 3.8 w/o causing any troubles for topic owners 
(otherwise they would have to switch to linux-linaro-core-3.7 branch),

and there would be no urgency in creating CI jobs for linux-linaro-core-3.7.


BTW, when booting I see the lockdep error also reported upstream:
https://lkml.org/lkml/2013/1/3/192


It looks like there is some progress in getting the fix, so it could 
probably be resolved by 13.01 release. No 100% guarantee of course..



Thanks,
Andrey

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

Re: When do we plan to move to Linux 3.8?

[Andrey Konovalov]

On 01/04/2013 06:33 PM, Andrey Konovalov wrote:

But if the topic owners fill comfortable with moving to 3.8, we can go

feel comfortable that is

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

Re: [ANNOUNCE] linux-linaro kernel schedule for 12.12

[Andrey Konovalov]

Greetings,

The ll tree has been updated to use llct-20121211.0 as the base.
It still has just the ARM LT topic; waiting for the v3.7 based topic 
from Samsung LT.
Also the hack by Bero to make perf to build on android has been removed: 
will see if it break the perf build on ubuntu (see the 
LinuxLinaroKernelSchedule for more details).


* December 13 is the last date to update ll for 12.12 *

The current status and the schedule is:
https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

Thanks,
Andrey

On 12/11/2012 01:54 PM, Andrey Konovalov wrote:

The llct based on v3.7 release is there, and is tagged llct-20121211.0



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

Re: [ANNOUNCE] linux-linaro kernel schedule for 12.12

[Andrey Konovalov]

10.12.2012 23:26, Andrey Konovalov пишет:

Greetings,

The 12.12 schedule has been updated on wiki:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

Both the llct and the ll trees have been updated (see the wiki page for
the details).

There should be no more planned updates to llct for 12.12 release except
moving from v3.7-rc8 to v3.7 release if Linus makes it tonight.


The llct based on v3.7 release is there, and is tagged llct-20121211.0

Thanks,
Andrey


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

Re: [ANNOUNCE] linux-linaro kernel schedule for 12.12

[Andrey Konovalov]

On 12/11/2012 06:13 PM, Liviu Dudau wrote:

On Tue, Dec 11, 2012 at 09:54:19AM +, Andrey Konovalov wrote:

10.12.2012 23:26, Andrey Konovalov пишет:

Greetings,

The 12.12 schedule has been updated on wiki:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

Both the llct and the ll trees have been updated (see the wiki page for
the details).

There should be no more planned updates to llct for 12.12 release except
moving from v3.7-rc8 to v3.7 release if Linus makes it tonight.


The llct based on v3.7 release is there, and is tagged llct-20121211.0


Isn't the tag supposed to be llct-20121212.0? I'm getting confused
between release codes and December days.


This tag is llct-MMDD.X where YYYMMDD is the date when the tree has 
been rebuilt. This is not related to the release codes. The release 
will be tagged using different format like linux-linaro-3.7-2012.12 
(tree name-kernel version-release code).


Thanks,
Andrey


Regards,
Liviu



Thanks,
Andrey


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





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

Re: [PATCH] merge_config.sh: Add option to specify output dir

[Andrey Konovalov]

On 12/10/2012 06:51 PM, Zhangfei Gao wrote:




On 10 December 2012 01:22, Michal Marek mma...@suse.cz
mailto:mma...@suse.cz wrote:

On Mon, Dec 03, 2012 at 09:05:26AM -0800, John Stultz wrote:
  On 12/02/2012 11:36 PM, Zhangfei Gao wrote:
  Provide a -O option to specify dir to put generated .config
  Then merge_config.sh does not need to be copied to target dir,
  for easy re-usage in other script
 
  Signed-off-by: Zhangfei Gao zhangfei@linaro.org
mailto:zhangfei@linaro.org
  Tested-by: Jon Medhurst (Tixy) t...@linaro.org
mailto:t...@linaro.org
  Acked-by: John Stultz john.stu...@linaro.org
mailto:john.stu...@linaro.org

Applied to kbuild.git#kconfig, thanks.

Michal


Thanks Michal and John.


This patch has also been included into linux-linaro-core-tracking tree 
[1], the llct-20121210.0 tag.


Thanks,
Andrey

[1] 
http://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git;a=summary , 
linux-linaro-core-tracking branch


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

Re: [ANNOUNCE] linux-linaro kernel schedule for 12.12

[Andrey Konovalov]

Greetings,

The 12.12 schedule has been updated on wiki:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

Both the llct and the ll trees have been updated (see the wiki page for 
the details).


There should be no more planned updates to llct for 12.12 release except 
moving from v3.7-rc8 to v3.7 release if Linus makes it tonight.


Beware: this Thursday is the code freeze for linux-linaro kernel tree!


Thanks,
Andrey



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

Re: [GIT PULL] cpufreq-interactive-gov-master-v1

[Andrey Konovalov]

05.12.2012 08:32, Viresh Kumar пишет:

On 5 December 2012 09:55, John Stultz john.stu...@linaro.org wrote:

So while I can try to update the linaro-android tree more frequently,
maintaining that tree is more of a background task. So when my other
commitments consume my attention, sometimes that update frequency is slower.
Also, given we're already 3 releases beyond the AOSP tree, keeping the two
branches in perfect sync is unlikely to happen (due to the higher chance of
collisions).   So if folks notice there is some critical functionality that
is updated in the AOSP tree, when they let me know, I can be sure to merge
it in (like was done with this case - albeit slower then I'd like).


That might be enough, i suppose.


Are you saying that cpufreq-interactive-gov would not be needed in this 
case? Thus excluding the case when someone wants the interactive 
governor, but without the rest of the android code. (I thought it was 
one of the reasons to have a separate cpufreq-interactive-gov topic vs 
more frequent updates to the existing android topic)



However, if you're maintaining your own tree anyway, why not have Andrey
pull your tree in addition to the current linaro-android-3.x-*rebase branch?

Since they are both contain a common subset, the merge will likely be quite
easy.


Not quite right. At least the android topic is the rebase, so these 
topics are quite different from git's perspective. I've tried merging 
Viresh's topic into llct containing the Anton's version of the android 
topic. There were 2 conflicting files. One file was 3 commits ahead of 
the llct, and it would be much more easier to cherry pick those commits 
into llct than trying to associate the combined diff with the 3 commits. 
As for the 2nd file, it was just one additional commit in the Viresh's 
branch, but it wasn't the topmost commit in that branch for some reason. 
That is such merge needs some manual work, and I don't feel comfortable 
doing such merges w/o good knowledge of android or the governor at 
least. Also there may be conflict resolutions or fixes done when 
creating or updating the android topic, and they can be omitted by 
occasion when merging cpufreq-interactive-gov-master into llct.


The things would be pretty trivial, if cpufreq-interactive-gov-master 
were based on the android topic. But cpufreq-interactive-gov-master is 
intended to be used without the android topic as well, right? This means 
outside the linux-linaro kernel trees btw.



That way Andrey's tree will have a better chance of having the latest
changes.

Does that seem ok?


That was the initial idea, but there were concerns from Tixy and Andrey on that.
@Andrey: Do you want to comment again?


imho the conflicts when merging cpufreq-interactive-gov-master into llct 
require interactive governor tests in the CI loop. Especially if we want 
cpufreq-interactive-gov-master to be updated frequently.


How difficult would it be to maintain a special version of the 
cpufreq-interactive-gov topic for llct: cpufreq-interactive-gov-master 
rebased onto the most recent android topic? E.g. 
cpufreq-interactive-gov-linux-linaro?



Thanks,
Andrey


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

[ANNOUNCE] linux-linaro kernel schedule for 12.12

[Andrey Konovalov]

Greetings,

The current 12.12 schedule has been published on wiki:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

This is a short cycle: the linux-linaro (ll) tree freeze is December 13.

llct has been updated to v3.7-rc8, the tag is llct-20121205.0
Tomorrow I'll rebuild the ll using llct-20121205.0 as the base.

Thanks,
Andrey


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

Re: [GIT PULL] cpufreq-interactive-gov-master-v1

[Andrey Konovalov]

On 11/30/2012 02:23 PM, Viresh Kumar wrote:

On 30 November 2012 15:22, Jon Medhurst (Tixy) t...@linaro.org wrote:

But if they aren't different why do we need your version?


To my understanding, having a separate topic for the interactive 
governor makes sense if some people need this governor, but do not want 
the rest of android code in their kernel. Viresh, is this the case? This 
seems to contradict with the initial idea of the single kernel tree 
(where all the releases should be made from), but may be valuable for 
the LTs/members and for some development work.


Viresh,
I'd like an explicit answer to why do we need a separate topic for the 
interactive governor (in addition to the android one). We must be sure 
we would do that extra work for a reason.



On Fri, 2012-11-30 at 07:47 +0530, Viresh Kumar wrote:
But if they aren't different why do we need your version? Thing is I not
sure who the 'other guy' is who is maintaining the Android topic, it use
to always be John Stultz but not sure now.


I believe John is maintaining it, as i can guess from git.linaro.org


John did all the Android topics updates for llct except the last one. 
Adding Anton (his Android topic has been used for 12.11), and Deepak.



  That will guarantee that all are using same and latest
version of this governor.


Is 'the latest version' the one in AOSP?


Yes.

https://android.googlesource.com/kernel/common


So it is from the same source as the android topic for llct.
Just the topic by Viresh is a bit more recent, and is a few commits 
ahead of the android topic currently merged into llct.



Over that it would be available for ubuntu also.


But surely it is already available for Ubuntu because the Android topic
branch is included in llct. E.g. if you boot a 12.11 Ubuntu image for
vexpress and do

   cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors

you will get:

   interactive ondemand performance


Yes. It is. :)


How do you suggest to solve these issues?


That you, Andrey and
the 'the guy maintaining the Android topic'


Deepak, is that ^^^ John, Anton, or someone else? :)


get together and work it out :-)



Of course, it could be that things go smoothly without any coordination.

I don't believe in that :( In a different world - maybe.


I just wanted to chime in and make sure that people knew that there
could be issues, because these things have a nasty habit of cropping up
a few days before a monthly release, when there is little time to fix
and test things.


Viresh,


@John/Andrey: Current linux-linaro surely doesn't have latest interactive
governor in it. How do you guys suggest to get over this issue? I have few
ideas:
- John pull it from my tree, and i will keep an eye on AOSP

... the problem here is that AOSP is not the interactive governor only.
John (or the other Android topic guy) would have to keep an eye on the 
rest of AOSP. Keeping two pars of eyes on the same thing requires 
coordination. Or are you volunteering to take over the android topic? :)

- John directly pick patches from AOSP
... and again, then you and the Android topic guy must synchronize 
somehow.

Otherwise we would get into the same situation with two slightly different
versions of the interactive governor in the two topics like we have now.

John, Anton,

If one of you will continue to maintain the android topic, for the next 
cycles could you split a separate interactive governor topic from the 
android one? Or any other ideas?


Thanks,
Andrey


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

[ANNOUNCE][Linux Linaro kernel] Re: linux-linaro kernel trees move to 3.7 and 12.11 schedule

[Andrey Konovalov]

Greetings,

The linux-linaro-core-tracking tree has been updated to v3.7-rc6.

The current 12.11 schedule is now:
* October 30: initial v3.7-rc3 based llct build, 3.6 based topics will
 not be included if there are conflicts
 - Done. The tag is llct-20121101.1. v3.7-rc3 based.
* November 6: updated big-LITTLE-MP topic arrives, llct rebuild
 (llct-20121106)
 - Done. The tag is llct-20121106.0. v3.7-rc4 based.
* November 8: linux-linaro (ll) rebuild based on llct-20121106
 - Done. The tag is ll-20121108.0
* November 13: llct rebuild (llct-20121113)
 - Done. The tag is llct-20121113.0. v3.7-rc5 based.
   Otherwise the only change is in the configs topic:
   babf06c configs: linaro-base: set CONFIG_AEABI=y
* November 15: ll rebuild based on llct-20121113
 - Done. The tag is ll-20121115.0. Origen support is back into the
   ll tree (the tracking topic from the Samsung LT).
* November 20: llct rebuild (llct-20121120)
 - Done. The tag is llct-20121120.1. v3.7-rc6 based.
   This is the last scheduled llct update for 12.11.
 - Updates:
   . new version of the big.LITTLE-MP topic
 (big-LITTLE-MP-master-v12),
   . configs topic renamed to core-configs,
   . basic-board-configs topic added,
   . devfreq patches from Rajagopal Venkat added
   . KBuild: Allow scripts/* to be cross compiled patch added to
 llct-v3.7-misc-fixes topic
 - Not included into llct-20121120.1:
   . android perf patch from Bernhard Rosenkraenzer (patch received,
   but no topic branch yet): too much conflicts in 
tools/perf/Makefile vs v3.7-rc6

   for me to resolve myself.
   If I get the version of this patch to apply cleanly to v3.7-rc6,
   it could be included right into the ll tree for 12.11. (The risk
   is low, as the patch makes no changes outside tools/perf).
* November 23: ll rebuild based on llct-20121120.1, ll code freeze (no
 massive ll topics updates after that; bugfixes only)
 - Done. The tag is ll-20121123.2.
   No more ll updates for 12.11 unless critical issues are found.
   Updates:
   . based on llct-20121120.1
   . android perf patch from Bernhard Rosenkraenzer. Not the latest
   version unfortunately, as it arrived too late for 12.11.
   In 12.12 the most recent version of this patch will go into llct.

Thanks,
Andrey


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

Re: [GIT PULL]; big LITTLE MP master v12

[Andrey Konovalov]

On 11/20/2012 11:30 AM, Viresh Kumar wrote:

On 19 November 2012 22:44, Andrey Konovalov andrey.konova...@linaro.org wrote:

I won't pull the big-LITTLE-MP-master-v12 into the
linux-linaro-core-tracking tree today due to the issues found by Tixy.

Tomorrow evening I am going to pull this topic anyway - whether these issues
are resolved, or not. If the build error is not fixed by Thursday morning
UTC, I'll move llct back to v11. Would it work for the Landing Teams? Tixy?


Hi Andrey,

I have updated master-v12 branch with fixes from tixy and ARM.
You can PULL it now :)


Done. Thanks!

Andrey



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

[ANNOUNCE][Linux Linaro kernel] Re: linux-linaro kernel trees move to 3.7 and 12.11 schedule

[Andrey Konovalov]

Greetings,

The linux-linaro-core-tracking tree has been updated to v3.7-rc6.

The current 12.11 schedule is now:
* October 30: initial v3.7-rc3 based llct build, 3.6 based topics will
not be included if there are conflicts
- Done. The tag is llct-20121101.1. v3.7-rc3 based.
* November 6: updated big-LITTLE-MP topic arrives, llct rebuild
(llct-20121106)
- Done. The tag is llct-20121106.0. v3.7-rc4 based.
* November 8: linux-linaro (ll) rebuild based on llct-20121106
- Done. The tag is ll-20121108.0
* November 13: llct rebuild (llct-20121113)
- Done. The tag is llct-20121113.0. v3.7-rc5 based.
  Otherwise the only change is in the configs topic:
  babf06c configs: linaro-base: set CONFIG_AEABI=y
* November 15: ll rebuild based on llct-20121113
- Done. The tag is ll-20121115.0. Origen support is back into the
  ll tree (the tracking topic from the Samsung LT).
* November 20: llct rebuild (llct-20121120)
- Done. The tag is llct-20121120.1. v3.7-rc6 based.
  This is the last scheduled llct update for 12.11.
- Updates:
  . new version of the big.LITTLE-MP topic
(big-LITTLE-MP-master-v12),
  . configs topic renamed to core-configs,
  . basic-board-configs topic added,
  . devfreq patches from Rajagopal Venkat added
  . KBuild: Allow scripts/* to be cross compiled patch added to
llct-v3.7-misc-fixes topic
- Not included into llct-20121120.1:
  . android perf patch from Bernhard Rosenkraenzer (patch received,
but no topic branch yet): too much conflicts in 
tools/perf/Makefile vs v3.7-rc6

for me to resolve myself.
  If I get the version of this patch to apply cleanly to v3.7-rc6,
  it could be included right into the ll tree for 12.11. (The risk
  is low, as the patch makes no changes outside tools/perf).
* November 22: ll rebuild based on llct-20121120.1, ll code freeze (no
massive ll topics updates after that; bugfixes only)


Thanks,
Andrey


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

Re: [GIT PULL]; big LITTLE MP master v12

[Andrey Konovalov]

Viresh,

I won't pull the big-LITTLE-MP-master-v12 into the 
linux-linaro-core-tracking tree today due to the issues found by Tixy.


Tomorrow evening I am going to pull this topic anyway - whether these 
issues are resolved, or not. If the build error is not fixed by Thursday 
morning UTC, I'll move llct back to v11. Would it work for the Landing 
Teams? Tixy?


Thanks,
Andrey

On 11/19/2012 07:57 PM, Chris Redpath wrote:

Hi Tixy,

These patches are mine and Olivier's, can you tell me what your config is to 
see even a 90s boot? I haven't noticed any boot-time extension on my system, 
but I'm booting from the A15 cluster. I'd like to reproduce your system here.

The build error is my mistake, I need to know which CPU a task is on and it 
looks like I have missed a dependency when I've changed the calling code. I 
will sort out a patch for that asap.

Best Regards,
Chris


-Original Message-
From: Jon Medhurst (Tixy) [mailto:t...@linaro.org]
Sent: 19 November 2012 15:41
To: Viresh Kumar
Cc: Andrey Konovalov; PDSW-power-team; Lists linaro-dev
Subject: Re: [GIT PULL]; big LITTLE MP master v12

On Sun, 2012-11-18 at 10:40 +0530, Viresh Kumar wrote:

Hi Andrey,

Please pull big-LITTLE-MP-master-v12 with following updates:

 - Based on v3.7-rc5
 - Stats:
  - Total Patches: 62
  - New Patches: 1
- genirq: Add default affinity mask command line option in
misc-patches branch
- top 3 patches in: sched-pack-small-tasks-v1
- top 2 patches in: task-placement-v2
- additional patch in: config-fragments
  - Dropped patches/branches (as they are managed in experimental
merge branch): 20
- patches in per-entity-load-tracking-with-core-sched-v1: 15
  - Updated Patches: 0



This version increases Android boot time by a factor of 3, from 91
seconds to 257 seconds, this is comparing it with the version of the
master-v12 branch created on Nov 15th. Looking at the differences in
the
code, one obvious thing which stands out is big-LITTLE-MP.conf now has:

CONFIG_HMP_VARIABLE_SCALE=y
CONFIG_HMP_FREQUENCY_INVARIANT_SCALE=y

If I remove this then boot time goes back to 90 seconds.

Also, if I build without big-LITTLE-MP.conf the I get a build error:

kernel/sched/fair.c: In function 'update_entity_load_avg':
kernel/sched/fair.c:1469:26: error: 'struct sched_entity' has no member
named 'cfs_rq'

--
Tixy


-x--x

---


The following changes since commit

77b67063bb6bce6d475e910d3b886a606d0d91f7:


   Linux 3.7-rc5 (2012-11-11 13:44:33 +0100)

are available in the git repository at:

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

for you to fetch changes up to

f942092bd1008de7379b4a52d38dc03de5949fc8:


   Merge branches 'arm-multi_pmu_v2', 'hw-bkp-v7.1-debug-v1',
'task-placement-v2', 'misc-patches', 'config-fragments' and
'sched-pack-small-tasks-v1' into big-LITTLE-MP-master-v12-v2
(2012-11-17 09:29:41 +0530)



Ben Segall (1):
   sched: Maintain per-rq runnable averages

Chris Redpath (1):
   ARM: Experimental Frequency-Invariant Load Scaling Patch

Dietmar Eggemann (1):
   ARM: hw_breakpoint: v7.1 self-hosted debug powerdown support

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

Liviu Dudau (2):
   Revert sched: secure access to other CPU statistics
   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

Marc Zyngier (1):
   ARM: perf: add guest vs host discrimination

Mark Rutland (1):
   ARM: perf: register cpu_notifier at driver init

Morten Rasmussen (15):
   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: SD_SHARE_POWERLINE buddy selection fix
   ARM: TC2: Re-enable SD_SHARE_POWERLINE

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

Paul Turner (15):
   sched: Track the runnable average on a per-task entity basis
   sched: Aggregate load contributed by task entities on parenting

cfs_rq

   sched: Maintain the load contribution of blocked entities

Re: [GIT PULL]; big LITTLE MP master v12

[Andrey Konovalov]

On 11/19/2012 10:17 PM, Jon Medhurst (Tixy) wrote:

On Mon, 2012-11-19 at 21:14 +0400, Andrey Konovalov wrote:

Viresh,

I won't pull the big-LITTLE-MP-master-v12 into the
linux-linaro-core-tracking tree today due to the issues found by Tixy.

Tomorrow evening I am going to pull this topic anyway - whether these
issues are resolved, or not. If the build error is not fixed by Thursday
morning UTC, I'll move llct back to v11. Would it work for the Landing
Teams? Tixy?


The timescales seem a bit wrong for that, working backwards...


That's correct..


- The monthly release is made from linux-linaro's state at end of
Thursday.

- You need to merge Landing Team's topics in before then.

- Landing Teams need to prepare their topics based on a given llct.

- To prepare their topics, Landing Teams need to be able to compile
their kernels.

So I would say that LT's need a final working llct tomorrow really. I
could manage OK getting this on Wednesday, don't know about other teams.

That's would then mean the monthly release candidate build comes from a
tree who's contents have never been built together before that day, so
it's trusting to luck somewhat.

Last month llct was created by the Monday morning so LT's could base
their branches on that and have them merged into linux-linaro by the end
of Tuesday. We then had two days to fix problems before Thursday's code
cutoff.


I'll push updated llct tree with v11 big-LITTLE-MP topic tonight.
If there is the build error fix by tomorrow, I can push one more llct 
update using the updated master v12 version tomorrow. Is the boot delay 
issue a show-stopper? If yes, we could just stick to the v11 for this cycle.


Thanks,
Andrey


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

Re: [GIT PULL]; big LITTLE MP master v12

[Andrey Konovalov]

On 11/19/2012 10:42 PM, Jon Medhurst (Tixy) wrote:

On Mon, 2012-11-19 at 22:24 +0400, Andrey Konovalov wrote:

On 11/19/2012 10:17 PM, Jon Medhurst (Tixy) wrote:

On Mon, 2012-11-19 at 21:14 +0400, Andrey Konovalov wrote:

Viresh,

I won't pull the big-LITTLE-MP-master-v12 into the
linux-linaro-core-tracking tree today due to the issues found by Tixy.

Tomorrow evening I am going to pull this topic anyway - whether these
issues are resolved, or not. If the build error is not fixed by Thursday
morning UTC, I'll move llct back to v11. Would it work for the Landing
Teams? Tixy?


The timescales seem a bit wrong for that, working backwards...


That's correct..


- The monthly release is made from linux-linaro's state at end of
Thursday.

- You need to merge Landing Team's topics in before then.

- Landing Teams need to prepare their topics based on a given llct.

- To prepare their topics, Landing Teams need to be able to compile
their kernels.

So I would say that LT's need a final working llct tomorrow really. I
could manage OK getting this on Wednesday, don't know about other teams.

That's would then mean the monthly release candidate build comes from a
tree who's contents have never been built together before that day, so
it's trusting to luck somewhat.

Last month llct was created by the Monday morning so LT's could base
their branches on that and have them merged into linux-linaro by the end
of Tuesday. We then had two days to fix problems before Thursday's code
cutoff.


I'll push updated llct tree with v11 big-LITTLE-MP topic tonight.
If there is the build error fix by tomorrow, I can push one more llct
update using the updated master v12 version tomorrow.


That's sounds like a sensible plan :-)


llct-20121120.0 has been pushed to g.l.o:
- v3.7-rc6 based
- the same v11 big-LITTLE-MP topic,
- configs topic renamed to core-configs,
- basic-board-configs topic added,
- devfreq topic added,
- KBuild: Allow scripts/* to be cross compiled patch added to
  llct-v3.7-misc-fixes topic


  Is the boot delay
issue a show-stopper?


It's not a show-stopper. It only manifests with a new config option in
the big-LITTPLE-MP config, so doesn't impact any board other than
vexpress and if required I could override it in my tree or we could add
a simple patch to linux-linaro later.

Someone else can't reproduce the problem so the slowness could be user
error on my part. (The build failure problem is definitely real
though :-)


OK :)

Thanks,
Andrey



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

Re: Add board config fragments to llct? (Re: Would like to add couple conf files to the config-boards-tracking branch)

[Andrey Konovalov]

On 11/15/2012 07:50 AM, Tushar Behera wrote:

On 11/14/2012 07:41 PM, Ryan Harkin wrote:

On 14 November 2012 11:38, Jon Medhurst (Tixy) t...@linaro.org wrote:

Adding linaro-dev list and replying with some comments...
On Tue, 2012-11-13 at 20:20 +0400, Andrey Konovalov wrote:

The llct tree itself has no suitable .conf or defconfig for vexpress at
all. That's the problem (wrt the ci jobs).

The easier way seemed to be a single kernel/configs.git,
config-boards-tracking branch to provide the config fragments for all
the llct jobs.
But it creates several instances of the same board.conf files and adds
confusion. Agreed.
Should we do in the jenkins jobs something like 'git checkout
arm_lt/integration-linaro-vexpress.conf -- linaro/configs/vexpress.conf'
for vexpress and similar (but different and unique) command for the
other boards?


Yes, I see the problem. But getting CI jobs to pull configs direct from
an LT tree seems like the wrong solution. I guess what people really
need is configs in linux-linaro-core-tracking (llct) (I'm sure people
have told me that before and I possibly didn't listen enough).

Now that the LT branches included in linux-linaro (ll) are based on
llct, then they could modify the board configs in llct if required for
the work in their topics. So at the moment, I can't think of a good
reason not to pub all the board configs into llct. Can anyone else?

I don't know if we need the board configs to be sourced from a single
repo, or allow board configs to be included in llct from LT trees. One
central repo means that people know where to go


This seems like the easiest option to me.  Let's do it this way unless
someone gives a valid objection.


(Unless we had
an official maintainer to manage all commits to the tree.)


I assume this would have to be Andrey.  Andrey, are you OK with that?
Or does someone else need to do it?

Each LT that is using LLCT would have to send a patch to get their
config updated.  So long as this happens in a timely manner, LTs
should be able to live with that process.



I suppose we are talking about the basic board config here. That should
be ok. The new board enablement config fragments should always go in
with the respective topic branches.


Yes, only the basic board configs are for LLCT.


Or course, once Linaro's build and test infrastructure supports config
fragments fully, then we could have have separate config fragments for
- basic board config
- new board enablement
- special features (e.g. big.LITTLE MP)
- testing or benchmarking config
and the configs could live in the tree relevant to the code they apply
to rather than having a single central board config we have to manage.


That sounds scarey - there would be no one place to get a config, but
I guess, if you need a config for feature X, you'd also need the
branch for feature X that contained the source and config, so it would
work out fine.

Cheers,
Ryan.

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







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

Re: Add board config fragments to llct? (Re: Would like to add couple conf files to the config-boards-tracking branch)

[Andrey Konovalov]

On 11/15/2012 04:01 PM, Ryan Harkin wrote:

On 15 November 2012 11:37, Jon Medhurst (Tixy) t...@linaro.org wrote:

On Thu, 2012-11-15 at 09:20 +0530, Tushar Behera wrote:

On 11/14/2012 07:41 PM, Ryan Harkin wrote:

On 14 November 2012 11:38, Jon Medhurst (Tixy) t...@linaro.org wrote:

[...]

Now that the LT branches included in linux-linaro (ll) are based on
llct, then they could modify the board configs in llct if required for
the work in their topics. So at the moment, I can't think of a good
reason not to pub all the board configs into llct. Can anyone else?

I don't know if we need the board configs to be sourced from a single
repo, or allow board configs to be included in llct from LT trees. One
central repo means that people know where to go


This seems like the easiest option to me.  Let's do it this way unless
someone gives a valid objection.


(Unless we had
an official maintainer to manage all commits to the tree.)


I assume this would have to be Andrey.  Andrey, are you OK with that?
Or does someone else need to do it?

Each LT that is using LLCT would have to send a patch to get their
config updated.  So long as this happens in a timely manner, LTs
should be able to live with that process.



I suppose we are talking about the basic board config here. That should
be ok. The new board enablement config fragments should always go in
with the respective topic branches.


I agree.


OK, can we do it then?  We're freezing for release today,


Are we?
https://wiki.linaro.org/Cycles/1211/Release/Calendar?highlight=%28release%29|%2812.11%29


but it's not
a big change, so we can get it in, right?

At some point in the past, Andrey asked:

My question is if this topic branch would be kernel/configs.git,


Sounds perfect



  config-boards-tracking branch or something else?


I don't have an opinion.  We'll probably have to live with it for a
long time, but as long as it looks sensible, I'm sure people will be
ok...

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




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

Re: Add board config fragments to llct? (Re: Would like to add couple conf files to the config-boards-tracking branch)

[Andrey Konovalov]

On 11/14/2012 06:11 PM, Ryan Harkin wrote:

On 14 November 2012 11:38, Jon Medhurst (Tixy) t...@linaro.org wrote:

Adding linaro-dev list and replying with some comments...
On Tue, 2012-11-13 at 20:20 +0400, Andrey Konovalov wrote:

The llct tree itself has no suitable .conf or defconfig for vexpress at
all. That's the problem (wrt the ci jobs).

The easier way seemed to be a single kernel/configs.git,
config-boards-tracking branch to provide the config fragments for all
the llct jobs.
But it creates several instances of the same board.conf files and adds
confusion. Agreed.
Should we do in the jenkins jobs something like 'git checkout
arm_lt/integration-linaro-vexpress.conf -- linaro/configs/vexpress.conf'
for vexpress and similar (but different and unique) command for the
other boards?


Yes, I see the problem. But getting CI jobs to pull configs direct from
an LT tree seems like the wrong solution. I guess what people really
need is configs in linux-linaro-core-tracking (llct) (I'm sure people
have told me that before and I possibly didn't listen enough).

Now that the LT branches included in linux-linaro (ll) are based on
llct, then they could modify the board configs in llct if required for
the work in their topics. So at the moment, I can't think of a good
reason not to pub all the board configs into llct. Can anyone else?


Having the boards config fragments in llct is fine for me. Advantageous 
even.



I don't know if we need the board configs to be sourced from a single
repo, or allow board configs to be included in llct from LT trees. One
central repo means that people know where to go


This seems like the easiest option to me.  Let's do it this way unless
someone gives a valid objection.


llct can only include topic branches. So I need to pull all the board 
configs into a single git branch anyway. See no big reason not to make 
this topic branch public (== the central repo known to people).


My question is if this topic branch would be kernel/configs.git, 
config-boards-tracking branch or something else?



(Unless we had
an official maintainer to manage all commits to the tree.)


I assume this would have to be Andrey.  Andrey, are you OK with that?


I am OK with that. Seems I just have no other choice :)
Just don't expect a lot of intelligence from me in this role, and be 
prepared to dumb questions when something is not good with the board 
config fragments.



Or does someone else need to do it?

Each LT that is using LLCT would have to send a patch to get their
config updated.  So long as this happens in a timely manner, LTs
should be able to live with that process.


Updating the board configs in the topic branch and the LLCT could be 
tied to the scheduled LLCT updates - every Tuesday that is. And on 
request if there is something urgent.


As for me, the board configs are good, as long as the resulting kernels 
build, boot ok in LAVA, and pass basic LAVA tests.



Or course, once Linaro's build and test infrastructure supports config
fragments fully, then we could have have separate config fragments for
- basic board config
- new board enablement


Not sure if I follow this 100%... Can I have an example of new board 
enablement vs basic board config config fragment?



- special features (e.g. big.LITTLE MP)
- testing or benchmarking config
and the configs could live in the tree relevant to the code they apply
to rather than having a single central board config we have to manage.


There is already big-LITTLE-MP.conf in the LLCT tree which comes from 
the big-LITTLE-MP topic.



That sounds scarey - there would be no one place to get a config, but
I guess, if you need a config for feature X, you'd also need the
branch for feature X that contained the source and config, so it would
work out fine.


Yes. This is the case for big.LITTLE MP, and hopefully the other 
upcoming topics would follow this as an example. In the testing config 
case, I wouldn't be surprised by a topic being just the config fragment 
(provided that all the relevant code is already in the tree). Then for 
building and testing the stuff in e.g. the LLCT, one would need just to 
specify the list of the (in the tree) config fragments to use. (But the 
build infrastructure should allow using the config fragments from other 
repositories/branches too.) The board config fragments would go into the 
LLCT via the board configs topic.


Thanks,
Andrey


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

Re: Add board config fragments to llct? (Re: Would like to add couple conf files to the config-boards-tracking branch)

[Andrey Konovalov]

On 11/14/2012 08:12 PM, Jon Medhurst (Tixy) wrote:

On Wed, 2012-11-14 at 19:06 +0400, Andrey Konovalov wrote:


Or course, once Linaro's build and test infrastructure supports config
fragments fully, then we could have have separate config fragments for
- basic board config
- new board enablement


Not sure if I follow this 100%... Can I have an example of new board
enablement vs basic board config config fragment?


I guess basic board config == config for features in Linus Torvald's
tree. new board enablement == config for things only in LT tree. For
us that's TC2 power managemnt and various drivers. Probably, most of the
time the config for this extra stuff in LT trees is harmless (i.e. just
gives KConfig warnings) but I imagine there might be things which would
break llct.


This makes sense. I see.
The new board enablement is not for the board configs topic for llct 
then.


Thanks,
Andrey


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

Re: [PATCH] genirq: Add default affinity mask command line option

[Andrey Konovalov]

On 11/13/2012 12:51 PM, Jon Medhurst (Tixy) wrote:

On Mon, 2012-11-12 at 22:32 +0530, Viresh Kumar wrote:

On 12 November 2012 22:27, Punit Agrawal punit.agra...@arm.com wrote:

I am attaching a patch by Thomas Gleixner which adds a kernel
command line parameter to set the defauilt IRQ affinity mask. Could
you please integrate this in your tree for the next Linaro release?

I've been using this patch for sometime now and it doesn't introduce
any regressions. There is a possibility that this patch will make it
upstream via the RT patches in the near future but in the meanwhile,
we'd like to carry this patch as well.


Hi Punit,

I agree with you that many of us would be interested in using this patch,
but i am not sure about which tree should it land into?

@Andrey/Tixy: Any other better tree you can suggest for carrying this one?
Or is my tree the best place :)


It's not really anything to do with vexpress enablement and I don't
believe it's Andrey's job to maintain patches, but I assume it's not
strictly related to big.LITTLE MP either. So I guess I'm saying that it
wants someone who agrees the patch is good to have to volunteer to
maintain it and create/find a suitable topic branch for inclusion into
llct.

But if someone called Viresh thought the patch looked useful for people
testing or experimenting with power management, and wasn't too worried
about it being the thin end of the wedge, then he might just take the
simplest approach and add it to his big.LITTLE MP branch ;-)


+1

Me to maintain patches is not the best option at all, as often I have 
very little idea of what the patch is doing. (Though I have to do that 
in very rare cases, and right now I have another patch floating around 
with no one willing to maintain it as it seems :( )


Thanks,
Andrey


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

[Linux Linaro kernel] Re: linux-linaro kernel trees move to 3.7 and 12.11 schedule

[Andrey Konovalov]

Greetings,

The linux-linaro-core-tracking tree has been updated to v3.7-rc5.

The current 12.11 schedule is now:
* October 30: initial v3.7-rc3 based llct build, 3.6 based topics will
   not be included if there are conflicts
   - Done. The tag is llct-20121101.1. v3.7-rc3 based.
* November 6: updated big-LITTLE-MP topic arrives, llct rebuild
   (llct-20121106)
   - Done. The tag is llct-20121106.0. v3.7-rc4 based.
* November 8: linux-linaro (ll) rebuild based on llct-20121106
   - Done. The tag is ll-20121108.0
* November 13: llct rebuild (llct-20121113)
   - Done. The tag is llct-20121113.0. v3.7-rc5 based.
 Otherwise the only change is in the configs topic:
 babf06c configs: linaro-base: set CONFIG_AEABI=y
* November 15: ll rebuild based on llct-20121113
* November 20: llct rebuild (llct-20121120)
   - Expected updates:
 . android perf patch from Bernhard Rosenkraenzer (patch received,
   but no topic branch yet),
 . devfreq patches from Rajagopal Venkat (waiting for the updated
   topic branch)
* November 22: ll rebuild based on llct-20121120, ll code freeze (no
   massive ll topics updates after that; bugfixes only)


Thanks,
Andrey


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

Re: New Gator version

[Andrey Konovalov]

Hi Tixy,

On 11/05/2012 07:34 PM, Jon Medhurst (Tixy) wrote:

Hi Andrey

Two weeks ago ARM released a new version of Developer Studio 5 (v5.12)
which as usual included a new version of the Streamline plugin and the
corresponding new versions of the Gator daemon and module which run on
the target device.

I have updated my tracking branch which is pulled into
linux-linaro-core-tracking so Linaro's Linux 3.7 kernels will get this
new Gator version. However, I suspect that some builds will be staying
with Linux 3.6 for a while so I have a separate topic branch suitable
for pulling into this. I'm not completely sure how such branches will be
managed


Well, me too.


but, if it is possible, can the Gator version in 3.6 be replaced
by the new one from the branch '3.6-armlt-gator-5.12' in ARM LT tree
(git://git.linaro.org/landing-teams/working/arm/kernel) ?


I'll add it to the linux-linaro-core-3.6 branch at 
git://git.linaro.org/kernel/linux-linaro-tracking.git.


Thanks,
Andrey


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

Re: linux-linaro kernel trees move to 3.7 and 12.11 schedule

[Andrey Konovalov]

Greetings,

This cycle some more attention is given to the shape of the ci builds 
done from the llct tree (the ones with llct in their name at 
https://ci.linaro.org/jenkins/view/Linux%20Linaro%20Tracking/). See below.


On 10/27/2012 12:39 PM, Andrey Konovalov wrote:

The 12.11 linux-linaro kernel release will be v3.7-rc5 or v3.7-rc6 based.

Please make sure to update your topics to 3.7.

Here is the plan:
* October 30: initial v3.7-rc3 based llct build, 3.6 based topics will
not be included if there are conflicts


Done. The tag is llct-20121101.1. v3.7-rc3 based.

Origen failed to boot in LAVA (silence after Uncompressing Linux... 
done, booting the kernel.)
mmc doesn't work on Panda when the kernel is built using the (old) 
config fragments 
(http://validation.linaro.org/lava-server/scheduler/job/37832/log_file).

Panda boots ok with omap2plus_defconfig.
vexpress boots ok.


* November 6: updated big-LITTLE-MP topic arrives, llct rebuild
(llct-20121106)


Done. The tag is llct-20121106.0. v3.7-rc4 based.

Android and big-LITTLE-MP topics are back. New Gator version (v5.12).

*ubuntu-sauce topic will be dropped* Anyone objects?

The same boot failure for Origen. Disabling device tree in the kernel
config makes the kernel to start booting 
(http://validation.linaro.org/lava-server/scheduler/job/37885/log_file). 
Could be arch/arm/boot/dts/exynos4210-origen.dts issue.


Thanks,
Andrey


* November 8: linux-linaro (ll) rebuild based on llct-20121106
* November 13: llct rebuild (llct-20121113)
* November 15: ll rebuild based on llct-20121113
* November 20: llct rebuild (llct-20121120)
* November 22: ll rebuild based on llct-20121120, ll code freeze (no
massive ll topics updates after that; bugfixes only)

(The dates above are milestones, there will be additional llct/ll
rebuilds on other dates as well)

The config fragment branches to be used in 12.11:
git://git.linaro.org/kernel/configs.git , config-core-tracking and
config-boards-tracking branches.

Thanks,
Andrey




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

Re: Planning topcs for inclusion in linux-linaro

[Andrey Konovalov]

On 10/17/2012 10:41 AM, Tushar Behera wrote:

On 10/06/2012 02:37 AM, Andrey Konovalov wrote:

Greetings,

Minor change to the plan:
  * The current llct is *llct-20121006.0*
  * October  9: ll rebuild based on llct-20121006.0
  * October 16: ll rebuild based on llct-20121012.N, ll code freeze (no
massive ll topics updates after that; bugfixes only)



Samsung LT kernel tree based on llct-20121012.0 has been pushed to g.l.o.

git://git.linaro.org/landing-teams/working/samsung/kernel.git
branch: tracking
tag: samsung-lt-v3.6-1

Let me know if there are issues after building linux-linaro tree. I
would be out of office for rest of the week and would be checking the
mails on coming Monday.


I've created ll-20121017.0 using the updated Samsung LT's tracking 
topic. The difference from the previous topic version is dropping the 
two commits:

   UBUNTU: dm-raid4-5: Fix compilation warning
   and
   CONFIG: ORIGEN: ANDROID: Disable HDMI/FIMC temporarily
I've restored the UBUNTU: dm-raid4-5: Fix compilation warning one, as 
it seems to be the correct fix.
So the resulting difference between ll-20121016.0 and ll-20121017.0 is 
just the android_origen_defconfig change:


diff --git a/arch/arm/configs/android_origen_defconfig 
b/arch/arm/configs/android_origen_defconfig

index d04cf03..869183e 100644
--- a/arch/arm/configs/android_origen_defconfig
+++ b/arch/arm/configs/android_origen_defconfig
@@ -125,6 +125,11 @@ CONFIG_VIDEO_S5K4ECGX_SLSI_4EC=y
 CONFIG_V4L_PLATFORM_DRIVERS=y
 CONFIG_V4L_USB_DRIVERS=y
 CONFIG_VIDEO_SAMSUNG_S5P_FIMC=y
+CONFIG_VIDEO_S5P_FIMC=y
+CONFIG_VIDEO_SAMSUNG_S5P_TV=y
+CONFIG_VIDEO_SAMSUNG_S5P_HDMI=y
+CONFIG_VIDEO_SAMSUNG_S5P_SDO=y
+CONFIG_VIDEO_SAMSUNG_S5P_MIXER=y
 CONFIG_V4L_MEM2MEM_DRIVERS=y
 CONFIG_VIDEO_SAMSUNG_S5P_G2D=y
 CONFIG_VIDEO_SAMSUNG_S5P_JPEG=y

Thanks,
Andrey


On 10/05/2012 05:25 PM, Jon Medhurst (Tixy) wrote:

On Fri, 2012-10-05 at 17:03 +0400, Andrey Konovalov wrote:

On 10/05/2012 12:12 PM, Jon Medhurst (Tixy) wrote:

On Thu, 2012-10-04 at 23:02 +0400, Andrey Konovalov wrote:

don't we need some kind of notification system where you
announce a plan to rebuild linux-linaro and give us a version of
llct to
base our LT branches off?


Yes, this makes sense.
Would the following plan be OK:
(N should normally be 0, but may be a small positive number)
* till the end of this week please use llct-20121004.0 as the base for
the linux-linaro (ll) topics
* October  9: ll rebuild based on llct-20121005.N
* October 16: ll rebuild based on llct-20121012.N
* October 23: ll rebuild based on llct-20121019.N, ll code freeze
(no
massive ll topics updates after that; bugfixes only)


Is this month following the normal release cycle? If so, isn't the
release day Oct 24th, and release candidates are built from the
previous
Thurday's code, i.e. Oct 18th. I.e. the freeze for the release
should be
Oct 16th not 23rd?


Oops.. Your are right. Why don't we have the Thursday, October 32
this year?

So the correct plan is the following:
* till the end of this week please use llct-20121004.0 as the base
for
the linux-linaro (ll) topics
* October  9: ll rebuild based on llct-20121005.N
* October 16: ll rebuild based on llct-20121012.N, ll code
freeze (no
  massive ll topics updates after that; bugfixes only)


Also, I assume we're not going to try to move to Linux 3.7 this month?


That's correct. We didn't have the kernel.org release based (vs -rc
based) ll release for quite a while. And the plan is to stick to v3.6
for 12.10 release unless someone needs to move to v3.7-rc* by all means
this cycle.
After October 19 the llct tree will move to v3.7-rc*, but the ll tree
will be frozen till the 12.10 is out.


That all sounds reasonable to me.









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

Re: Fix for HMP scheduler crash [ Re: [GIT PULL]: big LITTLE MP v10]

[Andrey Konovalov]

On 10/12/2012 05:41 PM, Viresh Kumar wrote:

On 12 October 2012 19:03, Jon Medhurst (Tixy) t...@linaro.org wrote:

On Fri, 2012-10-12 at 14:19 +0100, Jon Medhurst (Tixy) wrote:

The attached patch fixes the immediate problem by avoiding the empty
domain (which is probably a good thing anyway)


Oops, my last patch included some extra junk, the one attached to this
mail fixes this...


Tixy, do let me know if i should send another pull request with this
one applied.


I am going to apply the latest Tixy's patch to llct anyway. (so it will 
get into the ll too). Would be easier for me to get it as part of 
big.LITTLE-MP topic though. If it woun't be in big.LITTLE-MP, will apply 
to llct myself.
Today's linux-linaro trees are not RCs yet, so we should better try it 
now then right before the release. If there are issues there, there is 
one week (till Oct 18) to adjust the patch.


Thanks,
Andrey


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

Re: Call for 12.10 topics: reminder

[Andrey Konovalov]

Greeting,

llct-20121012.0 has been pushed to kernel/linux-linaro-tracking.git
Here is the pinned manifest:
http://git.linaro.org/gitweb?p=kernel/linux-linaro-manifest.git;a=commitdiff;h=0b9d2d998cd5dcda905c79d38ebe1547cfc2026f

 Minor change to the plan:
   * The current llct is *llct-20121006.0*
   * October  9: ll rebuild based on llct-20121006.0

ll-20121012.0 has been pushed to kernel/linux-linaro-tracking.git
The pinned manifest is:
http://git.linaro.org/gitweb?p=kernel/linux-linaro-manifest.git;a=commitdiff;h=0b60129d2f5f4d280708aada48d30fd86415ac9a
This time I tried not using llct as the base for ll-20121012.0 - just 
the LT's topics have been merged. Very similar to how the llt tree is 
being built.
So the llct version present in ll-20121012.0 depends on what llct tag 
the LT's topic are based (llct-20121006.0 in this case). This should 
give more control on the ll tree to the LTs, and should allow the LTs to 
test their topics with the same llct base which would be in the ll tree 
(earlier the LT's topics have been merged to a newer llct tree which 
these topics were not validated with by the LTs, ci testing only). But 
ll would slip a bit more behind the llct with this approach.


The next important date is:
  * October 16: ll rebuild based on llct-20121012.0, ll code freeze (no
massive ll topics updates after that; bugfixes only)

Thanks,
Andrey

On 10/12/2012 12:56 AM, Andrey Konovalov wrote:

Greetings,

If you have a new topic to add to linux-linaro-core-tracking tree in
12.10 release,
please make sure that it is submitted by October 12 evening
(*tomorrow*). The topics for llct should be based on v3.6 or (if there
is a need for that) on another llct topic.

If you have a new topic to add to linux-linaro tree in 12.10 release,
please make sure that it is submitted by October 16 evening. The ll
topics should be based
on llct, or (if there is a need for that) on v3.6 or another ll topic.
If an ll topic is based on an older llct version, it can be rebased to
the current one automatically, but the commit ids would be mangled (of
course). The current llct tree is tagged ll-20121010.0.

For the 12.10 the plan is to switch to config fragments for all the
supported boards. To my understanding the boards supported in v3.6 based
ll tree are:
* vexpress (ARM LT)
* origen (Samsung LT)
* snowball / u8500 (STE LT)
Please let me know if your board is missing from this list.

Please make sure that the config fragment for your
board is up-to-date here:
git://git.linaro.org/kernel/configs.git , config-boards-3.6 branch
(currently it has imx5.conf, omap4.conf (created by Platform team from
omap4plus_defconfig present in tilt-3.4), origen.conf, and
vexpress64.conf),
or in the linux-linaro topic for the board itself (this is the case for
vexpress).

Otherwise these instructions apply:
https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelTreeProcess

Thanks,
Andrey




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

Call for 12.10 topics: reminder

[Andrey Konovalov]

Greetings,

If you have a new topic to add to linux-linaro-core-tracking tree in 
12.10 release,
please make sure that it is submitted by October 12 evening 
(*tomorrow*). The topics for llct should be based on v3.6 or (if there 
is a need for that) on another llct topic.


If you have a new topic to add to linux-linaro tree in 12.10 release,
please make sure that it is submitted by October 16 evening. The ll 
topics should be based

on llct, or (if there is a need for that) on v3.6 or another ll topic.
If an ll topic is based on an older llct version, it can be rebased to
the current one automatically, but the commit ids would be mangled (of
course). The current llct tree is tagged ll-20121010.0.

For the 12.10 the plan is to switch to config fragments for all the
supported boards. To my understanding the boards supported in v3.6 based 
ll tree are:

* vexpress (ARM LT)
* origen (Samsung LT)
* snowball / u8500 (STE LT)
Please let me know if your board is missing from this list.

Please make sure that the config fragment for your
board is up-to-date here:
git://git.linaro.org/kernel/configs.git , config-boards-3.6 branch
(currently it has imx5.conf, omap4.conf (created by Platform team from 
omap4plus_defconfig present in tilt-3.4), origen.conf, and vexpress64.conf),
or in the linux-linaro topic for the board itself (this is the case for 
vexpress).


Otherwise these instructions apply:
https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelTreeProcess

Thanks,
Andrey


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

Re: Interesting(?) health failure

[Andrey Konovalov]

Hi Dave,

On 10/10/2012 11:35 AM, Dave Pigott wrote:

Hi all,

I found an interesting health failure today on origen07

http://validation.linaro.org/lava-server/scheduler/job/35016/log_file

When you look at the log, you see that the board starts off at the u-boot prompt. It then 
tries to do a reboot, which (obviously) fails. So naturally, it then does a 
hard reset, and this is where it does something very odd: It interrupts the boot and 
tries to boot the previously installed test image. I haven't yet looked at the dispatcher 
code to figure out why (that's my next job).

What then started alarm bells ringing was that I saw this:

1261680 bytes read
reading uInitrd

1532597 bytes read
reading board.dtb

** Unable to read board.dtb from mmc 0:5 **

So whatever the test image was, it was expecting a device tree blob, which I 
would have assumed would have to have been installed during 
deploy_linaro_image() being that if there is one it should just be part of the 
test boot deployment.

So I looked at the log from the previous job:

http://validation.linaro.org/lava-server/scheduler/job/34938/log_file#entry24

and sure enough, you'll see at that mark the same issue.

So there are two things:

1) There's some twisted logic in the dispatcher that's making it do odd things 
if it starts off in u-boot
2) Do we have an issue with dtbs not being handled properly by lava, or is it 
just that the hwpack was incomplete?


Regarding the 2).

No dtb in the hwpack.
I've created a very similar bug for another ci project:
https://bugs.launchpad.net/linaro-ci/+bug/1064686

Probably ubuntu packed kernels is the only project (view) in jenkins 
handling the dtb in the right way.


Please note, that the dtb must be properly described in the hwpack, so 
that it could be picked up by LAVA / l-m-c. This is out of scope of the 
bug 1064686.


Thanks,
Andrey

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

Questions about linux-linaro-tracking.git asked on IRC

[Andrey Konovalov]

(12:25:28 PM) hongbo_: amitk:  good afternoon. need I push u8500 thermal driver to 
linux-linaro?
  problems I found is that both the AmitDK's generic cpu cooling 
code and the generic thermal layer code
  are so old in this tree, if u8500 thermal driver has to be pushed 
into this tree, I have to edit it to
  an relevant old and useless version.
(12:27:16 PM) amitk: fabo: which build (and corresponding kernel) currently has 
the best enablement across various
  member HW. LLCT doesn't work on some hardware and is blocking 
michaelh|away from creating a PM-QA
  summary view for us
(12:27:25 PM) amitk: andrey_konovalov: ^


hongbo_ could try linux-linaro instead of linux-linaro-core-tracking.


(12:28:02 PM) amitk: hongbo_: the idea is never to go with older patchsets, but 
to refresh the depending patchset to
  a newer version.
(12:28:10 PM) hongbo_: amitk: my opinion is that both generic cooling and 
thermal framework should be update first,
  and then push u8500 codes later
(12:29:16 PM) hongbo_: amitk: who is responsible for refreshing generic cooling 
code? Amit DK has left.
(12:29:17 PM) amitk: hongbo_: correct, so can you ask andrey_konovalov to 
remove the old thermal fwk code (where do
  you find it, btw?) and supply him with a new version of the 
patchset (3.6+)
(12:29:25 PM) amitk: hongbo_: now you are :)
(12:31:12 PM) hongbo_: amitk: andrey_konovalov: I found the old thermal fwk 
here:
http://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git;a=tree;f=drivers/thermal;h=642a4a8ef2bc2834c6bab9cc1469c4459f330f4e;hb=13e6bbdf5e6e44b2168dbc876d8bba61d28f29c7


Wrong tree. This is *v3.4 based* linux-linaro-tracking (aka LLT) tree 
(git branch to be exact). It should not be used to develop new common 
code (this tree is created from LT's trees; there are no common topics 
in llt).


There is a short description of the linux-linaro-tracking.git branches here:
http://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git;a=summary
- and the link to
https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelTreeProcess


Thanks,
Andrey

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

Re: Planning topcs for inclusion in linux-linaro + call for 12.10 topics

[Andrey Konovalov]

Greetings,

On 10/06/2012 01:07 AM, Andrey Konovalov wrote:

Greetings,

Minor change to the plan:
  * The current llct is *llct-20121006.0*
  * October  9: ll rebuild based on llct-20121006.0


ll-20121010.0 has been pushed to linux-linaro-tracking.git.
The pinned manifest is:
http://git.linaro.org/gitweb?p=kernel/linux-linaro-manifest.git;a=blob;f=manifest.pin;h=84bb4172cbda8f5d603b1507f9f5299b5f60787b;hb=1c7ce72c6a6c9ee072987f6c8d964971fa8c3936

ll-20121010.0 is based on llct-20121009.0, which is llct-20121006.0 plus 
few fixes.

Here is the pinned manifest:
http://git.linaro.org/gitweb?p=kernel/linux-linaro-manifest.git;a=blob;f=manifest.pin;h=a6a0cb6c3415efc8ba2f020758f581846889123b;hb=linux-linaro-core-tracking


  * October 16: ll rebuild based on llct-20121012.N, ll code freeze (no
massive ll topics updates after that; bugfixes only)


If you have a new topic to add to 12.10, please make sure that it is 
submitted by October 12 (common topics to add to llct tree), or October 
16 (ll topics). The topics for llct should be based on v3.6 or (if there 
is a need for that) on another llct topic. The ll topics should be based 
on llct, or (if there is a need for that) on v3.6 or another ll topic. 
If an ll topic is based on an older llct version, it can be rebased to 
the current one automatically, but the commit ids would be mangled (of 
course).


For the 12.10 the plan is to switch to config fragments for all the 
supported boards. Please make sure that the config fragment for your 
board is up-to-date here:

git://git.linaro.org/kernel/configs.git , config-boards-3.6 branch

Otherwise these instructions apply: 
https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelTreeProcess


Thanks,
Andrey


On 10/05/2012 05:25 PM, Jon Medhurst (Tixy) wrote:

On Fri, 2012-10-05 at 17:03 +0400, Andrey Konovalov wrote:

On 10/05/2012 12:12 PM, Jon Medhurst (Tixy) wrote:

On Thu, 2012-10-04 at 23:02 +0400, Andrey Konovalov wrote:

don't we need some kind of notification system where you
announce a plan to rebuild linux-linaro and give us a version of
llct to
base our LT branches off?


Yes, this makes sense.
Would the following plan be OK:
(N should normally be 0, but may be a small positive number)
* till the end of this week please use llct-20121004.0 as the base for
the linux-linaro (ll) topics
* October  9: ll rebuild based on llct-20121005.N
* October 16: ll rebuild based on llct-20121012.N
* October 23: ll rebuild based on llct-20121019.N, ll code freeze
(no
massive ll topics updates after that; bugfixes only)


Is this month following the normal release cycle? If so, isn't the
release day Oct 24th, and release candidates are built from the
previous
Thurday's code, i.e. Oct 18th. I.e. the freeze for the release
should be
Oct 16th not 23rd?


Oops.. Your are right. Why don't we have the Thursday, October 32
this year?

So the correct plan is the following:
   * till the end of this week please use llct-20121004.0 as the base
for
   the linux-linaro (ll) topics
   * October  9: ll rebuild based on llct-20121005.N
   * October 16: ll rebuild based on llct-20121012.N, ll code
freeze (no
 massive ll topics updates after that; bugfixes only)


Also, I assume we're not going to try to move to Linux 3.7 this month?


That's correct. We didn't have the kernel.org release based (vs -rc
based) ll release for quite a while. And the plan is to stick to v3.6
for 12.10 release unless someone needs to move to v3.7-rc* by all means
this cycle.
After October 19 the llct tree will move to v3.7-rc*, but the ll tree
will be frozen till the 12.10 is out.


That all sounds reasonable to me.






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

Re: Planning topcs for inclusion in linux-linaro

[Andrey Konovalov]

Hi Tushar,

On 10/08/2012 08:04 AM, Tushar Behera wrote:

On 10/06/2012 02:37 AM, Andrey Konovalov wrote:

Greetings,

Minor change to the plan:
  * The current llct is *llct-20121006.0*
  * October  9: ll rebuild based on llct-20121006.0
  * October 16: ll rebuild based on llct-20121012.N, ll code freeze (no
massive ll topics updates after that; bugfixes only)



I am not in office during this week, so won't be able to update the
kernel. Current Samsung LT kernel is based on llct-20121004.0. I will be
updating this to llct-20121012.N next.


This shouldn't be a problem.
Thanks for the update!

Andrey


On 10/05/2012 05:25 PM, Jon Medhurst (Tixy) wrote:

On Fri, 2012-10-05 at 17:03 +0400, Andrey Konovalov wrote:

On 10/05/2012 12:12 PM, Jon Medhurst (Tixy) wrote:

On Thu, 2012-10-04 at 23:02 +0400, Andrey Konovalov wrote:

don't we need some kind of notification system where you
announce a plan to rebuild linux-linaro and give us a version of
llct to
base our LT branches off?


Yes, this makes sense.
Would the following plan be OK:
(N should normally be 0, but may be a small positive number)
* till the end of this week please use llct-20121004.0 as the base for
the linux-linaro (ll) topics
* October  9: ll rebuild based on llct-20121005.N
* October 16: ll rebuild based on llct-20121012.N
* October 23: ll rebuild based on llct-20121019.N, ll code freeze
(no
massive ll topics updates after that; bugfixes only)


Is this month following the normal release cycle? If so, isn't the
release day Oct 24th, and release candidates are built from the
previous
Thurday's code, i.e. Oct 18th. I.e. the freeze for the release
should be
Oct 16th not 23rd?


Oops.. Your are right. Why don't we have the Thursday, October 32
this year?

So the correct plan is the following:
* till the end of this week please use llct-20121004.0 as the base
for
the linux-linaro (ll) topics
* October  9: ll rebuild based on llct-20121005.N
* October 16: ll rebuild based on llct-20121012.N, ll code
freeze (no
  massive ll topics updates after that; bugfixes only)


Also, I assume we're not going to try to move to Linux 3.7 this month?


That's correct. We didn't have the kernel.org release based (vs -rc
based) ll release for quite a while. And the plan is to stick to v3.6
for 12.10 release unless someone needs to move to v3.7-rc* by all means
this cycle.
After October 19 the llct tree will move to v3.7-rc*, but the ll tree
will be frozen till the 12.10 is out.


That all sounds reasonable to me.









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

Re: Planning topcs for inclusion in linux-linaro

[Andrey Konovalov]

On 10/05/2012 12:12 PM, Jon Medhurst (Tixy) wrote:

On Thu, 2012-10-04 at 23:02 +0400, Andrey Konovalov wrote:

don't we need some kind of notification system where you
announce a plan to rebuild linux-linaro and give us a version of llct to
base our LT branches off?


Yes, this makes sense.
Would the following plan be OK:
(N should normally be 0, but may be a small positive number)
* till the end of this week please use llct-20121004.0 as the base for
the linux-linaro (ll) topics
* October  9: ll rebuild based on llct-20121005.N
* October 16: ll rebuild based on llct-20121012.N
* October 23: ll rebuild based on llct-20121019.N, ll code freeze (no
massive ll topics updates after that; bugfixes only)


Is this month following the normal release cycle? If so, isn't the
release day Oct 24th, and release candidates are built from the previous
Thurday's code, i.e. Oct 18th. I.e. the freeze for the release should be
Oct 16th not 23rd?


Oops.. Your are right. Why don't we have the Thursday, October 32 this year?

So the correct plan is the following:
 * till the end of this week please use llct-20121004.0 as the base for
 the linux-linaro (ll) topics
 * October  9: ll rebuild based on llct-20121005.N
 * October 16: ll rebuild based on llct-20121012.N, ll code freeze (no
   massive ll topics updates after that; bugfixes only)


Also, I assume we're not going to try to move to Linux 3.7 this month?


That's correct. We didn't have the kernel.org release based (vs -rc 
based) ll release for quite a while. And the plan is to stick to v3.6 
for 12.10 release unless someone needs to move to v3.7-rc* by all means 
this cycle.
After October 19 the llct tree will move to v3.7-rc*, but the ll tree 
will be frozen till the 12.10 is out.


Thanks,
Andrey


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

Re: Planning topcs for inclusion in linux-linaro

[Andrey Konovalov]

Greetings,

Minor change to the plan:
 * The current llct is *llct-20121006.0*
 * October  9: ll rebuild based on llct-20121006.0
 * October 16: ll rebuild based on llct-20121012.N, ll code freeze (no
   massive ll topics updates after that; bugfixes only)

Thanks,
Andrey

On 10/05/2012 05:25 PM, Jon Medhurst (Tixy) wrote:

On Fri, 2012-10-05 at 17:03 +0400, Andrey Konovalov wrote:

On 10/05/2012 12:12 PM, Jon Medhurst (Tixy) wrote:

On Thu, 2012-10-04 at 23:02 +0400, Andrey Konovalov wrote:

don't we need some kind of notification system where you
announce a plan to rebuild linux-linaro and give us a version of llct to
base our LT branches off?


Yes, this makes sense.
Would the following plan be OK:
(N should normally be 0, but may be a small positive number)
* till the end of this week please use llct-20121004.0 as the base for
the linux-linaro (ll) topics
* October  9: ll rebuild based on llct-20121005.N
* October 16: ll rebuild based on llct-20121012.N
* October 23: ll rebuild based on llct-20121019.N, ll code freeze (no
massive ll topics updates after that; bugfixes only)


Is this month following the normal release cycle? If so, isn't the
release day Oct 24th, and release candidates are built from the previous
Thurday's code, i.e. Oct 18th. I.e. the freeze for the release should be
Oct 16th not 23rd?


Oops.. Your are right. Why don't we have the Thursday, October 32 this year?

So the correct plan is the following:
   * till the end of this week please use llct-20121004.0 as the base for
   the linux-linaro (ll) topics
   * October  9: ll rebuild based on llct-20121005.N
   * October 16: ll rebuild based on llct-20121012.N, ll code freeze (no
 massive ll topics updates after that; bugfixes only)


Also, I assume we're not going to try to move to Linux 3.7 this month?


That's correct. We didn't have the kernel.org release based (vs -rc
based) ll release for quite a while. And the plan is to stick to v3.6
for 12.10 release unless someone needs to move to v3.7-rc* by all means
this cycle.
After October 19 the llct tree will move to v3.7-rc*, but the ll tree
will be frozen till the 12.10 is out.


That all sounds reasonable to me.




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

Re: Planning topcs for inclusion in linux-linaro

[Andrey Konovalov]

Hi Tixy

On 10/04/2012 12:55 PM, Jon Medhurst (Tixy) wrote:

Hi Andrey

Now I'm providing a single LT topic based off linux-linaro-core-tracking
(llct), and you said that you need everyone to base off the same version
of llct,


Yes, this is currently the case.


don't we need some kind of notification system where you
announce a plan to rebuild linux-linaro and give us a version of llct to
base our LT branches off?


Yes, this makes sense.
Would the following plan be OK:
(N should normally be 0, but may be a small positive number)
* till the end of this week please use llct-20121004.0 as the base for 
the linux-linaro (ll) topics

* October  9: ll rebuild based on llct-20121005.N
* October 16: ll rebuild based on llct-20121012.N
* October 23: ll rebuild based on llct-20121019.N, ll code freeze (no 
massive ll topics updates after that; bugfixes only)


ll and llct could be updated between these dates as well, but without 
changes in the normal ll topics - just my last-time-fixes pseudo 
topics could change.


Also I believe that the ll topics could actually based on *any* recent 
enough llct version. But I want to double check the pro's and contra's 
before making this statement official.


What concerns me now are the ll topics based on ll itself (just one real 
topic atm: ste-lt-next). Would it be a problem for any of the topic 
maintainers if I request all the ll topics to be based on llct, on 
another ll topic (I must be told about that), even on vM.N-rcX 
kernel.org tag if this is good for the topic maintainer, but not on ll 
itself?


Thanks,
Andrey

PS
The multiplatform topic is removed from llct starting from llct-20120924.0


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

Re: [GIT PULL]: big LITTLE MP v9

[Andrey Konovalov]

Hi Viresh,

On 10/03/2012 03:16 PM, Viresh Kumar wrote:

Hi Andrey,

Please PULL b.L MP V9 branch from my tree.


Merged into linux-linaro-core-tracking tree, the tag is llct-20121004.0.

Thanks,
Andrey


Updates:
---
- Based on v3.6
- Stats:
- Total Patches: 63
- New Patches: 0
- Merged Patches: 3
- f319da0 sched: Fix load avg vs cpu-hotplug
- 641f145 hwmon: (coretemp) Use get_online_cpus to avoid races
involving CPU hotplug
- 1ec3ddf hwmon: (via-cputemp) Use get_online_cpus to avoid races
involving CPU hotplug
- Dropped Patches: 0

NOTE: Below pull request is generated against v3.6 instead of linux-linaro.

8


The following changes since commit a0d271cbfed1dd50278c6b06bead3d00ba0a88f9:

   Linux 3.6 (2012-09-30 16:47:46 -0700)

are available in the git repository at:

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

for you to fetch changes up to 619245dc532b1d1b59cd414ae4d87e9b3ae42c65:

   Merge branches 'per-cpu-thread-hotplug-v3-fixed',
'task-placement-v2', 'cpu-hotplug-get_online_cpus-v1',
'arm-asymmetric-support-v3-v3.6-rc1', 'rcu-hotplug-v1',
'arm-multi_pmu_v1', 'scheduler-misc-v1' and 'config-fragments' into
big-LITTLE-MP-v9 (2012-10-03 16:29:42 +0530)



Axel Lin (1):
   ARM: ux500: Fix build error due to missing include of asm/pmu.h
in cpu-db8500.c

Ben Segall (1):
   sched: maintain per-rq runnable averages

Jon Hunter (1):
   ARM: PMU: Add runtime PM Support

Jon Medhurst (5):
   configs: Initial core configs
   configs: Make CONFIG_MODULES part of linaro-base
   configs: Replace CONFIG_PERF_COUNTERS with CONFIG_PERF_EVENTS
   configs: android: Enable FB_EARLYSUSPEND
   configs: android: Enable CONFIG_INPUT_UINPUT to get aidb working

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

Morten Rasmussen (10):
   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

Paul E. McKenney (4):
   rcu: Use smp_hotplug_thread facility for RCUs per-CPU kthread
   hotplug: Fix UP bug in smpboot hotplug code
   rcu: Remove _rcu_barrier() dependency on __stop_machine()
   rcu: Disallow callback registry on offline CPUs

Paul Turner (15):
   sched: track the runnable average on a per-task entitiy basis
   sched: aggregate load contributed by task entities on parenting cfs_rq
   sched: maintain the load contribution of blocked entities
   sched: add an rq migration call-back to sched_class
   sched: account for blocked load waking back up
   sched: aggregate total task_group load
   sched: compute load contribution by a group entity
   sched: normalize tg load contributions against runnable time
   sched: maintain runnable averages across throttled periods
   sched: replace update_shares weight distribution with per-entity
computation
   sched: refactor update_shares_cpu() - update_blocked_avgs()
   sched: update_cfs_shares at period edge
   sched: make __update_entity_runnable_avg() fast
   sched: implement usage tracking
   sched: introduce temporary FAIR_GROUP_SCHED dependency for load-tracking

Ricardo Salveti de Araujo (7):
   configs: moving previous ubuntu.conf as ubuntu-minimal and
creating a full ubuntu one
   configs: ubuntu: be compatible with the enforce script
   configs: ubuntu: disabling CODA_FS, seems to be broken atm
   configs: ubuntu: disabling CGROUPS as default
   configs: ubuntu: updating configs for 3.5
   configs: ubuntu: disabling CONFIG_MTD_NAND_NANDSIM=m, breaking build
   config: ubuntu: ATH6KL should be platform dependent

Silas Boyd-Wickizer (4):
   Use get_online_cpus to avoid races involving CPU hotplug
   Use get_online_cpus to avoid races involving CPU hotplug
   Use get_online_cpus to avoid races involving CPU hotplug
   Use get_online_cpus to avoid races involving CPU hotplug

Sudeep KarkadaNagesha (9):
   ARM: pmu: remove arm_pmu_type enumeration
   ARM: perf: move irq registration into pmu implementation
   ARM: perf: allocation of cpu_pmu at init time
   ARM: perf: change multiple arm_pmu function parameters to struct
perf_event
   ARM: perf: rework on armv7_pmnc_counter_valid
   ARM: perf: define per-cpu arm_pmu 

multiplatform topic will be removed from llct starting from 12.10 (was Re: Call for linux-linaro / linux-linaro-core-tracking topic updates)

[Andrey Konovalov]

Greetings,

On 09/14/2012 01:12 PM, Arnd Bergmann wrote:

I think we need to discuss whether the multiplatform branch should still
be included in the linux-linaro-core-tracking tree. At the ARM mini summit
in San Diego, we discussed in length about how we want to get to actual
multiplatform kernels, and decided *not* to use my testing/mach-headers
branch.
We could keep using it for a little longer, but I think eventually
we will have do thing differently as upstream moves on, so we might decide
to remove it right away.


The multiplatform topic is still present in 12.09, but it will be 
dropped next cycle. Current linux-linaro-core-tracking tree (the 
llct-20120924.0 tag) has it removed already.


Thanks,
Andrey


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

Re: [GIT PULL]: big LITTLE MP v8

[Andrey Konovalov]

Hi Viresh,

On 09/17/2012 01:49 PM, Viresh Kumar wrote:

Hi Andrey,

This is PULL request for big LITTLE MP v8 branch:


Merged into linux-linaro-core-tracking, the tag is llct-20120917.0.

Thanks,
Andrey


Major updates are:
 - Based on v3.6-rc5
 - new branch from Paulm: rcu-hotplug-v1, vincent:
scheduler-misc-v1 and sudeepk arm-multi_pmu_v1
 - new version of patches from Morten: task-placement-v2
 - config fragment updated for fast  slow cpu

Compile tested only.

-x-x---


The following changes since commit 55d512e245bc7699a8800e23df1a24195dd08217:

   Linux 3.6-rc5 (2012-09-08 16:43:45 -0700)

are available in the git repository at:

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

for you to fetch changes up to eb07c27e2987ab3c16cedee1367694988efe3ff4:

   Merge branches 'per-cpu-thread-hotplug-v3-fixed',
'task-placement-v2', 'cpu-hotplug-get_online_cpus-v1',
'arm-asymmetric-support-v3-v3.6-rc1', 'rcu-hotplug-v1',
'arm-multi_pmu_v1', 'scheduler-misc-v1' and 'config-fragments' into
big-LITTLE-MP-v8 (2012-09-17 09:26:07 +0530)



Axel Lin (1):
   ARM: ux500: Fix build error due to missing include of asm/pmu.h
in cpu-db8500.c

Ben Segall (1):
   sched: maintain per-rq runnable averages

Jon Hunter (1):
   ARM: PMU: Add runtime PM Support

Jon Medhurst (6):
   configs: Initial core configs
   configs: Make CONFIG_MODULES part of linaro-base
   Merge branch 'config-core-3.4' into config-core-tracking
   configs: Replace CONFIG_PERF_COUNTERS with CONFIG_PERF_EVENTS
   configs: android: Enable FB_EARLYSUSPEND
   configs: android: Enable CONFIG_INPUT_UINPUT to get aidb working

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

Morten Rasmussen (10):
   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

Paul E. McKenney (4):
   rcu: Use smp_hotplug_thread facility for RCUs per-CPU kthread
   hotplug: Fix UP bug in smpboot hotplug code
   rcu: Remove _rcu_barrier() dependency on __stop_machine()
   rcu: Disallow callback registry on offline CPUs

Paul Turner (15):
   sched: track the runnable average on a per-task entitiy basis
   sched: aggregate load contributed by task entities on parenting cfs_rq
   sched: maintain the load contribution of blocked entities
   sched: add an rq migration call-back to sched_class
   sched: account for blocked load waking back up
   sched: aggregate total task_group load
   sched: compute load contribution by a group entity
   sched: normalize tg load contributions against runnable time
   sched: maintain runnable averages across throttled periods
   sched: replace update_shares weight distribution with per-entity
computation
   sched: refactor update_shares_cpu() - update_blocked_avgs()
   sched: update_cfs_shares at period edge
   sched: make __update_entity_runnable_avg() fast
   sched: implement usage tracking
   sched: introduce temporary FAIR_GROUP_SCHED dependency for load-tracking

Peter Zijlstra (1):
   sched: Fix load avg vs cpu-hotplug

Ricardo Salveti de Araujo (8):
   configs: moving previous ubuntu.conf as ubuntu-minimal and
creating a full ubuntu one
   configs: ubuntu: be compatible with the enforce script
   configs: ubuntu: disabling CODA_FS, seems to be broken atm
   configs: ubuntu: disabling CGROUPS as default
   Merge branch 'config-core-3.4' into config-core-tracking
   configs: ubuntu: updating configs for 3.5
   configs: ubuntu: disabling CONFIG_MTD_NAND_NANDSIM=m, breaking build
   config: ubuntu: ATH6KL should be platform dependent

Silas Boyd-Wickizer (6):
   Use get_online_cpus to avoid races involving CPU hotplug
   Use get_online_cpus to avoid races involving CPU hotplug
   Use get_online_cpus to avoid races involving CPU hotplug
   Use get_online_cpus to avoid races involving CPU hotplug
   Use get_online_cpus to avoid races involving CPU hotplug
   Use get_online_cpus to avoid races involving CPU hotplug

Sudeep KarkadaNagesha (9):
   ARM: pmu: remove arm_pmu_type enumeration
   ARM: perf: move irq registration into pmu implementation
   ARM: perf: allocation of cpu_pmu at init time
   ARM: perf: 

Re: Call for linux-linaro / linux-linaro-core-tracking topic updates

[Andrey Konovalov]

On 09/14/2012 01:12 PM, Arnd Bergmann wrote:

On Friday 14 September 2012, Sachin Kamat wrote:

Hi Andrey,

On 12 September 2012 17:56, Andrey Konovalov
andrey.konova...@linaro.org wrote:

Greetings,

The linux-linaro-core-tracking (llct) tree has been moved to v3.6-rc5 base.
All the topics existed in the 12.08 version of llct have been carried over
into the updated tree with few easy to resolve conflicts. The only one which
needs attention is due to commit ASoC: Samsung: Fix build error [1]. In
fact I had to revert it because it doesn't work with the multiplatform topic
(the latter renames all the arch/arm/mach-name/include/mach dirs to
arch/arm/mach-name/include/mach-name). Sachin or Tushar, could you take
a look please?


CC'd Arnd.

mach/dma.h present in some Samsung driver files esp. related to
audio haven't been converted to mach-name/dma.h form mainly
because most Samsung mach-* directories have a dma.h file and those
need to be consolidated first. Kukjin's team is working on cleaning
this up. See the below link

http://permalink.gmane.org/gmane.linux.kernel.samsung-soc/12049

With the fix patch reverted, you will get build errors if you enable
pcm. However if you do not intend to enable pcm you may go ahead with
it. Alternatively, you may replace mach/dma.h with
mach-exynos/dma.h for your purpose (stopgap solution).


I think we need to discuss whether the multiplatform branch should still
be included in the linux-linaro-core-tracking tree. At the ARM mini summit
in San Diego, we discussed in length about how we want to get to actual
multiplatform kernels, and decided *not* to use my testing/mach-headers
branch.
We could keep using it for a little longer, but I think eventually
we will have do thing differently as upstream moves on, so we might decide
to remove it right away.


Guess I'll make one or couple more linux-linaro-core-tracking tree 
updates using the replace mach/dma.h with mach-exynos/dma.h 
workaround just in case, and then drop the multiplatform from the 
following linux-linaro-core-tracking tree updates starting from Tuesday, 
Sept 18. (So that we could use any of the two variants for the 12.09) 
Does anyone mind?


Thanks,
Andrey


Arnd




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

Re: llct stable trees

[Andrey Konovalov]

On 09/09/2012 11:40 AM, Ricardo Salveti wrote:

On Wed, Sep 5, 2012 at 7:55 AM, Andy Green andy.gr...@linaro.org wrote:

On 09/05/12 17:19, the mail apparently from Andy Green included:


On 09/04/12 12:13, the mail apparently from Ricardo Salveti included:

Hi -


1) Can we have linux stable point release content in tilt-3.4?
Rather than
my doing it, isn't it better to add it to llc-3.4 and merge it on the lt
history tree periodically?  That way every lt can get them from one
place.



I don't see why merging the stable release contents would be an issue.
We could keep updating the tree based on stable-only releases, as long
as we still have at least one Landing Team interested on consuming it.

This would be another job that would probably be automated by Andrey's
scripts.



Right it should usually be simple, although don't forget there is quite
a lot of avant garde content in llct, such as Androidization.  Just
today I saw Xavier at TI find that merging of stable had a patch
conflicting with llct Androidization content.



So, it turns out that is a good example.

I researched the conflict and found a thread from RMK rejecting the patch
96714b5dfe283cd8ab13aac1f9ccb565064af152 that seems to have come in by
Androidization series via llct.

http://lists.infradead.org/pipermail/linux-arm-kernel/2010-May/014116.html

We decided to take the kernel.org stable version of the patch
6019ae78aa65afe273da8c0dfeed8e89fb5edf8f which removes some locking evil in
the Androidization version, which RMK noted opened up a horrible race.

Xavier then found a ghastly bug that had previously been impossible to track
down disappeared.

So we now know that 96714b5dfe283cd8ab13aac1f9ccb565064af152 we had been
happily pushing out on everyone in llct-3.4 is a terrible idea, not just for
TILT but any kernel that has it in will suffer from very hard to reproduce
mm instability under stress, and needs reverting in favour of the version
that went in kernel.org stable.

But now we know about that flaw in llct-3.4 should we not do something about
it?


Yeah, at least for stable related changes I believe it'd make a lot of
sense to push those to llct-3.4.

Andrey, let's also coordinate the stable updates for llct-3.4 during
this cycle, and then review the issues, if we get any, after the first
merge/update.

Cheers,


I've created the linux-linaro-core-3.4 branch:
http://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git;a=shortlog;h=refs/heads/linux-linaro-core-3.4
(and the manifest: 
http://git.linaro.org/gitweb?p=kernel/linux-linaro-manifest.git;a=shortlog;h=refs/heads/linux-linaro-core-3.4)


At the moment this is just something to start from: the old known 
llct_3.4 with the updated Gator. The rest should follow soon.


Thanks,
Andrey

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

Call for linux-linaro / linux-linaro-core-tracking topic updates

[Andrey Konovalov]

Greetings,

The linux-linaro-core-tracking (llct) tree has been moved to v3.6-rc5 base.
All the topics existed in the 12.08 version of llct have been carried 
over into the updated tree with few easy to resolve conflicts. The only 
one which needs attention is due to commit ASoC: Samsung: Fix build 
error [1]. In fact I had to revert it because it doesn't work with the 
multiplatform topic (the latter renames all the 
arch/arm/mach-name/include/mach dirs to 
arch/arm/mach-name/include/mach-name). Sachin or Tushar, could you 
take a look please?
Also the big-LITTLE-MP topic has been updated to v3.6-rc5 based 
big-LITTLE-MP-v8.

The current list of the llct topics can be found in [2].

12.09 will most probably be v3.6-rc6 based. But for the moment I've 
tried rebasing the linux-linaro (ll) tree to the current v3.6-rc5 based 
llct, and encountered no merge issues. The current list of the ll topics 
can be found in [3]. The plan is to have single topic from the ARM LT 
(like the Samsung LT code is represented now) this month vs several 
one-per-feature topics.


In 12.08 the linux-linaro-tracking (llt) tree was v3.4 based, and had 
recent code from TI LT plus the older code (no changes for couple 
months) from ARM and Samsung LTs. Any changes here in 12.09? (Are we on 
v3.4 still, are there other LTs to add to this tree?).
And yes, this month llc-3.4 core stable tree will be introduced (first 
of all, to get the Gator updates for v3.4, and some critical fixes), and 
llt will start using it as a base. No more details atm,

should have something in git by the end of this week.

Please let me know if there are any updates to the existing topics, or 
new topics missing. And if there are obsoleted topics. The linux-linaro 
and linux-linaro-tracking trees will be frozen (only bug fixes would be 
accepted afterwards, no new additions) by the end of September 18.


Thanks,
Andrey

[1] 
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=61f5d61ef94d7082d96494e2a6dd79de2b4437d2


[2] 
http://git.linaro.org/gitweb?p=kernel/linux-linaro-manifest.git;a=blob;f=manifest;hb=linux-linaro-core-tracking


[3] 
http://git.linaro.org/gitweb?p=kernel/linux-linaro-manifest.git;a=blob;f=manifest;hb=linux-linaro


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

Re: [PATCH 0/2] Android fixes w.r.t. 3.6 kernel

[Andrey Konovalov]

On 09/11/2012 10:19 AM, John Stultz wrote:

On 09/10/2012 10:22 PM, Tushar Behera wrote:

Ping !!!

On 08/31/2012 09:57 AM, Tushar Behera wrote:

Required for android-3.6 tree.

Tushar Behera (2):
   netfilter: xt_quota2: Move away from NLMSG_PUT()
   netfilter: xt_quota2: Update parameter list in netlink_kernel_create

  net/netfilter/xt_quota2.c |   25 -
  1 files changed, 16 insertions(+), 9 deletions(-)


Without these patches, build of LT kernel based on llct(v3.6-rc5) fails
with following error message.


Thanks for the reminder, the patches landed in my mailbox during Linux
Plumbers, and got buried under a number of other items.
So my apologies. I've applied them and pushed them out to the
linaro-android-3.6-jstultz-rebase branch.


Merged into the linux-linaro-core-tracking branch, the llct-20120911.0 tag.

Thanks,
Andrey


thanks
-john


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



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

Re: New fast models device-tree topic for linux-linaro

[Andrey Konovalov]

On 08/15/2012 08:47 PM, Jon Medhurst (Tixy) wrote:

Hi Andrey

Can you include a new topic to linux-linaro which contains device-tree
files for ARM's fast models? This branch is tracking-armlt-rtsm [1] in
the ARM LT working tree.


Done, thanks! The git tag is ll-20120815.0.

*Tushar*,

I've commented out the Samsung LT's topics this time, as they seem to be 
v3.5-rc2 based. Do you have a plan to move them to v3.6-rc*?


Thanks,
Andrey


Thanks

For those interested...

These device-trees enable the the current Linaro vexpress kernel to boot
on fast-models when used with the boot-wrapper at [2], this includes
having a working display. However, on the big.LITLE models the A7 cores
don't start, giving Failed to boot -38.




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

Re: [GIT PULL] bit-LITTLE-MP-v5

[Andrey Konovalov]

On 08/14/2012 08:34 PM, Jon Medhurst (Tixy) wrote:

On Tue, 2012-08-14 at 17:28 +0530, Viresh Kumar wrote:

Hi Andrey,


Below is pull request for v5 of MP work, following are the main
changes:
1. Removed from this merge:
 - cpuidle-next-v4 - Already in rc1
 - wq-hotplug-v1 - Already in rc1
 - arm-asymmetric-support-v3 - Only one patch not mailined others
are dropped
2. Rebased over v3.6-rc1
3. Extra patch from Morten/Tixy


Thanks


NOTE: Compile tested only


I did a test merge of this new MP branch with our vexpress topics and
linaro-android-3.6-jstultz-rebase, and booted the resulting kernel on
TC2 with an Android Jelly Bean user-space. All seems to work and behave
as with the previous combination of Linux 3.5 + big-LITTLE-MP-v4


Great!
big-LITTLE-MP-v5 (together with the updated multiplatform topic) has 
been merged into linux-linaro-core-tracking tree. The tag is 
llct-20120814.0.


Thanks,
Andrey


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

Re: New Gator version (5.11) ready for Linaro kernels

[Andrey Konovalov]

On 08/13/2012 04:28 PM, Jon Medhurst (Tixy) wrote:

Hello All

ARM have released a new version of Developer Studio 5 (DS-5) and we now
have a new version of the Gator component [1] to go with this which
needs updating in all Linaro kernel trees that will be part of the 12.08
release.


Thanks Tixy!


For those people maintaining kernel trees here is what this means...

- If your kernels are including the linux-linaro-core-tracking [2]
branch then you will get the new Gator version from this when it is
updated over the next couple of days. You don't need to do anything
except to make sure you are up to date with this branch before the 12.08
release.


This new version of Gator has been included into the just published 
linux-linaro-core-tracking update (the tag is llct-20120813.0). But this 
is also the first v3.6-rc* based version of llct, so it misses a lot of 
topics included into 12.07 release (as those topics have not been 
updated for 3.6 yet), and may have problems common to early -rc's (like 
ethernet not working on Panda, if I got it correct).


Thanks,
Andrey


- For Ubuntu kernels not including linux-linaro-core-tracking (and not
being released from the common linux-linaro branch) then you should
replace your existing Gator topic branch (or add one if it is missing).
This new topic branch can be created by pulling from the ARM Landing
Team's tree [3], we have three topic branches available for the last
three kernel versions...

   tracking-armlt-gator (3.6-rc1)
   3.5-armlt-gator-5.10
   3.4-armlt-gator-5.10

The code in these branches is identical, they are just rebased onto
different Linux versions to make pulling easier.

- For Android kernels, if your kernel already includes the Gator topic,
then this should be updated as above. If it does not have the Gator
topic then chance are it is being included as a separate component in
the manifest file; in which case, there is nothing further which needs
doing as the git repo used for this has already been updated [4].

If anyone has any questions or if anything is unclear, please do
hesitate to contact me.

Note, for those people who have applied Mali driver patches to support
profiling by Gator: you don't need to modify those Mali patches, just
take the new version of Gator, this will still work OK.

Cheers




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

Call for topic updates and new topics for linux-linaro-core-tracking tree

[Andrey Konovalov]

Greetings,

The linux-linaro-core-tracking tree (llct, see 
http://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git;a=summary for 
some more details) is planned to be moved to v3.6-rc1 (or v3.6-rc2 if it 
is out) early next week.


There will be more updates to llct as long as new -rc's are out.
And this llct tree will be the base for the 12.08 linux-linaro release.

Most of the current llct topics need updating for that:

* topic svenkatr/ufs-for-linux-linaro :
  just 1 conflict, but there are newer commits by the topic owner in
  the kernel.org tree. Please update the topic
* topic amitdanielk/thermal_exynos4_imx6_work :
  3 conflicts
* topic android_jstultz/linaro-android-3.5-jstultz-rebase
  11 conflicts. This has been already discussed with the topic owner.
  We will both work on moving the current topic to v3.6.
* topic arm_soc/testing/multiplatform
  198 conflicts.
  Arnd, I don't see the multiplatform code in the current kernel.org
  tree. Could you please update me on the status of this effort?
  And if we want to keep the multiplatform topic in the llct tree,
  your help (updated or new branch for this topic) is needed.
* topic ll_quantal/linaro-ubuntu-sauce
  9 conflicts
* topic perf antipov/linaro
  2 conflicts. Looks like they are due to changes in the upstream.
  Dmitry, could you please rebase your topic branch over to
  v3.6-something (v3.6-rc1, current kernel.org tree, etc)?
  Just overwrite the existing topic branch (the earlier versions are
  saved in linux-linaro-tracking.git each time they are used for the
  llct updates, and could be reused later if needed).
* topic big-LITTLE-MP-v4 b_L_mp/big-LITTLE-MP-v4
  3 conflicts

Let me know if there are obsoleted topics.

And new topics are welcomed as usual :)
Please note, that llct is for generic topics, not the board specific 
ones. I'll get to linux-linaro tree (which has board specific topics) 
right after llct is moved to v3.6-rc*.


Thanks,
Andrey

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

Re: [GIT PULL] bit-LITTLE-MP-v4

[Andrey Konovalov]

On 07/26/2012 01:44 PM, Viresh Kumar wrote:

On 25 July 2012 18:14, Paul E. McKenney paul...@linux.vnet.ibm.com
mailto:paul...@linux.vnet.ibm.com wrote:

You are missing some fixes, please see below.  I can also email you the
updated patches, if that would be easier than pulling them from -rcu.


Hi Andrey,

So sorry, but you need to pull v4 again as there were few updated
patches from paul. :(
Can you please pull this again?


Sure, no problem.
The updated big-LITTLE-MP-v4 topic has been merged into 
linux-linaro-core-tracking tree, the tag is llct-20120726.0


Thanks,
Andrey


I have created another branch for new fixes from
Paul, per-cpu-thread-hotplug-v3-fixed,
as it wasn't a v4 actually.

I have updated the same merge branch big-LITTLE-MP-v4 that you can pull in.

@Paul: I have applied all three changes you suggested, please see if
everything is fine now.

--
viresh



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