Signed-off-by: Mark F. Brown <mark.brown314@gmail.com> --- arch/arm/mach-mmp/include/mach/regs-apmu.h | 12 ++++++++++++ 1 files changed, 12 insertions(+), 0 deletions(-) diff --git a/arch/arm/mach-mmp/include/mach/regs-apmu.h b/arch/arm/mach-mmp/include/mach/regs-apmu.h index 9190305..ac47023 100644 --- a/arch/arm/mach-mmp/include/mach/regs-apmu.h +++ b/arch/arm/mach-mmp/include/mach/regs-apmu.h @@ -33,4 +33,16 @@ #define APMU_FNRST_DIS (1 << 1) #define APMU_AXIRST_DIS (1 << 0) +/* ...

Version 1 1) Make pxa27x_keypad.h accessible to mach-mmp 2) Add a wakeup handler for pxa27x_keypad interrupts The wakeup callback fixes an issue on the pxa168 that prevents the keypad driver from being able to clear the keypad interrupt after reading KPC_PC 3) Add initial board level support Version 2 1) Clean up for wakeup handler moved from pxa168-irq to pxa27x_keypad 2) Reduced the number of rows to 5 for Aspenite Mark F. Brown (6): ARM: pxa27x/pxa3xx: moved pxa27x_keypad.h to ...

Signed-off-by: Mark F. Brown <mark.brown314@gmail.com> --- arch/arm/mach-mmp/include/mach/pxa168.h | 5 +++++ arch/arm/mach-mmp/pxa168.c | 10 ++++++++++ 2 files changed, 15 insertions(+), 0 deletions(-) diff --git a/arch/arm/mach-mmp/include/mach/pxa168.h b/arch/arm/mach-mmp/include/mach/pxa168.h index f34e663..1801e42 100644 --- a/arch/arm/mach-mmp/include/mach/pxa168.h +++ b/arch/arm/mach-mmp/include/mach/pxa168.h @@ -5,6 +5,7 @@ struct sys_timer; extern struct ...

Signed-off-by: Mark F. Brown <mark.brown314@gmail.com> --- arch/arm/mach-mmp/irq-pxa168.c | 23 ++++++++++++++++++++++- 1 files changed, 22 insertions(+), 1 deletions(-) diff --git a/arch/arm/mach-mmp/irq-pxa168.c b/arch/arm/mach-mmp/irq-pxa168.c index 52ff2f0..bfb0984 100644 --- a/arch/arm/mach-mmp/irq-pxa168.c +++ b/arch/arm/mach-mmp/irq-pxa168.c @@ -17,6 +17,8 @@ #include <linux/io.h> #include <mach/regs-icu.h> +#include <mach/regs-apmu.h> +#include <mach/cputype.h> ...

Signed-off-by: Mark F. Brown <mark.brown314@gmail.com> --- arch/arm/mach-mmp/aspenite.c | 27 +++++++++++++++++++++++++++ 1 files changed, 27 insertions(+), 0 deletions(-) diff --git a/arch/arm/mach-mmp/aspenite.c b/arch/arm/mach-mmp/aspenite.c index 9e1bd6b..1b788c5 100644 --- a/arch/arm/mach-mmp/aspenite.c +++ b/arch/arm/mach-mmp/aspenite.c @@ -24,6 +24,8 @@ #include <mach/pxa168.h> #include <mach/gpio.h> #include <video/pxa168fb.h> +#include <linux/input.h> +#include ...

Signed-off-by: Mark F. Brown <mark.brown314@gmail.com> --- arch/arm/mach-mmp/include/mach/regs-apmu.h | 12 ++++++++++++ 1 files changed, 12 insertions(+), 0 deletions(-) diff --git a/arch/arm/mach-mmp/include/mach/regs-apmu.h b/arch/arm/mach-mmp/include/mach/regs-apmu.h index 9190305..ac47023 100644 --- a/arch/arm/mach-mmp/include/mach/regs-apmu.h +++ b/arch/arm/mach-mmp/include/mach/regs-apmu.h @@ -33,4 +33,16 @@ #define APMU_FNRST_DIS (1 << 1) #define APMU_AXIRST_DIS (1 << 0) +/* ...

Reset vector for pxa168 is 0xffff_0000 not 0x0 This fix allows reboot to work Mark F. Brown (1): ARM: pxa168: fix corrected reset vector arch/arm/mach-mmp/include/mach/system.h | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --

Signed-off-by: Mark F. Brown <mark.brown314@gmail.com> --- drivers/mtd/nand/pxa3xx_nand.c | 6 ++++++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/drivers/mtd/nand/pxa3xx_nand.c b/drivers/mtd/nand/pxa3xx_nand.c index 4d89f37..4d01cda 100644 --- a/drivers/mtd/nand/pxa3xx_nand.c +++ b/drivers/mtd/nand/pxa3xx_nand.c @@ -1320,6 +1320,7 @@ static int pxa3xx_nand_probe(struct platform_device *pdev) goto fail_free_irq; } +#ifdef CONFIG_MTD_PARTITIONS if ...

I'm announcing the release of the 2.6.27.53 kernel. All users of the 2.6.27 kernel series are very strongly encouraged to upgrade. The updated 2.6.27.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.27.y.git and can be browsed at the normal kernel.org git web browser: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.27.y.git;a=summary thanks, greg k-h ------------ Makefile | 14 ...

I'm announcing the release of the 2.6.34.6 kernel. All users of the 2.6.34 kernel series must upgrade. As Og noted, this is the last .34 kernel being released, please move to .35 at this point if you are relying on this kernel series. The updated 2.6.34.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.34.y.git and can be browsed at the normal kernel.org git web browser: ...

diff --git a/Makefile b/Makefile index 948de60..9447d9d 100644 --- a/Makefile +++ b/Makefile @@ -1,7 +1,7 @@ VERSION = 2 PATCHLEVEL = 6 SUBLEVEL = 27 -EXTRAVERSION = .52 +EXTRAVERSION = .53 NAME = Trembling Tortoise # *DOCUMENTATION* @@ -440,7 +440,11 @@ ifeq ($(config-targets),1) include $(srctree)/arch/$(SRCARCH)/Makefile export KBUILD_DEFCONFIG -config %config: scripts_basic outputmakefile FORCE +config: scripts_basic outputmakefile FORCE + $(Q)mkdir -p include/linux ...

I think you should instead fix your hardware or maybe change --

http://ashtonduelm0383.angelfire.com/ --

It's not that much overhead and we had no complaints when we converted /me not - though I need to look at the patch itself Thanks, tglx --

--- On Thu, 8/26/10, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote: I know you don't say that every time someone makes different assumptions about context than you have. So for now I guess I'll just feel special... And I expect you'd have to admit that if indeed there were some IP reuse happening, then everything I said which assumed reuse would be true. Likewise, that such reuse does happen even for simple stuff like GPIOs (to facilitate reuse of program code ... even on the 8-bit micros ...

The patch below updates a broken web address in the MAINTAINERS file. Signed-off-by: Justin P. Mattock <justinmattock@gmail.com> --- MAINTAINERS | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index 11e34d5..e4dff75 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -3289,7 +3289,7 @@ F: scripts/package/ KERNEL JANITORS ...

Hi Linus, Please pull two PM QoS fixes for 2.6.36 from: git://git.kernel.org/pub/scm/linux/kernel/git/rafael/suspend-2.6.git pm-fixes They fix a kzalloc() call with swapped arguments and a kerneldoc comment that doesn't match the code it describes any more after the last PM QoS update. kernel/pm_qos_params.c | 12 +++++++----- 1 files changed, 7 insertions(+), 5 deletions(-) --------------- David Alan Gilbert (1): PM QoS: Fix kzalloc() parameters swapped in ...

You have won 2,500,000GBP from the Lotto 649. Contact our British Agent for more details. Mr. Datson Galleon via e-mail: datsongalleon649@24.com , Tel: +447031979972. Rita jonhson Lotto649 --

Fix missing consts in h8300's kernel_execve(): arch/h8300/kernel/sys_h8300.c: In function 'kernel_execve': arch/h8300/kernel/sys_h8300.c:59: warning: initialization from incompatible pointer type arch/h8300/kernel/sys_h8300.c:60: warning: initialization from incompatible pointer type Signed-off-by: David Howells <dhowells@redhat.com> --- arch/h8300/kernel/sys_h8300.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/h8300/kernel/sys_h8300.c ...

The perf-events backend for OProfile that Will Deacon wrote in 8c1fc96f6fd1f361428ba805103af0d0eee65179 ("ARM: 6072/1: oprofile: use perf-events framework as backend") is of use to more architectures than just ARM. Move the code into drivers/oprofile/ so that SH can use it instead of the nearly identical copy of its OProfile code. The benefit of the backend is that it becomes necessary to only maintain one copy of the PMU accessor functions for each architecture, with bug fixes and new features ...

Use the perf-events based wrapper for oprofile available in drivers/oprofile. This allows us to centralise the code to control performance counters. Signed-off-by: Matt Fleming <matt@console-pimps.org> --- Paul, I dropped the CONFIG_PERF_EVENTS dependency from the Makefile in this version because to do anything useful we need perf events anyway. arch/sh/oprofile/Makefile | 2 +- arch/sh/oprofile/common.c | 96 ++++++++----------------------------------- ...

From: Will Deacon <will.deacon@arm.com> The current implementation is not entirely safe in the case that oprofile_arch_init() fails. We need to make sure that we always call exit_driverfs() if we've called init_driverfs(). Also, avoid a potential double free when freeing 'counter_config', e.g. don't free 'counter_config' in both oprofile_arch_init() and oprofile_arch_exit(). Signed-off-by: Will Deacon <will.deacon@arm.com> --- arch/arm/oprofile/common.c | 15 ++++++++------- 1 files ...

This series of patches factors out all of cases of the giant switch statement in cciss_ioctl into separate functions. And there's one patch at the end that gets rid of some superfluous if statements in the big passthru path. I've run test programs that exercise all these ioctls and they appear to still work. --- Stephen M. Cameron (13): cciss: factor out cciss_getpciinfo cciss: factor out cciss_getintinfo cciss: factor out cciss_setintinfo cciss: factor out ...

From: Stephen M. Cameron <scameron@beardog.cce.hp.com> Signed-off-by: Stephen M. Cameron <scameron@beardog.cce.hp.com> --- drivers/block/cciss.c | 28 +++++++++++++++------------- 1 files changed, 15 insertions(+), 13 deletions(-) diff --git a/drivers/block/cciss.c b/drivers/block/cciss.c index 5ff5a1d..77db6ea 100644 --- a/drivers/block/cciss.c +++ b/drivers/block/cciss.c @@ -1293,6 +1293,20 @@ static int cciss_setintinfo(ctlr_info_t *h, void __user *argp) return 0; } +static ...

From: Stephen M. Cameron <scameron@beardog.cce.hp.com> Signed-off-by: Stephen M. Cameron <scameron@beardog.cce.hp.com> --- drivers/block/cciss.c | 307 ++++++++++++++++++++++++------------------------- 1 files changed, 151 insertions(+), 156 deletions(-) diff --git a/drivers/block/cciss.c b/drivers/block/cciss.c index 5a84080..a7ec339 100644 --- a/drivers/block/cciss.c +++ b/drivers/block/cciss.c @@ -1500,6 +1500,155 @@ static int cciss_passthru(ctlr_info_t *h, void __user *argp) ...

