Sinan,
if we get rid of the part this code:
if (BITS_PER_LONG == 64) {
struct page **pages;
pages = kmalloc(sizeof *pages * buf->nbufs, gfp);
if (!pages)
goto err_free;
Hi Marc,
On Wednesday 13 April 2016 05:10 PM, Vineet Gupta wrote:
> Now that we have Timers probed from DT, don't need legacy domain
>
> This however requires mapping to be called explicitly for the IRQ which
> still can't (and probably never) be probed from DT such as IPI and
> SOFTIRQ
>
> Sign
On Wed, Apr 13, 2016 at 1:07 AM, Luis R. Rodriguez wrote:
> On Mon, Apr 11, 2016 at 03:52:43PM +0200, Christian König wrote:
>> Am 11.04.2016 um 15:39 schrieb Oded Gabbay:
>> >On Mon, Apr 11, 2016 at 4:28 PM, Christian König
>> > wrote:
>> >>Am 09.04.2016 um 02:25 schrieb Luis R. Rodriguez:
>> >>>
Add the selection options for the cyclic scheduler
Signed-off-by: Bill Huey (hui)
---
drivers/rtc/Kconfig | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig
index 3e84315..8da9796 100644
--- a/drivers/rtc/Kconfig
+++ b/drivers/rtc/Kconfig
@@ -73,6
Redirect rtc update irqs so that it drives the cyclic scheduler timer
handler instead. Let the handler determine which slot to activate next.
Similar to scheduler tick handling but just for the cyclic scheduler.
Signed-off-by: Bill Huey (hui)
---
drivers/rtc/interface.c | 23
Add additional ioctl() values to rtc so that it can 'admit' the calling
thread into a red-black tree for tracking, set the execution slot pattern,
support for setting whether read() will yield or block.
Signed-off-by: Bill Huey (hui)
---
include/uapi/linux/rtc.h | 4
1 file changed, 4 inser
- timer frequency is derived from DT (no longer rely on top level
DT "clock-frequency" probed early and exported by asm/clk.h)
- TIMER0_IRQ need not be exported across arch code, confined to intc as
it is property of same
- Any failures in clockevent setup are considered pedantic and sys
Anonymous struct initialization
Signed-off-by: Bill Huey (hui)
---
include/linux/init_task.h | 18 ++
1 file changed, 18 insertions(+)
diff --git a/include/linux/init_task.h b/include/linux/init_task.h
index f2cb8d4..ac9b0d9 100644
--- a/include/linux/init_task.h
+++ b/include/l
wait-queue changes to rtc_dev_read so that it can support overrun count
reporting when multiple threads are blocked against a single wait object.
ioctl() additions to allow for those calling it to admit the thread into
the cyclic scheduler.
Signed-off-by: Bill Huey (hui)
---
drivers/rtc/rtc-dev
Makefile changes to support the menuconfig option
Signed-off-by: Bill Huey (hui)
---
kernel/sched/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/sched/Makefile b/kernel/sched/Makefile
index 414d9c1..1e12a32 100644
--- a/kernel/sched/Makefile
+++ b/kernel/sched/Makefile
@@ -2
Task tracking per file descriptor for thread death clean up.
Signed-off-by: Bill Huey (hui)
---
drivers/rtc/class.c | 3 +++
include/linux/rtc.h | 3 +++
2 files changed, 6 insertions(+)
diff --git a/drivers/rtc/class.c b/drivers/rtc/class.c
index 74fd974..ad570b9 100644
--- a/drivers/rtc/class
Initial bits to prevent priority changing of cyclic scheduler tasks by
only allow them to be SCHED_FIFO. Fairly hacky at this time and will need
revisiting because of the security concerns.
Affects task death handling since it uses an additional scheduler class
hook for clean up at death. Must be
SCHED_FIFO/RT tail/head runqueue insertion support, initial thread death
support via a hook to the scheduler class. Thread death must include
additional semantics to remove/discharge an admitted task properly.
Signed-off-by: Bill Huey (hui)
---
kernel/sched/rt.c | 41
64/32bit architecture related changes. Change for m68k architecture
compilation problems.
Need to mask out the lower 4 bits of the hash inserts itself into the
rbtree, better statistical reporting of overrun events, more procfs
support for setting the interrupt source, yield testing and backwards
Core implementation of the cyclic scheduler that includes admittance
handling, thread death supprot, cyclic timer tick handler, primitive proc
debugging interface, wait-queue modifications.
Signed-off-by: Bill Huey (hui)
---
kernel/sched/cyclic.c| 612
Add an anonymous struct to support admittance using a red-black tree,
overrun tracking, state for whether or not to yield or block, debugging
support, execution slot pattern for the scheduler.
Signed-off-by: Bill Huey (hui)
---
include/linux/sched.h | 15 +++
1 file changed, 15 inser
Initial attempt at documentation with a test program
Signed-off-by: Bill Huey (hui)
---
Documentation/scheduler/sched-cyclic-rtc.txt | 468 +++
1 file changed, 468 insertions(+)
create mode 100644 Documentation/scheduler/sched-cyclic-rtc.txt
diff --git a/Documentation/s
On Sat, 16 Apr 2016 09:06:35 +0900,
Stephen Boyd wrote:
>
> On 04/14, Yoshinori Sato wrote:
> > Some SoC use 16bit-word register. And required 16bit-word access.
> > This changes add 16-bit access mode.
> >
> > Signed-off-by: Yoshinori Sato
>
> Please implement a custom divider for your hardwar
On Tue, Apr 05, 2016 at 05:05:13PM +0300, Roger Quadros wrote:
> Introduce usb_otg_add/remove_hcd() for use by host
> controllers that are part of OTG/dual-role port.
>
> Non Device tree platforms can use the otg_dev argument
> to specify the OTG controller device. If otg_dev is NULL
> then the de
The commit dc37374 move a lot of device tree files into fsl directory
fixing Makefile for cuImage target only. Unfortunately there are others
target which require to embebbed device tree into the kernel image
(i.e. dtbImage.%). So use a more generic approach.
Signed-off-by: Alessio Igor Bogani
--
Scott,
On 17 April 2016 at 03:50, Scott Wood wrote:
> On Fri, 2016-04-15 at 10:27 +0200, Alessio Igor Bogani wrote:
[...]
>> Any comments?
>
> Looks OK to me.
Thanks for review it. Follow a no-RFC version.
Ciao,
Alessio
>-Original Message-
>From: Rajesh Bhagat [mailto:rajesh.bha...@nxp.com]
>Sent: Monday, March 14, 2016 2:41 PM
>To: ba...@ti.com
>Cc: gre...@linuxfoundation.org; linux-...@vger.kernel.org; linux-
>ker...@vger.kernel.org; linux-o...@vger.kernel.org; Sriram Dash
>; Rajesh Bhagat
>Subject: [PA
To summarize the issue observed in error cases:
SW Flow: For i2c message transfer, packet header and data payload is posted
and then required error/packet completion interrupts are enabled later.
HW flow: HW process the packet just after packet header is posted, if ARB
lost/NACK error occurs (SW
... remove the redundant second iteration, this is most
likely a copy/past buglet.
Signed-off-by: Davidlohr Bueso
---
kernel/locking/qspinlock_stat.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/kernel/locking/qspinlock_stat.h b/kernel/locking/qspinlock_stat.h
index d734b7502001..7272233
Specifically around the debugfs file creation calls,
I have no idea if they could ever possibly fail, but
this is core code (debug aside) so lets at least
check the return value and inform anything fishy.
Signed-off-by: Davidlohr Bueso
---
kernel/locking/qspinlock_stat.h | 14 ++
1 f
While playing with such statistics I ran into the following
splat on a VM when opening pv_hash_hops:
[ 25.267962] divide error: [#1] SMP
...
[ 25.268807] CPU: 17 PID: 1018 Comm: cat Not tainted 4.6.0-rc3-debug+ #2
[ 25.268853] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
Tracking events describe kernel and threads. They are generated by
reading /proc/kallsyms, /proc/*/maps and /proc/*/task/* during
initialization of 'perf record', serialized into event sequences and put
at the head of 'perf.data'. In case of output switching, each output
file should contain those e
On Fri, 15 Apr 2016 00:45:17 +0900,
Tejun Heo wrote:
>
> Hello,
>
> On Thu, Apr 14, 2016 at 04:26:03PM +0900, Yoshinori Sato wrote:
> > Support for non x86 targets.
>
> Being a bit more detailed would be nice.
>
> > Signed-off-by: Yoshinori Sato
> > ---
> > drivers/ata/pata_artop.c | 16 +
Without this patch, the last output doesn't have timestamp appended if
--timestamp-filename is not explicitly provided. For example:
# perf record -a --switch-output &
[1] 11224
# kill -s SIGUSR2 11224
[ perf record: dump data: Woken up 1 times ]
# [ perf record: Dump perf.data.201512262
The cost of buildid cache processing is high: reading all events in
output perf.data, opening each elf file to read buildids then copying
them into ~/.debug directory. In switch output mode, these heavy works
block perf from receiving perf events for too long.
Enable no-buildid and no-buildid-cach
With 'perf record --switch-output' without -a, record__synthesize() in
record__switch_output() won't generate tracking events because there's
no thread_map in evlist. Which causes newly created perf.data doesn't
contain map and comm information.
This patch creates a fake thread_map and directly ca
Allow 'perf record' to split its output into multiple files.
For example:
# ~/perf record -a --timestamp-filename --switch-output &
[1] 10763
# kill -s SIGUSR2 10763
[ perf record: dump data: Woken up 1 times ]
# [ perf record: Dump perf.data.2015122622314468 ]
# kill -s SIGUSR2 1076
v3 -> v4: Reimplement trigger class, rename states, describe the transitions
of it in header and change log.
Signed-off-by: Wang Nan
Cc: Adrian Hunter
Cc: He Kuang
Cc: Jiri Olsa
Cc: Masami Hiramatsu
Cc: Namhyung Kim
Cc: Zefan Li
Cc: pi3or...@163.com
Wang Nan (6):
perf tools: De
Use 'trigger' to model operations which need to be executed when
an event (a signal, for example) is observed.
States and transits:
OFF--(on)--> READY --(toggle)--> TOGGLED --(process)--> PROCESSING
^| |
|
Hi,
On 18.04.2016 00:44, Sakari Ailus wrote:
Hi Ivaylo,
On Sat, Apr 16, 2016 at 11:12:20AM +0300, Ivaylo Dimitrov wrote:
Some sensors (like the one in Nokia N900) provide metadata in the first
couple of lines. Make that information information available to the
pipeline.
Signed-off-by: Ivaylo
64/32bit architecture related changes. Change for m68k architecture
compilation problems.
Need to mask out the lower 4 bits of the hash inserts itself into the
rbtree, better statistical reporting of overrun events, more procfs
support for setting the interrupt source, yield testing and backwards
Hi Boris,
On Fri, Mar 25, 2016 at 4:35 PM, Boris Brezillon
wrote:
> Hi Peter,
>
> On Mon, 14 Mar 2016 02:47:55 +
> Peter Pan wrote:
>
>> From: Brian Norris
>>
>> Currently nand_bbt.c is tied with struct nand_chip, and it makes other
>> NAND family chips hard to use nand_bbt.c. Maybe it's t
On 04/17/16 23:14, Andy Lutomirski wrote:
>>
>> It's not "weird", it is the ABI as defined. We have to do this for all
>> the system call arguments, too; you just don't notice it because the
>> compiler does it for us. Some other architectures, e.g. s390, has the
>> opposite convention where the
On Sun, Apr 17, 2016 at 11:01 PM, H. Peter Anvin wrote:
> On 04/17/16 22:48, Andy Lutomirski wrote:
>>
>> I think I prefer the "reject weird input" behavior over the "accept
>> and normalize weird input" if we can get away with it, and I'm fairly
>> confident that we can get away with "reject weir
Hi Leonard and Jonathan,
basically the patch can not work.
Current ST infrastructure needs to use one i2c slave per driver (accel or magn
or gyro).
All sensors currently supported (including lsm303agr) have one i2c address per
sensor type (for example in lsm303agr, accel has one i2c address, mag
> -Original Message-
> From: Rajesh Bhagat
> Sent: Monday, April 18, 2016 11:31 AM
> To: 'ba...@ti.com'
> Cc: 'gre...@linuxfoundation.org' ; 'linux-
> u...@vger.kernel.org' ;
> 'linux-kernel@vger.kernel.org'
> ; 'linux-o...@vger.kernel.org' o...@vger.kernel.org>; Sriram Dash ; Rajesh B
On 18 April 2016 at 13:45, Herbert Xu wrote:
> On Mon, Apr 18, 2016 at 01:31:09PM +0800, Baolin Wang wrote:
>>
>> We've tried to do this in dm-crypt, but it failed.
>> The dm-crypt maintainer explained to me that I should optimize the
>> driver, not add strange hw-dependent crypto modes to dm-cryp
On 04/17/16 22:48, Andy Lutomirski wrote:
>
> I think I prefer the "reject weird input" behavior over the "accept
> and normalize weird input" if we can get away with it, and I'm fairly
> confident that we can get away with "reject weird input" given that
> distro kernels do exactly that already.
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
wb-buf-throttle
commit e7b81af035ddc1323090d86350627881fcf9b1b0 ("blk-wb: updates")
+++-
On Friday 15 April 2016 09:47 PM, David Lechner wrote:
> On 04/15/2016 05:24 AM, Sekhar Nori wrote:
>
>>
>> This made me notice that num-cs is populated wrongly for spi1. It
>> actually has 8 chip selects. This is fine though.
>
> I might as well fix it since I have to make changes anyway. Don't
> >
> > - all wilink family needs special init command for entering wspi mode.
> > extra clock cycles should be sent after the spi init command while the
> > cs pin is high.
> > - switch to controling the cs pin from the spi driver for achieveing the
> > above.
> > - the selected cs gpio is r
I.MX6Quad Plus has a slightly different version of PCIe core than
reqular i.MX6Quad.
Signed-off-by: Andrey Smirnov
---
Changes since v1:
- Patchset is rebased against
https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/log/?h=pci/host-imx6
- DTS files change
Use enumerated type instead of a boolean flag to specify the variant of
the PCIe IP block (6Q, 6SX, etc). This patch has zero functional impact,
however it makes the code easier to extend for the case of more than 2
possible variants of an IP block (of which there are).
Signed-off-by: Andrey Smirn
Sometimes update_curr() is called w/o tasks actually running, it is
captured by:
u64 delta_exec = rq_clock_task(rq) - curr->se.exec_start;
We should not trigger cpufreq update in this case for rt/deadline
classes, and this patch fix it.
Signed-off-by: Wanpeng Li
---
kernel/sched/deadlin
I.MX6+ has a dedicated bit for reseting PCIe core, which should be used
instead of a regular reset sequence since using the latter will hang the
SoC.
This commit is based on c34068d48273e24d392d9a49a38be807954420ed from
http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git
Signed-off-by: An
On 14/04/16 3:10 PM, "Dan Carpenter" wrote:
>Presumably it isn't possible to have empty lists here, but my static
>checker doesn't know that and complains that "ep" can be used
>uninitialized.
>
>Signed-off-by: Dan Carpenter
>
>diff --git a/drivers/scsi/bnx2i/bnx2i_iscsi.c
>b/drivers/scsi/bnx2
On Sun, Apr 17, 2016 at 10:45 PM, H. Peter Anvin wrote:
> On 04/17/16 22:39, Andy Lutomirski wrote:
>>>
>>> I'm reasonably confident they have, because we have had security bugs
>>> TWICE when someone has tried to "optimize" the code. The masking was
>>> generally done with a movl instruction, wh
Hi Felipe,
What do you think of this version patchset? Could you review this
patchset when you feel free? I really hope to move the usb charger
forwards with suggestions. Thanks.
On 7 April 2016 at 19:48, Baolin Wang wrote:
> Currently the Linux kernel does not provide any standard integration o
On Mon, Apr 18, 2016 at 01:31:09PM +0800, Baolin Wang wrote:
>
> We've tried to do this in dm-crypt, but it failed.
> The dm-crypt maintainer explained to me that I should optimize the
> driver, not add strange hw-dependent crypto modes to dm-crypt, this is
> not the first crypto accelerator that
On 04/17/16 22:39, Andy Lutomirski wrote:
>>
>> I'm reasonably confident they have, because we have had security bugs
>> TWICE when someone has tried to "optimize" the code. The masking was
>> generally done with a movl instruction, which confused people.
>>
>>> So the type of the syscall nr is a
Hi Sebastian,
On 2016년 04월 15일 23:13, Sebastian Reichel wrote:
> Hi,
>
> On Fri, Apr 15, 2016 at 09:43:34AM +0900, Chanwoo Choi wrote:
>> This patch removes the deprecated notifier API of extcon framework and then
>> use
>> the new extcon API[2] with the unique id[1] to indicate the each externa
snipped.
> > +
> > +void mtk_vcodec_dec_set_default_params(struct mtk_vcodec_ctx *ctx)
> > +{
> > + struct mtk_q_data *q_data;
> > +
> > + ctx->m2m_ctx->q_lock = &ctx->dev->dev_mutex;
> > + ctx->fh.m2m_ctx = ctx->m2m_ctx;
> > + ctx->fh.ctrl_handler = &ctx->ctrl_hdl;
> > + INIT_WORK(&ctx
On Sun, Apr 17, 2016 at 10:21 PM, H. Peter Anvin wrote:
> On 04/17/16 22:18, Andy Lutomirski wrote:
>> On Sun, Apr 17, 2016 at 9:50 PM, H. Peter Anvin wrote:
>>> On 04/17/16 17:47, Ben Hutchings wrote:
We've always masked off the top 32 bits when x32 is enabled, but
hopefully no-one rel
Hi all,
Changes since 20160415:
The net-next tree gained conflicts against the net tree.
The tip tree still had its build failure for which I reverted a commit
and gained another for which I applied a build fix.
The gpio tree gained a build failure so I used the version from
next-20160415.
The
Hi Sebastian,
On 2016년 04월 15일 23:20, Sebastian Reichel wrote:
> Hi,
>
> On Fri, Apr 15, 2016 at 09:43:35AM +0900, Chanwoo Choi wrote:
>> This patch removes the deprecated notifier API of extcon framework and then
>> use
>> the new extcon API[2] with the unique id[1] to indicate the each externa
Hi Herbert,
On 15 April 2016 at 21:48, Herbert Xu wrote:
> On Tue, Mar 15, 2016 at 03:47:58PM +0800, Baolin Wang wrote:
>> Now some cipher hardware engines prefer to handle bulk block by merging
>> requests
>> to increase the block size and thus increase the hardware engine processing
>> speed.
Since we're getting current's cgroup namespace info, and are not
modifying it, we can use rcu_read_lock() instead of cgroup_mutex.
Signed-off-by: Serge Hallyn
---
kernel/cgroup.c | 40
1 file changed, 36 insertions(+), 4 deletions(-)
diff --git a/kernel/
On 04/17/16 22:18, Andy Lutomirski wrote:
> On Sun, Apr 17, 2016 at 9:50 PM, H. Peter Anvin wrote:
>> On 04/17/16 17:47, Ben Hutchings wrote:
>>> We've always masked off the top 32 bits when x32 is enabled, but
>>> hopefully no-one relies on that. Now that the slow path is in C, we
>>> check all
On 04/17/16 22:18, Andy Lutomirski wrote:
> On Sun, Apr 17, 2016 at 9:50 PM, H. Peter Anvin wrote:
>> On 04/17/16 17:47, Ben Hutchings wrote:
>>> We've always masked off the top 32 bits when x32 is enabled, but
>>> hopefully no-one relies on that. Now that the slow path is in C, we
>>> check all
On Sun, Apr 17, 2016 at 9:50 PM, H. Peter Anvin wrote:
> On 04/17/16 17:47, Ben Hutchings wrote:
>> We've always masked off the top 32 bits when x32 is enabled, but
>> hopefully no-one relies on that. Now that the slow path is in C, we
>> check all the bits there, regardless of whether x32 is ena
Hi Will,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: c3b46c73264b03000d1e18b22f5caf63332547c9
commit: da48d094ce5d7c7dcdad9011648a81c42fd1c2ef Kconfig: remove
HAVE_LATENCYTOP_SUPPORT
date: 3 months ago
config:
Hi,
On Sun, Apr 17, 2016 at 05:29:23PM +0300, Ivaylo Dimitrov wrote:
> Without that, regulators are left in the mode last set by the bootloader or
> by the kernel the device was rebooted from. This leads to various problems,
> like non-working peripherals.
>
> Signed-off-by: Ivaylo Dimitrov
Rev
On 2016-04-18 00:00, David Miller wrote:
From: Sinan Kaya
Date: Sat, 16 Apr 2016 18:23:32 -0400
Current code is assuming that the address returned by
dma_alloc_coherent
is a logical address. This is not true on ARM/ARM64 systems. This
patch
replaces dma_alloc_coherent with dma_map_page API. T
On Sunday 17 April 2016 01:01 AM, David Lechner wrote:
>> +static int da850_async3_set_parent(struct clk *clk, struct clk *parent)
>> +{
>> +u32 val;
>> +
>> +val = readl(DA8XX_SYSCFG0_VIRT(DA8XX_CFGCHIP3_REG));
>> +
>> +/* Set the USB 1.1 PHY clock mux based on the parent clock. */
>
On Sun, Apr 17, 2016 at 01:07:52PM -0500, Andrew F. Davis wrote:
> On 04/16/2016 02:22 PM, Jonathan Cameron wrote:
> > On 10/04/16 20:07, Alison Schofield wrote:
> >> Driver includes struct regmap and struct device in its global data.
> >> Remove the struct device and use regmap API to retrieve dev
On 04/17/16 17:47, Ben Hutchings wrote:
> We've always masked off the top 32 bits when x32 is enabled, but
> hopefully no-one relies on that. Now that the slow path is in C, we
> check all the bits there, regardless of whether x32 is enabled. Let's
> make the fast path consistent with it.
We hav
Looks good...thanks Dan.
> -Original Message-
> From: Dan Carpenter [mailto:dan.carpen...@oracle.com]
> Sent: Friday, April 15, 2016 8:16 PM
> To: Chakravarty, Souvik K
> Cc: Darren Hart ; platform-driver-
> x...@vger.kernel.org; linux-kernel@vger.kernel.org; kernel-
> janit...@vger.kerne
Hi Jiri,
Today's linux-next merge of the livepatching tree got a conflict in:
arch/powerpc/kernel/process.c
between commit:
7f92bc569455 ("powerpc: sparse: Include headers for __weak symbols")
from the powerpc tree and commit:
5d31a96e6c01 ("powerpc/livepatch: Add livepatch stack to str
Hi,
Since the dawn of time, our background buffered writeback has sucked.
When we do background buffered writeback, it should have little impact
on foreground activity. That's the definition of background activity...
But for as long as I can remember, heavy buffered writers have not
behaved like t
This adds a new request flag, REQ_BG, that callers can use to tell
the block layer that this is background (non-urgent) IO.
Signed-off-by: Jens Axboe
---
include/linux/blk_types.h | 4 +++-
include/linux/fs.h| 4
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/include/
For blk-mq, ->nr_requests does track queue depth, at least at init
time. But for the older queue paths, it's simply a soft setting.
On top of that, it's generally larger than the hardware setting
on purpose, to allow backup of requests for merging.
Fill a hole in struct request with a 'queue_depth
If we end up waiting on a page that is dirty or marked writeback,
then increment the corresponding bdi_writeback counter.
Signed-off-by: Jens Axboe
---
mm/filemap.c | 42 +++---
1 file changed, 39 insertions(+), 3 deletions(-)
diff --git a/mm/filemap.c b/mm/f
For legacy block, we simply track them in the request queue. For
blk-mq, we track them on a per-sw queue basis, which we can then
sum up through the hardware queues and finally to a per device
state.
The stats are tracked in, roughly, 0.1s interval windows.
Add sysfs files to display the stats.
Add wbc_to_write_cmd(), which returns the write type to use, based on a
struct writeback_control. No functional changes in this patch, but it
prepares us for factoring other wbc fields for write type.
Signed-off-by: Jens Axboe
---
fs/block_dev.c| 2 +-
fs/buffer.c | 2 +
If we're doing background type writes, then use the appropriate
write command for that.
Signed-off-by: Jens Axboe
---
include/linux/writeback.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/writeback.h b/include/linux/writeback.h
index aa66fa05ff0d..6e4a35acaa3e 100644
---
Note in the bdi_writeback structure if a task is currently being
limited in balance_dirty_pages(), waiting for writeback to
proceed.
Signed-off-by: Jens Axboe
---
include/linux/backing-dev-defs.h | 2 ++
mm/backing-dev.c | 1 +
mm/page-writeback.c | 2 ++
3 files cha
Test patch that throttles buffered writeback to make it a lot
more smooth, and has way less impact on other system activity.
Background writeback should be, by definition, background
activity. The fact that we flush huge bundles of it at the time
means that it potentially has heavy impacts on foreg
Hi Jiri,
Today's linux-next merge of the livepatching tree got a conflict in:
arch/powerpc/Kconfig
between commit:
7f2bd0063342 ("powerpc/mm: enable page parallel initialisation")
from Linus' tree and commit:
85baa095497f ("powerpc/livepatch: Add live patching support on ppc64le")
from
On Sun, Apr 17, 2016 at 2:09 AM, Arnd Bergmann wrote:
> The newly added runtime PM support for the cadence spi driver
> causes harmless warnings when PM is disabled:
>
> drivers/spi/spi-cadence.c:681:12: warning: 'cnds_runtime_suspend' defined but
> not used
> drivers/spi/spi-cadence.c:652:12: wa
Hi Chen,
It's probably a bug fix that unveils the link errors.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 9d090d01e3efdcdb8f7f07e86fcac91e01ae30cd
commit: f69405ce6c0fc9f4a039011007371b31f80b470d openrisc: include: asm:
Kbuild: add default "vga.h"
On Sun, Apr 17, 2016 at 03:04:32PM -0500, serge.hal...@ubuntu.com wrote:
> From: Serge Hallyn
>
> When showing a cgroupfs entry in mountinfo, show the
> path of the mount root dentry relative to the reader's
> cgroup namespace root.
>
> Signed-off-by: Serge Hallyn
> ---
> fs/kernfs/mount.c
Hi Linus,
After merging the gpio tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/gpio/gpio-f7188x.c: In function 'f7188x_gpio_set_single_ended':
drivers/gpio/gpio-f7188x.c:331:26: error: implicit declaration of function
'gpio_data_mode' [-Werror=implicit-function-d
From: Arnd Bergmann
Date: Sat, 16 Apr 2016 22:35:08 +0200
> The newly added x550em_a support causes a link failure on ARM because of
> an overly long time passed into udelay():
>
> ERROR: "__bad_udelay" [drivers/net/ethernet/intel/ixgbe/ixgbe.ko] undefined!
>
> There are multiple variants of th
From: Arnd Bergmann
Date: Sat, 16 Apr 2016 22:29:33 +0200
> Two new functions in bpf contain a cast from a 'u64' to a
> pointer. This works on 64-bit architectures but causes a warning
> on all 32-bit architectures:
>
> kernel/trace/bpf_trace.c: In function 'bpf_perf_event_output_tp':
> kernel/t
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 9d090d01e3efdcdb8f7f07e86fcac91e01ae30cd
commit: 3194c6870158e305dac2af52f83681e9cb67280f NFC: nfcmrvl: add firmware
download support
date: 6 months ago
config: ia64-allmodconfig (attached as .config)
repr
From: Sinan Kaya
Date: Sat, 16 Apr 2016 18:23:32 -0400
> Current code is assuming that the address returned by dma_alloc_coherent
> is a logical address. This is not true on ARM/ARM64 systems. This patch
> replaces dma_alloc_coherent with dma_map_page API. The address returned
> can later by virt
Hi Hans,
On Fri, 2016-04-15 at 16:27 +0200, Hans Verkuil wrote:
> On 04/13/2016 02:01 PM, Tiffany Lin wrote:
> > Add v4l2 layer decoder driver for MT8173
> >
> > Signed-off-by: Tiffany Lin
> > ---
> > drivers/media/platform/mtk-vcodec/Makefile | 10 +-
> > drivers/media/platform/mtk-v
Any comments are welcome.
Thanks,
Zhonghui
On 4/13/2016 2:42 PM, Fu, Zhonghui wrote:
> Leave some work of SDIO card's resume process into it's runtime resume
> process to shorten system resume latency.
>
> Signed-off-by: Zhonghui Fu
> ---
> drivers/mmc/core/sdio.c | 21 ++--
On Mon, Apr 18, 2016 at 02:32:54AM +0100, Maciej W. Rozycki wrote:
> I'd be tempted to run with the patch below to see what's the value of
> `la_ptr' early on in processing (`entInt' code in entry.S looks sane to
> me, doesn't touch a2). NB a rebuild doesn't have to be costly if you only
> pok
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Diego Viola
[ Upstream commit ee50c130c82175eaa0820c96b6d3763928af2241 ]
The JMC260 network card fails to suspend/resume because the call to
jme_start_irq() was too early, moving the call to j
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit f971f2263deaa4a441e377b385c11aee0f3b3f9a upstream.
bug:
https://bugs.freedesktop.org/show_bug.cgi?id=94692
Signed-off-by: Alex Deucher
Signed-off-by: Greg Kroah-Hartman
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Helge Deller
commit e3893027a300927049efc1572f852201eb785142 upstream.
We want to avoid the kernel module loader to create function pointers
for the kernel fixup routines of get_user() and put
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 4a07083ed613644c96c34a7dd2853dc5d7c70902 upstream.
ALSA system timer backend stops the timer via del_timer() without sync
and leaves del_timer_sync() at the close instead.
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
[ Upstream commit 5d150a985520bbe3cb2aa1ceef24a7e32f20c15f ]
When ipv6_find_hdr is used to find a fragment header
(caller specifies target NEXTHDR_FRAGMENT) we erronously retu
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Thadeu Lima de Souza Cascardo
[ Upstream commit b6ee376cb0b7fb4e7e07d6cd248bd40436fb9ba6 ]
When creating an ip6tnl tunnel with ip tunnel, rtnl_link_ops is not set
before ip6_tnl_create2 is cal
1 - 100 of 619 matches
Mail list logo
