=== Highlights ===
* Mostly caught up from paternity leave
* Queued a few timekeeping patches for 3.8
* Discussed need for CLOCK_PERF and possible clock_gettime2() interfaces
on lkml
* Reviewed patches that allow for vdso pvclock.
* Took a quick look at the ashmem/binder fixes for 64bit
* Started testing and reviewing Minchan's madvise volatile patch
* Sent out Android upstreaming weekly email
=== Plans ===
* Continue playing with Minchans madvise volatile patch, trying to see
how to best integrate my needs with it.
* Try to get a closer review of the ashmem/binder 64bit fixes
=== Issues ===
* NA
Hello Jason,
Just as promised, I'm resending the series after the merge window.
This patchset implements "kiosk" mode for KDB debugger. The mode reduces
kdb features, so that it is no longer possible to leak sensitive data via
the debugger, and not possible to change program flow in a predefined
manner by an ordinary user. Root can control the capability.
There are a few patches, some are just cleanups, some are churn-ish
cleanups, but inevitable. And the rest implements the mode -- after all
the preparations, everything is pretty straightforward.
Thanks!
Anton.
--
include/linux/kdb.h | 20 ++--
kernel/debug/kdb/kdb_bp.c | 24 ++---
kernel/debug/kdb/kdb_main.c | 189 ++++++++++++++++++----------------
kernel/debug/kdb/kdb_private.h | 3 +-
kernel/trace/trace_kdb.c | 4 +-
5 files changed, 125 insertions(+), 115 deletions(-)
Hello Russell,
The KDB/NMI core support has been merged into v3.7-rc1, so the only ARM
bits are pending now. I believe I addressed all your previous comments,
but surely there might be something else to improve, thus would be great
if you could take a look at this.
The patches were rebased onto v3.7-rc1, and this is the only change in
v10.
Old changelogs and rationale for these patches can be found here:
v1-v5, rationale: http://lkml.org/lkml/2012/9/10/2
v6: http://lkml.org/lkml/2012/9/10/2
v7: http://lkml.org/lkml/2012/9/13/367
v8: http://lkml.org/lkml/2012/9/19/525
v9: http://lkml.org/lkml/2012/9/24/538
Thanks!
Anton.
--
arch/arm/Kconfig | 19 ++++
arch/arm/common/vic.c | 28 +++++
arch/arm/include/asm/hardware/vic.h | 2 +
arch/arm/include/asm/kgdb.h | 8 ++
arch/arm/kernel/Makefile | 1 +
arch/arm/kernel/entry-armv.S | 167 +---------------------------
arch/arm/kernel/entry-header.S | 170 +++++++++++++++++++++++++++++
arch/arm/kernel/kgdb_fiq.c | 124 +++++++++++++++++++++
arch/arm/kernel/kgdb_fiq_entry.S | 87 +++++++++++++++
arch/arm/mach-versatile/Makefile | 1 +
arch/arm/mach-versatile/kgdb_fiq.c | 31 ++++++
11 files changed, 472 insertions(+), 166 deletions(-)
== Highlights ==
* Prepared a new, reworked vmpressure API, addressed Minchan comments.
Apart of some minor API controversy (syscall vs. vmeventfd/sysfs, etc)
the main concern is cgroups integration. So I started working in this
direction -- it is definitely doable, but it won't be trivial, though;
* Rebased Linaro android tree on v3.7-rc3 (personally, I only tested it on
my qemu Versatile "machine", but it seems to work). Along the way, also
synced fiq debugger, lowmemorykiller and binder drivers with the latest
android-common tree;
* Still no reply on KDB/FIQ and KDB/Kiosk patches.
=== Highlights ===
* KVM/ARM VGIC state saving and restoring implementation.
1) Completed reading common gic code in kernel
2) Completed reading vgic code with refer to ARM GIC v2.0 spec
Understand the whole things well in the code including the IRQ
injection process
and how virtual distributor are implemented and cowork with
vitrual interface controller to
handle interrupt between host kernel mode and guest mode.
3) Started coding by refer to the common gic state support code,
suppose the patch can be
sent out within this week if everything goes well.
Planned to refer to the common gic suspend/resume state support
code like gic_dist_save
and gic_dist_restore or other exist interrupt controller kvm
state save&restore
code of other architecture in kvm framework.
* Reviewed the patch series [PATCH v4 00/13] KVM/ARM vGIC support from
Christoffer
Gave a few comment on some minor issues.
* Reviewed a few imx pinctrl patches
* Took a sick leave on 11/05 and 11/06
== Linus Walleij linusw ==
Sorry for delayed activity report, and Linaro Connect was
inbetween so now it's about time to report on what's been
going on.
=== Highlights ===
* SPARSE_IRQ patch set for Ux500 including the removal
of the entire arch/arm/plat-nomadik directory has been
merged to ARM SoC. The same patches have been applied
to our internal development kernel, so it's not coming back.
* Intense activity on pinctrl and gpio trees, sending pull
requests for fixes to Torvalds for all random stuff.
* Merged the U300 patches cleaning up some pinctrl
business to the pinctrl tree.
* Intensely debated default-hogging of pinctrl handles.
See blueprint just created for details:
https://blueprints.launchpad.net/linux-linaro/+spec/pinctrl-notifyhog
* At Connect Kevin Hilman from TI kindly took time to explain
to me and Ulf how runtime PM is to be done right. So what
needs to be done is major and will require commitment from
Linaro member companies, and I've filed a blueprint for it.
https://blueprints.launchpad.net/linux-linaro/+spec/runtime-pm
Amit K is informed.
* Merged a patch from Shiraz Hashin basically intended to
implement this blueprint:
https://blueprints.launchpad.net/linux-linaro/+spec/pinctrl-gpiorange-makeo…
Unfortunately there was some fallout and I set some
priority for this over all other work since the tree could
not be left in bad shape and I neither wanted to revert the
patch. Still hashing things out...
* Debated gpio_get(), see the thread beginning with this post:
http://marc.info/?l=linux-kernel&m=135167415211671&w=2
Basically the proper solution to this was another blueprint in the
making IMHO, so I just had to write it down:
https://blueprints.launchpad.net/linux-linaro/+spec/gpio-handles
* Russell merged a few SMP_TWD patches I sent making
the driver reentrant as cores come and go. This is required
for big.LITTLE MP scheduling I think. This is the interesting
commit:
http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=7563/1
* Pushed some Integrator-patches moving the irqchip driver
to drivers/irqchip and some more. Mainly therapeutic work.
* Even sent a clksrc patch for ARM64...
* Got IMPD1 and Versatile AB boards from Marc Zyngier @ARM.
I owe this guy a favor... now all happy hacking!
=== Plans ===
* Attack the remaining headers in arch/arm/mach-ux500
so we can move forward with multiplatform for v3.9
or so. (Make no promises, make no commitments...)
* Test the PL08x patches on the Ericsson Research
PB11MPCore and submit platform data for using
pl08x DMA on that platform.
* Look into other Ux500 stuff in need of mainlining...
using an internal tracking sheet for this.
* Look into regmap. Try something out, get to know it.
=== Issues ===
* Classified activity has taken some time and will be reported
in 1:1.
Thanks,
Linus Walleij
From: "hongbo.zhang" <hongbo.zhang(a)linaro.com>
Hi all,
This patch set is to upstream ST-Ericsson thermal driver and fix some bugs
of thermal layer at the same time.
All of these patches are based on v3.7-rc1.
[PATCH 1/5] Thermal: do bind operation after thermal zone or cooling
device register returns.
In the previous bind function, cdev->get_max_state(cdev, &max_state) is called
before the registration function finishes, but at this moment, the parameter
cdev at thermal driver layer isn't ready--it will get ready only after its
registration, so the the get_max_state callback cannot tell the max_state
according to the cdev input.
This problem can be fixed by separating the bind operation out of registration
and doing it when registration completely finished.
There is no such problem with the current exynos thermal driver because it
regsters cooling device before thermal zone device. As a generic thermal layer
any sequence should be supported, thermal zone first or cooling device first,
this will be also helpful to add/remove cooling device dynamically.
[PATCH 2/5] Thermal: add indent for code alignment.
[PATCH 3/5] Thermal: fix empty list checking method.
[PATCH 4/5] Thermal: make sure cpufreq cooling register after
cpufreq driver
Bug fix for generic cpufreq cooling layer as described in the commit logs.
[PATCH 5/5] Thermal: Add ST-Ericsson db8500 thermal dirver.
This patch is to add ST-Ericsson into the latest kervel version.
hongbo.zhang (5):
Thermal: do bind operation after thermal zone or cooling device
register returns.
Thermal: add indent for code alignment.
Thermal: fix empty list checking method.
Thermal: make sure cpufreq cooling register after cpufreq driver
Thermal: Add ST-Ericsson db8500 thermal dirver.
arch/arm/boot/dts/dbx5x0.dtsi | 11 +
arch/arm/configs/u8500_defconfig | 4 +
arch/arm/mach-ux500/board-mop500.c | 73 ++++
drivers/thermal/Kconfig | 20 ++
drivers/thermal/Makefile | 2 +
drivers/thermal/cpu_cooling.c | 19 +-
drivers/thermal/db8500_cpufreq_cooling.c | 118 +++++++
drivers/thermal/db8500_thermal.c | 507 +++++++++++++++++++++++++++
drivers/thermal/thermal_sys.c | 86 +++--
include/linux/platform_data/db8500_thermal.h | 39 +++
10 files changed, 847 insertions(+), 32 deletions(-)
create mode 100644 drivers/thermal/db8500_cpufreq_cooling.c
create mode 100644 drivers/thermal/db8500_thermal.c
create mode 100644 include/linux/platform_data/db8500_thermal.h
--
1.7.11.3
I remember someone pointing out in the last Linaro Connect
saying that we were supposed to push reset frameworks to
drivers/power, is that correct?
Anyone has a pointer to the relevant discussion?
Yours,
Linus Walleij
Hi guys,
Sorry if i am on the wrong list :(
I found it hard to log on to ask.linaro.org to see if i can answer some queries.
Or even to ask some queries.
I would love to have a mail + mailing-list interface for it. Please point me to
one if available.
--
viresh