From: Stephen M. Cameron <scameron@beardog.cce.hp.com> Signed-off-by: Stephen M. Cameron <scameron@beardog.cce.hp.com> --- drivers/block/cciss.c | 65 ++++++++++++++++++++++--------------------------- 1 files changed, 29 insertions(+), 36 deletions(-) diff --git a/drivers/block/cciss.c b/drivers/block/cciss.c index 77db6ea..90c1906 100644 --- a/drivers/block/cciss.c +++ b/drivers/block/cciss.c @@ -1307,6 +1307,34 @@ static int cciss_getnodename(ctlr_info_t *h, void __user *argp) ...

From: Stephen M. Cameron <scameron@beardog.cce.hp.com> Signed-off-by: Stephen M. Cameron <scameron@beardog.cce.hp.com> --- drivers/block/cciss.c | 28 +++++++++++++++------------- 1 files changed, 15 insertions(+), 13 deletions(-) diff --git a/drivers/block/cciss.c b/drivers/block/cciss.c index c1eca37..14380c4 100644 --- a/drivers/block/cciss.c +++ b/drivers/block/cciss.c @@ -1248,6 +1248,20 @@ static int cciss_getpciinfo(ctlr_info_t *h, void __user *argp) return 0; } +static ...

From: Stephen M. Cameron <scameron@beardog.cce.hp.com> Signed-off-by: Stephen M. Cameron <scameron@beardog.cce.hp.com> --- drivers/block/cciss.c | 24 +++++++++++++----------- 1 files changed, 13 insertions(+), 11 deletions(-) diff --git a/drivers/block/cciss.c b/drivers/block/cciss.c index d9d2e5a..013d023 100644 --- a/drivers/block/cciss.c +++ b/drivers/block/cciss.c @@ -1347,6 +1347,18 @@ static int cciss_getheartbeat(ctlr_info_t *h, void __user *argp) return 0; } +static int ...

From: Stephen M. Cameron <scameron@beardog.cce.hp.com> Signed-off-by: Stephen M. Cameron <scameron@beardog.cce.hp.com> --- drivers/block/cciss.c | 34 +++++++++++++++++----------------- 1 files changed, 17 insertions(+), 17 deletions(-) diff --git a/drivers/block/cciss.c b/drivers/block/cciss.c index eef94fa..c1eca37 100644 --- a/drivers/block/cciss.c +++ b/drivers/block/cciss.c @@ -1232,9 +1232,22 @@ static void check_ioctl_unit_attention(ctlr_info_t *h, CommandList_struct *c) ...

From: Miklos Szeredi <mszeredi@suse.cz> This union filesystem is a hybrid of entirely filesystem based (unionfs, aufs) and entierly VFS based (union mounts) solutions. The dentry tree is duplicated from the underlying filesystems, this enables fast cached lookups without adding special support into the VFS. This uses slightly more memory than union mounts, but dentries are relatively small. Inode structures are only duplicated for directories. Regular files, symlinks and special files ...

From: Miklos Szeredi <mszeredi@suse.cz> Hybrid union filesystem uses dummy inodes for non-directories. Allow rename to work in this case despite the inode being the same. Signed-off-by: Miklos Szeredi <mszeredi@suse.cz> --- fs/namei.c | 4 +++- include/linux/fs.h | 1 + 2 files changed, 4 insertions(+), 1 deletion(-) Index: linux-2.6/include/linux/fs.h =================================================================== --- linux-2.6.orig/include/linux/fs.h 2010-08-25 ...

I may be missing something but I looked at your patch series and I see no good reason for this patch at all. You just churned a lot of code for something that you don't even have a need for in the patch set. Your only two new callers of this function could just as easily have used the inode since it isn't doing anything special with the dentry. It actually pulls the inode out of it and uses it in generic_permission and security_inode_permission. If you are going to change this you should also ...

On Thu, Aug 26, 2010 at 12:13 PM, Ville Sundell The ll_temac driver uses phylib. The Ethtool ops should then also be implemented using phylib and not by writing to the ll_temac registers directly. Otherwise changes to the ll_temac speed will not be reflected in the PHY. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. --

[Empty message]

Hmmm... Why couldn't the thread in question set the next sleep time based on the timer period? Yes, if the function ran for longer than the period, there would be a delay, but the POSIX semantics allow such a delay, right? Thanx, Paul --

So we have the following components to this patch: - dynamic min_vruntime -- push the min_vruntime ahead at the rate of the runqueue wide virtual clock. This approximates the virtual clock, esp. when turning off sleeper fairness. And is cheaper than actually computing the virtual clock. It allows for better insertion and re-weighting behaviour, but it does increase overhead somewhat. - special wakeups using the next-buddy to get scheduled 'soon', ...

SIGEV_THREAD is the best proof that the whole posix timer interface was comitte[e]d under the influence of not to be revealed mind-altering substances. I completely object to add timer specific wakeup magic and support for braindead fork orgies to the kernel proper. All that mess can be fixed in user space by using sensible functionality. Providing support for misdesigned crap just for POSIX compliance reasons and to make some of the blind abusers of that very same crap happy would be a ...

C'mon, Thomas!!! That is entirely too sensible!!! ;-) But if you are going to create the thread at timer_create() time, why not just have the new thread block for the desired duration? Thanx, Paul --

Yeah, that sounds exactly like what I proposed about an hour ago on IRC ;) I'm pretty sure that would work. The only thing we might have to be careful about is what happens if the timer re-fires before the thread completes its execution. We might want to let the signal handler detect these overruns somehow. Thanks, -- Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com --

Extracted from a "sched-misc-bits.patch" patch from Peter Zijlstra <a.p.zijlstra@chello.nl>. Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com> CC: Peter Zijlstra <a.p.zijlstra@chello.nl> --- kernel/sched_fair.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) Index: linux-2.6-lttng.git/kernel/sched_fair.c =================================================================== --- linux-2.6-lttng.git.orig/kernel/sched_fair.c +++ ...

[Empty message]

Add the fair sleeper feature which disables sleeper extra vruntime boost on wakeup. This is makes the DYN_MIN_VRUNTIME feature behave better by keeping the min_vruntime value somewhere between MIN_vruntime and max_vruntime (see /proc/sched_debug output with CONFIG_SCHED_DEBUG=y). Turning on this knob is typically bad for interactivity. This is why a later patch introduces the "FAIR_SLEEPERS_INTERACTIVE" feature, which provides this combination of ...

Rename task struct in_iowait to sched_in_iowait, since it's only scheduler-specific. Extracted from a patch originally from Peter Zijlstra. Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com> CC: Peter Zijlstra <a.p.zijlstra@chello.nl> --- include/linux/sched.h | 7 +++---- kernel/sched.c | 8 ++++---- kernel/sched_fair.c | 2 +- 3 files changed, 8 insertions(+), 9 deletions(-) Index: ...

Incorrect handling of the following case: INTERACTIVE INTERACTIVE_SOMETHING_ELSE The comparison only checks up to each element's length. Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com> CC: Peter Zijlstra <a.p.zijlstra@chello.nl> --- kernel/sched.c | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) Index: linux-2.6-lttng.git/kernel/sched.c =================================================================== --- ...

Greetings I have been waiting for you to contact me for your Confirmable Bank-draft of $750.000.00 United States Dollars,but I did not hear from you. Then I went and deposited the Draft with FedEx COURIER SERVICE,The only money you will send to the FedEX COURIER SERVICE to deliver your Draft direct to your postal Address in your country is ($150.00 US) Dollars only being Security Keeping Fee of the Courier Company. 1) FULL NAMES: 2) CONTACT ADDRESS: 3) PHONE NUMBER/FAX: 4) COUNTRY: ...

We utilize the IOMMU_INIT macros to create this dependency: [null] | [pci_xen_swiotlb_detect] | [pci_swiotlb_detect_override] | [pci_swiotlb_detect_4gb] | +-------+--------+ / \ [detect_calgary] [gart_iommu_hole_init] | [amd_iommu_detect] Meaning that 'amd_iommu_detect' will be called ...

We return 1 if the IOMMU has been detected. Zero or an error number if we failed to find it. This is in preperation of using the IOMMU_INIT so that we can detect whether an IOMMU is present. I have not tested this for regression on Calgary, nor on AMD Vi chipsets as I don't have that hardware. CC: Muli Ben-Yehuda <muli@il.ibm.com> CC: "Jon D. Mason" <jdmason@kudzu.us> CC: "Darrick J. Wong" <djwong@us.ibm.com> CC: Jesse Barnes <jbarnes@virtuousgeek.org> CC: David Woodhouse ...

Commit-ID: 480125ba49ba62be93beea37770f266846e077ab Gitweb: http://git.kernel.org/tip/480125ba49ba62be93beea37770f266846e077ab Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> AuthorDate: Thu, 26 Aug 2010 13:57:57 -0400 Committer: H. Peter Anvin <hpa@linux.intel.com> CommitDate: Thu, 26 Aug 2010 15:13:13 -0700 x86, iommu: Make all IOMMU's detection routines return a value. We return 1 if the IOMMU has been detected. Zero or an error number if we failed to find it. This is in ...

Commit-ID: ee1f284f38c8dfcbc7b656915a039dde016de7d3 Gitweb: http://git.kernel.org/tip/ee1f284f38c8dfcbc7b656915a039dde016de7d3 Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> AuthorDate: Thu, 26 Aug 2010 13:58:05 -0400 Committer: H. Peter Anvin <hpa@linux.intel.com> CommitDate: Thu, 26 Aug 2010 15:14:52 -0700 x86, iommu: Utilize the IOMMU_INIT macros functionality. We remove all of the sub-platform detection/init routines and instead use on the .iommu_table array of structs ...

Commit-ID: 22e6daf41ba28ddc06295e42859b266f737b3e99 Gitweb: http://git.kernel.org/tip/22e6daf41ba28ddc06295e42859b266f737b3e99 Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> AuthorDate: Thu, 26 Aug 2010 13:58:03 -0400 Committer: H. Peter Anvin <hpa@linux.intel.com> CommitDate: Thu, 26 Aug 2010 15:14:30 -0700 x86, GART/AMD-VI: Make AMD GART and IOMMU use IOMMU_INIT_* macros. We utilize the IOMMU_INIT macros to create this dependency: [null] ...

So we have yet another magic section in vmlinux.lds.S A nice comemnt that expalins what this is used for and why it is discardable etc. would be nice. Lots of magic sections in same file miss this, but thats not an example to follwow. Sam --

Per our discussion at: http://lkml.org/lkml/2010/8/2/282 I've implemented an RFC set of patches to address the problem. This patch set adds a mechanism to "modularize" the IOMMUs we have on X86. Currently the count of IOMMUs is up to six and they have a complex relationship that requires careful execution order. 'pci_iommu_alloc' does that today, but most folks are unhappy with how it does it. This patch set addresses this and also paves a mechanism to jettison unused IOMMUs during ...

Commit-ID: efa631c26d3bb1162b8f95008801db602217f52b Gitweb: http://git.kernel.org/tip/efa631c26d3bb1162b8f95008801db602217f52b Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> AuthorDate: Thu, 26 Aug 2010 13:57:59 -0400 Committer: H. Peter Anvin <hpa@linux.intel.com> CommitDate: Thu, 26 Aug 2010 15:13:29 -0700 x86, swiotlb: Simplify SWIOTLB pci_swiotlb_detect routine. In 'pci_swiotlb_detect' we used to do two different things: a). If user provided 'iommu=soft' or ...

Commit-ID: c116c5457c46edb767df6f4e36d4905e3514ad37 Gitweb: http://git.kernel.org/tip/c116c5457c46edb767df6f4e36d4905e3514ad37 Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> AuthorDate: Thu, 26 Aug 2010 13:58:00 -0400 Committer: H. Peter Anvin <hpa@linux.intel.com> CommitDate: Thu, 26 Aug 2010 15:13:37 -0700 x86, swiotlb: Make SWIOTLB use IOMMU_INIT_* macros. We utilize the IOMMU_INIT macros to create this dependency: [pci_xen_swiotlb_detect] | ...

