Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in
drivers/block/mtip32xx/mtip32xx.c between commit 2077d947260c (mtip32xx:
Workaround for unaligned writes) from the block tree and commit
mtip32xx: convert to batch completion from the akpm tree.
I fixed it up (see below) and
On Tue, Apr 30 2013, remaper wrote:
/*
* We only want one -make_request_fn to be active at a time,
* else stack usage with stacked devices could be a problem.
* So use current-bio_list to keep a list of requests
* submited by a make_request_fn function.
* current-bio_list is also used
Hi,
One more point for your devicetree conversions,
On Mon, Apr 29, 2013 at 01:30:01PM +0530, Prabhakar Lad wrote:
From: Lad, Prabhakar prabhakar.cse...@gmail.com
add OF support for the mt9p031 sensor driver.
+static struct mt9p031_platform_data
+ *mt9p031_get_pdata(struct i2c_client
Remove the pci_* dma functions and replace with the more generic
versions.
In preparation of adding platform support, a new struct device *dev
is added to struct velocity_info which can be used by both the pci
and platform code.
Signed-off-by: Tony Prisk li...@prisktech.co.nz
---
v4 changes:
Code tidyup as requested by Francois Romieu
Removed '#ifdef PCI' around PCI code. Compile tested on (!)PCI and (!)PM.
v3 changes:
Rebased against net-next.
Fix errors in pm code.
v2 changes:
Drop patch #1 as requested by David Miller.
Correct the PHYID_ICPLUS_IP101A MII bits - should
Improve the clarity of the code in preparation for converting the
dma functions to generic versions, which require a struct device *.
This makes it possible to store a 'struct device *dev' in the
velocity_info structure.
Signed-off-by: Tony Prisk li...@prisktech.co.nz
---
Add support for the VIA Velocity network driver to be bound to a
OF created platform device.
Signed-off-by: Tony Prisk li...@prisktech.co.nz
---
.../devicetree/bindings/net/via-velocity.txt | 20 +
drivers/net/ethernet/via/Kconfig |3 +-
2013/4/29 Jan Kara j...@suse.cz:
On Fri 26-04-13 10:53:27, Marco Stornelli wrote:
Replaced sb_start_write with sb_start_write_killable inside
mnt_want_write and mnt_want_write_file.
The patch looks good. You can add:
Reviewed-by: Jan Kara j...@suse.cz
Hi,
On Mon, Apr 29, 2013 at 02:31:59PM -0700, Linus Torvalds wrote:
On Mon, Apr 29, 2013 at 2:14 PM, Alan Stern st...@rowland.harvard.edu wrote:
What other things seemed odd about Greg's pull request?
The only other thing I noticed was the new CONFIG_USB_PHY quesiton,
which is not
Commit-ID: 6296ace467c8640317414ba589b124323806f7ce
Gitweb: http://git.kernel.org/tip/6296ace467c8640317414ba589b124323806f7ce
Author: Li Zhong zh...@linux.vnet.ibm.com
AuthorDate: Sun, 28 Apr 2013 11:25:58 +0800
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Mon, 29 Apr 2013
Hi,
I'm just wondering why device nodes of some serial drivers (mostly
when arch != x86) are not always named ttyS[:digit:] ?
For example, I have a ARM based platform which has a serial device
node named ttymxc0.
I don't see any advantages to do this but only require one to handle
special cases
On Mon, Apr 29 2013, Philippe De Muyter wrote:
In alloc_read_gpt_entries and alloc_read_gpt_header, the kzalloc'ated
zones are either totally overwritten by the following read_lba call,
or freed. As kmalloc is cheaper than kzalloc, use kmalloc.
Applied, thanks.
--
Jens Axboe
--
To
Andi Kleen a...@firstfloor.org writes:
The FP registers are restored lazily, but the state for this is kept in
the kernel.
I'm not sure if I understand lazily in this context: Do you mean that FP
registers _are_ restored within the kernel, but _not_ from a (possibly modified)
ucontext of a
On Mon, Apr 29 2013, Philippe De Muyter wrote:
Hi Karel
On Mon, Apr 29, 2013 at 02:36:51PM +0200, Karel Zak wrote:
On Mon, Apr 29, 2013 at 01:40:41PM +0200, Philippe De Muyter wrote:
why not memset(pps_found, )? I also see magical constant 16
Actually 16 is the maximum
On Tue, Apr 30, 2013 at 08:41:52AM +0200, Jens Axboe wrote:
On Mon, Apr 29 2013, Philippe De Muyter wrote:
so sda is 8,0 and sdb is 8,16
and if, while discovering partitions of /dev/sda, I try to make a
partition 16 or higher, it is silently discarded by 'put_partition'.
Is that
On Fri, Apr 12, 2013 at 01:25:49PM +0100, Serban Constantinescu wrote:
The patch set has been successfully tested with a 64bit Linux userspace and
64bit binder unit-tests.
This patch set has been successfully tested on 32bit platforms(ARMv7 VExpress)
and 64bit platforms(ARMv8 RTSM) running a
On Mon, 22 Apr 2013 11:57:52 +0400, Dmitry Monakhov dmonak...@openvz.org
wrote:
Non-text part: multipart/mixed
Seriously. Am I an only one who use blktrace?
Jens can you please take it?
Hi,
Let someone please finally take care of this patch.
Originally it was submitted here
On 04/30/2013 06:50 AM, David VomLehn wrote:
Msleep_interruptible() on a dual processor system may wait a long time.
On some reboots, calling msleep_interruptible() from CPU 1 on a dual
processor system will not return for seconds or even minutes. This happens
because ksoftirqd/1 migrates to
On Mon, Apr 29, 2013 at 11:50:51PM +0200, Philippe De Muyter wrote:
On Mon, Apr 29, 2013 at 01:40:41PM +0200, Philippe De Muyter wrote:
On Mon, Apr 29, 2013 at 11:37:56AM +0200, Karel Zak wrote:
Philippe, do you have any disk image with AIX LVM? It would be nice to
have a way how to
On r8a7740 multiple DMA controllers can serve the same slaves with the
same DMA slave IDs. To use this feature DMA controller DT nodes have
to be grouped under dma-mux multiplexer nodes and slaves have to be
modified to reference multiplexer nodes instead of individual DMA DT
nodes. Future patches
Previously an issue has been discussed, arising on sh-/r-mobile ARM-based
systems. There we typically have multiple DMA controller instances with
exactly equal or very similar capabilities. Each of them can serve the same
slaves, using the same slave identifiers (request line IDs). With the
of_parse_phandle_with_args() and of_count_phandle_with_args() functions
are declared with their first parameter as const. However, their
respective stubs, used when CONFIG_OF isn't defined, don't have the const
modifier. This patch adds it to fix the mismatch.
Signed-off-by: Guennadi Liakhovetski
Hello,
On Tue, 30 Apr 2013, Simon Horman wrote:
This is intended for use in loops which read data protected by RCU and may
have a large number of iterations. Such an example is dumping the list of
connections known to IPVS: ip_vs_conn_array() and ip_vs_conn_seq_next().
The call
If a slave can use any of several DMA controllers on the system, multiple
DMA descriptors can be listed in its dmas DT property with the same
channel name and different DMA controller phandles. However, if multiple
such slaves can use any of a set of DMA controllers on the system, listing
them all
Sometimes it is useful to group similar DT nodes under a common parent,
when a different node can reference the group, meaning, that any subnode
will do the job. An example of such a group is a DMA multiplexer, when a
DMA slave can be served by any DMA controller from the group. This patch
x86/pci/mrst: force all pci config access toward 0:0:0, 0:2:0 and 0:3:0 to type
1
For real pci devices 0:0:0, 0:2:0 and 0:3:0, there is either no pci shim, or
no guarantee of data correctness of offset 256-4k. So for whatever reason,
Linux kernel should not do MMCFG pci config access to those
On Tue, Apr 30, 2013 at 09:08:40AM +0200, Philippe De Muyter wrote:
On Mon, Apr 29, 2013 at 11:50:51PM +0200, Philippe De Muyter wrote:
On Mon, Apr 29, 2013 at 01:40:41PM +0200, Philippe De Muyter wrote:
On Mon, Apr 29, 2013 at 11:37:56AM +0200, Karel Zak wrote:
Philippe, do you
Hi Yinghai, all,
I've tested this patch-set with my following patch-set:
[PATCH v1 00/12] Arrange hotpluggable memory in SRAT as ZONE_MOVABLE.
https://lkml.org/lkml/2013/4/19/94
Using ACPI table override, I overrided SRAT on my box like this:
[0.00] SRAT: Node 0 PXM 0 [mem
On 04/29/2013 10:46 PM, Bernhard Schiffner wrote:
Known issues:
- SLxB is broken on PowerPC.
- suspend / resume seems to program program the timer wrong and wait
ages until it continues.
Yes, it's a annoying problem here too.
How can I help to solve it?
Are you referring to
Hi.
I am working with a platform that has a problem with the RTC alarm
interrupt - tested with rtctest from /Documentation/rtc.txt.
So I thought that I could use the HPET emulation. As far as I
understand in the HPET emulation mode no RTC irq will be used -- RTC
alarm interrupt is done via HPET.
The difference between count and len is that len is capped at
4095. Changing it like this makes it match how sysfs_write_file() is
implemented.
Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
---
This is a static analysis patch. I haven't found any store_attribute()
functions where this
On Tue, Apr 30, 2013 at 10:12:38AM +0300, Julian Anastasov wrote:
Hello,
On Tue, 30 Apr 2013, Simon Horman wrote:
This is intended for use in loops which read data protected by RCU and may
have a large number of iterations. Such an example is dumping the list of
connections
Martin K. Petersen martin.peter...@oracle.com wrote:
Florian == Florian Westphal f...@strlen.de writes:
Florian After update to 3.8 dmesg is spammed with: kernel: [
Florian 280.272094] 3w-: scsi8: Unknown scsi opcode: 0x41 kernel: [
Florian 280.272107] sd 8:0:0:0: [sda] Unhandled error
Hi,
On 04/30/2013 02:55 AM, Stephen Rothwell wrote:
Hi Tomi,
In Linus' tree, today's linux-next build (powerpc ppc64_defconfig)
produced this warning:
drivers/video/ps3fb.c: In function 'ps3fb_mmap':
drivers/video/ps3fb.c:712:2: warning: suggest parentheses around '+' inside
''
Linus,
Please pull the latest x86-asm-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-asm-for-linus
HEAD: bec1b9e76353ecf05fac6a87f8e4102dfb618cd2 extable: Flip the sorting
message
Small tweak to reduce kmsg boot time spam.
out-of-topic
Hello,
On Tue, 30 Apr 2013, Simon Horman wrote:
+static void inline cond_resched_rcu_lock(void)
+{
+ if (need_resched()) {
Ops, it should be without above need_resched.
Thanks, to clarify, just this:
static void inline cond_resched_rcu_lock(void)
{
This patch looks like it should be in the 3.8-stable tree, should we apply
it?
--
From: Davidlohr Bueso davidlohr.bu...@hp.com
commit 30493cc9dddb68066dcc4878015660fdaa8e0965 upstream
Optimize the current version of the shift-and-subtract (hardware)
algorithm, described by John
Linus,
Please pull the latest x86-cleanups-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-cleanups-for-linus
HEAD: d50ba3687b99213501463a1947e3dd5b98bc2d99 x86/lib: Fix spelling, put
space between a numeral and its units
Misc smaller cleanups.
Linus,
Please pull the latest x86-cpu-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-cpu-for-linus
HEAD: 1077c932db63ecc571c31df1c24d4a44e30928e5 x86, CPU, AMD: Drop useless
label
The biggest change is x86 CPU bug handling refactoring and
From: Stephen Rothwell s...@canb.auug.org.au
Date: Fri, 26 Apr 2013 13:24:47 +1000
Today's linux-next merge of the net-next tree got a conflict in
drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c between commit
ecf01c22be03 (bnx2x: Prevent NULL pointer dereference in kdump) from
the net tree
From: Stephen Rothwell s...@canb.auug.org.au
Date: Fri, 26 Apr 2013 13:27:01 +1000
Today's linux-next merge of the net-next tree got a conflict in
drivers/net/ethernet/emulex/benet/be.h between commit bc0c3405abbb
(be2net: fix a Tx stall bug caused by a specific ipv6 packet) from the
net tree
From: Stephen Rothwell s...@canb.auug.org.au
Date: Fri, 26 Apr 2013 13:48:14 +1000
Hi all,
After merging the net-next tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
drivers/net/ethernet/emulex/benet/be_main.c: In function
'be_insert_vlan_in_pkt':
From: Stephen Rothwell s...@canb.auug.org.au
Date: Tue, 30 Apr 2013 12:24:23 +1000
Today's linux-next merge of the net-next tree got a conflict in
net/mac802154/mac802154.h between commit 2c1bbbffa0b6 (net: mac802154:
comparision issue of type cast, finding by EXTRA_CFLAGS=-W) from the net
Linus,
Please pull the latest x86-debug-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-debug-for-linus
HEAD: 147ea09119e45caf2e8bf57c9e54cc930ccfeda9 x86, early-printk: Update
earlyprintk documentation (and kill x86 copy)
Two small changes: a
Linus,
Please pull the latest x86-kaslr-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-kaslr-for-linus
HEAD: c889ba801dc3b3a0155fa77d567f2c3a6097de1c x86, relocs: Refactor the
relocs tool to merge 32- and 64-bit ELF
This merge contains changes
Linus,
Please pull the latest x86-mm-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-mm-for-linus
HEAD: 13f72756da86f155898e2c2022f7b3a106c3742e x86/iommu/dmar: Remove
warning for HPET scope type
Misc smaller changes all over the map.
Linus,
Please pull the latest x86-paravirt-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-paravirt-for-linus
HEAD: 4d681be3c33dd74efffbe2a8f70634f7128602ec x86, wakeup, sleep: Use pvops
functions for changing GDT entries
Various
Linus,
Please pull the latest x86-platform-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-platform-for-linus
HEAD: 06d219dc22daa26b79ec8e611caa68801607f15d x86/setup: Drop unneeded
include asm/dmi.h
Small fixes and cleanups all over the map.
On Tue, 2013-04-30 at 07:16 +0200, Mike Galbraith wrote:
Well now, that's not exactly what I expected to see for AIM7 compute.
Filesystem is munching cycles otherwise used for compute when load is
spread across the whole box vs consolidated.
So AIM7 compute performance delta boils down to:
Linus,
please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial.git for-linus
to receive 3.10 merge window updates from trivial queue.
==
Usual stuff, mostly comment fixes, typo fixes, printk fixes and small code
cleanups.
==
You are going to get two conflicts:
Linus,
please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-linus
to receive HID subsystem updates for 3.10. Highlights:
- hid driver transport cleanup, finalizing the long-desired decoupling of
core from transport layers, by Benjamin Tissoires and Henrik
Hi Arve,
On 30/04/13 00:13, Arve Hjønnevåg wrote:
On Mon, Apr 29, 2013 at 9:16 AM, Serban Constantinescu
serban.constantine...@arm.com wrote:
Hi all,
Any feedback or comments on this patch set?
You don't seem to have addressed my feedback on the previous patch set.
For v3 I have modified
Linus,
Please pull the latest x86-ras-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-ras-for-linus
HEAD: 5379f8c0d72cab43bbe6d974ceb3ad84dddc2b8e Merge tag 'edac_amd_f16h' of
git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras into x86/ras
This
Fix the following compilation warnings:
mm/slab.c: In function ‘kmem_cache_init_late’:
mm/slab.c:1778:2: warning: statement with no effect [-Wunused-value]
mm/page_cgroup.c: In function ‘page_cgroup_init’:
mm/page_cgroup.c:305:2: warning: statement with no effect [-Wunused-value]
* Mike Galbraith bitbuc...@online.de wrote:
On Tue, 2013-04-30 at 07:16 +0200, Mike Galbraith wrote:
Well now, that's not exactly what I expected to see for AIM7 compute.
Filesystem is munching cycles otherwise used for compute when load is
spread across the whole box vs consolidated.
This patch looks like it should be in the 3.8-stable tree, should we apply
it?
--
From: Chen Gang gang.c...@asianux.com
commit 12b2f117f3bf738c1a00a6f64393f1953a740bd4 upstream
audit_trim_trees() calls get_tree(). If a failure occurs we must call
put_tree().
On Mon, 29 Apr 2013, Clark Williams wrote:
On Mon, 29 Apr 2013 22:12:02 +0200
Sebastian Andrzej Siewior bige...@linutronix.de wrote:
- suspend / resume seems to program program the timer wrong and wait
ages until it continues.
It has to be something we're doing when we
* Matt Fleming m...@console-pimps.org wrote:
Hi folks,
This commit fixes the merge botch I created when merging -rc8 into
tip/x86/efi, where I dropped the select UCS2_STRING string from
drivers/firmware/Kconfig. The string actually needs to be moved to
arch/ia64 because parts of the core
* Paul E. McKenney paul...@linux.vnet.ibm.com wrote:
Hello, Ingo,
This series includes documentation for reducing OS jitter due to
per-CPU kthreads. It is available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/doc
for you to
* Paul E. McKenney paul...@linux.vnet.ibm.com wrote:
Hello, Ingo,
This change adds documentation for CONFIG_NO_HZ_IDLE and CONFIG_NO_HZ_FULL.
It is available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/nohz
for you to fetch
Hi Kirill,
On 30/04/13 08:31, Kirill A. Shutemov wrote:
On Fri, Apr 12, 2013 at 01:25:49PM +0100, Serban Constantinescu wrote:
The patch set has been successfully tested with a 64bit Linux userspace and
64bit binder unit-tests.
This patch set has been successfully tested on 32bit
On Tue, Apr 30, 2013 at 09:52:34AM +0100, Serban Constantinescu wrote:
Hi Kirill,
On 30/04/13 08:31, Kirill A. Shutemov wrote:
On Fri, Apr 12, 2013 at 01:25:49PM +0100, Serban Constantinescu wrote:
The patch set has been successfully tested with a 64bit Linux userspace and
64bit binder
memory_add_physaddr_to_nid() is declared in include/linux/memory_hotplug.h,
protected by CONFIG_NUMA. And in x86, the definitions are protected by
CONFIG_MEMORY_HOTPLUG.
memory_add_physaddr_to_nid() uses numa_meminfo to find the physical address's
nid. It has nothing to do with memory hotplug.
We mark out movable memory ranges and reserve them with MEMBLK_HOTPLUGGABLE
flag in
memblock.reserved. This should be done after the memory mapping is initialized
because the kernel now supports allocate pagetable pages on local node, which
are kernel pages.
The reserved hotpluggable will be
Arrange hotpluggable memory as ZONE_MOVABLE will cause NUMA performance
decreased
because the kernel cannot use movable memory.
For users who don't use memory hotplug and who don't want to lose their NUMA
performance, they need a way to disable this functionality.
So, if users specify
Since we have introduced hotplug info into struct numa_meminfo, we need
to consider it when cleanup numa_meminfo.
The original logic in numa_cleanup_meminfo() is:
Merge blocks on the same node, holes between which don't overlap with
memory on other nodes.
This patch modifies
On 04/30/2013 02:15 AM, Bjorn Helgaas wrote:
On Mon, Apr 29, 2013 at 08:19:10AM -0700, Yinghai Lu wrote:
On Mon, Apr 29, 2013 at 3:04 AM, Gu Zheng guz.f...@cn.fujitsu.com wrote:
On 04/27/2013 05:01 AM, Yinghai Lu wrote:
On Fri, Apr 26, 2013 at 1:53 PM, Bjorn Helgaas bhelg...@google.com wrote:
node-life-cycle data (whose life cycle is the same as a node)
allocated by memblock should be marked so that when we free usable
memory to buddy system, we can skip them.
This patch introduces a flag MEMBLK_LOCAL_NODE for memblock to reserve
node-life-cycle data. For now, it is only kernel direct
We reserved hotpluggable memory in memblock. And when memory initialization
is done, we have to free it to buddy system.
This patch free memory reserved by memblock with flag MEMBLK_HOTPLUGGABLE.
Signed-off-by: Tang Chen tangc...@cn.fujitsu.com
---
include/linux/memblock.h |1 +
In memory hotplug situation, the hotpluggable memory should be
arranged in ZONE_MOVABLE because memory in ZONE_NORMAL may be
used by kernel, and Linux cannot migrate pages used by kernel.
So we need a way to specify hotpluggable memory as movable. It
should be as easy as possible.
According to
If all the memory ranges in SRAT are hotpluggable, we should not
arrange them all in ZONE_MOVABLE. Otherwise the kernel won't have
enough memory to boot.
This patch introduce a global variable kernel_nodemask to mark
all the nodes the kernel resides in. And no matter if they are
hotpluggable, we
Since we modify movablecore boot option to support
movablecore=acpi, this patch adds doc for it.
Signed-off-by: Tang Chen tangc...@cn.fujitsu.com
---
Documentation/kernel-parameters.txt |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git
There is no flag in memblock to discribe what type the memory is.
Sometimes, we may use memblock to reserve some memory for special usage.
For example, as Yinghai did in his patch, allocate pagetables on local
node before all the memory on the node is mapped.
Please refer to Yinghai's patch:
v1:
On Mon, Apr 22, 2013 at 12:22:32PM +0200, Nicolas Ferre wrote:
On 04/19/2013 11:11 AM, ludovic.desroc...@atmel.com :
From: Ludovic Desroches ludovic.desroc...@atmel.com
Update at_hdmac driver to support generic DMA device tree binding. Devices
can still request channel with
Since Yinghai has implement Allocate pagetable pages in local node, for a
node with hotpluggable memory, we have to allocate pagetable pages first, and
then reserve the rest as hotpluggable memory in memblock.
But the kernel parse SRAT first, and then initialize memory mapping. So we have
to
The Hot-Pluggable field in SRAT suggests if the memory could be
hotplugged while the system is running. Print it as well when
parsing SRAT will help users to know which memory is hotpluggable.
Signed-off-by: Tang Chen tangc...@cn.fujitsu.com
---
arch/x86/mm/srat.c |9 ++---
1 files
The Hot-Pluggable Fired in SRAT specified which memory ranges are hotpluggable.
We will arrange hotpluggable memory as ZONE_MOVABLE for users who want to use
memory hotplug functionality. But this will cause NUMA performance decreased
because kernel cannot use ZONE_MOVABLE.
So we improve
From: Yasuaki Ishimatsu isimatu.yasu...@jp.fujitsu.com
If system can create movable node which all memory of the
node is allocated as ZONE_MOVABLE, setup_node_data() cannot
allocate memory for the node's pg_data_t.
So, use memblock_alloc_try_nid() instead of memblock_alloc_nid()
to retry when the
Hi Steve and all RT Folks
I'm pleased to announce the 3.4.41-rt55-feat3 feature release.
Note, I first uploaded -feat2 then realized I didn't add a compile fix by
Mike Galbraith, and then created the -feat3 with that fix.
I just wanted to say thanks that this patch enables compilation again
Hi,
Today I discovered an issue while building linux-next for at91:
CC arch/arm/mach-at91/at91sam9260_devices.o
In file included from
/home/nferre/dev/lnx_buid_test/arch/arm/mach-at91/at91sam9260_devices.c:12:0:
/home/nferre/dev/lnx_buid_test/arch/arm/include/asm/mach/arch.h:46:2: error:
Dave Hansen reported strange utime/stime values on his system:
https://lkml.org/lkml/2013/4/4/435
This happens because prev-stime value is bigger than rtime value.
Root of the problem are non-monotonic rtime values (i.e. current rtime
is smaller than previous rtime) and that should be debugged
This reverts commit f792685006274a850e6cc0ea9ade275ccdfc90bc.
Scaling cputime code was changed and does not need div64_u64_rem
primitives. They seems to have no other users, so let's remove them.
Signed-off-by: Stanislaw Gruszka sgrus...@redhat.com
---
include/linux/math64.h | 19
Due to rounding in scale_stime(), for big numbers, scaled stime values
will grow in chunks. Since rtime grow in jiffies and we calculate utime
like below:
prev-stime = max(prev-stime, stime);
prev-utime = max(prev-utime, rtime - prev-stime);
we could erroneously account stime
Here is patch, which add Linus cputime scaling algorithm to the kernel.
This is follow up of commit d9a3c9823a2e6a543eb7807fb3d15d8233817ec5
sched: Lower chances of cputime scaling overflow which try to avoid
multiplication overflow, but not guarantee that the overflow will not
happen.
Linus
On Tue, 2013-04-30 at 10:41 +0200, Ingo Molnar wrote:
* Mike Galbraith bitbuc...@online.de wrote:
On Tue, 2013-04-30 at 07:16 +0200, Mike Galbraith wrote:
Well now, that's not exactly what I expected to see for AIM7 compute.
Filesystem is munching cycles otherwise used for compute
On Tue, Apr 30, 2013 at 11:33 AM, Nicolas Ferre nicolas.fe...@atmel.com wrote:
So, I am wondering if the best correction is to add the types.h header file
in the asm/mach/arch.h file, like this:
--- a/arch/arm/include/asm/mach/arch.h
+++ b/arch/arm/include/asm/mach/arch.h
@@ -8,6 +8,8 @@
From: Jan-Simon Möller dl...@gmx.de
Signed-off-by: Jan-Simon Möller dl...@gmx.de
---
include/acpi/acpiosxf.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/acpi/acpiosxf.h b/include/acpi/acpiosxf.h
index 5b3d2bd..64b8c76 100644
--- a/include/acpi/acpiosxf.h
+++
Commit b00adbe0 (ARM: sunxi: Rename uart nodes to serial) changed the
node names in the DTSI, changes that were not accordingly made to the
Mini X-Plus device tree. This breakage slipped through because it was
not properly declared in the Makefile.
Fix both issues.
Signed-off-by: Maxime Ripard
I get the following warning on boot:
[ cut here ]
WARNING: at drivers/base/core.c:575 device_create_file+0x9a/0xa0()
Hardware name: -[8737R2A]-
Write permission without 'store'
Modules linked in: sb_edac(+) edac_core i2c_i801 i2c_core lpc_ich mfd_core
shpchp wmi ioatdma
On Tue, 2013-04-30 at 11:35 +0200, Mike Galbraith wrote:
On Tue, 2013-04-30 at 10:41 +0200, Ingo Molnar wrote:
Which are the workloads where 'powersaving' mode hurts workload
performance measurably?
Well, it'll lose throughput any time there's parallel execution
potential but it's
Hi,
I have an idea to improve the Kconfig dependencies, especially for
subsystem maintainers. First a bit of history:
I recently changed the Kconfig rules for omapdss driver to not depend on
OMAP platform, as the driver itself uses no OMAP specific APIs, and can
be compiled fine on, say, x86.
The A13 has a lot less clocks than the one found in the Allwinner A10.
Add these stripped down clocks to the clock driver and in the
documentation.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
---
Documentation/devicetree/bindings/clock/sunxi.txt | 117 +++--
The Allwinner A13 has a smaller clock set than the one found in the A10.
Fix the A13 device tree and documentation to reflect this.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
---
arch/arm/boot/dts/sun5i-a13.dtsi | 35 ---
1 file changed, 12
On Tue, 2013-04-30 at 11:49 +0200, Mike Galbraith wrote:
On Tue, 2013-04-30 at 11:35 +0200, Mike Galbraith wrote:
On Tue, 2013-04-30 at 10:41 +0200, Ingo Molnar wrote:
Which are the workloads where 'powersaving' mode hurts workload
performance measurably?
Well, it'll lose
From: Jan-Simon Möller dl...@gmx.de
The variable name events_group is already in used and led to a compilation error
when using clang to build the Linux Kernel . The fix is just to rename the var.
No functional change. Please apply.
Fix suggested in discussion by PaX Team pagee...@freemail.hu
- *busw = 0;
- if (le16_to_cpu(p-features) 1)
- *busw = NAND_BUSWIDTH_16;
+
+ *busw = (onfi_feature(chip) ONFI_FEATURE_16_BIT_BUS) ?
+ NAND_BUSWIDTH_16 : 0;
Is this really needed ? you have already checked the 'onfi_version' above in
Add new property tx-rx-clk-separate which we can distinquish between common
and separate clock for tx and rx blocks.
Signed-off-by: Marek Belisko marek.beli...@streamunlimited.com
---
.../bindings/sound/davinci-mcasp-audio.txt |2 ++
include/linux/platform_data/davinci_asp.h
On 30/04/13 11:04, Kirill A. Shutemov wrote:
On Tue, Apr 30, 2013 at 09:52:34AM +0100, Serban Constantinescu wrote:
Hi Kirill,
On 30/04/13 08:31, Kirill A. Shutemov wrote:
On Fri, Apr 12, 2013 at 01:25:49PM +0100, Serban Constantinescu wrote:
The patch set has been successfully tested with a
Hi Arnd,
On Tue, Apr 30, 2013 at 12:00:19AM +0200, Arnd Bergmann wrote:
There is no reason for ssbi to have its own top-level driver directory
when the only users of this interface are all MFD drivers. The only
mainline driver using it at the moment (PM8921) is marked broken and in
fact does
So, my idea is to have a new kind of Kconfig dependency. I'll call it
softdepends in lack of better name. A driver maintainer could use
softdepends on ARCH_OMAP, instead of depends on ARCH_OMAP, to say
that this driver does not actually build depend on ARCH_OMAP, but for
all normal purposes
1 - 100 of 926 matches
Mail list logo
