Hi,
I had a really good meeting with Paul Larson this week to discuss
the automated test framework that Linaro is developing and wanted
to follow up with the team on brainstorming around what we want
to be running on a regular basis to test the kernels. The current testing
includes:
"x11perf",
"gtkperf",
"glmemperf",
"posixtestsuite",
"gmpbench",
"pybench",
"stream"
I think the obvious missing one is LTP which Shawn is working on
getting up and running on ARM for the 11.11 cycle. Arnd's flash
testing tool might also be a good fit, but I am not sure of the side
effects it might have to the underlying device after extended use.
I also think that adding board specific tests such as "run i2cdetect
and validate that we see all the devices we expect" is something
useful to do in the long-term to validate that driver changes, DT
updates, etc do not break support for a given board.
I'm interested in hearing ideas that others have on what kinds of
tests we should be running.
Thanks,
~Deepak
Hi,
after Nicolas' announcement of linaro-2.6.39 [1] I had a look to the
bsp/freescale/linux-linaro-natty.git lt-2.6.38 kernel [2] what has to
be done to port that to 2.6.39.
Looking at that lt-2.6.38 branch, I exported 184 patches [3] which
seem to be specific for this lt kernel (?).
Then, I rebase them to Nicolas' linaro-2.6.39 using quilt. See the
attached quilt series file for which patches were used and which were
dropped (because they seem to be already in 2.6.39 mainline).
The result does compile with the imx5_defconfig. I've done no boot
tests, yet. So this is only compile tested.
The resulting quilt patch series is ~2,5MB bz2 compressed. I don't
want to send it to the mailing list. I will send it as a reply to this
mail to Eric and Nicolas. Let me know if you are interested in it, too
(or where to put it so that everybody can access it).
Note: I couldn't figure how to put binary firmware files into a patch.
This does mean that the patch series misses the firmware/imx/sdma/
files. You have to download them from [4] and put them manually to
firmware/imx/sdma/ to be able to compile imx5_defconfig successfully.
Opinions?
Best regards
Dirk
[1] http://lists.linaro.org/pipermail/linaro-kernel/2011-June/000461.html
[2]
http://git.linaro.org/gitweb?p=bsp/freescale/linux-linaro-natty.git;a=short…
[3] Starting with
http://git.linaro.org/gitweb?p=bsp/freescale/linux-linaro-natty.git;a=commi…
i.e.
4f2a27a2bf1185e553c85a957102022db67773d6...adcf32a87785f44c19189996a23ecfc09cd0ccef
(adcf32a87785f44c19189996a23ecfc09cd0ccef == recent head)
[4]
http://git.linaro.org/gitweb?p=bsp/freescale/linux-linaro-natty.git;a=tree;…
== Highlights ==
* Fill in the blueprint of 11.11. cycle, continue study some information
* MX53 u-boot upstream, loco board support patch serials already in
u-boot master branch
and will be included into the v2011.06 release.
== Plans ==
* Fill the blueprint spec.
* Some u-boot patches upstream review and revision.
== Absence ==
* vacation from 12 June to 29 June,
== Per Forlin <perfor> ==
=== Highlights ===
* Reviewing dependencies of the storage blueprints,
* investigated sdio single irq issue in libertas.
* Setting up wl12xx_sdio_test on pandaboard (ongoing)
== Thomas Abraham <thomas-ab> ==
=== Highlights ===
* Discussed with IBM Engineer, Ankita Garg, about memory regions patchset.
* Study of DDR3 specification and a Samsung DDR3 part datasheet to
understand power consumed during various bank states.
* Measured power consumed by DDR3 on smdkv310 board.
* Discussed with Samsung Landing team about ARM consolidation work.
=== Plans ===
* Complete all the power measurements on smdkv310 board as suggested by Ankita.
* Test memory regions patches on Exynos4 platform.
== Shawn Guo (shawnguo) ==
=== Device Tree ===
* It exposed build error when sdhci-pltfm&OF-consolidation patch set
hits linux-next tree. It turns out there is problem with multiple
sdhci-pltfm based drivers compiling and module build. Sent a
follow-up patch to fix these problems. Chris had picked it up on
mmc-next tree.
=== ARM/imx consolidation ===
* The patches that move imx gpio drivers under subarch into
drivers/gpio have hit Grant's tree.
* The patches converting gpio-mxc and gpio-mxs to use basic_mmio_gpio
library are on the way to be accepted. Tens of LOC will be saved
for each driver.
=== Misc ===
* Sent the v2 of dma-set/get-max_segment_number patch to explain why
the patch is needed.
* Added leds-gpio support for mx28evk board.
=== Plan ===
* Keep looking at if the imx irq_chip and gpio_irq_chip can be migrated
to generic_irq_chip
--
Regards,
Shawn
Just a heads up, I'm out Weds-Friday next week.
=== Highlights ===
* Rebased linaro+android tree to Nico's final 2.6.38 kernel for the
11.05 release
* Sent out first pass at suspend/resume drift improvement (Similar
method to what Android uses)
* Had an initial meeting with AndyG and Zach
* Sent out a number of clocksource_register_khz/hz cleanups
* Queued an prepped a bunch of community RTC, and PTP fixups for 3.0 and
sent Thomas pull requests.
* Queued a few RTC fixups and TSC improvements for 3.1
* Started work on 2.6.39 based Linaro+Android tree on top of Nico's
2.6.39 tree.
* BeagleBoard seems to be working fine
* Panda HDMI output support is gone (need to be rebased and merged
into Nico's tree)
* Started working on an internal presentation.
=== Plans ===
* Short week: I'm on vacation Weds-Friday.
* Try to queue suspend/resume drift correction for 3.1
* Continue working bug #789089
* Continue to work RTC issue from lkml.
* More internal presentation prep
=== Issues ===
* NA
== Paul E. McKenney <paulmck> ==
=== Highlights ==
* Continued tracking down issues relating to RCU priority boosting in mainline,mostly boot-time slowdowns that I cannot reproduce.
* Worked on ARM server whitepaper.
* Attended public plan reviews.
== Miscellaneous ==
* Got out third release of "Is Parallel Programming Hard, And, If So, What Can You Do About It?" (http://paulmck.livejournal.com/26906.html).
* Linux Plumbers Conference refereed-track submissions reviewed. Jesse Barker's "Unified Memory Management" microconference proposal accepted.
Sorry for this being late! Took most of Friday off and forgot to send it
before heading to the coast!
=== Highlights ===
* "Facilitated discussion" (AKA: Nagged enough developers) on android
scheduler trivial tree patch I sent out earlier, that it got queued and
merged.
* Android trivial mm patch was merged upstream
* Spent a few days chasing down a HDMI regression on beagle XM (thanks
to Ricardo Salveti for helping!). Finally got it resolved and pushed the
fix.
* Merged and made a git pull request for Richard Cochran's PTP patches
that have been in the works for awhile. Patches were able to land for
3.0-rc1.
* Merged RTC fixups for stmp3xxx from Wolfram, but they will need
further work to get upstream.
* Took an initial stab at the RTC suspend/resume drift correction
suggested by Arve.
* Starting working on the repeated console suspend failure notification
issue ( https://bugs.launchpad.net/linaro-android/+bug/789089 ).
=== Plans ===
* Refresh Linaro Android tree with latest bits from Nico
* Continue working bug #789089
* Try to get a patch to lkml for suspend/resume drift correction
* Rework Wolfram's RTC patches
* Try to diagnose RTC issue from lkml.
=== Issues ===
* NA
== Dave Martin <dmart> ==
=== General Activity ===
* Discussed work items and assignments with Deepak Saxena.
* kernel snapshot testing
=== linaro-kernel-o-standard-arch ===
* {set,get}_fiq_regs patches for Thumb-2 compatibility now
merged upstream.
=== Plans ===
* Test Thumb-2 kernel on vexpress. If it works (likely)
follow up with John Rigby so we can use Thumb-2 on vexpress
by default.
* Sync up with freescale landing team regarding Thumb-2 kernel
testing and reployment.
== Deepak Saxena <dsaxena> ==
=== Highlights ===
* Continued coordination of 11.11 Blueprints
* Sent out release announcement for 2011.05 Kernel.
Thanks to everyone for their input!
* Sent 11.11 Technical Requirements change request to TSC
* Had 1:1 with Zach to discuss Android needs
* Lunch meeting with Paul M. to discuss 11.11 items and process
* Started work on public plan review slides
* Various meetings with Mounir to close out on 11.11 blueprints,
team allocation, etc.
* Starting to coordinate discussions between sub-teams within KWG
for 11.11 cycle.
* Got Natty installed and up and running on new work laptop, don't
really like Unity shell.
=== Plans for Next Week ===
* Finalize presentation for planning review (Due 05/31 to TSC)
* Put together outline for "ARM Porting Guide"
* Close out on all BPs
* Attend public plan review meetings
* Start conversation with other teams and WGs re: kernel release process
* Start scheduling regular 1:1s with team members
=== Upcoming Travel/Time Off ===
Out Monday May 30th, US Holiday
Out Friday June 3rd, possibly on IRC and email
Out Friday June 17th - Mon June 20th
== Highlights ==
* 11.11 cycle blueprint review, Deepak give me some information about
the context of
such blueprint and some discussions about it at Budapest. Thanks,
* MX53 u-boot upstream, LOCO board support, patches in ARM maintainer tree.
== Plans ==
* Fill in the blueprint of 11.11. cycle,
* Some u-boot patches upstream review and revision.
== Absence ==
* vacation from 12 June to 29 June,
== Highlights ==
* Continued discussions about ARM maintainership
* Lots of code review:
mxs-gpio, pwm, clkdev, sdhci-pxa, csr subarch, at91-isi, pruss, stm
* New arch maintainance: arch/tile, arch/unicore32, arch/openrisc
== Plans ==
* Get better overview of all subarchitectures
* Set up git tree on kernel.org
== Absence ==
* Public holiday in Germany this thursday
= Thomas Abraham <thomas-ab> ==
=== Highlights ===
* Submitted second version of the clkdev patchset for Samsung platforms.
- clkdev reduces 400 lines of code from Samsung platform and machine code.
- http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg04750.html
* Studying of memory regions patches submitted by IBM engineer.
* Reviewed generic clock patches.
=== Plans ===
* Complete the study of memory regions patches submitted by IBM.
* Test memory regions patches on Exynos4 platform.
=== Misc ===
* Took leave on 23rd and 24th May.
== Per Forlin <perfor> ==
=== Highlights ===
* Updates to blueprints, gadget mass storage, dmaengine.
* Generalise mmc async patch v4 submitted.
* Commented on dmaengine documentation.
=== Plans ===
* public holiday on June 2,3 and 5th
== Manjunath GK <gkmanju> ==
=== Highlights ===
* DT build and setup
* Testing 2011.05 kernel on panda board with DT enabled and disabled.
* Observed issues with SD/MMC during bootup
- It might be due to issue with my panda board since other users are not
able to reproduce the same.
=== Plans for Next Week ===
* Need to get replacement for non working panda board with working one.
* DT support for OMAP panda. Will be working on board file for adapting it
to DT.
-Manjunath
== Shawn Guo (shawnguo) ==
=== Device Tree ===
* Sent updated sdhci-pltfm&OF-consolidation patch set per Wolfram's
comments. Dropped the patch of esdhc consolidation, and will
revisit it when the churn of cpu_is_mx gets cleaned up.
=== Misc ===
* Sent the v2 of the patch that moves mxs gpio driver into
drivers/gpio to address Arnd's comments. (Thanks Arnd for the
review)
* Sent a patch to add new dma api for set/get max_segment_number
=== Plan ===
* Keep working on moving mxc gpio driver into drivers/gpio
* Try to see if the imx irq_chip and gpio_irq_chip can be migrated
to generic_irq_chip
--
Regards,
Shawn
== Niklas Hernaeus <nhe> ==
=== General activity ===
* Setup of workplace done.
* Started to view the device-tree code.
* Added a blueprint for device-tree for u8500
=== Upcoming Travel/Time Off ===
* Vacation Monday May 30 to June 1.
* Swedish holidays from June 2 to June 6.
The Linaro Kernel Working Group (KWG) is excited to announce the
availability our May 2011 development snapshot: linux-linaro-11.05-2.6.38
This is the first of a new monthly series of development snapshots from
the KWG that will provide a way for developers to work with the Linaro
kernels without needing to follow the git tree on a daily basis. As the
word "snapshot" implies, these are meant as development kernels and have
not been fully validated. You should expect issues and to help us deliver
a better kernel in the future, you should file bugs in Launchpad at
https://bugs.launchpad.net/linux-linaro.
The source tarball is available at:
https://launchpad.net/linux-linaro/11.05/11.05-final/+download/linux-linaro…
The kernel sources can also be accessed using git at:
git://git.linaro.org/kernel/linux-linaro-2.6.38.git
tag: linaro-11.05-2.6.38
A pre-packaged kernel for OMAP boards is available at:
https://launchpad.net/~linaro-maintainers/+archive/kernel/+files/linux-imag…
This snapshot is based on the 2.6.38.7 stable kernel with a number
of changes developed by Linaro and integrated from upstream trees
including the 2.6.39, OMAP, and Power Management trees to name a few.
The changes from 2.6.38.7 include:
* Initial Device Tree support for MX51, MX53, Overo, SMDKV310, Beagle,
IGEPv2/v3, Panda, Tegra, and Versatile boards. This support allows
memory size and board type to be passed via the Device Tree.
* The ARM kprobes code has been updated to correctly handle a number
of instructions that did not previously work and to work on kernels
w/o frame pointers.
* The coredump code has been updated so you can now analyze VFP
register state using GDB. Using this feature requires the upstream
GDB trunk tree or the Linaro snapshot available from
https://launchpad.net/gdb-linaro/+download
* CPUIDLE support for Samsung Orion has been added, allowing for
longer battery life on platforms based on this chipset.
* Experimental support for LTTng on ARM, allowing developers to perform
deep analysis of system state transitions. See http://lttng.org/ for
more information on using LTTng.
A full changelog against 2.6.38.7 is available at:
https://launchpad.net/linux-linaro/11.05/11.05-final/+download/CHANGELOG-li…
High Priority Known Issues:
* The combination of a device-tree enabled kernel and and Linaro's
2011-03 u-boot will make WiFi and HDMI unuseable on the IGEP board.
(LP #768680)
* imx51 randomly truncates serial input at 31 characters
(LP #754254)
* OMAP Beagle C4: kernel does not reliably find SD card on boot
(LP #712175)
* wl12** driver causes networking to hang on ubuntu-desktop image
(LP #785739)
* Only half of RAM useable when using Device Tree on Panda board
(LP #707047)
Mailing list: http://lists.linaro.org/mailman/listinfo/linaro-dev
Questions? https://ask.linaro.org/
Hi all,
The Kernel Working Group is getting ready to release the first of our new
monthly development snapshot in a few days and we would like folks
to do some quick sanity boot testing on their boards. Please
grab or update the kernel from
git://git.linaro.org/kernel/linux-linaro-2.6.38.git,
and checkout the linaro-11.05-2.6.38 tag (which happens to be same
as master at this moment) and give it a quick spin. Note that this is just
the stock Linaro kernel and does not include any binary graphics drivers
or other bits provided by Linaro's landing team kernels, so we just
need the basic build and boot tested along with some simple
testing of devices that can be used w/o extra drivers.
Thanks!
~Deepak
Hi Dave
I've managed to reproduce a relocation error when loading a module built
for Thumb. The runtime error message is:
section 4 reloc 247 sym '': relocation 30 out of range (0xbf9710c6 ->
0xbf96c000)
Relocation 30 is R_ARM_THM_JUMP24, and looking at apply_relocate() in
arch/arm/kernel/module.c it looks like the error is caused by 'offset'
being even here ...
/* only Thumb addresses allowed (no interworking) */
if (!(offset & 1) ||
offset <= (s32)0xff000000 ||
offset >= (s32)0x01000000) {
pr_err("%s: section %u reloc %u sym '%s': relocation %u out of range (%#lx -> %#x)\n",
module->name, relindex, i, symname,
ELF32_R_TYPE(rel->r_info), loc,
sym->st_value);
return -ENOEXEC;
}
I seem to remember you posting some similar issue to a mailing list
recently, or is my memory faulty?
I have some labels declared in inline assembler, and after adding
.type name_of_label, %function
the relocation error goes away, presumably because the label is now
thumbified by having bit 0 set.
--
Tixy
== Shawn Guo (shawnguo) ==
=== Device Tree ===
* Wolfram gave partial comments on sdhci-pltfm&OF-consolidation,
and still wait for more to start v3. Mostly, the patch #5 which
consolidates imx and mpc esdhc support will get dropped.
=== LTP Blueprint ===
* Drafted work items
https://blueprints.launchpad.net/linux-linaro/+spec/linaro-kernel-o-ras-fix…
=== Misc ===
* Tested RMK's MMIO-clocksources-consolidation patch on mxs
* Tested Wolfram's rtc-stmp37xx patch on mxs
* Posted the first try of moving mxs gpio driver into drivers/gpio
=== Plan ===
* Try to move mxc gpio driver into drivers/gpio
--
Regards,
Shawn
== Paul E. McKenney <paulmck> ==
=== Highlights ==
* Attended Budapest summit, led maintainership and Android meetings.
* Blogged maintainership meetings and published LWN article (http://lwn.net/Articles/443510/).
* RCU priority-boosting commits accepted into mainline for 2.6.40.
* Cheng Xu found a fix for the related scheduler bug, which is now in mainline.
* Frederic Weisbecker found a fix for a bug in lock self-test that was resulting in RCU grace-period hangs, which I queued up in my -rcu tree.
* Compiler-sensitive slowdowns located by Yinghai Lu, currently tracking this down.
== Miscellaneous ==
* Handled a license request.
* Discussed the possibility of heavy-duty RCU correctness tools with researchers at Queen Mary University in London.
* Discussed the possibility of formalizing Linux-kernel memory-barrier semantics with researchers at Cambridge University in Cambridge.
* Queued a modification to RCU's fast-path in response to a code-generation complaint from Linus Torvalds.
== Per Forlin <perfor> ==
=== Highlights ===
* Updating blueprints
* Generalise mmc async patch, running validation test is ongoing.
* Studied wl12xx_sdio_test, to be used for sdio async request validation.
=== Plans ===
* Get started with Snowball.
== Deepak Saxena <dsaxena> ==
=== Highlights ===
* Coordinating development of 11.11 blueprints
* Coordination of closing out 11.05 items:
- DT support for IGEP and u8500
- Started work on 11.05 kernel release
* Sent 11.11 Technical Requirements change request to TSC
* 1:1 with Jason H., John S., Mounir B.
=== Plans for Next Week ===
* Final review of blueprints and work items for 11.11 cycle
* Develop presentation for planning review (Due 05/31 to TSC)
* Put together outline for "ARM Porting Guide"
* Start scheduling regular 1:1s with team members
* Meeting with Zach, re: Android team needs, driver best practices howto
* Meeting with Paul L., re: Kernel testing process
* Meeting with Paul M., re: KWG 11.11 cycle
* Get Natty installed and up and running on new work laptop
=== Upcoming Travel/Time Off ===
Out Friday June 3rd, possibly on IRC and email
Out Friday June 17th - Mon June 20th
=== Highlights ===
* Posix Alarm Timers merged in mainline for 2.6.40-rc1
* Number of clocksource cleanups merged for 2.6.40-rc1
* A number of my RTC fixes were merged for 2.6.39
* My re-implementation of the virtual-battery driver functionality into
test_power driver is being pushed by the maintainer for 2.6.40
* task->comm locking fixes shot down by Ingo/Linus
* Sadly this burned a bit of time.
* But ok, as I wasn't strongly motivated to push the patches.
* Updated Linaro+Android git tree
* Included recent HDMI fixes from nico's tree
* Met with Deepak for 1:1 lunch.
* Took an initial swipe at blueprint workitems for 11.11 cycle.
* Emailed with Rafael and spent more time looking at pm_stay_awake
infrastructure
* Reviewed and tested some clocksource patches for Thomas which will
help extend NOHZ idle times beyond 5 seconds.
=== Plans ===
* Rebase and freshen up my current development git trees
* Continue researching pm_stay_awake/pm_relax infrastructure
* Try to adapt Arve's earlier RTC suggestions into suspend/resume path
=== Issues ===
* NA
Hi all,
Since we didn't have any meetings last two weeks, I wanted to send out
a reminder that we are having
our regular 8am PST and 8pm PST meetings this Monday. #linaro-kernel
on freenode.
Thanks,
~Deepak
== Thomas Abraham <thomas-ab> ==
=== Highlights ===
* Listed the work items for memory regions TR for
linaro-kernel-o-general-performance blueprint.
* Submitted patches of clkdev support on Samsung platforms. This is
prerequisite for common clock and device tree support.
(http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg04708.html)
* Continued testing of kexec-crashdump work item on s5pv310 platform.
Could not identify the reason for kernel reboot failure. Will continue
to debug this.
=== Plans ===
* Complete testing of kexec-crashdump on s5pv310 platform.
* Submit first version of common clock support for Samsung platforms.
Hi all,
We're trying to close out on a few 11.05 items and two that stand out
are completing DT support on IGEP and u8500 boards. The code is in
place in the linaro-2.6.38 kernel but we need someone with HW to debug
why it's not working. I'm working on sorting out the u8500 testing,
but does anyone in the kernel team or landing team have the HW on hand
and able to coordinate with Grant on debugging on the IGEP?
~Deepak
Hi kernel folks,
there's an upstream GCC PR about banked registers not being properly
utilized in FIQ routines, specified by GCC attibutes, see here:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48429
I was just wondering, is this GCC __attribute__(("FIQ")) feature used in
the Linux kernel as well, or are the entry paths in Linux already done
in assembler?
Thanks,
Chung-Lin
== Deepak Saxena <dsaxena> ==
=== Highlights ===
* Attended LDS
=== Plans ===
* Summarize blueprint next steps for kernel team & put together and
send off first
pass of 11.11 assignments/priorities for team review
* Start coordinating 1:1s with team members
* Meetings: platform team, release, kernel team meeting planning with Mounir
* Follow up with Nicolas on monthly kernel drops
== Per Forlin <perfor> ==
=== Highlights ===
* Attending LDS
* SDIO single IRQ patch merged
=== Plans ===
* Update blueprints
* Submit mmc async patch with common parallel request handling in core.c
* 2 days absence planned for this week due to child with otitis
=== Highlights ===
* Did a full audit of the RTC drivers to catch boot time hangs due to
un-initialized drvdata.
* Submitted along with revised fixes from community for 2.6.39.
* Thomas merged them into -tip
* Sent out updated v2 of task->comm locking patch queue, with %ptc
printk formatting method
* Got good feedback, and sent out v3 patchset as well
* Attended LDS Android upstreaming meeting remotely
* 3-5minute audio lag was a problem
* Submitted time() fix for 2.6.32-longterm
* Worked with IBMer on suspend-blocker-like driver being used to keep
systems from suspending while firmware updates are running
* Spent time reading over and trying to make use of
pm_stay_awake/pm_relax api
* So far, no luck. Mailed Rafael with questions.
* Updated Linaro+Android kernel git tree.
=== Plans ===
* Continue to push task->comm fixes in
* Continue working on pm_stay_awake/pm_relax infrastructure
* Try to adapt Arve's earlier RTC suggestions into suspend/resume path
* Catch up on LDS discussions I missed.
=== Issues ===
* NA
Hi all,
I have a couple of schedule changes for tomorrow to announce:
1. The kernel wg + landing team discussion has been moved from 5pm to
2pm in the TAS room.
Scott B. synced up with me and Nicolas is leaving at 4pm and it is
critical that he be involved in
this discussion hence the move.
2. The kernel working group team meeting that was scheduled for 2pm
tomorrow obviously
not happening at the same time and will be reschedule for a
different time and send
out and update.
Thanks,
~Deepak
Hello!
Demonstrating dynamic scheduling due to the inevitable conflicts...
The meeting to discuss upstreaming has been moved from Tuesday 10AM to
Monday at noon. It is in the Ond meeting room (room 19).
Thanx, Paul
== Shawn Guo (shawnguo) ==
=== Device Tree ===
* Sent v2 of sdhci-pltfm&OF-consolidation which has been rebased on mmc-next
=== LTP Blueprint ===
* More discussion on K9.1 ltp-fix drafting with Paul Larson
=== Plan ===
* Attend LDS
--
Regards,
Shawn
== Deepak Saxena <dsaxena> ==
=== Highlights ===
* Started at Linaro!
* Had 1:1 meetings with Amit Kucheria, Angus, Grant, Jesse Barker,
Paul Larson, John Stultz
* Went through kernel bug backlog and pinged kernel team to revisit
and update with latest information
* Read through lots of documentation (blue print process, understading
our dev cycle, etc) in wiki
=== Plans ===
* Attend LDS
Hi,
I am working on minimizing the latency between two block requests in
the mmc framework. The approach is simple. If there are more than one
request in the block queue the 2nd request will be prepared while the
1st request is being transfered. When the 1 st request is completed
the 2nd request will start with minimal latency cost.
For writes this work fine:
root@(none):/ dd of=/dev/mmcblk0p2 if=/dev/zero bs=4k count=2560
2560+0 records in
2560+0 records out
root@(none):/ dmesg
[mmc_queue_thread] req d97a2ac8 blocks 1024
[mmc_queue_thread] req d97a2ba0 blocks 1024
[mmc_queue_thread] req d97a2c78 blocks 1024
[mmc_queue_thread] req d97a2d50 blocks 1024
[mmc_queue_thread] req d97a2e28 blocks 1024
[mmc_queue_thread] req d97a2f00 blocks 1024
[mmc_queue_thread] req d954c9b0 blocks 1024
[mmc_queue_thread] req d954c800 blocks 1024
[mmc_queue_thread] req d954c728 blocks 1024
[mmc_queue_thread] req d954c650 blocks 1024
[mmc_queue_thread] req d954c578 blocks 1024
[mmc_queue_thread] req d954c4a0 blocks 1024
[mmc_queue_thread] req d954c8d8 blocks 1024
[mmc_queue_thread] req d954c3c8 blocks 1024
[mmc_queue_thread] req d954c2f0 blocks 1024
[mmc_queue_thread] req d954c218 blocks 1024
[mmc_queue_thread] req d954c140 blocks 1024
[mmc_queue_thread] req d954c068 blocks 1024
[mmc_queue_thread] req d954cde8 blocks 1024
[mmc_queue_thread] req d954cec0 blocks 1024
mmc block queue is never empty. All the mmc request preparations can
run in parallel with an ongoing transfer.
[mmc_queue_thread] req (null) blocks 0
[mmc_queue_thread] req (null) blocks 0
"req (null)" indicates there are no requests pending in the mmc block
queue. This is expected since there are no more requests to process.
For reads on the other hand it look like this
root@(none):/ dd if=/dev/mmcblk0 of=/dev/null bs=4k count=256
256+0 records in
256+0 records out
root@(none):/ dmesg
[mmc_queue_thread] req d954cec0 blocks 32
[mmc_queue_thread] req (null) blocks 0
[mmc_queue_thread] req (null) blocks 0
[mmc_queue_thread] req d954cec0 blocks 64
[mmc_queue_thread] req (null) blocks 0
[mmc_queue_thread] req d954cde8 blocks 128
[mmc_queue_thread] req (null) blocks 0
[mmc_queue_thread] req d954cec0 blocks 256
[mmc_queue_thread] req (null) blocks 0
[mmc_queue_thread] req d954cde8 blocks 256
[mmc_queue_thread] req (null) blocks 0
[mmc_queue_thread] req d954cec0 blocks 256
[mmc_queue_thread] req (null) blocks 0
[mmc_queue_thread] req d954cde8 blocks 256
[mmc_queue_thread] req (null) blocks 0
[mmc_queue_thread] req d954cec0 blocks 256
[mmc_queue_thread] req (null) blocks 0
[mmc_queue_thread] req d954cde8 blocks 256
[mmc_queue_thread] req (null) blocks 0
[mmc_queue_thread] req d954cec0 blocks 256
[mmc_queue_thread] req (null) blocks 0
[mmc_queue_thread] req d954cde8 blocks 256
[mmc_queue_thread] req (null) blocks 0
[mmc_queue_thread] req d954cec0 blocks 256
[mmc_queue_thread] req (null) blocks 0
[mmc_queue_thread] req (null) blocks 0
There are never more than one read request in the mmc block queue. All
the mmc request preparations will be serialized and the cost for this
is roughly 10% lower bandwidth (verified on ARM platforms ux500 and
Pandaboard).
> page_not_up_to_date:
> /* Get exclusive access to the page ... */
> error = lock_page_killable(page);
I looked at the code in do_generic_file_read(). lock_page_killable
waits until the current read ahead is completed.
Is it possible to configure the read ahead to push multiple read
request to the block device queue?
Thanks,
Per
== Per Forlin <perfor> ==
=== Highlights ===
* Prepare blueprints for LDS
* K7.3 Non-Blocking Request in MMC
* K7.4 eMMC Background Maintenance
* K7.6 SDIO Single Function Support
* K7.10 DMA Engine on ARM
* K7.11 USB gadget mass storage
* Submit patch to optimize SDIO for single IRQ
* Submit patch v3 of nonblocking mmc with some minor fixes.
=== Plans ===
* Attending LDS
== Paul E. McKenney <paulmck> ==
=== Highlights ==
* Pre-Budapest specification work
* Submitted two smaller RCU-related patchsets to LKML.
* Submitted git pull request to Ingo Molnar for TREE_RCU priority boosting.
* Cheng Xu is working towards a fix to the related scheduler bug.
=== Highlights ===
* Had jury duty on weds, so was mostly out for that day.
* Met Deepak for 1:1 lunch meeting
* Lots of community bugs/issues coming out of the woodwork!
* Worked on debugging a boot-time delay seemingly caused by earlier
TSC refinement patch.
* Worked on time() bug found on P7 hardware
* Did a full audit of the rtc drivers to resolve issues with bad
initialization that was uncovered by my RTC infrastructure fixes
* Discussed methods for reducing xtime_lock contention
* Wrote up spec for Kconfig work
* Got two Alarmtimer fixes merged into -tip, worked with Thomas to
resolve some other minor alarmtimer issues.
=== Plans ===
* Spend time reviewing the pm_stay_awake/pm_relax code
* Try to adapt Arve's earlier RTC suggestions into the tree.
* Try to implement printk task_comm %P value
* Get Android Trivial branches cpufreq and cgroup sent out.
=== Issues ===
* Crazy number of community bugs taking lots of my time right now.
Hoping this calms down soon.
Hi all,
I am going through the Linaro kernel bug backlog to wrap my head
around the status of what that the kernel and landing team has been
working on. I made some simple notes for myself and want some input
from folks who've been involved longer to understand what should be
closed, what should remain open, and what should be re-prioritized
based on deliverables as we start up the 11.11 cycle so please speak
up with any thoughts. Some of these bugs have no assignees and since I
still need to figure out what everyone's availability and skill set
is, please speak up if there's a bug you are called to take.
Mounir, I think it'd be good for you and I to sit down towards the end
of LDS next week and do a review of all kernel bugs.
Starting with http://goo.gl/6k7GS - Importance field not set
645663 2.6.35-1006-linaro-omap occasional oops during boot
This was opened in September of last year on a very old kernel,
should be closed?
754247 2.6.38 halts under heavy load
This looks like it should be a medium priority bug and needs to be
reproduced
on a single board with serial console logged running latest Linaro kernel.
754248 Processes do not distribute across cores when running CoreMark
Related to WIP code for TI Panda board, needs re-testing with CPU_FREQ
disabled to validate. Importance should be low as it is a mostly known
issue and possibly needs to just be marked a dup if we already have
a bug tracking the CPU_FREQ development?
776856 uboot won't boot until running 'mmc part 0'
Needs to be tested/reproduced on latest U-Boot by John. I consider this
a low priority bug as developer's can still boot a board by running
'mmc part 0'.
Next, we have http://goo.gl/kfk7L - High and Medium priority bugs.
754254 imx51 randomly truncates serial input at 31 characters
Probably trivial to fix, just needs someone with HW to fix it.
Probably someone
from landing team?
615972 Neon registers missing in core files
In progress, patches merged into Linaro trees and headed upstream.
720055 CONFIG_OMAP2_DSS_SDI on OMAP4 causes...
Issue is resolved in linux-linaro-omap. Does it need to be pulled
into Nicolas'
tree to close out the linux-linaro component?
754254 imx51 randomly truncates serial input at 31 characters
Needs to be assigned to someone, likely in the Freescale Landing Team?
615974 Interrupted system call handling
Patch is in Linaro tree, needs submitting to RMK's patch system.
660639 twl driver failed to transfer msgs etc
Patch has been submitted upstream by Andy that possibly fixes the issue
but needs to be retested by Tom, original submitter and then likely added
to Linaro kernel tree if not already merged.
709245 panda: USB disk IO slow
Was assigned to Mian, will re-assign to Venkat.
712025 asoc: interface omap-mcbsp-dai hw params failed
Patch sent upstream, needs merging into Linaro kernel.
712175 OMAP Beagle C4: kernel does not reliably find SD card on boot
No update since April 04, probably want to retest on latest kernel.
717677 wifi is not recognized in latest netbook image on IGEP v2
No update since March 21st. Does this need testing on latest kernel?
762026 Problem with SMP IRQ affinity
Known issue, needs an assignee to fix.
768680 Boot does not complete on IGEP with Device Tree
Currently assigned to Grant. Grant, do you have time to dig into this or
should we reassign to someone else with access to HW?
Without device_type property set as memory for the node, the generated
dtb can still work when it gets passed to kernel by u-boot, since
u-boot will fix it up. But kernel will not boot due to that it fails
to parse the memory node, when the dtb is appended to kernel image as
it is.
The patch adds a property device_type="memory" for memory node to fix
the problem.
Signed-off-by: Shawn Guo <shawn.guo(a)linaro.org>
---
It applies on branch devicetree/test.
arch/arm/boot/dts/babbage.dts | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/babbage.dts b/arch/arm/boot/dts/babbage.dts
index 8f9b47c..4805168 100644
--- a/arch/arm/boot/dts/babbage.dts
+++ b/arch/arm/boot/dts/babbage.dts
@@ -21,6 +21,7 @@
interrupt-parent = <&tzic>;
memory {
+ device_type = "memory";
reg = <0x90000000 0x20000000>;
};
--
1.7.4.1
On Mon, Apr 04, 2011 at 10:54:00PM -0600, Grant Likely wrote:
> On Fri, Apr 01, 2011 at 03:49:16PM +0800, Shawn Guo wrote:
> > On Thu, Mar 31, 2011 at 10:09:40AM -0600, Grant Likely wrote:
> > > On Fri, Mar 25, 2011 at 03:13:58PM +0800, Shawn Guo wrote:
> > > > After fec dt support is added, the following compile error will be
> > > > seen when building a pure non-dt kernel.
> > > >
> > > > drivers/net/fec.c: In function ‘fec_probe’:
> > > > drivers/net/fec.c:1383: error: implicit declaration of function ‘of_match_device’
> > > > drivers/net/fec.c:1383: warning: assignment makes pointer from integer without a cast
> > >
> > > Earlier today I suggested fixing this by adding an empty
> > > implementation of of_match_device, but I forgot that an .of_match
> > > pointer has been added to struct device for exactly this purpose. You
> > > can use that instead.
> > >
> > > That change is currently in mainline, but it has not been backported
> > > to the Linaro 2.6.38 tree (yet).
> > >
> > This simply is a fix to commit 54898b86fa9813313b3eb981c44610ff483b0067
> > "net/fec: add device tree matching support", which only sits on branch
> > devicetree/test-2.6.38 right now. However, .of_match is not available
> > on that tree yet. So I can not do anything until ether this patch
> > shows on devicetree/test or .of_match is back ported on
> > devicetree/test-2.6.38. Or you can simply ignore this patch since I
> > just want let you know such a compile error.
>
> Okay, of_match is in my devicetree/test branch now since I've rebased
> to 2.6.38-rc1. I'll happily take a fixup patch from you now. :-)
>
Sorry, Grant. I overlooked this reply, and noticed it when re-visiting
the thread today. I just sent an updated patch. Please take a look.
--
Regards,
Shawn
Andy Green has worked on a set of patches adding many features to OMAP4
such as HDMI audio/video, FM receiver, etc. Before I merge that into
the Linaro kernel tree I need some assurance that this won't break
existing OMAP3 support, especially video. The branch is available in
the linux-linaro-2.6.38 Git repository on git.linaro.org, in the
"testing" branch.
So please if you have an OMAP3 board and can perform some testing that
would be appreciated.
Nicolas
Hi,
Probably most of you are aware of LTTng since it is already integrated
in Linaro's kernel, in this session I will focus on the new LTTng
patchset which has the following characteristics :
1) The size of the kernel patchset has been shrinked for Linux
distributions by removing all LTTng-specific instrumentation from the tree.
2) The lttng-modules package now implements an ABI based on anonymous
file descriptors (inspired from perf) rather than the full-blown VFS
tree the previous LTTng versions were implementing.
3) lttng-modules now exports trace data and metadata in the CTF (Common
Trace Format).
4) lttng-modules now uses the Generic Ring Buffer Library.
LTTng will probably not enter in the Oneiric Ubuntu kernel, but our
target is to upstream most of our patches before the next LTS.
The purpose of this session is :
- to show the benefit developers and sysadmins have with LTTng
kernel and userspace tracers for debugging and QA;
- to highlight the main differences between the current stable LTTng and
this new patchset and the new tools associated with it;
- to find a way to test LTTng in Oneiric to have something rocking in
the next LTS.
The session will be held in room Jozsef on Wednesday 11th between 12:00
and 13:00, the blueprint associated is here :
https://blueprints.launchpad.net/ubuntu/+spec/other-o-lttng
Thanks,
Julien
Hello all,
I want to introduce myself to the linaro-kernel and linaro-dev lists as I
just started at Linaro today in the role of Kernel Working Group Technical
Lead and will be working closely with all of you on enhancing the ARM Linux
ecosystem. I've been using Linux since 1993 and working with the Linux
kernel for over 10 years for a variety of companies including silicon
vendors, OSVs, and device vendors with a broad variety of experience
including ARM CPU and board bring up, hacking on a variety of device
drivers, maintaining a distro kernel, maintaining a few ARM
sub-architectures, educating HW vendors and new developers about the open
source development model, etc. I've been a bit out of the loop of the open
source community the last 1-2 years and am really excited to be involved
with Linaro working on community-focused technology enablement and
enhancement.
I expect this first week to be mostly focused on reading up on process,
existing deliverables, mailing list archives, etc to wrap my head around
where we are right now and where we're headed with the 11.11 release. I'll
be at LDS and look forward to meeting many of you next week and I want to
encourage anyone who won't be at LDS but has concerns, ideas, questions
related to the kernel WG to drop me an email.
Thanks!
~Deepak
Hello!
A call for hardware needs -- please speak now or hold your peace for
another cycle.
Thanx, Paul
----- Forwarded message from James Westby <james.westby(a)linaro.org> -----
Date: Fri, 29 Apr 2011 18:01:18 -0400
From: James Westby <james.westby(a)linaro.org>
To: techleads(a)linaro.org
Subject: LDS: hardware requirements for next cycle
Hi,
I'm organising a session at LDS to collate and prioritise hardware needs
across Linaro.
https://blueprints.launchpad.net/linaro/+spec/linaro-other-o-hardware-needs
If your team needs some hardware that isn't currently ordered then
either come along to the session, or email me beforehand, and tell me:
* What hardware you need (type, quantity)
* When you need it by
* What you need if for (i.e. what won't be able to happen if you don't
have it)
We'll then be able to use this to come up with a shopping list that we
can request hardware from, and balance priorities if we can't have
everything.
If the request is already on the Hardware wiki page then you don't need
to re-send it.
Also, this isn't to say that if you don't mention it now you can't have
it, but it will be helpful to have a comprehensive snapshot of the
requirements before the session.
Thanks,
James
----- End forwarded message -----