Commit-ID: d2aa232f3d0b5a3e22f91b736fe68eddcf0d5ea3 Gitweb: http://git.kernel.org/tip/d2aa232f3d0b5a3e22f91b736fe68eddcf0d5ea3 Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> AuthorDate: Thu, 26 Aug 2010 13:58:02 -0400 Committer: H. Peter Anvin <hpa@linux.intel.com> CommitDate: Thu, 26 Aug 2010 15:14:15 -0700 x86, calgary: Make Calgary IOMMU use IOMMU_INIT_* macros. We utilize the IOMMU_INIT macros to create this dependency: [pci_xen_swiotlb_detect] | ...

We utilize the IOMMU_INIT macros to create this dependency: [null] | [pci_xen_swiotlb_detect] | [pci_swiotlb_detect_override] | [pci_swiotlb_detect_4gb] In other words, we set 'pci_xen_swiotlb_detect' to be the first detection to be run during start. CC: H. Peter Anvin <hpa@zytor.com> CC: Fujita Tomonori <fujita.tomonori@lab.ntt.co.jp> Signed-off-by: Konrad Rzeszutek Wilk ...

Commit-ID: 5bef80a4b826b9cee1c6aec7ecc371ec395260cc Gitweb: http://git.kernel.org/tip/5bef80a4b826b9cee1c6aec7ecc371ec395260cc Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> AuthorDate: Thu, 26 Aug 2010 13:57:58 -0400 Committer: H. Peter Anvin <hpa@linux.intel.com> CommitDate: Thu, 26 Aug 2010 15:13:19 -0700 x86, iommu: Add proper dependency sort routine (and sanity check). We are using a very simple sort routine which sorts the .iommu_table array in the order of ...

On Thu, Aug 26, 2010 at 10:57:33AM -0700, David Brownell wrote: I would agree yesterday, but now I tend to like anton_gpio.c. :-D You seemed to be fine with meaningless amba-9999 or dw_abc names, but now, when I propose such a marvellous name, you seem to lean to a synonym of an old one, the one that I used in v1? Wouldn't it be a step backwards? :-) Just kiding, of course. basic_mmio.c works for me. I also think it makes sense to drop gpio_ prefix, as the driver is already in gpio/ ...

Should be fixed by a8ec105c0764c848d59f18a31f91fa00c99b2e7f -- Matthew Garrett | mjg59@srcf.ucam.org --

Seems reasonable. Still, if there is no write IO going on and no congestion there seems to be no point going to sleep for the full timeout. It still feels wrong. -- Mel Gorman Part-time Phd Student Linux Technology Center University of Limerick IBM Dublin Software Lab --

On every retired io request the congestion state on the bdi is checked and the congestion waitqueue woken up. So without congestion, we still only wait until the next write retires, but without any IO, we sleep the full timeout. Check __freed_requests() in block/blk-core.c. --

Verilog ? Its far far more primitive than that. You'll find exactly that arrangement in prehistoric 8bit micro support chips - eg the 6522. In fact the only reason I can see for not using it on primitive 8bit micro No they are implementing trivial common sense logic. It's a bit like complaining we have multiple drivers that use addition. I think you need a reality check. Its a VLSI undergraduate project level device, or was back when they taught undergraduates a sampling of chip design by ...

Half the thing here is that it's barely IP - it's the sort of thing that's so trivial to implement that it'd take more time to locate a suitable IP than to just hook up the output pins to the register map Essentially all this sort of GPIO controller is is a straight wire through of a set of register bits to an output signal (especially if you don't have a separate clear register). It's the first thing a hardware engineer would think of for implementing this - it's not even copy and paste ...

You want to send this to postmaster@vger.kernel.org (cc-ed). --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** --

More likely, to stop a loop in too_many_isolated() consuming CPU time it I think the reasoning here might be a little off. How about; If many processes enter direct reclaim or memory compaction, too many pages can get isolated. In this situation, too_many_isolated() can call congestion_wait() but if there is no congestion, it fails to go to sleep and instead spins until it's quota expires. This patch checks if congestion_wait() returned without sleeping. If it did because there was no ...

Fix a comma that got accidentally deleted from sys_osf_statfs() leading to the following warning: arch/alpha/kernel/osf_sys.c: In function 'SYSC_osf_statfs': arch/alpha/kernel/osf_sys.c:255: error: syntax error before 'buffer' Signed-off-by: David Howells <dhowells@redhat.com> --- arch/alpha/kernel/osf_sys.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/arch/alpha/kernel/osf_sys.c b/arch/alpha/kernel/osf_sys.c index fb58150..5d1e6d6 100644 --- ...

When alloc fails, free_table is being called. Depending on the number of bytes requested, we determine if we are going to call _get_free_page() or kmalloc(). When alloc fails, our math is wrong (due to sg_size - 1), and the last buffer is wrongfully assumed to have been allocated by kmalloc. Hence, kfree gets called and a panic occurs. This fix sets the end marker and allows the proper freeing of the buffers. Signed-off-by: Olusanya Soyannwo <c23746@motorola.com> Cc: Tejun Heo ...

email subject Or patch description. It's neither generic (IP-block-specific) nor simple. It's not simple; I've seen far simpler GPIO controllers. Just rename it to match the IP block used. That removes all confusion. Engineers will be able to know more easily whether this driver is even relevant to them. An example might be "amba-9999 (a made-up number, likely not matching a GPIO controller). DesignWare drivers tend to use dw_* prefixes. - Dave --

The Anton GPIO controllers are not so complex controllers that may be found in various on-board FPGAs that are used to control board's switches, LEDs, chip-selects, Ethernet/USB PHY power, etc. Usually these controllers do not privide any means of pin setup (in/out/open drain). The driver provides: - Support for 8/16/32/64 bits registers; - Support for GPIO controllers with clear/set registers; - Support for GPIO controllers with a single "data" register; - Support for big endian bits/GPIOs ...

Signed-off-by: Guenter Roeck <guenter.roeck@ericsson.com> --- tempX_emergency will be used by max6696. It can also be used for other chips supporting three upper temperature limits. Documentation/hwmon/sysfs-interface | 6 ++++++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/Documentation/hwmon/sysfs-interface b/Documentation/hwmon/sysfs-interface index ff45d1f..1ceb2b9 100644 --- a/Documentation/hwmon/sysfs-interface +++ b/Documentation/hwmon/sysfs-interface @@ -310,6 ...

Do you have a better wording in mind ? Guenter --

$ find -name TODO | wc -l 40 --

Since T: and L: are already taken, add U: for URL of todo list. Also add the RCU todo list to both the RCU and RCUTORTURE projects. Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com> diff --git a/MAINTAINERS b/MAINTAINERS index 3f21c27..1c57186 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -103,6 +103,7 @@ Descriptions of section entries: matches patches or files that contain one or more of the words printk, pr_info or pr_err One regex pattern per line. ...

These W: links from MAINTAINERS seem dead. Should they be ...

TODO might disappear without implementation, if you decide that the idea Yep, I do not want to be restricted to updating TODO during merge window only as the changes to the list are not likely to count as bugfixes ;) -- Dmitry --

While you are at it, I am aware at least of these additional ones: http://vger.kernel.org/~davem/net_todo.html http://wireless.kernel.org/en/developers/todo-list https://ieee1394.wiki.kernel.org/index.php/To_Do http://selinuxproject.org/page/Kernel_Development -- Jiri Kosina SUSE Labs, Novell Inc. --

Those folk might be better playing/practicing/honing skills in staging where there already are TODO files. --

Did you have an alternate suggestion? Do you prefer a Grand Unified Todo List? I don't mind the kernelnewbies list/location, but we need to give it some TLC. --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** --

That may not be the case if you use a public todo list on rememberthemilk.com. It doesn't make sense to end multiple todo list names with "todo" for on site that's specifically designed to help with todo lists. I like the idea of a separate letter for todo lists URLs. Sarah Sharp --

Also renamed NETWORKING patch queue from "W:" to "Q:" Signed-off-by: Joe Perches <joe@perches.com> --- MAINTAINERS | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index a1df54b..3d29d8c 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -2346,6 +2346,7 @@ FIREWIRE SUBSYSTEM M: Stefan Richter <stefanr@s5r6.in-berlin.de> L: linux1394-devel@lists.sourceforge.net ...

On Thu, 26 Aug 2010 09:29:23 -0700 I have to say that I'm not yet convinced that keeping a todo list in a place that's not with the actual source code does not give me warm fuzzy feelings. Every time we've kept information about the source code separate from our source code it's been a failure; it gets out of sync fast and it just adds to the maintenance. A git commit that both fixes an issue and removed the line from the todo file (or moves it to a "done" section, whatever) is the ...

I don't have a tree that gets pulled. Andrew Morton generally picks up MAINTAINERS fixes. --

alright.. I sent it out to trivial.. if they want it's it there.. Justin P. Mattock --

Iram reported compaction's too_many_isolated loops forever. (http://www.spinics.net/lists/linux-mm/msg08123.html) The meminfo of situation happened was inactive anon is zero. That's because the system has no memory pressure until then. While all anon pages was in active lru, compaction could select active lru as well as inactive lru. That's a different thing with vmscan's isolated. So we has been two too_many_isolated. While compaction can isolated pages in both active and inactive, current ...

If congestion_wait() is called when there is no congestion, the caller will wait for the full timeout. This can cause unreasonable and unnecessary stalls. There are a number of potential modifications that could be made to wake sleepers but this patch measures how serious the problem is. It keeps count of how many congested BDIs there are. If congestion_wait() is called with no BDIs congested, the tracepoint will record that the wait was unnecessary. Signed-off-by: Mel Gorman ...

I am not convinced that unnecessary is the right word. On a workload without any IO (i.e. no congestion_wait() necessary, ever), I noticed the VM regressing both in time and in reclaiming the right pages when simply removing congestion_wait() from the direct reclaim paths (the one in __alloc_pages_slowpath and the other one in do_try_to_free_pages). So just being stupid and waiting for the timeout in direct reclaim while kswapd can make progress seemed to do a better job for that load. I ...

Hmm.. Now congestion_wait's semantics "wait for _a_ backing_dev to become uncongested" But this seems to consider whole backing dev. Is your intention? or Am I missing now? -- Kind regards, Minchan Kim --

Reviewed-by: Johannes Weiner <hannes@cmpxchg.org> --

Stub out vm_get_page_prot() if there's no MMU. This was added by commit: commit 804af2cf6e7af31d2e664b54e657dddd9b531dbd Author: Hugh Dickins <hugh@veritas.com> Date: Wed Jul 26 21:39:49 2006 +0100 Subject: [AGPGART] remove private page protection map and is used in commit: commit c07fbfd17e614a76b194f371c5331e21e6cffb54 Author: Daniel De Graaf <dgdegra@tycho.nsa.gov> Date: Tue Aug 10 18:02:45 2010 -0700 Subject: fbmem: VM_IO set, but not propagated in the fbmem video ...

Per-thread events with a cpu filter, i.e., cpu != -1, were not reporting correct timings when the thread never ran on the monitored cpu. The time enabled was reported as a negative value. This patch fixes the problem by updating tstamp_stopped, tstamp_running in event_sched_out() for events with filters and which are marked as INACTIVE. The function group_sched_out() is modified to systematically call into event_sched_out() to avoid duplicating the timing adjustment code twice. With the ...

we've got a local patch doing pretty much the same thing, but it's waiting on driver patches being applied. so once those are all set, i can push up the Blackfin one. -mike --

