On Fri, 30 Sep 2016, Waiman Long wrote:
> + WRITE_ONCE(state->owner, current);
> + preempt_disable();
> + for (;;) {
> + ret = futex_trylock(uaddr, vpid, &uval, true);
Did you actually read what I said? You CANNOT access userspace in a preempt
disabled region without disabl
Please click outlookteam.ulcraft.com to update your outlook account to
the new secured version.
Thank You
On Wed, Sep 28, 2016 at 10:12:42PM -0400, Sinan Kaya wrote:
> Getting ready for the MSI interrupts. The pending_tre_count is used
> in the interrupt handler to make sure all outstanding requests are
> serviced.
>
> Making it atomic so that it can be updated from multiple contexts.
How is it multi
On Wed, Sep 28, 2016 at 10:12:41PM -0400, Sinan Kaya wrote:
> Configure the DMA bindings for the device tree based firmware.
>
> Signed-off-by: Sinan Kaya
> ---
> drivers/dma/qcom/hidma_mgmt.c | 5 -
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/dma/qcom/hidma_mg
On Sat, Sep 24, 2016 at 12:37:05PM +0800, Baoyou Xie wrote:
> We get 2 warnings when building kernel with W=1:
> drivers/dma/virt-dma.c:22:14: warning: no previous prototype for
> 'vchan_tx_submit' [-Wmissing-prototypes]
> drivers/dma/virt-dma.c:52:5: warning: no previous prototype for
> 'vchan_t
On Fri, Sep 16, 2016 at 01:53:15PM +0300, Peter Ujfalusi wrote:
> From: Misael Lopez Cruz
>
> Enable the burst and data pack modes for the scatter-gather
> in order to improve the throughput of the data transfers.
>
> The improvement has been verified with MMC HS200 mode in
> the DRA72 EVM using
Hi Joonwoo,
On Wed, Sep 28, 2016 at 07:25:26PM -0700, Joonwoo Park wrote:
> Perf sched latency is handy to find out the maximum sched latency and
> the time stamp of the event. After running sched latency, if a found
> latency looks suspicious it's quite reasonable to run perf script
> subsequent
Hi SeongSoo,
On Fri, Sep 30, 2016 at 8:44 AM, SeongSoo Cho wrote:
> As you know, there are the common colored printing of percents so overhead(%)
> can be colored with the rule.
> But Delta means difference percents from percents of overhead between two
> files e.g. perf.data and perf.data.old.
To avoid canceling the delayed workqueue needlessly, and scheduling an
immediate polling. Check if the new poll_interval value is different
than the previous setting.
Cc: Tony Lindgren
Cc: Sebastian Reichel
Signed-off-by: Matt Ranostay
---
drivers/power/supply/bq27xxx_battery.c | 3 ++-
1 file
Add some more description on the limitations for smaps/maps readings, as well
as some guaruntees we can make.
Changelog:
v2:
Adopt Dave Hansen's revision from v1 as the description.
Signed-off-by: Robert Ho
---
Documentation/filesystems/proc.txt | 12
1 file changed, 12 ins
Recently, Redhat reported that nvml test suite failed on QEMU/KVM,
more detailed info please refer to:
https://bugzilla.redhat.com/show_bug.cgi?id=1365721
Actually, this bug is not only for NVDIMM/DAX but also for any other file
systems. This simple test case abstracted from nvml can easily rep
On Fri, Sep 30, 2016 at 7:01 PM, Andy Lutomirski wrote:
>
> Peter, how nasty would it be to add some lightish-weight lock that
> lets us pin a task in a non-running state? Maybe we could take the rq
> lock, do something to the task to make it sleepy (steal it off the
> queue?), unlock the lock, d
On 9/30/2016 7:39 AM, Petr Mladek wrote:
> On Thu 2016-09-29 19:55:56, Sean Hudson wrote:
>> This debug feature provides a convenient way to collect log entries across
>> multiple, warmboot cycles and to share those entries with a boot loader.
>> It allows the kernel to use an external buffer for k
From: Markus Elfring
Date: Sat, 1 Oct 2016 05:55:05 +0200
* A multiplication for the size determination of a memory allocation
indicated that an array data structure should be processed.
Thus use the corresponding function "kmalloc_array".
This issue was detected by using the Coccinelle so
Instantiating the rmi4 I2C transport driver without interrupts assigned
(for example using manual i2c instantiation from the command line)
caused the driver to fail to load, but it does not clean up its regulator
or transport device registrations. Result is a crash at a later time,
for example when
Instantiating the rmi4 SPI transport driver without an interrupt assigned
caused the driver to fail to load, but it does not clean up its transport
device registration. Result may be a crash at a later time, for example
when rebooting the system.
Fixes: 8d99758dee31 ("Input: synaptics-rmi4 - add S
On 09/30/2016 04:02 PM, Dmitry Torokhov wrote:
On Fri, Sep 30, 2016 at 03:54:03PM -0700, Dmitry Torokhov wrote:
On Thu, Sep 29, 2016 at 10:55:40AM -0700, Bjorn Andersson wrote:
On Wed 28 Sep 17:37 PDT 2016, Guenter Roeck wrote:
Instantiating the rmi4 I2C transport driver without interrupts as
On Friday 30 September 2016, Ido Schimmel wrote:
> BTW, which flags did you pass to generate this error? I can only
> reproduce this with EXTRA_CFLAGS="-Wmaybe-uninitialized -Werror", but
> for some reason EXTRA_CFLAGS="-Wall -Werror" is silent. Any idea why? I
> would like to add this to my git ho
On Saturday 01 October 2016, David Howells wrote:
> commit 35510eefc29e2757c1ac46218cded2e505093fc2
> Author: David Howells
> Date: Sat Oct 1 00:35:15 2016 +0100
>
> rxrpc: Split rxrpc_send_call_packet()
>
> Split rxrpc_send_data_packet() to separate ACK generation (which is more
>
F54 diagnostics report functions provide data based on the number of
enabled rx and tx electrodes, which is not identical to the number of
electrodes reported with F54:Query0 and F54:Query1. Those values report
the number of supported electrodes, not the number of enabled electrodes.
The number of
receiver assignment) and
F55:Ctrl2 (sensor transmitter assignment).
Support for additional sensor tuning functions may be added later.
Signed-off-by: Guenter Roeck
---
This patch applies to next-20160930.
drivers/input/rmi4/Kconfig | 9 +++
drivers/input/rmi4/Makefile | 1
Instantiating the rmi4 SPI transport driver without an interrupt assigned
caused the driver to fail to load, but it does not clean up its transport
device registration. Result may be a crash at a later time, for example
when rebooting the system.
Fixes: 8d99758dee31 ("Input: synaptics-rmi4 - add S
On (09/30/16 13:27), Petr Mladek wrote:
> > > > This patch set extends a lock-less NMI per-cpu buffers idea to
> > > > handle recursive printk() calls. The basic mechanism is pretty much the
> > > > same -- at the beginning of a deadlock-prone section we switch to
> > > > lock-less
> > > >
On 09/30/2016 03:54 PM, Dmitry Torokhov wrote:
On Thu, Sep 29, 2016 at 10:55:40AM -0700, Bjorn Andersson wrote:
On Wed 28 Sep 17:37 PDT 2016, Guenter Roeck wrote:
Instantiating the rmi4 I2C transport driver without interrupts assigned
(for example using manual i2c instantiation from the comman
-03-16.cgz-811565123a194d9cc0b490719bef761e1730dbf4-20160930-107145-1d180kz-0.yaml
ARCH=i386 kconfig=i386-randconfig-sb0-09262308
branch=linux-devel/devel-hourly-2016092605
commit=811565123a194d9cc0b490719bef761e1730dbf4
BOOT_IMAGE=/pkg/linux/i386-randconfig-sb0-0926
On (09/30/16 13:15), Petr Mladek wrote:
[..]
> > and the decision was to keep `unsigned long flags' on stack in the
> > alt_enter/exit caller. besides in most of the cases we already have
> > it (in vprintk_emit() and console_unlock()).
>
> I would pass the pointer to flags as alt_enter() paramete
On Fri, Sep 30, 2016 at 6:56 PM, Sean Hudson wrote:
> On 9/29/2016 8:36 PM, Kees Cook wrote:
>> On Thu, Sep 29, 2016 at 5:55 PM, Sean Hudson
>> wrote:
>>> This patch set is based on Linus' v4.8-rc8 tag.
>>>
>>> This debug feature allows the kernel to use an external buffer and
>>> control block f
On (10/01/16 00:17), Sergey Senozhatsky wrote:
[..]
> +void alt_printk_enter(void)
> +{
> + unsigned long flags;
-
> + local_irq_save(flags);
> + if (!(this_cpu_read(alt_printk_ctx) & ALT_PRINTK_CONTEXT_MASK))
> + this_cpu_write(alt_printk_irq_flags, flags);
> + this_cpu
[cc: PeterZ]
On Fri, Sep 30, 2016 at 11:56 AM, Jann Horn wrote:
> On Fri, Sep 30, 2016 at 10:58:56AM -0700, Andy Lutomirski wrote:
>> Reporting these fields on a non-current task is dangerous. If the
>> task is in any state other than normal kernel code, they may contain
>> garbage or even kerne
On 9/29/2016 8:36 PM, Kees Cook wrote:
> On Thu, Sep 29, 2016 at 5:55 PM, Sean Hudson
> wrote:
>> This patch set is based on Linus' v4.8-rc8 tag.
>>
>> This debug feature allows the kernel to use an external buffer and
>> control block for kernel log messages. The feature is controlled by
>> an o
On 9/27/2016 10:35 AM, Frederic Weisbecker wrote:
On 8/16/2016 5:19 PM, Chris Metcalf wrote:
Here is a respin of the task-isolation patch set.
Again, I have been getting email asking me when and where this patch
will be upstreamed so folks can start using it. I had been thinking
the obvious pa
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive updates for the input subsystem. One small change to make
joydev (which is used by older games) to bind to devices that export Z
axis but not X or Y (such as TRC rudder).
Change
This patch add update_ckpt_flags() to clean up the flow.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/checkpoint.c | 56 +++-
1 file changed, 33 insertions(+), 23 deletions(-)
diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c
index 7e26328..7e9b5
On Sat, Oct 01, 2016 at 08:26:20AM +0800, Chao Yu wrote:
> On 2016/10/1 1:10, Jaegeuk Kim wrote:
> > @@ -1089,6 +1079,9 @@ static int do_checkpoint(struct f2fs_sb_info *sbi,
> > struct cp_control *cpc)
> > if (is_sbi_flag_set(sbi, SBI_NEED_FSCK))
> > set_ckpt_flags(ckpt, CP_FSCK_FL
Hi,
> -Original Message-
> From: Guenter Roeck [mailto:gro...@google.com]
> Sent: Saturday, October 01, 2016 2:45 AM
> To: Jun Li
> Cc: Guenter Roeck ; Felipe Balbi
> ; Chandra Sekhar Anagani
> ; Bruce Ashfield
> ; Bin Gao ; Pranav Tipnis
> ; Heikki Krogerus
> ; linux-kernel@vger.kernel.or
On Fri, Sep 30, 2016 at 04:09:09PM +0200, Richard Weinberger wrote:
>
> if I read the ext4 code correctly, you pass encrypted filenames to
> ext4fs_dirhash().
> These filenames are not encoded and therefore binary gibberish.
That's correct.
> Isn't this a problem for the ext4 hash functions? My
On 2016/10/1 1:10, Jaegeuk Kim wrote:
> @@ -1089,6 +1079,9 @@ static int do_checkpoint(struct f2fs_sb_info *sbi,
> struct cp_control *cpc)
> if (is_sbi_flag_set(sbi, SBI_NEED_FSCK))
> set_ckpt_flags(ckpt, CP_FSCK_FLAG);
>
> + /* set this flag to activate crc|cp_ver for re
On Wed, Sep 28, 2016 at 04:34:01PM +0200, Benjamin Tissoires wrote:
> i2c_smbus_read_block_data() returns negative errno else the number of
> data bytes in the slave's response.
>
> Checking for error not null means the function always fails if the device
> answers properly.
>
> So given that we
Nudge, poke.
On Thu, Sep 29, 2016 at 5:33 AM, Jason A. Donenfeld wrote:
> Though the time_before and time_after family of functions were nicely
> extended to support jiffies64, so that the interface would be
> consistent, it was forgotten to also extend the before/after jiffies
> functions to sup
On Wed, Sep 28, 2016 at 04:34:03PM +0200, Benjamin Tissoires wrote:
> The Thinkpad series 13 uses Host Notify to report the interrupt.
> Add elan_smb_alert() to handle those interrupts and disable the irq
> handling on this case.
>
> Signed-off-by: Benjamin Tissoires
> ---
> drivers/input/mouse/
Something like the attached.
David
---
commit 35510eefc29e2757c1ac46218cded2e505093fc2
Author: David Howells
Date: Sat Oct 1 00:35:15 2016 +0100
rxrpc: Split rxrpc_send_call_packet()
Split rxrpc_send_data_packet() to separate ACK generation (which is more
complicated) from ABO
On Wed, Sep 28, 2016 at 04:34:02PM +0200, Benjamin Tissoires wrote:
> it's always easier to retrieve these information in bug reports when
> it is always printed in the dmesg.
>
> Signed-off-by: Benjamin Tissoires
> ---
> drivers/input/mouse/elan_i2c_core.c | 2 +-
> 1 file changed, 1 insertion(
Arnd Bergmann wrote:
> A number of reworks went into rxrpc_send_call_packet() recently, which
> introduced another warning when built with -Wmaybe-uninitialized:
>
> In file included from ../net/rxrpc/output.c:20:0:
> net/rxrpc/output.c: In function 'rxrpc_send_call_packet':
> net/rxrpc/ar-inter
On Fri, 2016-09-30 at 18:38 +0200, Christophe LEROY wrote:
> I don't have any ppc64 target, I only have mpc8xx and mpc83xx which
> bothÂ
> are ppc32
That's what qemu is for :-)
Cheers,
Ben.
Fix checkpatch.pl warning:
WARNING: braces {} are not necessary for single statement blocks
Signed-off-by: Wayne Porter
---
drivers/staging/android/ion/hisilicon/hi6220_ion.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/android/ion/hisilicon/hi6220_ion.
On Fri, Sep 30, 2016 at 03:54:03PM -0700, Dmitry Torokhov wrote:
> On Thu, Sep 29, 2016 at 10:55:40AM -0700, Bjorn Andersson wrote:
> > On Wed 28 Sep 17:37 PDT 2016, Guenter Roeck wrote:
> >
> > > Instantiating the rmi4 I2C transport driver without interrupts assigned
> > > (for example using manu
Alignment fixes
Signed-off-by: Wayne Porter
---
drivers/staging/android/ion/hisilicon/hi6220_ion.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/android/ion/hisilicon/hi6220_ion.c
b/drivers/staging/android/ion/hisilicon/hi6220_ion.c
index 659aa71..a
On Fri, Sep 30, 2016 at 2:23 PM, Jacek Anaszewski
wrote:
> Hi Matt,
>
> Thanks for the patch.
>
>
> On 09/30/2016 09:27 PM, Matt Ranostay wrote:
>>
>> Turn off LEDS on suspend and put device in low power state, and restore
>> settings on resume.
>>
>> Cc: Tony Lindgren
>> Cc: Richard Purdie
>> C
On Thu, Sep 29, 2016 at 10:55:40AM -0700, Bjorn Andersson wrote:
> On Wed 28 Sep 17:37 PDT 2016, Guenter Roeck wrote:
>
> > Instantiating the rmi4 I2C transport driver without interrupts assigned
> > (for example using manual i2c instantiation from the command line)
> > caused the driver to fail t
Cleanup extra line found by checkpatch.pl
Signed-off-by: Wayne Porter
---
drivers/staging/android/uapi/ion_test.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/android/uapi/ion_test.h
b/drivers/staging/android/uapi/ion_test.h
index ffef06f..480242e 100644
--- a/drivers/stag
On Fri, Sep 30, 2016 at 06:22:33PM +0200, Arnd Bergmann wrote:
> The newly added ektf2127 driver uses the SIMPLE_DEV_PM_OPS macro
> to conditionally refer to the resume/suspend functions, which
> causes a warning when CONFIG_PM_SLEEP is disabled:
>
> drivers/input/touchscreen/ektf2127.c:168:12: er
On Fri, Sep 30, 2016 at 01:21:27AM -0400, David Miller wrote:
> From: Dmitry Torokhov
> Date: Thu, 29 Sep 2016 08:46:05 -0700
>
> > Hi David,
> >
> > On Wed, Aug 10, 2016 at 2:36 PM, Dmitry Torokhov
> > wrote:
> >> If net namespace is attached to a user namespace let's make container's
> >> roo
The mm-of-the-moment snapshot 2016-09-30-15-24 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
From: Tyler Hicks
The capability check should not be audited since it is only being used
to determine the inode permissions. A failed check does not indicate a
violation of security policy but, when an LSM is enabled, a denial audit
message was being generated.
The denial audit message caused co
On Wed, Sep 21, 2016 at 06:54:59AM +, Po Liu wrote:
> > > > Will the new kernel work with existing/old DTB? I'm trying to
> > > > understand the dependency between driver and DTS changes.
> > >
> > > Yes, We've never use name 'intr' before. So we remove it is ok.
> > > 'aer' is a dts nam
In order to aid debugging, we add a debugfs interface to the driver
that allows direct interaction with the AVS co-processor.
The debugfs interface provides a means for reading all and writing some
of the mailbox registers directly from the shell prompt and enables a
user to execute the communicat
This driver supports voltage and frequency scaling on Broadcom STB SoCs
using AVS firmware with DFS and DVFS support.
Actual frequency or voltage scaling is done exclusively by the AVS
firmware. The driver merely provides a standard CPUfreq interface to
other kernel components and userland, and in
Add the binding document for the new brcmstb-avs-cpufreq driver.
Signed-off-by: Markus Mayer
---
.../bindings/cpufreq/brcm,stb-avs-cpu-freq.txt | 77 ++
MAINTAINERS| 7 ++
2 files changed, 84 insertions(+)
create mode 100644
Docu
This series contains the CPUfreq driver for Broadcom SoCs that use "AVS
Firmware" for voltage and frequency scaling. All voltage and frequency
transitions are performed by the firmware and are therefore hidden from
Linux.
The driver provides a standard CPUfreq interface to other kernel
components
There is no need to clk_disable_unprepare(dev->clk)
before it was initialized.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/net/ethernet/marvell/mvmdio.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers
On 09/29/2016 10:56 AM, Srinivas Pandruvada wrote:
On Thu, 2016-09-29 at 14:19 +0200, Rafael J. Wysocki wrote:
[...]
My laptop was inadvertently put to sleep while I was gone. I forgot
to leave a
note for my wife and she quieted the noisy cpu fan. :)
It looks like in 4.8-rc we made a change t
Dear RT folks!
I'm pleased to announce the v4.6.7-rt14 patch set.
Changes since v4.6.7-rt13:
- It is possible that a task which got priority boosted, de-boosted
itself too early in the unlock path. This leads to then priority
inversion because the waiter with priority waits while a pr
Fixed coding style issue.
Signed-off-by: Nadim Almas
---
drivers/staging/dgnc/dgnc_neo.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/dgnc/dgnc_neo.c b/drivers/staging/dgnc/dgnc_neo.c
index e794056..bc15584 100644
--- a/drivers/staging/dgnc/dgnc_neo.c
+++
Remove error from struct rxrpc_skb_priv as it is no longer used.
Signed-off-by: David Howells
---
net/rxrpc/ar-internal.h |1 -
1 file changed, 1 deletion(-)
diff --git a/net/rxrpc/ar-internal.h b/net/rxrpc/ar-internal.h
index fd64a2bd1072..141c1458e719 100644
--- a/net/rxrpc/ar-internal.h
From: Michal Hocko
We have received a hard to explain oom report from a customer. The oom
triggered regardless there is a lot of free memory:
PoolThread invoked oom-killer: gfp_mask=0x280da, order=0, oom_adj=0,
oom_score_adj=0
PoolThread cpuset=/ mems_allowed=0-7
Pid: 30055, comm: PoolThread Ta
Switch to Congestion Avoidance mode at cwnd == ssthresh rather than relying
on cwnd getting incremented beyond ssthresh and the window size, the mode
being shifted and then cwnd being corrected.
We need to make sure we switch into CA mode so that we stop marking every
packet for ACK.
Signed-off-b
The call timer's concept of a call timeout (of which there are three) that
is inactive is that it is the timeout has the same expiration time as the
call expiration timeout (the expiration timer is never inactive). However,
I'm not resetting the timeouts when they expire, leading to repeated
proce
Keep that call timeouts as ktimes rather than jiffies so that they can be
expressed as functions of RTT.
Signed-off-by: David Howells
---
include/trace/events/rxrpc.h | 25 +++---
net/rxrpc/ar-internal.h |8 ++---
net/rxrpc/call_event.c | 73 ++
When we receive an ACK from the peer that tells us what the peer's receive
window (rwind) is, we should reduce ssthresh to rwind if rwind is smaller
than ssthresh.
Signed-off-by: David Howells
---
net/rxrpc/input.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/net/rxrpc/input.c b/net
The offset field in struct rxrpc_skb_priv is unnecessary as the value can
always be calculated.
Signed-off-by: David Howells
---
net/rxrpc/ar-internal.h |1 -
net/rxrpc/conn_event.c |3 ++-
net/rxrpc/input.c | 23 ---
net/rxrpc/local_event.c |3 ++-
net/
Actually display in the tx_data trace the retransmission note added in a
previous patch.
Signed-off-by: David Howells
---
include/trace/events/rxrpc.h |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/trace/events/rxrpc.h b/include/trace/events/rxrpc.h
index 8ba8d
s.git/log/?h=rxrpc-rewrite
Tagged thusly:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
rxrpc-rewrite-20160930
David
---
David Howells (7):
rxrpc: Actually display the tx_data trace retransmission note
rxrpc: Switch to Congestion Avoidance mode at
On 9/30/2016 5:27 PM, Rafael J. Wysocki wrote:
> On Fri, Sep 30, 2016 at 11:14 PM, Sinan Kaya wrote:
>> On 9/30/2016 5:04 PM, Rafael J. Wysocki wrote:
>
> I hope it makes sense now. I tend to skip details sometimes. Feel free to
> send more questions.
>>> Thanks for the information!
>>
A new futex implementation called throughput-optimized (TP) futexes
is introduced. The goal of this new futex type is to maximize locking
throughput at the expense of fairness and deterministic latency. Its
throughput is higher than that of the wait-wake futexes especially
on systems with a large n
Currently, the futex state objects can only be located indirectly as
hash bucket => futex_q => futex state
Actually it can be beneficial in some cases to locate the futex state
object directly from the hash bucket without the futex_q middleman.
Therefore, a new list head to link the futex
The TP futexes don't have code to handle the death of futex
owners. There are 2 different cases that need to be considered.
As top waiter gets a reference to the task structure of the futex
owner, the task structure will never go away even if the owner dies.
When the futex owner died while the top
As there are three different ways for a TP futex waiter in the kernel
to acquire the lock. It may be useful to pass this information out so
that user space has a better view of what is happening in the kernel.
With this change, different non-negative values will now be returned
depending on how the
Two new helper functions (task_pi_list_add & task_pi_list_del)
are created to consolidate all the pure pi_state_list addition and
insertion codes. The set_owner argument in task_pi_list_add() will
be needed in a later patch.
Signed-off-by: Waiman Long
---
kernel/futex.c | 67 ++
Unlike other futexes, TP futexes do not accept the specification of
a timeout value. To align with the other futexes, timeout support is
now added. However, the timeout isn't as precise as the other futex
types due to the fact that timer expiration can't be detected when
the thread is waiting in t
Two new helper functions cmpxchg_futex_value() and get_futex_value()
are added to access and change the futex value without the hash
bucket lock. As a result, page fault is enabled and the page will
be faulted in if not present yet.
Signed-off-by: Waiman Long
---
kernel/futex.c | 15 +
This microbenchmark simulates how the use of different futex types
can affect the actual performanace of userspace mutex locks. The
usage is:
perf bench futex mutex
Three sets of simple mutex lock and unlock functions are implemented
using the wait-wake, PI and TP futexes respectively. T
As the futex_state structure will be overloaded in later patches
to be used by non-PI futexes, it is necessary to add a type field to
distinguish among different types of futexes.
Signed-off-by: Waiman Long
---
kernel/futex.c | 14 ++
1 files changed, 10 insertions(+), 4 deletions(
This patch adds a new document file on how to use the TP futexes.
Signed-off-by: Waiman Long
---
Documentation/00-INDEX |2 +
Documentation/tp-futex.txt | 147
2 files changed, 149 insertions(+), 0 deletions(-)
create mode 100644 Documentati
This patchset includes changes to the futex(2) and futex(7) manpages
to add descriptions for the new throughput-optimized (TP) futexes
that can be used to implement userspace mutexes.
This patchset includes a place holder (4.X) for the exact version that
the new TP futexes code is merged. That wil
v2->v3:
- Use the abbreviation TP for the new futexes instead of TO.
- Make a number of changes accordingly to review comments from
ThomasG, PeterZ and MikeG.
- Breaks the main futex patch into smaller pieces to make them easier
to review.
- Integrate the microbenchmark into the "p
The FUTEX_LOCK and FUTEX_UNLOCK operation pair is for supporting the
new throughput-optimized futexes. The futex(7) manpage is extended
to include description about the operations.
Signed-off-by: Waiman Long
---
man7/futex.7 | 22 ++
1 files changed, 22 insertions(+), 0 del
On Fri, Sep 30, 2016 at 11:14 PM, Sinan Kaya wrote:
> On 9/30/2016 5:04 PM, Rafael J. Wysocki wrote:
>>> >
>>> > I hope it makes sense now. I tend to skip details sometimes. Feel free to
>>> > send more questions.
>> Thanks for the information!
>>
>> IIUC, basically, what you are proposing would b
The FUTEX_LOCK and FUTEX_UNLOCK operation pair is for supporting the
new throughput-optimized futexes. The futex(2) manpage is extended
to include description about the operations.
Signed-off-by: Waiman Long
---
man2/futex.2 | 49 +
1 files chang
The futex_pi_state structure will be overloaded in later patches to
store state information about non-PI futexes. So the structure name
itself is no longer a good description of its purpose. So its name
is changed to futex_state, a more generic name.
Some of the functions that process the futex st
A new futex_setup_timer() helper function is added to consolidate all
the hrtimer_sleeper setup code.
Signed-off-by: Waiman Long
---
kernel/futex.c | 67 +++-
1 files changed, 37 insertions(+), 30 deletions(-)
diff --git a/kernel/futex.c b/k
The current TP futexes has no guarantee that the top waiter
(serialization mutex owner) can get the lock within a finite time.
As a result, lock starvation can happen.
A lock handoff mechanism is added to the TP futexes to prevent lock
starvation from happening. The idea is that the top waiter can
Hi Matt,
Thanks for the patch.
On 09/30/2016 09:27 PM, Matt Ranostay wrote:
Turn off LEDS on suspend and put device in low power state, and restore
settings on resume.
Cc: Tony Lindgren
Cc: Richard Purdie
Cc: Jacek Anaszewski
Signed-off-by: Matt Ranostay
---
drivers/leds/leds-pca963x.c |
On 09/12/2016 08:55 AM, Yuriy Kolerov wrote:
> In the end of "arc_init_IRQ" STATUS32.IE flag is going to be affected by
> "flag" instruction but "flag" never touches IE flag on ARCv2. So "kflag"
> instruction must be used instead of "flag".
>
> Signed-off-by: Yuriy Kolerov
> ---
> arch/arc/kerne
The driver don't take into account the differences between packed, semi
planar and multi planar formats when calculating the pixel format bytes
per lines and image size values. This makes GStreamer to fail when the
following formats are used NV12, NV21, NV16, NV61, YV12, I420 and Y42B:
"gst_video_
The driver exposes 32-bit A/XRGB 8-8-8-8 as supported format but testing
shows that using this format produces frames with wrong colors. The test
was done with the following GStreamer pipeline:
$ gst-launch-1.0 videotestsrc num-buffers=20 ! video/x-raw,format=UYVY \
! v4l2video3convert ! video/x-r
User-space applications can use the VIDIOC_REQBUFS ioctl to determine if a
memory mapped, user pointer or DMABUF based I/O is supported by a driver.
For example, GStreamer attempts to determine the I/O methods supported by
the driver by doing many VIDIOC_REQBUFS ioctl calls with different memory
t
The driver try_fmt handler prints a message each time that the image
size has been changed due the maximum and minimum width and height.
Since user-space can try different format and sizes, this logs a lot
of unnecessary messages. Change the message log level to debug and
while being there, also a
Hello,
This patch series contains a cleanup and some fixes for the exynos-gsc
driver. I found these issues when trying to use the driver with the
GStreamer v4l2videoconvert element. I wasn't able to display to Exynos
DRM/KMS driver and only a small set of formats were working correctly.
After the
On 9/30/2016 5:04 PM, Rafael J. Wysocki wrote:
>> >
>> > I hope it makes sense now. I tend to skip details sometimes. Feel free to
>> > send more questions.
> Thanks for the information!
>
> IIUC, basically, what you are proposing would be to restore the old
> penalizing method for IRQs in the 0-2
Commit d9676fa152c83b ("ARCv2: Enable LOCKDEP"), changed
local_save_flags() to not return raw STATUS32 but encoded in the form
such that it could be fed directly to CLRI/SETI instructions.
However the STATUS32.E[] was not captured correctly as it corresponds to
bits [4:1] in the register and not [3
1 - 100 of 471 matches
Mail list logo
