Ding Tianhong reported a live-lock situation where a constant stream
of incoming optimistic spinners blocked a task in the wait list from
getting the mutex.
This patch attempts to fix this live-lock condition by enabling the
woken task in the wait queue to enter into an optimistic spinning
loop it
On Mon, Jul 18, 2016 at 1:11 PM, John Stultz wrote:
> When an interface to allow a task to change another tasks
> timerslack was first proposed, it was suggested that something
> greater then CAP_SYS_NICE would be needed, as a task could be
> delayed further then what normally could be done with n
On Mon, Jul 18, 2016 at 1:11 PM, John Stultz wrote:
> As requested, this patch implements a task_settimerslack and
> task_gettimerslack LSM hooks so that the /proc//timerslack_ns
> interface can have finer grained security policies applied to it.
>
> I've kept the CAP_SYS_NICE check in the timersl
On Mon, 18 Jul 2016 18:35:19 +0200, Benjamin Tissoires wrote:
> On Jul 18 2016 or thereabouts, Jean Delvare wrote:
> > But what happens on i2c_adapter removal? What prevents the following
> > sequence from happening?
> >
> > 1* A Host Notify event happens.
> > 2* The event is handled and queued by
On 07/18/2016 01:59 PM, Jason Low wrote:
On Tue, 2016-03-22 at 13:46 -0400, Waiman Long wrote:
v2->v3:
- Remove patch 4 as it is not useful.
- Allow need_resched() check for waiter& add more comments about
changes to address issues raised by PeterZ.
v1->v2:
- Set task state to runnin
Am Donnerstag, 14. Juli 2016, 18:24:33 schrieb Brian Norris:
> It's nicer to see this:
>
> # ls -l /sys/bus/spi/devices/
> total 0
> lrwxrwxrwx 1 root root 0 Dec 31 1969 spi0.0 ->
> ../../../devices/platform/ff1c.spi/spi_master/spi0/spi0.0 lrwxrwxrwx 1
> root root 0 Dec 31 1969 s
Am Freitag, 15. Juli 2016, 09:10:05 schrieb Shawn Lin:
> commit 1ade61c141e2 ("arm64: dts: rockchip: remove broken-cd
> from emmc and sdio") was intended to remove the abuse of
> broken-cd property from mmc. But somehow it forgot to remove
> this property from sdio0 node. Let's remove it now.
>
>
On 07/18/2016 08:30 PM, Liang, Kan wrote:
On 07/18/2016 08:55 AM, kan.li...@intel.com wrote:
[...]
On a higher level picture, why for example, a new cgroup in combination
with tc shouldn't be the ones resolving these policies on resource usage?
The NET policy doesn't support cgroup yet, but i
On Mon, 18 Jul 2016, Michal Hocko wrote:
> > There's
> > two fundamental ways to go about it: (1) ensure mempool_alloc() can make
> > forward progress (whether that's by way of gfp flags or access to memory
> > reserves, which may depend on the process context such as PF_MEMALLOC) or
> > (2) r
The touchscreen may have a margin where not all the matrix is used. Read
the parameters from T9 and T100 and take account of the difference.
Note: this does not read the XORIGIN/YORIGIN fields so it assumes that
the touchscreen starts at (0,0)
Signed-off-by: Nick Dyer
---
drivers/input/touchscr
Register a video device to output T37 diagnostic data.
Signed-off-by: Nick Dyer
---
drivers/input/touchscreen/Kconfig|6 +-
drivers/input/touchscreen/atmel_mxt_ts.c | 245 ++
2 files changed, 249 insertions(+), 2 deletions(-)
diff --git a/drivers/input/t
Function 54 implements access to various RMI4 diagnostic features.
This patch adds support for retrieving this data. It registers a V4L2
device to output the data to user space.
Signed-off-by: Nick Dyer
Tested-by: Andrew Duggan
Tested-by: Chris Healy
---
drivers/input/rmi4/Kconfig | 11
Invert the diagnostic data to match the orientation of the input device.
Signed-off-by: Nick Dyer
---
drivers/input/touchscreen/atmel_mxt_ts.c | 26 +-
1 file changed, 21 insertions(+), 5 deletions(-)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
b/drivers/inp
I'm leaving ITDev, so change to my personal email. My understanding is
that someone at Atmel will take this on once their takeover by Microchip
has settled down.
Signed-off-by: Nick Dyer
---
MAINTAINERS |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/MAINTAINERS b/MA
Atmel maXTouch devices have a T37 object which can be used to read raw
touch deltas from the device. This consists of an array of 16-bit
integers, one for each node on the touchscreen matrix.
Signed-off-by: Nick Dyer
---
drivers/input/touchscreen/Kconfig|6 ++
drivers/input/touchscre
The mXT1386 family of chips have a different architecture which splits
the diagnostic data into 3 columns.
Signed-off-by: Nick Dyer
---
drivers/input/touchscreen/atmel_mxt_ts.c | 31 +++---
1 file changed, 28 insertions(+), 3 deletions(-)
diff --git a/drivers/input/tou
Support both V4L2_TCH_FMT_TU08 and V4L2_PIX_FMT_GREY for backwards
compatibility.
Note: I have not tested these changes (I have no access to the hardware)
so not signing off.
---
drivers/input/touchscreen/sur40.c | 122 +++--
1 file changed, 89 insertions(+), 33 d
There are different datatypes available from a maXTouch chip. Add
support to retrieve reference data as well.
Signed-off-by: Nick Dyer
---
drivers/input/touchscreen/atmel_mxt_ts.c | 57 ++
1 file changed, 51 insertions(+), 6 deletions(-)
diff --git a/drivers/input/
This is a series of patches to add output of raw touch diagnostic data via V4L2
to the Atmel maXTouch and Synaptics RMI4 drivers.
It's a rewrite of the previous implementation which output via debugfs: it now
uses a V4L2 device in a similar way to the sur40 driver.
We have a utility which can rea
From: Nick Dyer
Signed-off-by: Nick Dyer
---
Documentation/media/uapi/mediactl/media-types.rst | 24 +++--
Documentation/media/uapi/v4l/dev-touch.rst| 55 ++
Documentation/media/uapi/v4l/devices.rst |1 +
Documentation/media/uapi/v4l/pixfmt-tch-td08.rst | 80
Some touch controllers send out touch data in a similar way to a
greyscale frame grabber.
Add new device type VFL_TYPE_TOUCH:
- This uses a new device prefix v4l-touch for these devices, to stop
generic capture software from treating them as webcams. Otherwise,
touch is treated similarly to vi
Signed-off-by: Nick Dyer
---
utils/v4l2-compliance/v4l2-compliance.cpp| 51 +-
utils/v4l2-compliance/v4l2-compliance.h |1 +
utils/v4l2-compliance/v4l2-test-input-output.cpp |4 +-
3 files changed, 53 insertions(+), 3 deletions(-)
diff --git a/utils
On 7/18/2016 1:32 PM, Alex Williamson wrote:
> The implementation looks pretty fixed, it seems like a lot would break
> if that were changed, so the callers of the function would need to be
> updated, including this one. The ternary below is already paranoid
> enough to handle an API change, but i
On Mon, Jul 18, 2016 at 1:39 PM, Sinan Kaya wrote:
> The of_msi_configure routine is only accessible by the built-in
> kernel drivers. Export this function so that modules can use it
> too.
>
> This function is useful for configuring MSI on child device tree
> nodes on hierarchical objects.
>
> Si
On Thu, Jun 23, 2016 at 1:57 PM, Rob Herring wrote:
> Copy the config fragments from the AOSP common kernel android-4.4
> branch. It is becoming possible to run mainline kernels with Android,
> but the kernel defconfigs don't work as-is and debugging missing config
> options is a pain. Adding the
> OK. I think caching per-port (and thus per-bridge) ageing time would do
> the trick and keep DSA drivers simple. What about the following patch?
Hi Vivien
This looks good. I would suggest you do some testing with a printk,
and force some topology changes, just to make sure it works how we
think
Hi Guenter,
On Sat, Jul 16, 2016 at 9:35 AM, Guenter Roeck wrote:
> On 07/11/2016 05:30 PM, Hoan Tran wrote:
>>
>> This patch adds hardware temperature and power reading support for
>> APM X-Gene SoC using the mailbox communication interface.
>>
>> Signed-off-by: Hoan Tran
>> ---
>> Documentat
On Mon, Jul 18, 2016 at 06:01:08AM +, Wang Nan wrote:
> New LLVM will issue newly assigned EM_BPF machine code. The new code
> will be propogated to glibc and libelf.
>
> This patch introduces the new machine code to libbpf.
>
> Signed-off-by: Wang Nan
> Cc: Alexei Starovoitov
> Cc: Arnaldo
Few comments inline
On 17/06/16 11:52, Enric Balletbo i Serra wrote:
This patch adds and entry to the sysfs to start firmware upload process
on the specified device with the requested firmware.
The uploading of the firmware needs only to happen once per firmware
upgrade, as the firmware is stor
On Sun, Jun 26, 2016 at 3:11 PM, Michal Suchanek wrote:
> The tree returned from of_fdt_unflatten_tree cannot be attached to the
> live tree because it is not marked as detached so mark it as such. The
> dt resolver checks the flag and refuses to process the tree otherwise.
>
> Signed-off-by: Mich
Some distros has been playing with toolchain changes that can affect
the type of ELF objects built. Occasionally, this goes wrong and
the vDSO ends up not being a DSO at all. This causes the kernel to
end up broken in a surprisingly subtle way -- glibc apparently
silently ignores a vDSO that isn'
On Sun, Jun 26, 2016 at 3:11 PM, Michal Suchanek wrote:
> Applying overlay fails silently in case of an error. Add error prints.
> Most notably the lack of symbols in the live tree is not reported.
>
> Signed-off-by: Michal Suchanek
> ---
> drivers/of/resolver.c | 6 ++
> 1 file changed, 6 i
Hello,
On Mon, Jul 18, 2016, at 21:43, Andi Kleen wrote:
> > I wonder if this can be attacked from a different angle. What would be
> > missing to add support for this in user space? The first possibility
> > that came to my mind is to just multiplex those hints in the kernel.
>
> "just" is the h
On Monday, July 18, 2016 09:42:19 AM Chen Yu wrote:
> It is reported the hibernation fails at 2nd attempt, which
> hangs at hibernate() -> syscore_resume() -> i8237A_resume()
> -> claim_dma_lock(), because the lock has already been taken.
> However there is actually no other process would like to g
Hi,
On 18/07/16 12:14, Sergei Shtylyov wrote:
Hello.
On 7/18/2016 12:30 AM, Philippe Reynes wrote:
The private structure contain a pointer to phydev, but the structure
net_device already contain such pointer. So we can remove the pointer
phydev in the private structure, and update the driver
The tree returned from of_fdt_unflatten_tree cannot be attached to the
live tree because it is not marked as detached so mark it as such. The
dt resolver checks the flag and refuses to process the tree otherwise.
Signed-off-by: Michal Suchanek
---
- rebase on top of 4.7rc
---
drivers/of/fdt.c |
On 07/17/2016 02:30 PM, Philippe Reynes wrote:
> There are two generics functions phy_ethtool_{get|set}_link_ksettings,
> so we can use them instead of defining the same code in the driver.
>
> Signed-off-by: Philippe Reynes
> ---
> - cmd.phy_address = pep->phy_addr;
> - cmd.speed = pep->
On Thu, Jul 14, 2016 at 2:22 PM, Chris Metcalf wrote:
> On 7/14/2016 5:03 PM, Andy Lutomirski wrote:
>>
>> On Thu, Jul 14, 2016 at 1:48 PM, Chris Metcalf
>> wrote:
>>>
>>> Here is a respin of the task-isolation patch set. This primarily
>>> reflects feedback from Frederic and Peter Z.
>>
>> I st
On Mon, 2016-07-18 at 10:59 +0200, Pavel Machek wrote:
> On Fri 2016-07-08 10:19:26, Linus Torvalds wrote:
> >
> > [ rare comment rant. I think I'll do this once, and then ignore the
> > discussion ]
> >
> > On Fri, Jul 8, 2016 at 9:45 AM, Herbert Xu
> > wrote:
> > >
> > >
> > > Nack. As I
Pwm channels don't send uevents when exported, this change adds the
channels to a pwm class and set their device type to pwm_channel so
uevents are sent.
To do this properly, the device names need to change to uniquely
identify a channel. This change is from pwmN to pwmchipM:N
Signed-off-by: Dav
On Mon, Jul 18, 2016 at 4:27 PM, Tomas Winkler wrote:
> The user space API is achieved via two synchronous IOCTL.
> Simplified one, RPMB_IOC_REQ_CMD, were read result cycles is performed
> by the framework on behalf the user and second, RPMB_IOC_SEQ_CMD where
> the whole RPMB sequence including RE
> Signed-off-by: Pratik Prajapati
comments below; nice addition
it seems this patch clashes with the recent changes to this driver in
iio-testing; can you rebase on top please?
I suggest to split out the transition to regmap in a separate patch
> ---
> drivers/iio/light/vcnl4000.c | 119
>
From: Linus Torvalds
thread_info may move in the future, so use the accessors.
[Andy Lutomirski wrote this changelog message and changed
"task_thread_info(child)->cpu" to "task_cpu(child)".]
Message-Id:
Signed-off-by: Andy Lutomirski
---
arch/x86/um/ptrace_32.c | 8
1 file changed,
Hi Arnaldo,
On Mon, 18 Jul 2016 17:36:34 -0300 Arnaldo Carvalho de Melo
wrote:
>
> Em Mon, Jul 18, 2016 at 01:04:34PM -0700, Andy Lutomirski escreveu:
> > On Sun, Jul 17, 2016 at 10:18 PM, Stephen Rothwell
> > wrote:
> > > On Fri, 15 Jul 2016 12:43:26 -0300 Arnaldo Carvalho de Melo
> > > w
On Mon, Jul 18, 2016 at 3:22 PM, Andy Lutomirski wrote:
> From: Linus Torvalds
>
> thread_info may move in the future, so use the accessors.
>
> [Andy Lutomirski wrote this changelog message and changed
> "task_thread_info(child)->cpu" to "task_cpu(child)".]
>
> Message-Id:
>
> Signed-off-by:
Hello, Pang.
On Fri, Jul 15, 2016 at 12:39:59PM +, Pang Raymond wrote:
> Hi Tejun,
>
>
> Yes! It only happens when the device is shutdown.
>
> I think you're right. It's more wiser to add clearing operation to driver
>
> clean up path.
>
> So we can add it to ahci_port_stop()
>
>
> liba
VLAN and MQ control was doing DMA from the stack. Fix it.
Cc: Michael S. Tsirkin
Cc: "net...@vger.kernel.org"
Signed-off-by: Andy Lutomirski
---
I tested VLAN addition and removal with CONFIG_VMAP_STACK=y,
CONFIG_DEBUG_SG=y and it got rid of the warnings I saw. I haven't
tested the MQ part b
Since the previous patch allows creating SPI slaves without specifying
what device the CS connects to make spi-max-frequency also optional.
The spi-max-frequency is device-specific and the driver can set it
anyway.
Signed-off-by: Michal Suchanek
---
drivers/spi/spi.c | 6 +++---
1 file changed,
This patch makes spidev into a bus addon rather than a separate driver.
spidev character device is created for each spi slave. When a spi slave
driver is bound the spidev IOCTLs return -EBUSY.
This is similar to i2c bus which alows access to any address not claimed
by a kernel driver and should pr
Hello,
this simplifies spidev to not pose as SPI driver but instead attach a character
device on each SPI slave indiscriminately. This does not require spidev to be
matched during driver binding and hence does not require it to be specified in
devicetree.
Any SPI slave device for which a driver i
SPI slave devices are not created when looking up driver for the slave
fails. Create a device anyway so it can be used with spidev.
Signed-off-by: Michal Suchanek
---
drivers/spi/spi.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
ind
On Mon, 2016-07-18 at 11:04 +0200, Boris Brezillon wrote:
> On Mon, 18 Jul 2016 10:39:18 +0200
> Hector Palacios wrote:
>
> >
> > nand_do_write_ops() determines if it is writing a partial page with the
> > formula:
> > part_pagewr = (column || writelen < (mtd->writesize - 1))
> >
> > When '
On Mon, 18 Jul 2016, William Breathitt Gray wrote:
> The Apex Embedded Systems STX104 is primarily an analog-to-digital
> converter device. The STX104 IIO driver was initially placed in the DAC
> directory because only the DAC portion of the STX104 was supported at
> the time. Now that ADC support
Em Mon, Jul 18, 2016 at 04:32:59PM +0200, Jiri Olsa escreveu:
> On Fri, Jul 15, 2016 at 11:08:12AM +0100, Mark Rutland wrote:
> > In systems with heterogeneous CPU PMUs, it's possible for each evsel to
> > cover a distinct set of CPUs, and hence the cpu_map associated with each
> > evsel may have a
Em Mon, Jul 18, 2016 at 02:14:09PM +0200, Jiri Olsa escreveu:
> On Mon, Jul 18, 2016 at 01:46:02PM +0200, Jiri Pirko wrote:
>
> SNIP
>
> > >diff --git a/tools/perf/tests/is_printable_array.c
> > >b/tools/perf/tests/is_printable_array.c
> > >new file mode 100644
> > >index ..42e13393e
On Fri, Jul 15, 2016 at 05:15:41PM +, Topi Miettinen wrote:
> There are clear semantics for the limits themselves, either they apply
> per task or per user. It makes sense to gather values according to these
> semantics. Then with systemd or other tools you can use the valuse to
> set the limit
Hi,
[auto build test ERROR on v4.7-rc7]
[also build test ERROR on next-20160718]
[cannot apply to tip/core/locking]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Peter-Zijlstra/locking-percpu
On Tue, Jul 19, 2016 at 12:35:40AM +0200, Michal Suchanek wrote:
> config SPI_SPIDEV
> - tristate "User mode SPI device driver support"
> + bool "User mode SPI device driver support"
This is a step back, it would require spidev to be built in.
> - spin_lock_irq(&spidev->spi_lock);
>
On Tue, Jul 19, 2016 at 12:35:41AM +0200, Michal Suchanek wrote:
> SPI slave devices are not created when looking up driver for the slave
> fails. Create a device anyway so it can be used with spidev.
> rc = of_modalias_node(nc, spi->modalias,
> sizeof(spi->moda
On Mon, Jul 18, 2016 at 03:34:49PM -0700, Andy Lutomirski wrote:
> VLAN and MQ control was doing DMA from the stack. Fix it.
>
> Cc: Michael S. Tsirkin
> Cc: "net...@vger.kernel.org"
> Signed-off-by: Andy Lutomirski
Acked-by: Michael S. Tsirkin
> ---
>
> I tested VLAN addition and removal
The device tree code checks for the presence of a reset driver and calls
the of_reset function pointer by looking up the reset driver as a module.
ACPI defines _RST method to perform device level reset. After the _RST
method is executed, the OS can resume using the device. _RST method is
expected
During discussions with various people interested in moving their
remoteproc-related out-of-tree patches towards mainline I have come
across a set of topics common among various teams. The purpose of this
email is to share some insight into these discussions and the current
ideas for moving forward
Getting ready to bring out extra debug information to the caller
so that more verbose information can be printed when an error is
observed.
Signed-off-by: Sinan Kaya
Reviewed-by: Baptiste Reynal
---
drivers/vfio/platform/vfio_platform_common.c | 9 +
1 file changed, 5 insertions(+), 4 d
The code is using the compatible DT string to associate a reset driver
with the actual device itself. The compatible string does not exist on
ACPI based systems. HID is the unique identifier for a device driver
instead.
Signed-off-by: Sinan Kaya
---
drivers/vfio/platform/vfio_platform_common.c
Open call is ignoring the return code from reset call and can
potentially continue even though reset call failed.
If reset_required module parameter is set, this patch is going
to validate the return code and will abort open if reset fails.
Signed-off-by: Sinan Kaya
Reviewed-by: Baptiste Reynal
On 07/18/2016 07:48 AM, Benjamin Tissoires wrote:
On Jul 13 2016 or thereabouts, Andrew Duggan wrote:
Calling of_find_node_by_name() assumes that the caller has incremented
the refcount of the of_node being passed in. Currently, the caller is
not incrementing the refcount of the of_node which re
On Fri, Jul 15, 2016 at 01:57:33PM -0700, Andrew Morton wrote:
> On Fri, 15 Jul 2016 13:00:40 -0600 Ross Zwisler
> wrote:
>
> >
> > ...
> >
> > In looking at this more, I agree that your patch fixes this particular bug,
> > but I think that ultimately we might want something more general.
> >
The reset call sequence seems to replicate itself multiple times
across the file. Grouping them together for maintenance reasons.
Signed-off-by: Sinan Kaya
Reviewed-by: Eric Auger
Reviewed-by: Baptiste Reynal
---
drivers/vfio/platform/vfio_platform_common.c | 30 +---
1
On 07/11/2016 10:08 AM, Stephen Warren wrote:
On 07/11/2016 08:14 AM, Rob Herring wrote:
On Thu, Jul 07, 2016 at 12:35:02PM -0600, Stephen Warren wrote:
On 07/07/2016 12:13 PM, Sivaram Nair wrote:
On Tue, Jul 05, 2016 at 05:04:22PM +0800, Joseph Lo wrote:
Add DT binding for the Hardware Synch
Renaming the reset function to of_reset as it is only used
by the device tree based platforms.
Signed-off-by: Sinan Kaya
Reviewed-by: Eric Auger
Reviewed-by: Baptiste Reynal
---
drivers/vfio/platform/vfio_platform_common.c | 30 +--
drivers/vfio/platform/vfio_platform_
Release call is ignoring the return code from reset call and can
potentially continue even though reset call failed.
If reset_required module parameter is set, this patch is going
to validate the return code and will cause stack dump with
WARN_ON and warn the user of failure.
Signed-off-by: Sinan
The code was allowing platform devices to be used without a supporting
VFIO reset driver. The hardware can be left in some inconsistent state
after a guest machine abort.
The reset driver will put the hardware back to safe state and disable
interrupts before returning the control back to the host
Creating a new function to determine if this driver supports reset
function or not. This is an attempt to abstract device tree calls
from the rest of the code.
Signed-off-by: Sinan Kaya
Reviewed-by: Eric Auger
Reviewed-by: Baptiste Reynal
---
drivers/vfio/platform/vfio_platform_common.c | 7 ++
Just caught this spew during a fuzz-run.
[ 4971.564511]
==
[ 4971.570505] BUG: KASAN: use-after-free in proc_map_files_readdir+0x2e3/0x5a0
at addr 88044feb2044
[ 4971.582570] Read of size 4 by task trinity-main/29845
[ 4971.5886
From: Arnaldo Carvalho de Melo
It uses the likely/unlikely macros, so need to include
.
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Wang Nan
Link: http://lkml.kernel.org/n/tip-p0xrhgbkicsii9ohmhhpr...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
---
tool
From: Dan Carpenter
It doesn't change the runtime behavior, but my static checker complains
that curly braces were intended.
Signed-off-by: Dan Carpenter
Cc: Adrian Hunter
Cc: Alexander Shishkin
Cc: Peter Zijlstra
Cc: Stephane Eranian
Cc: kernel-janit...@vger.kernel.org
Link: http://lkml.ke
From: Arnaldo Carvalho de Melo
Not used anymore, remove one more file referencing kernel sources, i.e.
outside of tools/
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Wang Nan
Link: http://lkml.kernel.org/n/tip-ykfjt3t8l0npxfwmekiww...@git.kernel.org
Signed-off-by: Ar
From: Dan Carpenter
The 'info.e_machine' struct member is an uint16_t so 'm' is never less
than zero. It looks like this was maybe left over code from earlier
versions so I've just removed it.
Signed-off-by: Dan Carpenter
Cc: Adrian Hunter
Cc: Alexander Shishkin
Cc: Peter Zijlstra
Cc: Steph
From: Arnaldo Carvalho de Melo
It hasn't been used since we made tools/ self sufficiente wrt list.h.
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jiri Olsa
Cc: Josh Poimboeuf
Cc: Namhyung Kim
Cc: Wang Nan
Fixes: d1b39d41ebec ("tools: Make list.h self-sufficient")
Link: http://lkml.kernel.org/n/ti
From: Arnaldo Carvalho de Melo
No need to copy it to a detached tarball as they aren't used anymore
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Wang Nan
Link: http://lkml.kernel.org/n/tip-lopmaqi439ke10g1j9cxr...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Mel
From: Jiri Olsa
Add automated test for is_printable_array function.
Signed-off-by: Jiri Olsa
Cc: David Ahern
Cc: Jiri Pirko
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc: Steven Rostedt
Link:
http://lkml.kernel.org/r/1468685480-18951-4-git-send-email-jo...@kernel.org
Signed-off-by: Arnaldo Carva
From: Jiri Olsa
It's used from 2 objects in perf, so it's better to keep just one copy.
Signed-off-by: Jiri Olsa
Cc: David Ahern
Cc: Jiri Pirko
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc: Steven Rostedt
Link:
http://lkml.kernel.org/r/1468685480-18951-3-git-send-email-jo...@kernel.org
Signed-o
Hi Rafael,
> -Original Message-
> From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
> Sent: Tuesday, July 19, 2016 6:02 AM
> To: Chen, Yu C
> Cc: John Stultz; Thomas Gleixner; linux-kernel@vger.kernel.org; Linux PM list
> Subject: Re: [PATCH] timekeeping: Fix memory overwrite of sleep_ti
available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
tags/perf-core-for-mingo-20160718
for you to fetch changes up to 988dd774dcbd9151c2a643fc7284c5c3c4d0adb7:
perf tests: Add is_printable_array test (2016-
From: Mark Rutland
In some cases it's necessry to figure out the map-local index of a given
Linux logical CPU ID. Add a new helper, cpu_map__idx, to acquire this.
As the logic is largely the same as the existing cpu_map__has, this is
rewritten in terms of the new helper.
At the same time, add th
From: Mark Rutland
In create_perf_stat_counter, when a target CPU has not been provided, we
call __perf_evsel__open with empty_cpu_map, and open a single FD per
thread. However, in read_counter we assume that we opened events for the
product of threads and CPUs described in the evsel's cpu_map.
From: Arnaldo Carvalho de Melo
We were also using this directly from the kernel sources, the two last
cases, fix it.
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Wang Nan
Link: http://lkml.kernel.org/n/tip-7o14xvacqcjc5llc7gvjj...@git.kernel.org
Signed-off-by: Arnald
From: Jiri Olsa
Jirka reported that python code returns all arrays as strings. This
makes impossible to get all items for byte array tracepoint field
containing 0x00 value item.
Fixing this by scanning full length of the array and returning it as
PyByteArray object in case non printable byte is
From: Masami Hiramatsu
Warn unmatched function filter correctly instead of warning
"symbol-loading error", since that can be a filter issue.
>From the technical point of view, this adds a filter chech in map__load
and if there is a filter, it returns -2 (filter-out), instead of -1
(error), and p
Hello, Waiman.
On Fri, Jul 15, 2016 at 01:39:40PM -0400, Waiman Long wrote:
> Suggested-by: Tejun Heo
Not sure I should be on suggested-by given that this wasn't my idea at
all.
> +/*
> + * include/linux/dlock-list.h
> + *
> + * A distributed (per-cpu) set of lists each of which is protected by
From: Arnaldo Carvalho de Melo
Not used anymore. This also stops include linux/swab.h directly
from the kernel sources, remove that reference from the MANIFEST.
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Wang Nan
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/
From: Arnaldo Carvalho de Melo
copy some more kernel files accessed from tools/, check for drift.
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Wang Nan
Link: http://lkml.kernel.org/n/tip-omz8xdyvvxgjiuqzwj6ec...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
The mm-of-the-moment snapshot 2016-07-18-16-40 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
On Sat, Jul 16, 2016 at 01:50:17PM +0530, Bhaktipriya Shridhar wrote:
> swap_queue was created to handle shrinking in low memory situations.
> A separate workqueue was used in order to avoid other workqueue tasks
> from being blocked since work items on swap_queue spend a lot of time
> waiting for
Em Tue, Jul 19, 2016 at 08:22:35AM +1000, Stephen Rothwell escreveu:
> Hi Arnaldo,
>
> On Mon, 18 Jul 2016 17:36:34 -0300 Arnaldo Carvalho de Melo
> wrote:
> >
> > Em Mon, Jul 18, 2016 at 01:04:34PM -0700, Andy Lutomirski escreveu:
> > > On Sun, Jul 17, 2016 at 10:18 PM, Stephen Rothwell
> > >
On Sat, Jul 16, 2016 at 02:00:25PM +0530, Bhaktipriya Shridhar wrote:
> alloc_workqueue replaces deprecated create_singlethread_workqueue().
>
> The MFC device driver is a v4l2 driver which can encode/decode video
> raw/elementary streams and has support for all popular video codecs.
>
> The driv
weiyj...@163.com writes:
> From: Wei Yongjun
>
> Use kmemdup rather than duplicating its implementation.
>
> Generated by: scripts/coccinelle/api/memdup.cocci
>
> Signed-off-by: Wei Yongjun
Hi Wei!
This code has been removed by other changes in modules-next,
so your very nice cleanup is
Hi all-
There are four core patches needed for the THREAD_INFO_IN_TASK thing,
and they apply cleanly to -mm now. The x86 patch to flip the feature
on does not apply cleanly anywhere because it depends on changes in
-tip *and* in -mm. I'd like to get all of this as well as the rest of
the vmap-st
On Sat, Jul 16, 2016 at 02:00:25PM +0530, Bhaktipriya Shridhar wrote:
> alloc_workqueue replaces deprecated create_singlethread_workqueue().
>
> The MFC device driver is a v4l2 driver which can encode/decode video
> raw/elementary streams and has support for all popular video codecs.
>
> The driv
On Sat, Jul 16, 2016 at 02:02:34PM +0530, Bhaktipriya Shridhar wrote:
> The workqueue "workqueue" is involved in polling the pvrusb2 hardware
> (pvr2_hdw).
>
> It has a single work item(&hdw->workpoll) and hence doesn't require
> ordering. Also, it is not being used on a memory reclaim path.
> Hen
601 - 700 of 862 matches
Mail list logo