Add a missing dependency (mach/blackfin.h) to asm/irqflags.h so that bfin_read_IMASK() can be used by inline functions. Signed-off-by: David Howells <dhowells@redhat.com> --- arch/blackfin/include/asm/irqflags.h | 9 ++++++++- 1 files changed, 8 insertions(+), 1 deletions(-) diff --git a/arch/blackfin/include/asm/irqflags.h b/arch/blackfin/include/asm/irqflags.h index 813a1af..f3ed931 100644 --- a/arch/blackfin/include/asm/irqflags.h +++ b/arch/blackfin/include/asm/irqflags.h @@ -8,6 ...

Rename the PC2() symbol in the generic DES crypto module to be prefixed with DES_ to avoid collision with arch code (Blackfin in this case). Signed-off-by: David Howells <dhowells@redhat.com> --- crypto/des_generic.c | 130 +++++++++++++++++++++++++------------------------- 1 files changed, 65 insertions(+), 65 deletions(-) diff --git a/crypto/des_generic.c b/crypto/des_generic.c index 249f903..873818d 100644 --- a/crypto/des_generic.c +++ b/crypto/des_generic.c @@ -614,7 +614,7 @@ ...

Fix the IRQ flag handling naming. In linux/irqflags.h under one configuration, it maps: local_irq_enable() -> raw_local_irq_enable() local_irq_disable() -> raw_local_irq_disable() local_irq_save() -> raw_local_irq_save() ... and under the other configuration, it maps: raw_local_irq_enable() -> local_irq_enable() raw_local_irq_disable() -> local_irq_disable() raw_local_irq_save() -> local_irq_save() ... This is quite confusing. There should be one set of names expected of ...

[Note that this patch only alters X86, FRV, MN10300, ARM and Blackfin at the moment. The other arches will need altering too as part of this patch]. The final patch of the series makes the naming of the general irq flag functions sane. Currently, under one configuration, linux/irqflags.h maps: local_irq_enable() -> raw_local_irq_enable() local_irq_disable() -> raw_local_irq_disable() local_irq_save() -> raw_local_irq_save() ... and under the other configuration, it ...

unfortunately this is one Blackfin define we cant easily hide away in a peripheral-specific header and avoid global namespace pollution. it represents a pin that can be used across different peripherals. so it'd be nice if the crypto/ guys took this change :) Signed-off-by: Mike Frysinger <vapier@gentoo.org> -mike --

From: Borislav Petkov <borislav.petkov@amd.com> When the Overflow MCi_STATUS bit is set, EDAC reports the lost error with a "no information available" message which often puzzles users parsing the dmesg. This doesn't make much sense since this error has been lost anyway so no need for reporting it separately. Thus, report the overflow bit setting in the MCE dump instead. While at it, remove reporting of MiscV and ErrorEnable (en) which are superfluous. Now it looks like this: [ ...

This patch set contains a collection of patches to the SGI UV GRU driver. These patches fix various bugs found in the testing of the driver on real hardware. No changes are made to non-UV files. --

From: Jack Steiner <steiner@sgi.com> Reorder the servicing of CBR completion interrupts & TLB miss interrupts. There is a small performance gain to service TLB misses first. Completion interrupts are rare. Signed-off-by: Jack Steiner <steiner@sgi.com> --- drivers/misc/sgi-gru/grufault.c | 24 +++++++++++++----------- 1 file changed, 13 insertions(+), 11 deletions(-) Index: linux/drivers/misc/sgi-gru/grufault.c =================================================================== --- ...

From: Jack Steiner <steiner@sgi.com> Update the GRU instruction macros to match what is actually implemented in initial silicon. Signed-off-by: Jack Steiner <steiner@sgi.com> --- drivers/misc/sgi-gru/gru_instructions.h | 2 -- 1 file changed, 2 deletions(-) Index: linux/drivers/misc/sgi-gru/gru_instructions.h =================================================================== --- linux.orig/drivers/misc/sgi-gru/gru_instructions.h 2010-06-09 08:11:31.528038315 -0500 +++ ...

From: Jack Steiner <steiner@sgi.com> SGI UV driver. Delete some debug code that has outlived it's usefullness. The code is not part of a supported API Signed-off-by: Jack Steiner <steiner@sgi.com> --- drivers/misc/sgi-gru/grufile.c | 25 ------------------------- drivers/misc/sgi-gru/grulib.h | 3 --- 2 files changed, 28 deletions(-) Index: linux/drivers/misc/sgi-gru/grufile.c =================================================================== --- ...

From: Jack Steiner <steiner@sgi.com> If the GRU malfunctions, print a message instead of panicing the system. This simplifies debugging since some of the debug tools can be used on a live system. Flush the cache on instruction timeouts in case the malfunction is related to a coherency issue (never seen this but I'm paranoid). Signed-off-by: Jack Steiner <steiner@sgi.com> --- drivers/misc/sgi-gru/gruhandles.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) Index: ...

From: Jack Steiner <steiner@sgi.com> Header file cleanup & reorganization. A variant of the gru_instructions.h header file is part of the user API. Move items that are NOT part of the user API from this header file to internal header files. - move the CBX definition - move the exception retrybits - remove the option for mapped/unmapped mode from the instruction macros. Users always run in mapped mode; the kernel always runs in ummapped mode. This option does not need to an ...

From: Jack Steiner <steiner@sgi.com> This patch substantially reworks the way the GRU driver steals contexts from users in order to use the GRU resources for kernel use. The new version fixes some ugly locking bugs and is overall more efficient. Signed-off-by: Jack Steiner <steiner@sgi.com> --- drivers/misc/sgi-gru/grufault.c | 2 drivers/misc/sgi-gru/grukservices.c | 271 +++++++++++++++++------------------- drivers/misc/sgi-gru/gruprocfs.c | 12 + ...

From: Jack Steiner <steiner@sgi.com> The GRU hardware has reserved a few bits for software use. Add these "software reserved" fields to the structure definitions. Signed-off-by: Jack Steiner <steiner@sgi.com> --- drivers/misc/sgi-gru/gru_instructions.h | 19 +++++++++++++------ 1 file changed, 13 insertions(+), 6 deletions(-) Index: linux/drivers/misc/sgi-gru/gru_instructions.h =================================================================== --- ...

From: Jack Steiner <steiner@sgi.com> Update the CBRSTATE definitions to match what was actually implemented in hardware. Signed-off-by: Jack Steiner <steiner@sgi.com> --- drivers/misc/sgi-gru/gruhandles.h | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) Index: linux/drivers/misc/sgi-gru/gruhandles.h =================================================================== --- linux.orig/drivers/misc/sgi-gru/gruhandles.h 2010-07-19 10:25:57.000000000 -0500 +++ ...

From: Jack Steiner <steiner@sgi.com> Add the GRU hub number to the output of the GRU cch_status & gru_status files (in /proc/sgi_uv/gru). Signed-off-by: Jack Steiner <steiner@sgi.com> --- drivers/misc/sgi-gru/gruprocfs.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) Index: linux/drivers/misc/sgi-gru/gruprocfs.c =================================================================== --- linux.orig/drivers/misc/sgi-gru/gruprocfs.c 2010-06-09 08:11:42.456084620 ...

From: Jack Steiner <steiner@sgi.com> Delete unused structure that was left over from debugging. Signed-off-by: Jack Steiner <steiner@sgi.com> --- drivers/misc/sgi-gru/gru.h | 15 --------------- 1 file changed, 15 deletions(-) Index: linux/drivers/misc/sgi-gru/gru.h =================================================================== --- linux.orig/drivers/misc/sgi-gru/gru.h 2010-06-09 08:11:45.375993599 -0500 +++ linux/drivers/misc/sgi-gru/gru.h 2010-06-09 08:11:48.856038221 ...

From: Jack Steiner <steiner@sgi.com> Change the name of GRU_GSEG_PAGESIZE to GRU_MIN_GSEG_PAGESIZE to more accurately reflect it's use. This is in preparation for allocating contexts using hugepages. Signed-off-by: Jack Steiner <steiner@sgi.com> --- drivers/misc/sgi-gru/gru.h | 10 ++-------- drivers/misc/sgi-gru/gru_instructions.h | 2 +- 2 files changed, 3 insertions(+), 9 deletions(-) Index: ...

From: Jack Steiner <steiner@sgi.com> Misc clean: - update debug messages - update stale comments in the code Signed-off-by: Jack Steiner <steiner@sgi.com> --- drivers/misc/sgi-gru/grufault.c | 1 - drivers/misc/sgi-gru/grukservices.h | 3 +-- drivers/misc/sgi-gru/grulib.h | 1 - drivers/misc/sgi-gru/grumain.c | 26 +++++++++++++------------- drivers/misc/sgi-gru/grutlbpurge.c | 1 - 5 files changed, 14 insertions(+), 18 deletions(-) Index: ...

Hello. You've dropped call check_stack_overflow() call in do_IRQ() -- was that intentional? WBR, Sergei --

Of course NO. It is awful, I have say. I spent a lot of time to struggle with git yesterday. When I revised the coding style problem and tried to format-patch to master branch, then I got 2 patches but not all in one. How could I rebase my working copy and get an all-in-one patch of this? I tried to revert my commit and redo this patch, then I lost to calling it in do_IRQ(); Best regards, --

When I am running the kgdbts to test the hw_breakpoint_layer with kgdb, I get a call trace as following and this problem is hardly to reproduce. Maybe the root cause was from kgdb/hw_breakpoint_layer, but add a checking is good to us and harmless. :-) Thanks, Dongdong ------------[ cut here ]------------ WARNING: at /buildarea/ddeng/build/linux/drivers/misc/kgdbts.c:703 run_simple_test+0x1fc/0x2a0() Hardware name: Moon Creek platform Modules linked in: Pid: 668, comm: sh Tainted: ...

--

Remove initramfs_data.{lzo,lzma,gz,bz2}.S variants and use a common implementation in initramfs_data.S. The common implementation expects the file name of the initramfs to be defined in INITRAMFS_IMAGE. Change the Makefile to set the INITRAMFS_IMAGE define symbol according to the selected compression method. Signed-off-by: Hendrik Brueckner <brueckner@linux.vnet.ibm.com> --- usr/Makefile | 6 ++++-- usr/initramfs_data.S | 5 +++-- usr/initramfs_data.bz2.S | 29 ...

Hi, After successfully building the kernel version 2.6.36-rc2-git4(commitid d4348c678977c) with the config file attached(used make oldconfig), P5 and P6 power machines fails to reboot with the following logs Logs collected while rebooting into today next, same occurs with the upstream kernel too. Please wait, loading kernel... Allocated 01a00000 bytes for kernel @ 03500000 Elf64 kernel loaded... Loading ramdisk... ramdisk loaded 00841ae7 @ 04f00000 OF stdout device is: ...

This patch implement fetching POSIX ACL from the server Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> --- fs/9p/acl.c | 63 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ fs/9p/xattr.c | 4 +++ fs/9p/xattr.h | 2 + 3 files changed, 69 insertions(+), 0 deletions(-) diff --git a/fs/9p/acl.c b/fs/9p/acl.c index 5de599b..e122e63 100644 --- a/fs/9p/acl.c +++ b/fs/9p/acl.c @@ -93,3 +93,66 @@ int v9fs_check_acl(struct inode *inode, int mask) } ...

