On Tue, Aug 05, 2014 at 06:21:39PM -0700, Paul E. McKenney wrote:
> > Yeah, idle threads can be affected by the trampolines. That is, we can
> > still hook a trampoline to some function in the idle loop.
> >
> > But we should be able to make the hardware call that puts the CPU to
> > sleep a quies
于 2014/8/4 17:43, Marc Zyngier 写道:
> Hi Liu,
>
> On 04/08/14 05:17, Liu Hua wrote:
>> When using kdump on ARM platform, if kernel panics in interrupt handler
>> (maybe PPI), the capture kernel can not recive certain interrupt, and
>> fails to boot.
>>
>> On this situation, We have read register G
efi rtc depends on efi runtime services, so if efi runtime services are not
usable it should error out.
Without this patch rtc-efi will panic with 'noefi' boot
Signed-off-by: Dave Young
---
drivers/rtc/rtc-efi.c |3 +++
1 file changed, 3 insertions(+)
Index: linux-2.6/drivers/rtc/rtc-efi.
Adding a noefi boot param like in X86 to disable efi runtime services support.
This will be useful for debugging uefi problems. Also it will be useful
for later kexec/kdump work. Kexec on uefi support in X86 depends on a fixed vm
area specific for uefi runtime 1:1 mapping, kernel will switch to a
There are three clock for ESAI, esai_extal, esai_ipg, esai_mem. Rename
'esai' to 'esai_extal', 'esai_ahb' to 'esai_mem', and add 'esai_ipg'.
Make the clock for ESAI more clear and align them with imx6sx.
Signed-off-by: Shengjiu Wang
---
arch/arm/mach-imx/clk-imx6q.c |7 ---
i
This patch mainly adds the clock route from external 24.576MHz OSC to internal
ESAI clock via analog clock2 PADs on the SoC and pll4 so that ESAI can get an
entirely synchronous clock source against CS42888.
[ 1, We found if using pll4 to generate a 24.576MHz from inernal 24.0MHz OSC,
we would g
refine clock tree for esai in imx6q
Changes for V2
- Add pll5_sel And update the comments for patch 2.
- As the bypass mode is not supported in clk tree, so update the
- comments for patch 3.
Shengjiu Wang (3):
ARM: clk-imx6q: refine clock tree for ESAI
ARM: clk-imx6q: Add missing lvds and a
anaclk1 and anaclk2 is the clock source for lvds1_in and lvds2_in. lvds1_in
and lvds2_in can be used to provide external clock source to the internal
pll, such as pll4_audio and pll5_video.
pll4_audio and pll5_video can have multiple source, not only "osc", so
add them.
Signed-off-by: Nicolin Chen
On Tue, Aug 05, 2014 at 09:57:51AM +0200, Christian Borntraeger wrote:
> commit 4badad352a6bb202ec68afa7a574c0bb961e5ebc (locking/mutex: Disable
> optimistic spinning on some architectures) fenced spinning for
> architectures without proper cmpxchg.
> There is no need to disable mutex spinning on s
On 06.08.2014, Nick Krause wrote:
> I am going to have to ask a few questions first, what distribution is
> and is this a vanilla kernel?
Read his mail. He's on Debian, and it's a Debian kernel.
> If it's not just send the report to the distribution developers.
His mail is quite sure a copy fr
On Wed, Aug 06, 2014 at 11:51:29AM +0400, Ilya Dryomov wrote:
> OK, this one is a bit different.
>
> WARNING: CPU: 1 PID: 1744 at kernel/sched/core.c:7104
> __might_sleep+0x58/0x90()
> do not call blocking ops when !TASK_RUNNING; state=1 set at
> [] prepare_to_wait+0x50 /0xa0
> [] __might_sle
Hi Pekon,
On 08/05/2014 11:30 PM, pe...@pek-sem.com wrote:
> Hi Roger,
>
> On Tuesday 05 August 2014 09:45 PM, Grazvydas Ignotas wrote:
>> On Tue, Aug 5, 2014 at 1:11 PM, Roger Quadros wrote:
>>> For v3.12 and prior, 1-bit Hamming code ECC via software was the
>>> default choice. Commit c66d0391
On Wed, Aug 06, 2014 at 05:29:48AM +0800, Fengguang Wu wrote:
> Hi Peter,
>
> FYI, we noticed the below changes on
>
> git://internal_merge_and_test_tree devel-athens-alpha-201408042000
> commit 36932a9e2b1043506d06414fa988cd5b9592841f ("sched: Fix
> finish_task_switch vs prev_state")
>
> test
On Tue, Aug 05, 2014 at 03:36:39PM -0700, Linus Torvalds wrote:
> On Tue, Aug 5, 2014 at 2:07 PM, Frank Ch. Eigler wrote:
> >
> > Actually, "perf probe" does (via HAVE_DWARF_SUPPORT), to place probes
> > and to extract variables at those probes, much as systemtap does.
> > Without var-tracking, pr
On Tue, 2014-08-05 at 16:30 -0400, Nick Krause wrote:
> I understand if you don't want to give me a second change , but if you want to
> help me learn, I would love to be cced into anything I can learn from. In
> terms of subsystems support I would like to help out in a few. My list is
> below.
>
On 6 August 2014 03:36, Saravana Kannan wrote:
> Stephen and I looked into this. This is not a sysfs framework difference.
> The reason we don't have this issue when we use global tunables is because
> we add the attribute group to the cpufreq_global_kobject and that kobject
> doesn't have a kobj_
Bad situation:
double_lock_balance() drops busiest_rq lock. The busiest_rq is *busiest*,
and a lot of tasks and context switches there. We are dropping the lock
and waiting for it again.
Let's just detach the task and once finally unlock it!
Warning: this admits unlocked using of can_migrate_ta
This is a new state which will be used to indicate that
a task is in a process of migrating between two RQs. It
allows to get rid of double_rq_lock(), which we used to
use to change rq of a queued task before.
Let's consider the example. To move a task between src_rq
and dst_rq we will do the fol
Keep on_rq = ONRQ_MIGRATING, while task is migrating, instead.
Signed-off-by: Kirill Tkhai
---
kernel/sched/fair.c | 99 ---
1 file changed, 70 insertions(+), 29 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index cfeafb1.
Implement task_queued() and use it everywhere instead of on_rq check.
No functional changes.
The only exception is we do not use the wrapper in check_for_tasks(),
because it requires to export task_queued() in global header files.
Next patch in series would return it back, so it doesn't matter.
Let's use ONRQ_MIGRATING instead.
Signed-off-by: Kirill Tkhai
---
kernel/sched/core.c | 23 +++
1 file changed, 15 insertions(+), 8 deletions(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 1cf5109..05687ce 100644
--- a/kernel/sched/core.c
+++ b/kernel/sch
(sched_entity::on_rq == 1) does not guarantee the task is pickable;
changes on throttled cfs_rq must not lead to reschedule.
Check for task_struct::on_rq instead.
Signed-off-by: Kirill Tkhai
---
kernel/sched/fair.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/ke
This series aims to get rid of some places where locks of two RQs are held
at the same time.
Patch [1/6] is a fix/preparation. It's new in v4 version of series.
Patch [2/6] is a preparation/cleanup. It replaces old (task_struct::on_rq == 1)
with new (task_struct::on_rq == ONRQ_QUEUED) everywhere
Hi,
This patch get a compile warn.
I'll resend one.
Thanks
On 2014/8/6 2:29, Greg Kroah-Hartman wrote:
> 3.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Gao feng
>
> commit 33d99113b1102c2d2f8603b9ba72d89d915c13f5 upstream.
>
> co
Hi Gražvydas,
On 08/05/2014 07:15 PM, Grazvydas Ignotas wrote:
> On Tue, Aug 5, 2014 at 1:11 PM, Roger Quadros wrote:
>> For v3.12 and prior, 1-bit Hamming code ECC via software was the
>> default choice. Commit c66d039197e4 in v3.13 changed the behaviour
>> to use 1-bit Hamming code via Hardware
On Tue, Aug 5, 2014 at 5:06 PM, Peter Zijlstra wrote:
> On Tue, Aug 05, 2014 at 12:33:16PM +0400, Ilya Dryomov wrote:
>> On Mon, Aug 4, 2014 at 2:30 PM, Peter Zijlstra wrote:
>> > Hi,
>> >
>> > Ilya recently tripped over a nested sleep which made Ingo suggest we should
>> > have debug checks for
This fixes a error handling scenario where clocks were not being disabled
when QUP_OUTPUT_BLOCK_SIZE returns a size greater thanat size of blk_sizes
array. So this patch adds a statement to jump to err lable to release the
clocks.
CC: Wolfram Sang
CC: Grant Likely
CC: Bjorn Andersson
CC: Andy G
This fixes a error handling scenario where clocks were not being disabled
when QUP_OUTPUT_BLOCK_SIZE returns a size greater thanat size of blk_sizes
array. So this patch adds a statement to jump to err lable to release the
clocks.
Wolfram Sang
Grant Likely
Bjorn Andersson
Andy Gross
"Ivan T. I
On Wed, 2014-08-06 at 07:41 +0200, Mike Galbraith wrote:
> You're reading me entirely wrong, I'm not trying to discourage you from
> inventing a better bullet, I just think this particular bullet is a dud.
Anyway, I'll try to assume you're talking to the _reasonable_ people on
this list in any re
On 05/08/2014 at 21:43:16 -0700, Hans Wennborg wrote :
> The prefix suggests the number should be printed in hex, so use
> the %x specifier to do that.
>
> Found by using regex suggested by Joe Perches.
>
> Signed-off-by: Hans Wennborg
Acked-by: Alexandre Belloni
> ---
> drivers/pinctrl/pinct
On Wednesday 30 July 2014 10:10 PM, Mark Brown wrote:
* PGP Signed by an unknown key
On Wed, Jul 30, 2014 at 04:53:03PM +0100, Mark Rutland wrote:
On Wed, Jul 30, 2014 at 02:54:00PM +0100, Laxman Dewangan wrote:
+Required properties:
+- compatible : Must be "reg-userspace-consumer".
> -Original Message-
> From: Ulf Hansson [mailto:ulf.hans...@linaro.org]
> Sent: Wednesday, July 02, 2014 5:01 PM
> To: Chen, Alvin
> Cc: Chris Ball; linux-mmc; linux-kernel@vger.kernel.org; Ong, Boon Leong
> Subject: Re: [PATCH v2] mmc: sdhci-pci: SDIO host controller support for Intel
> Q
On 05/08/14 16:53, Eduardo Valentin wrote:
Hello Mikko,
On Tue, Aug 05, 2014 at 03:18:57PM +0300, Mikko Perttunen wrote:
This adds support for the Tegra SOCTHERM thermal sensing and management
system found in the Tegra124 system-on-chip. This initial driver supports
the four thermal zones with
On Fri, Aug 01, 2014 at 09:12:06AM +0900, Gioh Kim wrote:
>
>
> 2014-08-01 오전 7:57, Andrew Morton 쓴 글:
> >On Thu, 31 Jul 2014 11:22:35 +0900 Gioh Kim wrote:
> >
> >>The previous PATCH inserts invalidate_bh_lrus() only into CMA code.
> >>HOTPLUG needs also dropping bh of lru.
> >>So v2 inserts in
Hi all,
Please do not add code intended for v3.18 until after v3.17-rc1 is
released.
Changes since 20140805:
The powerpc tree gained a build failure that only affected the powerpc
allyesconfig build, so I left it btroken.
The sparc-next tree gained a conflict against the sparc tree.
The drm tr
On 08/06/2014 06:43 AM, Hans Wennborg wrote:
The prefix suggests the number should be printed in hex, so use
the %x specifier to do that.
Found by using regex suggested by Joe Perches.
Signed-off-by: Hans Wennborg
---
drivers/scsi/cxgbi/libcxgbi.c | 2 +-
drivers/scsi/nsp32.c
> > static int i2c_imx_dma_write(struct imx_i2c_struct *i2c_imx,
> > struct i2c_msg *msgs)
> >
> > run checkpatch.pl on this patch...
>
> Sorry for my code style. I will match open parenthesis in this case.
FYI, I am not strict on the open parenthesis thingie.
signatu
On Wed, Aug 06, 2014 at 04:18:26PM +0900, Joonsoo Kim wrote:
> Joonsoo Kim (8):
> mm/page_alloc: correct to clear guard attribute in DEBUG_PAGEALLOC
> mm/isolation: remove unstable check for isolated page
> mm/page_alloc: fix pcp high, batch management
> mm/isolation: close the two race pro
Mel Gorman writes:
> From d0c77a2b497da46c52792ead066d461e5111a594 Mon Sep 17 00:00:00 2001
> From: Mel Gorman
> Date: Tue, 5 Aug 2014 12:06:50 +0100
> Subject: [PATCH] mm: Remove misleading ARCH_USES_NUMA_PROT_NONE
>
> ARCH_USES_NUMA_PROT_NONE was defined for architectures that implemented
> _P
i.MX6SX has some new features of thermal interrupt function,
there are LOW, HIGH and PANIC irq for thermal sensor, so add
platform data to separate different thermal version;
The reset value of LOW ALARM is 0 which means the highest
temp, so the LOW ALARM will be triggered once irq is enabled,
so
Current isolation logic isolates each pageblock individually.
This causes freepage counting problem when page with pageblock order is
merged with other page on different buddy list. We can prevent it by
following solutions.
1. decrease MAX_ORDER to pageblock order
2. prevent merging buddy pages if
The check '!PageBuddy(page) && page_count(page) == 0 &&
migratetype == MIGRATE_ISOLATE' would mean the page on free processing.
Although it could go into buddy allocator within a short time,
futher operation such as isolate_freepages_range() in CMA, called after
test_page_isolated_in_pageblock(), c
The check '!PageBuddy(page) && page_count(page) == 0 &&
migratetype == MIGRATE_ISOLATE' would mean the page on free processing.
Although it could go into buddy allocator within a short time,
futher operation such as isolate_freepages_range() in CMA, called after
test_page_isolated_in_pageblock(), c
Current isolation logic isolates each pageblock individually.
This causes freepage counting problem when page with pageblock order is
merged with other page on different buddy list. To prevent it, we should
handle whole range at one time in start_isolate_page_range(). This patch
is preparation of t
There is a mistake on moving freepage from normal buddy list to isolate
buddy list. If we move page from normal buddy list to isolate buddy list,
We should subtract freepage count in this case, but, it didn't.
And, previous patches ('mm/isolation: close the two race problems related
to pageblock i
In __free_one_page(), we check the buddy page if it is guard page.
And, if so, we should clear guard attribute on the buddy page. But,
currently, we clear original page's order rather than buddy one's.
This doesn't have any problem, because resetting buddy's order
is useless and the original page's
Hello,
This patchset aims at fixing problems during memory isolation found by
testing my patchset [1].
These are really subtle problems so I can be wrong. If you find what I am
missing, please let me know.
Before describing bugs itself, I first explain definition of freepage.
1. pages on buddy
Current pageblock isolation logic has a problem that results in incorrect
freepage counting. move_freepages_block() doesn't return number of
moved pages so freepage count could be wrong if some pages are freed
inbetween set_pageblock_migratetype() and move_freepages_block(). Although
we fix move_fr
per cpu pages structure, aka pcp, has high and batch values to control
how many pages we perform caching. This values could be updated
asynchronously and updater should ensure that this doesn't make any
problem. For this purpose, pageset_update() is implemented and do some
memory synchronization. B
We got migratetype of the freeing page without holding the zone lock so
it could be racy. There are two cases of this race.
1. pages are added to isolate buddy list after restoring original
migratetype.
2. pages are added to normal buddy list while pageblock is isolated.
If case 1 happens, we can
In __free_one_page(), we check the buddy page if it is guard page.
And, if so, we should clear guard attribute on the buddy page. But,
currently, we clear original page's order rather than buddy one's.
This doesn't have any problem, because resetting buddy's order
is useless and the original page's
per cpu pages structure, aka pcp, has high and batch values to control
how many pages we perform caching. This values could be updated
asynchronously and updater should ensure that this doesn't make any
problem. For this purpose, pageset_update() is implemented and do some
memory synchronization. B
Am 05.08.2014 21:49, schrieb David Miller:
> From: walter harms
> Date: Tue, 05 Aug 2014 09:11:52 +0200
>
>>
>>
>> Am 04.08.2014 22:47, schrieb Andrey Utkin:
>>> This commit is a guesswork, but it seems to make sense to drop this
>>> break, as otherwise the following line is never executed and
Hi Morimoto-san,
On Wed, Aug 6, 2014 at 2:30 AM, Kuninori Morimoto
wrote:
>> >> > > Required properties:
>> >> > > -- compatible : "renesas,rcar-thermal"
>> >> > > +- compatible : "renesas,thermal-",
>> >> > > "renesas,rcar-thermal"
>> >> > > + as fallb
Fix the following warning reported by checkpatch.pl:
WARNING: else is not generally useful after a break or return
Signed-off-by: Kiran Padwal
---
drivers/i2c/i2c-core.c | 28 ++--
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/drivers/i2c/i2c-core.c b
Hi Fugang,
Duan Fugang wrote:
[...]
>+ dma_sconfig.dst_addr_width = DMA_SLAVE_BUSWIDTH_1_BYTE;
>+ dma_sconfig.dst_maxburst = 1;
> The maxburst is 1 cause very slow efficiency for DMA copy, which system
> performance even is slower Than cpu mode.
There is no FIFO for IMX i2c, so the maxb
601 - 656 of 656 matches
Mail list logo
