From: "karam.lee"
Recently rw_page block device operation has been added.
This patchset implements rw_page operation for zram block device
and does some clean-up.
Patches 1~2 are for clean-up.
Patch 3 is for implementation of rw_page operation.
With the rw_page operation, zram can do I/O
From: "karam.lee"
This patch changes parameter of valid_io_request for common usage.
The purpose of valid_io_request() is to determine if bio request is
valid or not.
This patch use I/O start address and size instead of a BIO parameter
for common usage.
Signed-off-by: karam.lee
---
PM freezer relies on having all tasks frozen by the time devices are
getting frozen so that no task will touch them while they are getting
frozen. But OOM killer is allowed to kill an already frozen task in
order to handle OOM situtation. In order to protect from late wake ups
OOM killer is
From: "karam.lee"
This patch implements rw_page operation for zram block device.
I implemented the feature in zram and tested it.
Test bed was the G2, LG electronic mobile device, whtich has msm8974
processor and 2GB memory.
With a memory allocation test program consuming memory, the system
as per 0c740d0afc3b (introduce for_each_thread() to replace the buggy
while_each_thread()) get rid of do_each_thread { } while_each_thread()
construct and replace it by a more error prone for_each_thread.
This patch doesn't introduce any user visible change.
Suggested-by: Oleg Nesterov
From: "karam.lee"
This patch removes an unnecessary parameter(bio)
from zram_bvec_rw() and zram_bvec_read().
zram_bvec_read() doesn't use a bio parameter, so remove it.
zram_bvec_rw() calls a read/write operation not using bio, so a rw parameter
replaces a bio parameter.
Signed-off-by:
Hi Andrew, Rafael,
this has been originally discussed here [1] and previously posted here [2].
I have updated patches according to feedback from Oleg.
The first and third patch are regression fixes and they are a stable
material IMO. The second and fourth patch are simple cleanups.
The 1st
On Tue, 21 Oct 2014 06:33:47 + Ronny Egner
wrote:
> Dear All,
>
> i was wondering what happened with the patch posted by Andrea Mazzoleni
> back in Februrary 2014 (this Thread:
> http://thread.gmane.org/gmane.linux.kernel/1654735).
>
> Why wash´t it added to the code? Something
On 20.10.2014 23:05, Javier Martinez Canillas wrote:
> Hello,
>
> This series add support for Exynos platforms to prepare regulators for
> system suspend. The regulator core has a set of helpers functions to be
> used when the system is entering and leaving from a suspend state but
> currently
From: Danielle Costantino
This patch enforces correct I2C error returned codes from Freescale's
MPC i2c bus driver, allowing for proper user-space/kernel error
handling.
Signed-off-by: Danielle Costantino
---
diff --git a/drivers/i2c/busses/i2c-mpc.c b/drivers/i2c/busses/i2c-mpc.c
index
On Mon, Oct 20, 2014 at 08:53:55PM +0100, Thomas Graf wrote:
> Heiko,
>
> Can you test the following patch:
>
> The synchronize_rcu() in netlink_release() introduces unacceptable
> latency. Reintroduce minimal lookup so we can drop the
> synchronize_rcu() until socket destruction has been
> > I am seeing this BUG on 3 different sparc64 machines with yesterdays
> > git. sparc64-specific known problems were just fixed before,
> > 3.17.0-07551-g052db7e + slab alignment fix patch + sparc64 SIGBUS fix
> > patch is working stable for me, whereas 3.17.0-09670-g0429fbc + SIGBUS
> >
On 10/20/14 13:09, Andreas Werner wrote:
> On Mon, Oct 20, 2014 at 05:11:41PM +0800, Greg KH wrote:
>> On Mon, Oct 20, 2014 at 10:33:45AM +0200, Andreas Werner wrote:
>>> On Thu, Oct 16, 2014 at 01:44:02PM +0200, Andreas Werner wrote:
On Thu, Oct 16, 2014 at 11:59:10AM +0200, Wolfram Sang
On Tue 21-10-14 10:31:19, Vladimir Davydov wrote:
> On Mon, Oct 20, 2014 at 08:53:06PM +0200, Michal Hocko wrote:
> > On Mon 20-10-14 19:11:29, Vladimir Davydov wrote:
> > > The activate_kmem_mutex is used to serialize memcg.kmem.limit updates,
> > > but we already serialize them with
Hello
[...]
- Use raw notifiers protected by spinlocks instead of atomic notifiers
[...]
+/**
+ * do_kernel_power_off - Execute kernel poweroff handler call chain
+ *
+ * Calls functions registered with register_power_off_handler.
+ *
+ * Expected to be called from
Hi!
I detected a problem with an Intel (imsm, ICH) RAID1 reported as "clean" by
Linux, while the BIOS and Windows claimed the RAID is in state "rebuild". This
was for an older kernel, and the bug had been reported to openSUSE bugzilla as
bug #902000. Anyone interested can find the details
On Mon, Oct 20, 2014 at 8:31 PM, Kevin Hilman wrote:
> Sudhir Sreedharan writes:
>
>> In ST16650V2 based serial uarts, while initalizing the PM state,
>> LCR registers are being initialized to 0 in serial8250_set_sleep().
>> If console port is already initialized and being used, this will
>>
Hello Wim,
On Mon, Oct 20, 2014 at 09:53:20PM +0200, Wim Van Sebroeck wrote:
> commit 4846e3784585173f48e267b76f968bcb4a12d3b2
> Author: Uwe Kleine-König
> Date: Tue Sep 9 22:18:31 2014 +0200
>
> watchdog: simplify definitions of WATCHDOG_NOWAYOUT(_INIT_STATUS)?
>
>
Dear All,
i was wondering what happened with the patch posted by Andrea Mazzoleni
back in Februrary 2014 (this Thread:
http://thread.gmane.org/gmane.linux.kernel/1654735).
Why wash´t it added to the code? Something missing/wrong?
In my opinion the posted patch is awesome and would enable a
On Oct 21, 2014, at 7:56 AM, Ankit Jindal wrote:
> Currently, three types of mem regions are supported: UIO_MEM_PHYS,
> UIO_MEM_LOGICAL and UIO_MEM_VIRTUAL. Among these UIO_MEM_PHYS helps
> UIO driver export physcial memory to user space as non-cacheable
> user memory. Typcially memory-mapped
On Mon, Oct 20, 2014 at 08:53:06PM +0200, Michal Hocko wrote:
> On Mon 20-10-14 19:11:29, Vladimir Davydov wrote:
> > The activate_kmem_mutex is used to serialize memcg.kmem.limit updates,
> > but we already serialize them with memcg_limit_mutex so let's remove the
> > former.
> >
> >
On 21 October 2014 11:47, Varka Bhadram wrote:
> On 10/21/2014 11:46 AM, Ankit Jindal wrote:
>>
>> On 21 October 2014 11:34, Varka Bhadram wrote:
>>>
>>> On 10/21/2014 11:26 AM, Ankit Jindal wrote:
The Applied Micro X-Gene SOC has on-chip QMTM (Queue manager
and Traffic manager)
On 10/21/2014 11:46 AM, Ankit Jindal wrote:
On 21 October 2014 11:34, Varka Bhadram wrote:
On 10/21/2014 11:26 AM, Ankit Jindal wrote:
The Applied Micro X-Gene SOC has on-chip QMTM (Queue manager
and Traffic manager) which is hardware based Queue or Ring
manager. This QMTM device can be used
On 21 October 2014 11:34, Varka Bhadram wrote:
> On 10/21/2014 11:26 AM, Ankit Jindal wrote:
>>
>> The Applied Micro X-Gene SOC has on-chip QMTM (Queue manager
>> and Traffic manager) which is hardware based Queue or Ring
>> manager. This QMTM device can be used in conjunction with
>> other
On Mon, 20 Oct 2014 20:14:53 +0200
Paolo Bonzini wrote:
> On 10/18/2014 06:28 PM, Dave Hansen wrote:
> > > Currently it is an all or nothing thing, but for a future change we might
> > > want to just
> > > tag the guest memory instead of the complete user address space.
> >
> > I think it's a
On 10/21/2014 11:26 AM, Ankit Jindal wrote:
The Applied Micro X-Gene SOC has on-chip QMTM (Queue manager
and Traffic manager) which is hardware based Queue or Ring
manager. This QMTM device can be used in conjunction with
other devices such as DMA Engine, Ethernet, Security Engine,
etc to assign
On Mon, Oct 20, 2014 at 10:44:18PM -0700, Andy Lutomirski wrote:
> You're exactly correct, or at least you seem to understand it the way I do :)
Ok, cool.
Now, if I had more time, I'd take a guest and add some debugging
code to see when exactly that happens and how prev->context.ldt and
Hi , could someone help to review my patch ?
在 10/07/2014 09:43 AM, Jianqun 写道:
> The driver is used for rockchip board using a max98090.
> Test on RK3288 board with max98090.
>
> Signed-off-by: Jianqun Xu
> ---
> sound/soc/rockchip/Kconfig | 9 +
> sound/soc/rockchip/Makefile
Hi , could someone help to review my patch ?
在 10/07/2014 09:43 AM, Jianqun 写道:
The driver is used for rockchip board using a max98090.
Test on RK3288 board with max98090.
Signed-off-by: Jianqun Xu jay...@rock-chips.com
---
sound/soc/rockchip/Kconfig | 9 +
On Mon, Oct 20, 2014 at 10:44:18PM -0700, Andy Lutomirski wrote:
You're exactly correct, or at least you seem to understand it the way I do :)
Ok, cool.
Now, if I had more time, I'd take a guest and add some debugging
code to see when exactly that happens and how prev-context.ldt and
On 10/21/2014 11:26 AM, Ankit Jindal wrote:
The Applied Micro X-Gene SOC has on-chip QMTM (Queue manager
and Traffic manager) which is hardware based Queue or Ring
manager. This QMTM device can be used in conjunction with
other devices such as DMA Engine, Ethernet, Security Engine,
etc to assign
On Mon, 20 Oct 2014 20:14:53 +0200
Paolo Bonzini pbonz...@redhat.com wrote:
On 10/18/2014 06:28 PM, Dave Hansen wrote:
Currently it is an all or nothing thing, but for a future change we might
want to just
tag the guest memory instead of the complete user address space.
I think
On 21 October 2014 11:34, Varka Bhadram varkabhad...@gmail.com wrote:
On 10/21/2014 11:26 AM, Ankit Jindal wrote:
The Applied Micro X-Gene SOC has on-chip QMTM (Queue manager
and Traffic manager) which is hardware based Queue or Ring
manager. This QMTM device can be used in conjunction with
On 10/21/2014 11:46 AM, Ankit Jindal wrote:
On 21 October 2014 11:34, Varka Bhadram varkabhad...@gmail.com wrote:
On 10/21/2014 11:26 AM, Ankit Jindal wrote:
The Applied Micro X-Gene SOC has on-chip QMTM (Queue manager
and Traffic manager) which is hardware based Queue or Ring
manager. This
On 21 October 2014 11:47, Varka Bhadram varkabhad...@gmail.com wrote:
On 10/21/2014 11:46 AM, Ankit Jindal wrote:
On 21 October 2014 11:34, Varka Bhadram varkabhad...@gmail.com wrote:
On 10/21/2014 11:26 AM, Ankit Jindal wrote:
The Applied Micro X-Gene SOC has on-chip QMTM (Queue manager
On Mon, Oct 20, 2014 at 08:53:06PM +0200, Michal Hocko wrote:
On Mon 20-10-14 19:11:29, Vladimir Davydov wrote:
The activate_kmem_mutex is used to serialize memcg.kmem.limit updates,
but we already serialize them with memcg_limit_mutex so let's remove the
former.
Signed-off-by:
On Oct 21, 2014, at 7:56 AM, Ankit Jindal ankit.jin...@linaro.org wrote:
Currently, three types of mem regions are supported: UIO_MEM_PHYS,
UIO_MEM_LOGICAL and UIO_MEM_VIRTUAL. Among these UIO_MEM_PHYS helps
UIO driver export physcial memory to user space as non-cacheable
user memory.
Dear All,
i was wondering what happened with the patch posted by Andrea Mazzoleni
back in Februrary 2014 (this Thread:
http://thread.gmane.org/gmane.linux.kernel/1654735).
Why wash´t it added to the code? Something missing/wrong?
In my opinion the posted patch is awesome and would enable a
Hello Wim,
On Mon, Oct 20, 2014 at 09:53:20PM +0200, Wim Van Sebroeck wrote:
commit 4846e3784585173f48e267b76f968bcb4a12d3b2
Author: Uwe Kleine-König u.kleine-koe...@pengutronix.de
Date: Tue Sep 9 22:18:31 2014 +0200
watchdog: simplify definitions of WATCHDOG_NOWAYOUT(_INIT_STATUS)?
On Mon, Oct 20, 2014 at 8:31 PM, Kevin Hilman khil...@kernel.org wrote:
Sudhir Sreedharan ssreedha...@mvista.com writes:
In ST16650V2 based serial uarts, while initalizing the PM state,
LCR registers are being initialized to 0 in serial8250_set_sleep().
If console port is already initialized
Hi!
I detected a problem with an Intel (imsm, ICH) RAID1 reported as clean by
Linux, while the BIOS and Windows claimed the RAID is in state rebuild. This
was for an older kernel, and the bug had been reported to openSUSE bugzilla as
bug #902000. Anyone interested can find the details there. I
Hello
[...]
- Use raw notifiers protected by spinlocks instead of atomic notifiers
[...]
+/**
+ * do_kernel_power_off - Execute kernel poweroff handler call chain
+ *
+ * Calls functions registered with register_power_off_handler.
+ *
+ * Expected to be called from
On Tue 21-10-14 10:31:19, Vladimir Davydov wrote:
On Mon, Oct 20, 2014 at 08:53:06PM +0200, Michal Hocko wrote:
On Mon 20-10-14 19:11:29, Vladimir Davydov wrote:
The activate_kmem_mutex is used to serialize memcg.kmem.limit updates,
but we already serialize them with memcg_limit_mutex so
On 10/20/14 13:09, Andreas Werner wrote:
On Mon, Oct 20, 2014 at 05:11:41PM +0800, Greg KH wrote:
On Mon, Oct 20, 2014 at 10:33:45AM +0200, Andreas Werner wrote:
On Thu, Oct 16, 2014 at 01:44:02PM +0200, Andreas Werner wrote:
On Thu, Oct 16, 2014 at 11:59:10AM +0200, Wolfram Sang wrote:
* PGP
I am seeing this BUG on 3 different sparc64 machines with yesterdays
git. sparc64-specific known problems were just fixed before,
3.17.0-07551-g052db7e + slab alignment fix patch + sparc64 SIGBUS fix
patch is working stable for me, whereas 3.17.0-09670-g0429fbc + SIGBUS
patch fails
On Mon, Oct 20, 2014 at 08:53:55PM +0100, Thomas Graf wrote:
Heiko,
Can you test the following patch:
The synchronize_rcu() in netlink_release() introduces unacceptable
latency. Reintroduce minimal lookup so we can drop the
synchronize_rcu() until socket destruction has been RCUfied.
From: Danielle Costantino danielle.costant...@gmail.com
This patch enforces correct I2C error returned codes from Freescale's
MPC i2c bus driver, allowing for proper user-space/kernel error
handling.
Signed-off-by: Danielle Costantino danielle.costant...@gmail.com
---
diff --git
On 20.10.2014 23:05, Javier Martinez Canillas wrote:
Hello,
This series add support for Exynos platforms to prepare regulators for
system suspend. The regulator core has a set of helpers functions to be
used when the system is entering and leaving from a suspend state but
currently there is
On Tue, 21 Oct 2014 06:33:47 + Ronny Egner
ronnyeg...@ronnyegner-consulting.de wrote:
Dear All,
i was wondering what happened with the patch posted by Andrea Mazzoleni
back in Februrary 2014 (this Thread:
http://thread.gmane.org/gmane.linux.kernel/1654735).
Why wash´t it added to the
Hi Andrew, Rafael,
this has been originally discussed here [1] and previously posted here [2].
I have updated patches according to feedback from Oleg.
The first and third patch are regression fixes and they are a stable
material IMO. The second and fourth patch are simple cleanups.
The 1st
as per 0c740d0afc3b (introduce for_each_thread() to replace the buggy
while_each_thread()) get rid of do_each_thread { } while_each_thread()
construct and replace it by a more error prone for_each_thread.
This patch doesn't introduce any user visible change.
Suggested-by: Oleg Nesterov
From: karam.lee karam@lge.com
This patch removes an unnecessary parameter(bio)
from zram_bvec_rw() and zram_bvec_read().
zram_bvec_read() doesn't use a bio parameter, so remove it.
zram_bvec_rw() calls a read/write operation not using bio, so a rw parameter
replaces a bio parameter.
From: karam.lee karam@lge.com
Recently rw_page block device operation has been added.
This patchset implements rw_page operation for zram block device
and does some clean-up.
Patches 1~2 are for clean-up.
Patch 3 is for implementation of rw_page operation.
With the rw_page operation, zram
From: karam.lee karam@lge.com
This patch changes parameter of valid_io_request for common usage.
The purpose of valid_io_request() is to determine if bio request is
valid or not.
This patch use I/O start address and size instead of a BIO parameter
for common usage.
Signed-off-by: karam.lee
PM freezer relies on having all tasks frozen by the time devices are
getting frozen so that no task will touch them while they are getting
frozen. But OOM killer is allowed to kill an already frozen task in
order to handle OOM situtation. In order to protect from late wake ups
OOM killer is
From: karam.lee karam@lge.com
This patch implements rw_page operation for zram block device.
I implemented the feature in zram and tested it.
Test bed was the G2, LG electronic mobile device, whtich has msm8974
processor and 2GB memory.
With a memory allocation test program consuming memory,
From: Cong Wang xiyou.wangc...@gmail.com
Since f660daac474c6f (oom: thaw threads if oom killed thread is frozen
before deferring) OOM killer relies on being able to thaw a frozen task
to handle OOM situation but a3201227f803 (freezer: make freezing() test
freeze conditions in effect instead of
Hi,
These are two patches with the same commit log, in the same file. You
can probably squash them.
On 20/10/2014 at 21:48:47 -0500, Brian Vandre wrote :
This patch-set fixes 2 checkpatch.pl warnings
dealing with lines over 80 characters.
Brian Vandre (2):
Staging: iio: adc: fix line
From: Cong Wang xiyou.wangc...@gmail.com
__thaw_task() no longer clears frozen flag since commit a3201227f803
(freezer: make freezing() test freeze conditions in effect instead of
TIF_FREEZE).
Cc: David Rientjes rient...@google.com
Cc: Rafael J. Wysocki r...@rjwysocki.net
Cc: Tejun Heo
On 9 October 2014 16:58, Peter Zijlstra pet...@infradead.org wrote:
On Tue, Oct 07, 2014 at 02:13:36PM +0200, Vincent Guittot wrote:
@@ -6214,17 +6178,21 @@ static inline void update_sd_lb_stats(struct lb_env
*env, struct sd_lb_stats *sd
/*
* In case the child
On Monday 20 October 2014 15:23:38 Jassi Brar wrote:
On 8 October 2014 11:09, Jassi Brar jaswinder.si...@linaro.org wrote:
Hi Linus,
A framework for Mailbox controllers and clients have been cooking for
more than a year now. Everybody in the CC list had been copied on
patchset revisions
On Mon, Oct 20, 2014 at 03:24:22PM -0700, j...@joshtriplett.org wrote:
On Mon, Oct 20, 2014 at 11:48:37PM +0200, Pieter Smith wrote:
Many embedded systems will not need this syscall, and omitting it
saves space. Add a new EXPERT config option CONFIG_SENDFILE_SYSCALL
(default y) to support
On Tuesday 21 October 2014 14:14:02 Alexandre Courbot wrote:
We have enforced naming things for the dmaengine binding, which has
just led to everyone calling things rx and tx. My fear is that
if we start to enforce giving a name, we'd end up with lots of
drivers that use a gpio-gpios
On Mon, 2014-10-20 at 19:57 +0300, Tanya Brokhman wrote:
If there is more then one UBI device mounted, there is no way to
distinguish between messages from different UBI devices.
Add device number to all ubi layer message types.
The R/O block driver messages were replaced by pr_* since
Hi!
(and thank you for the pointer to the example with the ssc-dai in master mode)
Hi Peter,
On 10/20/2014 09:45 PM, Peter Rosin wrote:
From 1e5621d7b9887c648d1a66238dc82d715c1e2cad Mon Sep 17 00:00:00
2001
From: Peter Rosin p...@axentia.se
Date: Mon, 20 Oct 2014 14:38:04 +0200
Hello,
I stumbled across a reproducible RCU stall related to the AF_UNIX code
(on 3.17, on an ARM SMP system), and I'm not sure whether the problem
is caused by:
* The af_unix.c code using spin_lock() on sk-sk_receive_queue.lock
while it should be using spin_lock_irqsave().
OR
* The mvpp2
Add structure type domain_values_entry used for kdump;
Add context functions needed for kdump.
Bill Sumner:
Original version;
Li, Zhenhua:
Changed the name of new functions, make them consistent with current
context get/set functions.
Signed-off-by: Bill Sumner
Signed-off-by: Li,
When a none 0xff character is found in the flash buffer, an error message is
printed. This error message claims to provide the offset of the FIRST corrupted
byte but due to a missing break in the for loop, the former code always prints
the offset of the byte immediately after the end of the tested
The following series implements a fix for:
A kdump problem about DMA that has been discussed for a long time.
That is, when a kernel panics and boots into the kdump kernel, DMA that was
started by the panicked kernel is not stopped before the kdump kernel is booted;
and the kdump kernel disables
On 10/20/2014 11:35 PM, Sasha Levin wrote:
On 10/20/2014 06:54 AM, Andrey Ryabinin wrote:
UBSan uses compile-time instrumentation to catch undefined behavior (UB).
Compiler inserts code that perform certain kinds of
checks before operations that could cause UB.
If check fails (i.e. UB
Allow specification of the domain-id for the new domain.
This patch only adds the 'did' parameter to iommu_attach_domain()
and modifies all of its callers to specify the default value of -1
which says no did specified, allocate a new one.
This is no functional change from current behaviour --
Interfaces for when a new domain in the crashdump kernel needs some
values from the panicked kernel's context entries.
Signed-off-by: Bill Sumner
---
drivers/iommu/intel-iommu.c | 46 +
1 file changed, 46 insertions(+)
diff --git
On 20 October 2014 11:04, Krzysztof Kozlowski k.kozlow...@samsung.com wrote:
Add amba_pclk_prepare() and amba_pclk_unprepare() inline functions for
handling the AMBA bus clock by device drivers.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
Reviewed-by: Ulf Hansson
This patch fixes __jffs2_dbg_dump_buffer(): this function prints a message
claiming to dump len bytes. However, depending on the start offset, the former
code drops up to 31 (JFFS2_BUFDUMP_BYTES_PER_LINE - 1) bytes.
Signed-off-by: Cyrille Pitchen cyrille.pitc...@atmel.com
---
fs/jffs2/debug.c |
Hi,
This series of patches fixes some bugs in the output of jffs2 debug functions.
Cyrille Pitchen (2):
jffs2: fix wrong offset in an error msg from
__jff2_dbg_prewrite_paranoia_check
jffs2: fix buffer dump debug output
fs/jffs2/debug.c | 26 ++
1 file changed,
Modify the operation of the following functions when called during crash dump:
device_to_domain_id
get_domain_for_dev
init_dmars
intel_iommu_init
Signed-off-by: Bill Sumner
---
drivers/iommu/intel-iommu.c | 134 +++-
1 file changed, 121 insertions(+),
On Mon, Oct 20, 2014 at 04:41:45PM -0700, Linus Torvalds wrote:
On Mon, Oct 20, 2014 at 2:56 PM, Peter Zijlstra pet...@infradead.org wrote:
Manage the VMAs with SRCU such that we can do a lockless VMA lookup.
Can you explain why srcu, and not plain regular rcu?
Especially as you then
Populate it with support functions to copy iommu translation tables from
from the panicked kernel into the kdump kernel in the event of a crash.
Bill Sumner:
Original version, the creation of the data types and functions.
Li, Zhenhua:
Minor change: update the usage of context_get_* and
On Mon 20-10-14 19:55:54, Vladimir Davydov wrote:
If we fail to reclaim anything from a cgroup during a soft reclaim pass
we want to get the next largest cgroup exceeding its soft limit. To
achieve this, we should obviously remove the current group from the tree
and then pick the largest
LINK perf
libperf.a(skip-callchain-idx.o): In function `arch_skip_callchain_idx':
/root/gen/trunk/knl/tools/perf/arch/powerpc/util/skip-callchain-idx.c:250:
undefined reference to `pr_debug'
libperf.a(skip-callchain-idx.o): In function `check_return_addr':
On Mon, Oct 20, 2014 at 05:07:02PM -0700, Andy Lutomirski wrote:
On 10/20/2014 02:56 PM, Peter Zijlstra wrote:
Hi,
I figured I'd give my 2010 speculative fault series another spin:
https://lkml.org/lkml/2010/1/4/257
Since then I think many of the outstanding issues have changed
On 10/21/2014 08:11 AM, Martin Schwidefsky wrote:
I agree with Dave (I thought I disagreed, but I changed my mind while
writing down my thoughts). Just define mm_forbids_zeropage in
arch/s390/include/asm, and make it return mm-context.use_skey---with a
comment explaining how this is only for
On Tue, Oct 21, 2014 at 03:18:58AM +, Thomas Shao wrote:
In some situation, the user is not able to enable guest VM to sync with
external
time source, like NTP. But the host is still synced with a trusted time
source.
But the guest *is* networked, right?
(Otherwise syncing the
On Mon, 20 Oct 2014, Guenter Roeck wrote:
Devicetree bindings are supposed to be operating system independent
and should thus not describe how a specific functionality is implemented
in Linux.
Cc: Rob Herring robh...@kernel.org
Cc: Pawel Moll pawel.m...@arm.com
Cc: Mark Rutland
On Tue, 2014-10-21 at 10:05 +0200, Cyrille Pitchen wrote:
This patch fixes __jffs2_dbg_dump_buffer(): this function prints a message
claiming to dump len bytes. However, depending on the start offset, the former
code drops up to 31 (JFFS2_BUFDUMP_BYTES_PER_LINE - 1) bytes.
Signed-off-by:
On Tue, 21 Oct 2014, Thomas Shao wrote:
I still do not have a consistent argument from you WHY you need to abuse
do_adjtimex() to do that host - guest synchronization in the first place.
I need a function to gradually slew guest time. do_adjtimex() provides all
the
functionality.
On Mon, Oct 20, 2014 at 04:41:45PM -0700, Linus Torvalds wrote:
On Mon, Oct 20, 2014 at 2:56 PM, Peter Zijlstra pet...@infradead.org wrote:
Manage the VMAs with SRCU such that we can do a lockless VMA lookup.
Can you explain why srcu, and not plain regular rcu?
Especially as you then
On Mon, Oct 20, 2014 at 11:02:13PM -0500, Jeff Epler wrote:
It's interesting to imagine that a virtualization host could present a
time service to the guest *userspace*, even when the guest is not
otherwise exposed to the internet at large. This could take the form of
an NTP server on a
* Traversal of the ACPI device tree was not done right. It should lookup
PPI only under the ACPI device that it is associated. Otherwise, it could
match to a wrong PPI interface if there are two TPM devices in the device
tree.
* Removed global ACPI handle and version string from tpm_ppi.c as
On Tue, 21 Oct 2014, Thomas Shao wrote:
I didn't find a way to detect whether NTPd is running in the hyper-v module.
And you better do not try at all.
In http://doc.ntp.org/4.1.0/ntpd.htm, it mentioned: Normally, the
time is slewed if the offset is less than the step threshold, which
is
Hi ZhenHua,
(2014/10/20 11:19), Li, ZhenHua wrote:
Hi Takao Indoh,
According to this discussion
https://lkml.org/lkml/2014/10/17/107
It seems that we can not do the resetting on the first kernel. It can
only be called during kdump kernel boots.
Sounds like that. Do you know any
On Tue, 21 Oct 2014, Thomas Shao wrote:
I'm also thinking if NTPd could expose some interface to allow other
application to directly provide time source for it to consume. In my
opinion, emulating the ntp source should be very hard and error
prone.
Well, if done right it would be pretty
Hi,
This patchset makes use of Javier Martinez Cainllas changes [1].
It allows disabling some of the regulators during suspend to RAM.
Javier's patchset is necessary only to test it.
[1] [PATCH v3 0/2] ARM: EXYNOS: Call regulator suspend prepare/finish
https://lkml.org/lkml/2014/10/20/545
Some LDOs of Maxim 77686 PMIC support disabling during system suspend
(LDO{2,6,7,8,10,11,12,14,15,16}). This was already implemented as part
of set_suspend_mode function. In that case the mode was one of:
- disable,
- normal mode,
- low power mode.
However there are no bindings for setting the
Add suspend to RAM configuration for max77686 regulators. Some LDOs and
bucks are disabled. This reduces energy consumption during S2R,
approximately from 17 mA to 9 mA.
Additionally remove old and not supported bindings:
- regulator-mem-off
- regulator-mem-idle
- regulator-mem-on
The max77686
On Tue, 2014-10-21 at 10:14 +0200, Hans de Goede wrote:
Hi,
Checkpatch gives the following warning:
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#31:
new file mode 100644
total: 0 errors, 1 warnings, 352 lines checked
v3:
Changed patch 1/2 to incorporate feedback from Steven Rostedt and
Masami Hiramatsu: rename helper function check_ftrace_location()
to arch_check_ftrace_location() and convert it to a weak function,
so architectures can override it without the need for new config
option.
v2:
Changed patch 1/2
If the function tracer is enabled, allow to set kprobes on the first
instruction of a function (which is the function trace caller):
If no kprobe is set handling of enabling and disabling function tracing
of a function simply patches the first instruction. Either it is a nop
(right now it's an
On Tue, Sep 30, 2014 at 8:09 AM, Pramod Gurav
pramod.gu...@smartplayin.com wrote:
This change fixes below sparse error,
drivers/pinctrl/pinctrl-st.c:1515:31: error: incompatible types for operation
()
drivers/pinctrl/pinctrl-st.c:1515:31:left side has type void [noderef]
Christoph Hellwig h...@infradead.org writes:
On Sat, Oct 18, 2014 at 07:21:26PM +0400, Dmitry Monakhov wrote:
sys_fadvise result in direct f_mode modification, which may be not
suitable for some unusual filesytems where file mode invariant is more
complex. In order to support such
801 - 900 of 1656 matches
Mail list logo