We need update the acl value on chmod Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> --- fs/9p/acl.c | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++++ fs/9p/acl.h | 5 ++++ fs/9p/vfs_inode.c | 4 +++ 3 files changed, 64 insertions(+), 0 deletions(-) diff --git a/fs/9p/acl.c b/fs/9p/acl.c index fc06467..d717487 100644 --- a/fs/9p/acl.c +++ b/fs/9p/acl.c @@ -97,6 +97,61 @@ int v9fs_check_acl(struct inode *inode, int mask) return ...

Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> --- Documentation/filesystems/9p.txt | 4 +++- fs/9p/acl.c | 37 ++++++++++++++++++++++++++++++++++++- fs/9p/fid.c | 1 + fs/9p/v9fs.c | 12 ++++++++++++ fs/9p/v9fs.h | 8 ++++++-- fs/9p/vfs_inode.c | 14 ++++++++++---- fs/9p/vfs_super.c | 16 +++++++++++----- 7 files changed, 79 insertions(+), 13 ...

--- Gigabit Ethernet driver of Topcliff PCH Topcliff PCH is the platform controller hub that is going to be used in Intel's upcoming general embedded platform. All IO peripherals in Topcliff PCH are actually devices sitting on AMBA bus. Topcliff PCH has Gigabit Ethernet I/F. Using this I/F, it is able to access system devices connected to Gigabit Ethernet. Signed-off-by: Masayuki Ohtake <masa-korg@dsn.okisemi.com> --- drivers/net/Kconfig | 5 + drivers/net/Makefile ...

Hi Sam Thank you for your comment. The reply's comment was buried in following. I will modify this patch. Thanks, Ohtake(OKISEMI) ----- Original Message ----- From: "Sam Ravnborg" <sam@ravnborg.org> To: "Masayuki Ohtake" <masa-korg@dsn.okisemi.com> Cc: "LKML" <linux-kernel@vger.kernel.org>; "ML netdev" <netdev@vger.kernel.org>; "Greg Rose" <gregory.v.rose@intel.com>; "Maxime Bizon" <mbizon@freebox.fr>; "Kristoffer Glembo" <kristoffer@gaisler.com>; "Ralf Baechle" ...

Use cpu_relax here to allow other hyper-thread to run. /* wait busy */ while ((ioread32(&hw->reg->ADDR_MASK) & PCH_GBE_BUSY)) cpu_relax(); --

+static int pch_gbe_probe(struct pci_dev *pdev, + const struct pci_device_id *pci_id) +{ + struct net_device *netdev; + struct pch_gbe_adapter *adapter; + unsigned long mmio_start; + unsigned long mmio_len; + int i, ret; + + PCH_GBE_DEBUG("pch_gbe_probe\n"); + ret = pci_enable_device(pdev); + if (ret) + return ret; + + if (!dma_set_mask(&pdev->dev, DMA_BIT_MASK(64)) + && !dma_set_coherent_mask(&pdev->dev, DMA_BIT_MASK(64))) { + ; + } else { + ret = dma_set_mask(&pdev->dev, ...

On Thu, 26 Aug 2010 18:56:55 +0900 Don't invent your own mutex mechanism. Either use spin lock or mutex. -- --

or perhaps better still convert to netdev_info My message logging order preference: if there's a netif_msg_<type> and a struct net_device netif_<level> (struct private *, netif_msg_<type>, struct net_device *, fmt, args...) if there's a struct net_device netdev_<level> (struct net_device *, fmt, args...) if there's a struct device dev_<level> (struct device *, fmt, args...) otherwise pr_<level> (fmt, args...) --

On Thu, 26 Aug 2010 18:56:55 +0900 Should be const -- --

On Thu, 26 Aug 2010 18:56:55 +0900 No need for cast to u32 on the masking: ecmd->supported &= ~(SUPPORTED_TP | SUPPORTED_1000baseT_Half); ecmd->advertising &= ~(ADVERTISED_TP | ADVERTISED_1000baseT_Half); Awkward use of if, and don't set other bits in duplex if (!netif_carrier_ok(adapter->netdev)) ecmd->speed = -1; -- --

Hmmm it is definitely btrfs related. Do you continue to get it after rebooting? -chris --

No, after rebooting chromium refused to open (like it did during the BUG) but no BUG: message appeared. Then I deleted all chromium cache+config from the memory card and chromium worked again, but after suspending to RAM I noticed this: [ 6035.423238] PM: Syncing filesystems ... done. [ 6036.524889] Freezing user space processes ... [ 6056.533079] Freezing of tasks failed after 20.00 seconds (1 tasks refusing to freeze): [ 6056.533119] chrome D 00000000ffffffff 0 7028 7015 ...

This adds a sysfs file at /sys/power/coresight_save which is used to control if the ETM and debug components' states should be saved and restored across OFF modes. Signed-off-by: Alexander Shishkin <virtuoso@slind.org> Cc: Tony Lindgren <tony@atomide.com> Cc: Russell King <linux@arm.linux.org.uk> Cc: Paul Walmsley <paul@pwsan.com> Cc: Kevin Hilman <khilman@deeprootsystems.com> Cc: linux-omap@vger.kernel.org Cc: linux-arm-kernel@lists.infradead.org Cc: linux-kernel@vger.kernel.org --- ...

Currently JBD2 relies blkdev_issue_flush() draining the queue when ASYNC_COMMIT feature is set. This property is going away so make JBD2 wait for buffers it needs on its own before submitting the cache flush. Signed-off-by: Jan Kara <jack@suse.cz> Signed-off-by: Tejun Heo <tj@kernel.org> --- Fixed overindentation noticed by Sergei. git tree updated accordingly. Thanks. fs/jbd2/commit.c | 29 ++++++++++++++++------------- 1 files changed, 16 insertions(+), 13 deletions(-) diff --git ...

From 49f4cef00a1bd3c79fb2fe1f982c5157f0792867 Mon Sep 17 00:00:00 2001 From: Jan Kara <jack@suse.cz> Currently JBD2 relies blkdev_issue_flush() draining the queue when ASYNC_COMMIT feature is set. This property is going away so make JBD2 wait for buffers it needs on its own before submitting the cache flush. Signed-off-by: Jan Kara <jack@suse.cz> Signed-off-by: Tejun Heo <tj@kernel.org> --- This patch is necessary before enabling flush/fua support in jbd2. The flush-fua git tree has been ...

Hi, booting 2.6.36-rc2-git4 (commit d4348c678977c7093438bbbf2067c49396ae941b) results in a screen resolution of 1024x768 instead of 1680x1050. It works fine with 2.6.35.2. The framebuffer console uses the correct resolution, but only uses a part of the screen for text output. Xorg output looks distorted. Xorg log is attached. $ xrandr Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096 VGA1 disconnected (normal left inverted right x axis y axis) DVI1 connected ...

There are drivers/leds/leds-pwm.c and drivers/video/backlight/pwm_bl.c that implement led and backlight drivers based on generic pwm interface. -- Sincerely yours, Mike. --

This patch exports functions to set and get ab8500 pwm intensity, which in turn is used by backlight/led driver. Signed-off-by: Arun Murthy <arun.murthy@stericsson.com> Acked-by: Mattias Wallin <mattias.wallin@stericsson.com> Acked-by: Linus Walleij <linus.walleij@stericsson.com> --- drivers/mfd/Kconfig | 8 ++ drivers/mfd/Makefile | 1 + drivers/mfd/ab8500-pwm.c | 191 +++++++++++++++++++++++++++++++++ ...

This patch adds led class driver for controlling u8500 leds and backlight. LED intensity is controlled by by Ananlog Baseband Chip AB8500 Pulse Width Modulation(pwm). Signed-off-by: Arun Murthy <arun.murthy@stericsson.com> Acked-by: Mattias Wallin <mattias.wallin@stericsson.com> Acked-by: Linus Walleij <linus.walleij@stericsson.com> --- drivers/leds/Kconfig | 9 ++ drivers/leds/Makefile | 1 + drivers/leds/leds-ab8500.c | 201 ++++++++++++++++++++++++++++++++++++++++++++ ...

From: Hugh Dickins <hughd@google.com> Interesting, is the condition which allows this to trigger specific to this merge window or was it always possible? --

Hi Hugh, I don't get it, the anon_vma can be freed and reused only after we run rcu_read_unlock(). And the anon_vma->root can't change unless the anon_vma is freed and reused. Last but not the least by the time page->mapping points to "anon_vma" the "anon_vma->root" is already initialized and stable. The page_mapped test is only relevant against the rcu_read_lock, not the spin_lock, so how it can make a difference to run it twice inside the same rcu_read_lock protected critical section? ...

From: Hugh Dickins <hughd@google.com> Ok, because I've been seeing mysterious hangs recently on one of my sparc64 boxes and I was wondering if this might explain them :-) --

Acked-by: mark gross <markgross@thegnar.org> thanks! --mgross --

Signed-off-by: Rafi Rubin <rafi@seas.upenn.edu> --- drivers/hid/hid-ntrig.c | 21 +++++++++++++++++++++ 1 files changed, 21 insertions(+), 0 deletions(-) diff --git a/drivers/hid/hid-ntrig.c b/drivers/hid/hid-ntrig.c index ab0ca7f..e341e88 100644 --- a/drivers/hid/hid-ntrig.c +++ b/drivers/hid/hid-ntrig.c @@ -375,6 +375,26 @@ static ssize_t set_deactivate_slack(struct device *dev, static DEVICE_ATTR(deactivate_slack, S_IWUSR | S_IRUGO, show_deactivate_slack, ...

Signed-off-by: Rafi Rubin <rafi@seas.upenn.edu> --- drivers/hid/hid-ntrig.c | 18 +++++++++--------- 1 files changed, 9 insertions(+), 9 deletions(-) diff --git a/drivers/hid/hid-ntrig.c b/drivers/hid/hid-ntrig.c index fb69b8c..43e95de 100644 --- a/drivers/hid/hid-ntrig.c +++ b/drivers/hid/hid-ntrig.c @@ -377,8 +377,8 @@ static struct attribute_group ntrig_attribute_group = { */ static int ntrig_input_mapping(struct hid_device *hdev, struct hid_input *hi, - struct hid_field ...

This adds the requested documentation for the driver and some code to identify the current running firmware to aid debug and support. Rafi --

From: Ian Munsie <imunsie@au1.ibm.com> This patch wires up the various socket system calls on PowerPC so that userspace can call them directly, rather than by going through the multiplexed socketcall system call. Signed-off-by: Ian Munsie <imunsie@au1.ibm.com> --- arch/powerpc/include/asm/systbl.h | 19 +++++++++++++++++++ arch/powerpc/include/asm/unistd.h | 21 ++++++++++++++++++++- 2 files changed, 39 insertions(+), 1 deletions(-) diff --git a/arch/powerpc/include/asm/systbl.h ...

Mark F. Brown (2): pxa168: added framebuffer support code. pxa168: added initial support for TPO TD043MTEA1 LCD display on Aspenite arch/arm/mach-mmp/aspenite.c | 60 +++++++++++++++++++++++++++++++ arch/arm/mach-mmp/include/mach/pxa168.h | 8 ++++ arch/arm/mach-mmp/pxa168.c | 3 ++ 3 files changed, 71 insertions(+), 0 deletions(-) --

Signed-off-by: Mark F. Brown <mark.brown314@gmail.com> --- arch/arm/mach-mmp/include/mach/pxa168.h | 8 ++++++++ arch/arm/mach-mmp/pxa168.c | 3 +++ 2 files changed, 11 insertions(+), 0 deletions(-) diff --git a/arch/arm/mach-mmp/include/mach/pxa168.h b/arch/arm/mach-mmp/include/mach/pxa168.h index 27e1bc7..220738f 100644 --- a/arch/arm/mach-mmp/include/mach/pxa168.h +++ b/arch/arm/mach-mmp/include/mach/pxa168.h @@ -10,6 +10,7 @@ extern void __init pxa168_init_irq(void); ...

Hello. WBR, Sergei --

When the feature PTS is not supported by CPU, the sysfile package_power_limit_count for package should not be generated. This patch is used for fixing missing { and }. But I have not confirmed this patch because I don't have such machine. Signed-off-by: Jin Dongming <jin.dongming@np.css.fujitsu.com> --- arch/x86/kernel/cpu/mcheck/therm_throt.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/arch/x86/kernel/cpu/mcheck/therm_throt.c ...

The argument is right. A concise message (e.g. missing { and }) would be better. Format of this patch is broken. It would be applied to kernel tree. Could you generate a patch with right format? Thanks. -Fenghua --

-- 潘卫平 Peter Pan Red Flag Software Co.,Ltd --

Hi Marek, 1) I removed the __init because it was causing a section mismatch warning wth this kernel. Since pxa168fb_probe() is calling pxa168fb_init_mode(), I cannot declare pxa168fb_init_mode() as an __init function. If pxa168fb_probe gets called after the __init section is wiped then it will attempt to run the deleted pxa168fb_init_mode() code. WARNING: vmlinux.o(.data+0x17984): Section mismatch in reference from the variable pxa168fb_driver to the ...

Hi, Create small patches that do not break stuff and are easy to review. By adding small touches, you actually create a nice whole picture in the end :) What I'd like to see is you to keep aspenite.c additions separate from cpu-wide additions etc. This eventually also simplifies bisection if something goes wrong. --

---------------------------------------------- ^--- one patch above SNIP, please split into two patches v--- another patch below Cheers --

Some serial wacom devices support two-finger touch. Test for this during init and parse the touch packets accordingly. Touch packets are processed using Protocol B (MT Slots). Note: there are several wacom versions that do touch but not two-finger touch. These are not catered for here, touch events for these are simply discarded. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> CC: Henrik Rydberg <rydberg@euromail.se> --- Changes to v1: - model MT slot approach after Henrik's ...

I agree :) Reviewed-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> --

On Thu, 26 Aug 2010 09:29:45 +0800 And ">" fits with the name "exceeded" better than ">=" does. I think it is an aesthetic improvement as well as a functional one. Reviewed-by: NeilBrown <neilb@suse.de> Thanks, --

There is another potential bug that may cause zero power. I actually saw similar problem a while back, while I was playing around with rt_avg stuff. But, I have only seen the problem with my modified kernel (playing with softirq accouting part) and not with vanilla kernel. May be your workload includes some RT tasks that triggers this in vanilla kernel as well. This is what I saw happening in my case: scale_rt_power() - In some corner case total ends up being less than rq->rt_avg. - As a ...

Hi all, After merging the cifs tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: fs/cifs/sess.c: In function 'CIFS_SessSetup': fs/cifs/sess.c:623: warning: unused variable 'ntlmsspblob' Introduced by commit 9fbc590860e75785bdaf8b83e48fabfe4d4f7d58 ("[CIFS] Fix ntlmv2 auth with ntlmssp"). -- Cheers, Stephen Rothwell sfr@canb.auug.org.au http://www.canb.auug.org.au/~sfr/

It's possible for modules that use #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt and pr_<level> to reduce image the format string and use pr_<level> functions to emit the module name. This could reduce total image size by about 200KB. Of course in a 800MB+ image, 200KB is pretty small. The general idea is to verify any pr_fmt(prefix) is KBUILD_MODNAME, have the compiler remove it from the format, then have pr_<level> functions emit it using the module name derived from the _RET_IP_ of ...

Perhaps you could consider it a consistency change for easier grepping $ grep -rPoh --include=*.[ch] "\blist_for\w+\s*\(" drivers/firewire | sort | uniq -c 3 list_for_each_entry ( 21 list_for_each_entry( 10 list_for_each_entry_safe( --

I know at least two completely different platforms that might reuse this driver. One is PowerPC with ~10 different boards, and another is an ARM board. On PowerPC we use arch/powerpc/sysdev/simple_gpio.c, but the new driver is much more generic, and is aimed to replace the PowerPC specific one. So it is 'generic' in this exact sense. I also think that it is impractical to name the driver after the particular FPGA IP codename, or even depend on 'FPGA' word at all (as the GPIOs might be ...

How is it required? Its currently implemented as such, and its sure a lot easier to do that way, but I could imagine that unplugging a CPU could be done without it. --

I would argue against that.. we should try and rid ourselves of stopmachine, not add more dependencies on it. If you want to sync against preempt_disable thingies synchronize_sched() is your friend. --

Yep, thanks Jon, I owe a bit more documentation in that file, coming up. --

Hello, Probably similar rationale of not doing stop_machine() on module unload, I suppose. Onlining something is usually considered hotter path than offlining. Performance penalty caused by the difference between possible and online cpumask or cpu onlining probably only matters for very large machines and on those machines stop-machine is very expensive. If there's a pressing need, doing stop_machine for IMHO, in most configurations the difference between possible and online cpumasks ...

Not that reworking unplug to not use stop_machine is anywhere near my todo list, but it would be really nice to have ;-) --

Who? This is a very particular kind of device, on which you can install Linux only through some trick, thus machine coverage will most probably be very low. Having to activate a module by hand is really not a I don't remember and will let Shérab answer. Samuel --

Yes, just PCI I think. Below is the output of lspci -v if that helps. Best wishes, Shérab. 00:00.0 Host bridge: Cyrix Corporation PCI Master Flags: bus master, medium devsel, latency 0 00:02.0 Ethernet controller: Davicom Semiconductor, Inc. 21x4x DEC-Tulip compatible 10/100 Ethernet (rev 40) Subsystem: Davicom Semiconductor, Inc. DM9102A (DM9102AE, SM9102AF) Ethernet 100/10 MBit Flags: bus master, medium devsel, latency 165, IRQ 11 I/O ports at 1000 [size=256] Memory at ...

Hi again, It's included below. Shérab. 00:00.0 0600: 1078:0001 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 00:02.0 0200: 1282:9102 (rev 40) Subsystem: 0291:8212 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- ...

Hello Sam, Then still the unpack_to_rootfs() function will not get the correct size of the compressed file, because "__initramfs_end - __initramfs_start" can be bigger than the real file size depending on the used the alignment. I would assume that not all decompression functions will work, if a bigger value is passed to decompress_method(). Michael --

Yes, Shall send the refreshed patch now -- Thanks and Regards Srikar --

According to www.multitech.com/en_us/news/articles/success_stories/eurobraille.pdf : "EURObraille’s latest invention is the IRIS portable assistant. The use of a powerful microprocessor coupled with the most advanced Microsoft Windows operating system provides the blind with a powerful computing solution" What version of Microsoft Windows ships on this box? Does it run in ACPI mode? Does it power-off successfully? Does Linux run in ACPI mode? Please send along the dmesg from a Linux ...

I don't know and I don't think it would be possible to determine it, since one just has access to a dedicated application and not to the It's attached. Thanks, Shérab.

On Wed, 25 Aug 2010 19:50:22 -0700 (PDT) yes. For defineing/understanding priority, oom_score_adj is that. yes. under 8G system, -250 will allow ingnoring 2G of usage. == How about this text ? == When you set a task's oom_score_adj, it can get priority not to be oom-killed. oom_score_adj gives priority proportional to the memory limitation. Assuming you set -250 to oom_score_adj. Under 4G memory limit, it gets 25% of bonus...1G memory bonus for avoiding OOM. Under 8G memory ...

You'll want to look at section 3.1 of Documentation/filesystems/proc.txt, I'd hesitate to state the formula outside of the implementation and instead focus on the semantics of oom_score_adj (as a proportion of available memory compared to other tasks), which I tried doing in section 3.1. Then, the userspace tool only need be concerned about the units of oom_score_adj rather than whether rss, swap, or later extentions such as shm are added. Thanks for working on this, Kame! --

I understand it's a little tricky when dealing with memcg-constrained oom conditions versus system-wide oom conditions. Think of it this way: if the system is oom, then every memcg, every cpuset, and every mempolicy is also oom. That doesn't imply that something in every memcg, every cpuset, or every mempolicy must be killed, however. What cgroup happens to be penalized in this scenario isn't necessarily the scope of oom_score_adj's purpose. oom_score_adj certainly does have a stronger ...

It's a memory leak on unload for a driver for a device integrated into an embedded SoC - I'd be astonished if anyone managed to run into it in production. --

On Wed, 25 Aug 2010 19:45:00 +0530 See Paul Menage's mail. He said "allocating css object under kernel/cgroup.c Hmm. will look into. Thanks, --

Acked-by: Christoph Lameter <cl@linux.com> --

Applied, thanks! --

On Thu, 2010-08-26 at 12:55 +0900, KOSAKI Motohiro wrote: You can do that if you like, but it seems a bit long for a commit message. By the way, I was able to reproduce this bug in RHEL 3 (kernel based on 2.4.21) so it seems to have been around for a while. Ben. -- Ben Hutchings, Senior Software Engineer, Solarflare Communications Not speaking for my employer; that's the marketing department's job. They asked us to note that Solarflare product names are trademarked. --

[...] This example seems to have both server (serv, s2) and client (s1) in the same process for simplicity. The server socket (s2) is closed and the client cannot be expected to know that. Of course the client ought to drop the connection after the first EPIPE, but it's reasonable to expect that this is a sticky condition just as it would be for a pipe. Here's a similar test case in C: #include <assert.h> #include <signal.h> #include <stdio.h> #include <sys/select.h> #include ...

Great! Thank you!! --

From: Ben Hutchings <bhutchings@solarflare.com> It's existed since September 1998: commit 6275af56642b5b9ed9ef15bf5d9718661c5fe79d Author: freitag <freitag> Date: Sat Sep 26 06:20:25 1998 +0000 Some small fixes. - Remove second check for sk->err in poll as discussed with Linus. - Don't signal writability when the local end has been shut down. - Comment fixes. diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c index 5a09639..16d4308 100644 --- a/net/ipv4/tcp.c +++ ...

I have a handful of other changes queued up, do you want to take them too? --

Commit-ID: 9ea77bdb39b62c9bf9fd3cdd1c25a9420bccd380 Gitweb: http://git.kernel.org/tip/9ea77bdb39b62c9bf9fd3cdd1c25a9420bccd380 Author: H. Peter Anvin <hpa@linux.intel.com> AuthorDate: Wed, 25 Aug 2010 16:38:20 -0700 Committer: H. Peter Anvin <hpa@linux.intel.com> CommitDate: Wed, 25 Aug 2010 17:10:49 -0700 x86, bios: Make the x86 early memory reservation a kernel option Add a kernel command-line option so the x86 early memory reservation size can be adjusted at runtime instead of ...

When we unify alloc_buddy_huge_page() as commented for patch 2/8, _vma suffix is not necessary any more. Your suggestion to drop unused arguments sounds reasonable, so I merge the attached patch into patch 2/8. Thanks, Naoya --

From: Joe Perches <joe@perches.com> Applied. --

Hi Greg, I have an objection! We've found a problem, it breaks stuff fairly thoroughly. >:( Mikey has submitted http://patchwork.ozlabs.org/patch/62757/ to Ben's tree to fix it, but it might be easier all round to drop this and we can resubmit the indivisible pair of commits to -stable later? (You'd selected this for {34,35}-stable also.) Really for the inconvenience, --

I thought it's not urgent and next patch would apply based on this patch without HUNK. If Andrew doesn't have a response, I will resend as a standalone. Thanks. -- Kind regards, Minchan Kim --

Please send this patch on its own as it looks like it should be merged and arguably is a stable candidate for 2.6.35. Alternatively, Andrew, can you pick up just this patch? It seems unrelated to the second patch on COMPACTPAGEFAILED. -- Mel Gorman Part-time Phd Student Linux Technology Center University of Limerick IBM Dublin Software Lab --

Yes, the slab layer calls the page allocator when there are no objects available and passes the __GFP_NOFAIL that the user may have set in the call to the page allocator. Why then add new functions that do the same? --

I didn't say impossible, just that there's no way we can always guarantee of forward progress with a specific, bound pool of memory. Sure, we know what the worst case amount of log space is needed for each transaction (i.e. how many pages that will be dirtied), but that does not take into account all the blocks that need to be read to make those modifications, the memory needed for stuff like btree cursors, log tickets, transaction commit vectors, btree blocks needed to do the searches, etc. ...

And what Dave and I are saying is that we'll either need to do our on loop to avoid the deprecation warning, or the use of the deprecated function will probably be used forever... - Ted --

It would take a handful of concurrent transactions in XFS with worst case memory allocation requirements to exhaust that pool, and then we really would be in trouble. Alternatively, it would take a few allocations from each of a couple of thousand concurrent transactions to get to the same point. Bound memory pools only work when serialised access to the pool can be enforced and there are no dependencies on other operations in progress for completion of the work and freeing of the ...

Agreed with the fact that 400k isn't much to worry about. Not agreed with the GFP_ATOMIC stmt. Direct reclaim already has PF_MEMALLOC, but then we also need a concurrency limit on that, otherwise you can still easily blow though your reserves by having 100 concurrency users of it, resulting in an upper bound of 40000k instead, which will be too much. There were patches to limit the direct reclaim contexts, not sure they ever got anywhere.. It is something to consider in the re-design ...

Yes, that's the intent. We'd like to add the WARN_ON_ONCE(get_order(size) >= PAGE_ALLOC_COSTLY_ORDER) warning, though, so we're ensured that redefinition of that #define doesn't cause allocations to fail to that don't have appropriate error handling or future callers use higher order allocs. The _nofail() functions help that and do some due diligence in ensuring that we aren't changing gfp flags based only on the current page allocator implementation which may later change with very ...

Hello, Yeah, maybe. Then we also can guarantee that percpu allocator always honors alignment (which wq code currently requires and papers over with similarly ugly workaround). It would add a mostly redundant allocator code tho. I'll look into how easily it can be done. Thanks. -- tejun --

--

So do I. Here is a slightly less hacky version through using kmalloc_large instead: Subject: Slub: UP bandaid Since the percpu allocator does not provide early allocation in UP mode (only in SMP configurations) use __get_free_page() to improvise a compound page allocation that can be later freed via kfree(). Compound pages will be released when the cpu caches are resized. Acked-by: David Rientjes <rientjes@google.com> Signed-off-by: Christoph Lameter <cl@linux.com> --- mm/slub.c | ...

I created a Bugzilla entry at https://bugzilla.kernel.org/show_bug.cgi?id=17151 for your bug report, please add your address to the CC list in there, thanks! -- Maciej Rutecki http://www.maciek.unixy.pl --

Hi Phil I found a solution myself using the grub embedded "search --fs-uuid". I do it once the linux boot partition and also on one partition of the external disk. If the search on the external disk report an error, I know root=/dev/sda1 else root=/dev/sdb1. But I really think this should be linux job! I also converted my /etc/fstab to LABEL=foo /foo syntax. Now I'm really puzzled grub2 as a "search by fs uuid" command that linux is unable to deliver for the root device! I have ...

On advanced cluster-area networks with large MTUs, the ACK packets in TCP will probably kill your performance. That's one of the main reasons we keep NFS over UDP on life support! :-) -- chuck[dot]lever[at]oracle[dot]com --

On Thu, 26 Aug 2010 08:43:42 -0600 (Mountain Daylight Time) Infiniband device driver needs to be fixed to do SG and checksum offload. Otherwise it is insane to try and run large MTU over it. I even wonder if the dev_change_mtu() function should reject > PAGESIZE mtu for devices that don't do scatter/gather or at least a raise a warning. --

Umm, that contains some legaleese, but nothing useful...? -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html --

The patch seems fine. - Gary ________________________________________ From: Liam Girdwood [lrg@slimlogic.co.uk] Sent: Wednesday, August 25, 2010 2:53 AM To: Mike Rapoport Cc: Mark Brown; Gary King; Axel Lin; linux-kernel Subject: Re: [PATCH 2/2] regulator: tps6586x-regulator - fix bit_mask parameter for tps6586x_set_bits() Do we have any news on this testing ? I'd like to have these upstream for rc3. Thanks Liam -- Freelance Developer, SlimLogic Ltd ASoC and Voltage Regulator ...

Hi, it might also be nice to add a workqueue chapter to the traceopint docbook. Since you've already included kernel-doc style comments, the below is all that we need. current book is at: http://www.kernel.org/doc/htmldocs/tracepoint/ thanks, -Jason Add a workqueue chapter to the tracepoint docbook Signed-off-by: Jason Baron <jbaron@redhat.com> --- Documentation/DocBook/tracepoint.tmpl | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) diff --git ...

It was really in Peter's patch, just a stupid hack for now. Cheers, Don diff --git a/arch/x86/kernel/cpu/perf_event_intel.c b/arch/x86/kernel/cpu/perf_event_intel.c index 4539b4b..9e65a7b 100644 --- a/arch/x86/kernel/cpu/perf_event_intel.c +++ b/arch/x86/kernel/cpu/perf_event_intel.c @@ -777,7 +777,9 @@ again: done: intel_pmu_enable_all(0); - return handled; + if (!handled) + return handled; + return ++handled; } static struct event_constraint * --

This could also be a race in the counter handling code, or we do not proper count the number of handled counters. Maybe 2 counters actually fired but we only noticed one counter and then accidentially cleared the 2nd without processing it. -Robert -- Advanced Micro Devices, Inc. Operating System Research Center --

Sounds promising, mind to post new inter-diff? Ie what you have changed from Robert's patch. -- Cyrill --

ok, it seems it just treat any unknown nmi as being came from PMU, no? -- Cyrill --

I'm aware that grabbing a large chunk at boot time is a bit of waste of space and because of it I'm hoping to came up with a way of reusing the space when it's not used by CMA-aware devices. My current idea was to OK. -- Best regards, _ _ | Humble Liege of Serenely Enlightened Majesty of o' \,=./ `o | Computer Science, Michał "mina86" Nazarewicz (o o) +----[mina86*mina86.com]---[mina86*jabber.org]----ooO--(_)--Ooo-- --

At this point I need to say that I have no experience with hotplug memory but I think that for this to make sense the regions of memory would have to be smaller. Unless I'm misunderstanding something, the above would convert a region of sizes in order of GiBs to use for CMA. -- Best regards, _ _ | Humble Liege of Serenely Enlightened Majesty of o' \,=./ `o | Computer Science, Michał "mina86" Nazarewicz (o ...

No. CMA's designed for systems without IOMMU. If system has IOMMU then there is no need for contiguous memory blocks since all discontiguousnesses Essentially that's the idea. Platform init code adds early regions and later on reserves memory for all of the early regions. For the former some In the first version I've used unsigned long as return type but then it was suggested that maybe dma_addr_t would be better. This is easily If I understood you correctly this is something I'm ...

Comments are always welcome. :) -- Best regards, _ _ | Humble Liege of Serenely Enlightened Majesty of o' \,=./ `o | Computer Science, Michał "mina86" Nazarewicz (o o) +----[mina86*mina86.com]---[mina86*jabber.org]----ooO--(_)--Ooo-- --

Yeah, if we can do this, that will avoid rebooting for kdump to reserve memory. Thanks. --

I elaborates my statement for preventing confusing due to using _pinned page_. I means that anon pages isn't not a fragment problem but space problem for the devices. -- Kind regards, Minchan Kim --

On Thu, 26 Aug 2010 13:06:28 +0900 yes, I think so. But, IIRC, it's own purpose of Chirstoph's work is for removing zones. please be careful what's really necessary. Thanks, -Kame --

On Thu, 26 Aug 2010 04:12:10 +0200 Now, x86's section size is == #ifdef CONFIG_X86_32 # ifdef CONFIG_X86_PAE # define SECTION_SIZE_BITS 29 # define MAX_PHYSADDR_BITS 36 # define MAX_PHYSMEM_BITS 36 # else # define SECTION_SIZE_BITS 26 # define MAX_PHYSADDR_BITS 32 # define MAX_PHYSMEM_BITS 32 # endif #else /* CONFIG_X86_32 */ # define SECTION_SIZE_BITS 27 /* matt - 128 is convenient right now */ # define MAX_PHYSADDR_BITS 44 # define ...

On Thu, Aug 26, 2010 at 12:44 PM, KAMEZAWA Hiroyuki True. Doesn't patch's idea of Christoph helps this ? http://lwn.net/Articles/200699/ -- Kind regards, Minchan Kim --

Hello Andrew, I think Pawel has replied to most of your comments, so I'll just add my own I think that the biggest problem is fragmentation here. For instance, I think that a situation where there is enough free space but it's fragmented so no single contiguous chunk can be allocated is a serious problem. However, I would argue that if there's simply no space left, a multimedia device could fail and even though it's not desirable, it would not be such a big issue in my eyes. So, if ...

On Thu, 26 Aug 2010 11:50:17 +0900 Ah, I need to clarify what I want to say. With compaction, it's helpful, but you can't get contiguous memory larger than MAX_ORDER, I think. To get memory larger than MAX_ORDER on demand, memory hot-plug code has almost all necessary things. you may able to add # echo 0xa0000000-0xa80000000 > /sys/devices/system/memory/cma to get contiguous isolated memory. BTW, just curious...the memory for cma need not to be saved at hibernation ? Or drivers has to ...

If you'd actually looked at the page allocator you'd see its capable of doing exactly that! I has the notion of movable pages, it can defragment free space (called compaction). Use it! --

For handling fragmentation, there is the option of ZONE_MOVABLE so it's usable by normal allocations but the CMA can take action to get it cleared out if necessary. Another option that is trickier but less disruptive would be to select a range of memory in a normal zone for CMA and mark it MIGRATE_MOVABLE so that movable pages are allocated from it. The trickier part is you need to make that bit stick so that non-movable pages are never allocated from that range. That would be trickish ...

It's another topic. I agree highmem isn't a gorgeous. But my desktop isn't real machine? Important thing is that we already have a highmem and many guys No. Until now, many embedded devices have used to small memory. In that case, only there is a DMA zone in system. But as I know, mobile phone starts to use big(?) memory like 1G or above sooner or later. So they starts to use HIGHMEM. Otherwise, 2G/2G space configuration. Some embedded device uses many thread model to port easily from ...

Real machines don't have highmem, highmem sucks!! /me runs Does cross zone movement really matter, I though these crappy devices were mostly used on crappy hardware with very limited memory, so pretty much everything would be in zone_normal.. no? But sure, if there's really a need we can look at maybe doing cross zone movement. --

Right, so to me that looks like going at the problem backwards. That will complicate the page-cache instead of your bad hardware drivers (really, hardware should use IOMMUs already). So why not work on the page allocator to improve its contiguous allocation behaviour. If you look at the thing you'll find pageblocks and migration types. If you change it so that you pin the migration type of one or a number of contiguous pageblocks to say MIGRATE_MOVABLE, so that they cannot be used for ...

Commit-ID: 9b861528a8012e7bc4d1f7bae07395b225331477 Gitweb: http://git.kernel.org/tip/9b861528a8012e7bc4d1f7bae07395b225331477 Author: Haicheng Li <haicheng.li@linux.intel.com> AuthorDate: Fri, 20 Aug 2010 17:50:16 +0800 Committer: H. Peter Anvin <hpa@linux.intel.com> CommitDate: Thu, 26 Aug 2010 14:02:33 -0700 x86-64, mem: Update all PGDs for direct mapping and vmemmap mapping changes When memory hotplug-adding happens for a large enough area that a new PGD entry is needed for the ...

Technically, that may not be quite correct. <digression into weeds> The RDTSC instruction will return a monotonically increasing unique value, but the execution and retirement of the instruction are unserialized. So technically, two simultaneous RDTSC could be issued to multiple execution units, and they may either return the same values, or the earlier one may stall and complete after the latter. rdtsc mov %eax, %ebx mov %edx, %ecx rdtsc cmp %edx, %ecx jb fail cmp %ebx, ...

Here I disagree with you: "that can be used for any device for a device". Reserved coherent memory can be only and exclusively used by the __same__ device whose device->dma_mem is touched. No other devices are influenced because their device->dma_mem are NULL. and dma_alloc_from_coherent() is not invoked for them. That is why I think this hack is not dangerous. If some device driver decide to reserve some chunk of memory it is for its private use and no other device in the system Here I ...

On Fri, 20 Aug 2010 14:50:12 +0300 Then, we should avoid using coherent memory as I exaplained before. In addition, dma_alloc_coherent can't provide large enough contigous memory for some drivers so this patch doesn't help much. We need the proper API for contiguous memory. Seem that we could have something: http://lkml.org/lkml/2010/8/20/167 --

On Thu, 26 Aug 2010 09:04:14 +0300 If you add something to the videobuf-dma-contig API, that's fine by me because drivers/media/video/videobuf-dma-contig.c uses the own structure and plays with dma_alloc_coherent. As long as a driver doesn't touch device->dma_mem directly, it's fine, I think (that is, dt3155v4l driver is broken). There are already some workarounds for contigous memory in several drivers anyway. We will have the proper API for contiguous memory. I don't think that adding such ...

No, this will not work - this API has to be used from board code and We have currently a number of boards broken in the mainline. They must be fixed for 2.6.36. I don't think the mentioned API will do this for us. So, as I suggested earlier, we need either this or my patch series http://thread.gmane.org/gmane.linux.ports.sh.devel/8595 for 2.6.36. Thanks Guennadi --- Guennadi Liakhovetski, Ph.D. Freelance Open-Source Software Developer http://www.open-technology.de/ --

The patch that made the problem obvious for ARM is 309caa9cc6ff39d261264ec4ff10e29489afc8f8 aka v2.6.36-rc1~591^2~2^4~12. So this went in before v2.6.36-rc1. One of the "architectures which similar restrictions" is x86 BTW. And no, we won't revert 309caa9cc6ff39d261264ec4ff10e29489afc8f8 as it addresses a hardware restriction. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | ...

On Thu, 26 Aug 2010 11:53:11 +0200 How these drivers were able to work without hitting the hardware restriction? --

On Thu, 26 Aug 2010 10:01:52 +0300 I don't think so. device->dma_mem can be accessed only via the DMA-API. I think that the DMA-API says that dma_declare_coherent_memory declares coherent memory that can be access exclusively by a certain device. It's not for reserving coherent memory that can be used for any device for a device. Anway, you don't need coherent memory. So using the API for coherent I don't think that's a good idea. Adding temporary workaround to the generic API and removing ...

No. ioremap on memory mapped by the kernel is just plain not permitted with ARMv6 and ARMv7 architectures. It's not something you can say "oh, need to find another way" because there is _no_ software solution to having physical regions mapped multiple times with different attributes. It's an architectural restriction. We can't unmap the kernel's memory mapping either, as I've already explained several times this month - and I'm getting frustrated at having to keep on explaining that ...

Hi Russell, Just because ioremap on memory mapped by the kernel is just plain not permitted I have proposed a new pair of functions: dma_reserve_coherent_memory()/dma_free_reserved_memory() http://lkml.org/lkml/2010/8/19/200 but it is not quite well accepted from the community. What is your opinion? Thanks, --

I guess that simply running finger @kernel.org will give you exactly the information you are looking for which much less pain of connecting to www server, parsing html, etc. -- Jiri Kosina SUSE Labs, Novell Inc. --

I have a script that reads finger_banner then adds mmotm & its base kernel tree, & linux-next & its base kernel tree to the finger_banner. (It was written before finger_banner included linux-next info.) Output today is: The latest linux-next version of the Linux kernel is: next-20100826 The latest snapshot 2.6 version of the Linux kernel is: 2.6.36-rc2-git4 The latest mainline 2.6 version of the Linux kernel is: 2.6.36-rc2 The latest stable 2.6.35 version of the Linux ...

Hmm, I can't understand, if target_core_stgt.c is "NOT being tagged as a mainline .37 item", then the STGT ABI compatibility for being a drop in This is exactly what we are discussing. Thanks, Vlad --

Yes, I see. That output looks useful. --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** --

Sure, I can't say I care much, had "all" in mind when I came up with !A. I fixed up the command, and can change that and resend. johannes --

From: Johannes Berg <johannes.berg@intel.com> When you don't use !E or !I but only !F, then it's very easy to miss including some functions, structs etc. in documentation. To help finding which ones were missed, allow printing out the unused ones as warnings. For example, using this on mac80211 yields a lot of warnings like this: Warning: didn't use docs for DOC: mac80211 workqueue Warning: didn't use docs for ieee80211_max_queues Warning: didn't use docs for ieee80211_bss_change ...

Probably not very important .. but .. other drivers are called *-laptop.c, not *_laptop.c .. asus-laptop.c classmate-laptop.c compal-laptop.c dell-laptop.c eeepc-laptop.c fujitsu-laptop.c msi-laptop.c panasonic-laptop.c sony-laptop.c topstar-laptop.c -- Corentin Chary http://xf.iksaif.net --

Hum, that's a "bug" in asus-laptop, because I used KBUILD_MODNAME (asus_laptop) instead of "asus-laptop" as the driver name. And I don't know if I can change that now without breaking backward compatibility. But other drivers should work (I tested sony-laptop). -- Corentin Chary http://xf.iksaif.net --

Applied, thanks. Michal --

Hello! First of all, thanks a lot for your help - I really appreciate it. I applied your new patches on top of your old patches. Hopefully that was okay. Unfortunately, it didn't work this time. Here's a sample output from the new patch. === 8< === [58.050208] PM: Preallocating image memory... [58.159881] shrink_all_memory start [58.232411] PM: shrink memory: pass=1, req:312373 reclaimed:15864 free:358420 [58.342041] PM: shrink memory: pass=2, req:296509 reclaimed:21837 ...

Hm, apparently it was separated out by the mail server. Here it is again with some of the headers removed I guess. Cheers, Don From: Don Zickus <dzickus@redhat.com> Date: Thu, 19 Aug 2010 22:48:26 -0400 Subject: [PATCH] [lockup detector] sync touch_*_watchdog back to old semantics During my rewrite, the semantics of touch_nmi_watchdog and touch_softlockup_watchdog changed enough to break some drivers (mostly over preemptable regions). This change brings those touch_*_watchdog ...

Hi, I'm wondering if the temperature info can be exported to userspace, and let a daemon to do the relocation (by ioctl). A userspace daemon is more flexible. Thanks, Shaohua --

Hi Neil, I concur that since EC firmware does not seem to support full PS/2 protocol we should got with the original driver creating an input device rather than serio. Please send me the latest version of your driver and I will apply it to my .37 queue. Thanks. -- Dmitry --

Thanks - I'll incorporate review comments and post an updated patch. -- Neil -- Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. --

On Fri, 20 Aug 2010 07:51:52 +1000 Ok. I've seen that someone submitted a patch to print the dma_mask under sysfs, I supposed, for debugging to check if a driver misuses the DMA API or the bus can't do 64bit DMA when the device can support 64bit DMA but only gets a buffer under 32bit. But yeah, we can live withtout it. Lots of drivers call dma_set_coherent_mask with 64bit mask and then call it with 32bit mask if 64bit mask fails. So we don't have driver's OK. like dma_set_mask(), we ...

On Thu, 26 Aug 2010 20:55:09 +0900 btw, I'm still not sure, letting architectures to clip the dma mask (and coherent mask) behind a driver is correct by defintion of the DMA API (it's not a real problem). DMA-API.txt defines dma_set_mask is "checks to see if the mask is possible and update the device parameters if it is". It means that architectures can't clip the mask behind a driver, I think. Lots of drivers do something like: if (dma_set_mask(dev, DMA_BIT_MASK(64))) if ...

On Mon, 9 Aug 2010 06:43:14 +0200 Please don't send unchangelogged patches. The title tells us what the patch does but provides no hint as to why He's probably unaware of the patch. Let's cc him. --

On Sun, 08 Aug 2010 14:42:57 +0200 --

It seems that security subsystem has lower standards than rest of the kernel. Sad. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html --

If that helps -- there's a serial port option available for the T60's UltraBay too that works as ttyS0. Maciej --

[Empty message]

After reviewing the output from dmidecode I determined that your model T60 is slightly different than mine. It appears that you have the widescreen version. Is that correct? Also you seem to be running a fairly old version of the BIOS (1.08). The latest is 1.18: http://www-307.ibm.com/pc/support/site.wss/MIGR-67020.html I would recommend that you upgrade your BIOS. If that does not help we can continue with the investigation. I will also try to locate a widescreen T60 that would hopefully help ...

Map ACPI tables as WB on x86_64. No substantive changes to IA64. Signed-off-by: Jack Steiner <steiner@sgi.com> --- V2 - Change the patch to unconditionally map ACPI tables as WB on x86_64. I'm still some paranoid about this because of the potential imapct on some platforms with weird BIOSs. However, note that on EFI-enabled systems (like UV), the ACPI tables are already mapped as WB memory. This is done in the EFI function efi_enter_virtual_mode(). The ACPI code in ...

Sorry for the lag on this one. Queueing for 2.6.37 in linux-davinci.git Kevin --

I think my patch actually does more than the Tejun's one. I need to have a deeper look at them both. I'm still testing the Tejun's patch on my system where I was able to reproduce the problem, but so far it's been working. Thanks, Rafael --

Well, no luck. I was able to reproduce the issue on my box with this patch applied on top of 2.6.32-rc2. Which probably means that the link power management is not really involved here and seems to turn up this statement: rc = ata_host_request_pm(host, mesg, 0, ATA_EHI_QUIET, 1); in ata_host_suspend() as the culprit. Does it make sense? Thanks, Rafael --

On Thu, 26 Aug 2010 08:16:24 -0500 I suppose that nobody in ARM has been interested in the feature. It was invented to improve I/O performance with large I/O requests. No wonder embeded people aren't interested in it. fujita@rose:~/git/linux-2.6$ find arch -name 'scatterlist.h'|xargs grep HAS_SG arch/x86/include/asm/scatterlist.h:#define ARCH_HAS_SG_CHAIN arch/ia64/include/asm/scatterlist.h:#define ARCH_HAS_SG_CHAIN arch/sparc/include/asm/scatterlist.h:#define ...

Ok, so let me try SG chain, that should be the correct fix. Thanks a lot, Fernando. --

I have not thought about possible fixes inside iovmm, but now I am reviewing the patches I will figure out how to fix this inside iovmm. Since he workaround still I can try, but it looks tricky for me. Maybe someone else can tell us why SG chain is not supported for ARM or if there is a problem just defining ARCH_HAS_SG_CHAIN. Regards, Fernando. --

On Wed, Aug 25, 2010 at 10:42 PM, Guzman Lugo, Fernando But in the meantime the bug is still there, and there's no timeline When exactly? -- Felipe Contreras --

[Empty message]

No, I can change it when I apply the patch next week (sorry, swamped at the moment.) thanks, greg k-h --