Re: [PATCH net-next 2/4] net: dsa: remove phy arg from port enable/disable

> Historical reasons mostly. Considering the complexity of > dsa_slave_phy_setup(), I would certainly be extremely careful in > changing any of this, the potential for breakage is pretty big. Yes, i took a look at this, wondering how to convert to phylink. I went away and got a stiff drink :-)

[PATCH net-next v2 2/3] net: dsa: make slave close symmetrical to open

The DSA slave open function configures the unicast MAC addresses on the master device, enable the switch port, change its STP state, then start the PHY device. Make the close function symmetric, by first stopping the PHY device, then changing the STP state, disabling the switch port and restore

[PATCH v3 08/33] tracing: Add hist trigger timestamp support

Add support for a timestamp event field. This is actually a 'pseudo-' event field in that it behaves like it's part of the event record, but is really part of the corresponding ring buffer event. To make use of the timestamp field, users can specify "$common_timestamp" as a field name for any

[PATCH v3 09/33] tracing: Add per-element variable support to tracing_map

In order to allow information to be passed between trace events, add support for per-element variables to tracing_map. This provides a means for histograms to associate a value or values with an entry when it's saved or updated, and retrieved by a subsequent event occurrences. Variables can be

[PATCH v3 04/33] ring-buffer: Redefine the unimplemented RINGBUF_TIME_TIME_STAMP

RINGBUF_TYPE_TIME_STAMP is defined but not used, and from what I can gather was reserved for something like an absolute timestamp feature for the ring buffer, if not a complete replacement of the current time_delta scheme. This code redefines RINGBUF_TYPE_TIME_STAMP to implement absolute time

[PATCH v3 05/33] tracing: Give event triggers access to ring_buffer_event

The ring_buffer event can provide a timestamp that may be useful to various triggers - pass it into the handlers for that purpose. Signed-off-by: Tom Zanussi --- include/linux/trace_events.h| 14 ++- kernel/trace/trace.h| 9 +++

[PATCH v3 03/33] ring-buffer: Add interface for setting absolute time stamps

Define a new function, tracing_set_time_stamp_abs(), which can be used to enable or disable the use of absolute timestamps rather than time deltas for a trace array. This resets the buffer to prevent a mix of time deltas and absolute timestamps. Only the interface is added here; a subsequent

[PATCH v3 06/33] tracing: Add ring buffer event param to hist field functions

Some events such as timestamps require access to a ring_buffer_event struct; add a param so that hist field functions can access that. Signed-off-by: Tom Zanussi --- kernel/trace/trace_events_hist.c | 39 --- 1 file changed, 24

[PATCH v3 07/33] tracing: Break out hist trigger assignment parsing

This will make it easier to add variables, and makes the parsing code cleaner regardless. Signed-off-by: Tom Zanussi Signed-off-by: Rajvi Jingar --- kernel/trace/trace_events_hist.c | 72 1 file

Re: [PATCH] mm/device-public-memory: Enable move_pages() to stat device memory

On Fri, Sep 22, 2017 at 08:13:56PM +, Reza Arbab wrote: The move_pages() syscall can be used to find the numa node where a page currently resides. This is not working for device public memory pages, which erroneously report -EFAULT (unmapped or zero page). Argh. Please disregard this

Re: [PATCH] lib/lz4: make arrays static const, reduces object code size

On Fri, Sep 22, 2017 at 9:17 PM, Arnd Bergmann wrote: > On Fri, Sep 22, 2017 at 7:21 PM, Joe Perches wrote: >> On Fri, 2017-09-22 at 09:48 +0200, Arnd Bergmann wrote: >>> On Fri, Sep 22, 2017 at 1:11 AM, Colin Ian King > >>>textdata bss dec

Re: Contribution to Linux Kernel.

Hi Jon, Thank you very much for your suggestion. Best Regards, Javi El 22/09/17 a las 16:15, Jonathan Corbet escribió: On Thu, 21 Sep 2017 18:16:12 -0300 Javier Romero wrote: My name is Javier, live in Argentina, and work as a Linux Server admin in

[PATCH net-next] hv_netvsc: Fix the real number of queues of non-vRSS cases

From: Haiyang Zhang For older hosts without multi-channel (vRSS) support, and some error cases, we still need to set the real number of queues to one. This patch adds this missing setting. Fixes: 8195b1396ec8 ("hv_netvsc: fix deadlock on hotplug") Signed-off-by: Haiyang

Re: [PATCH 3/4] extable: Enable RCU if it is not watching in kernel_text_address()

On Fri, Sep 22, 2017 at 06:15:46PM -0400, Steven Rostedt wrote: > From: "Steven Rostedt (VMware)" > > If kernel_text_address() is called when RCU is not watching, it can cause an > RCU bug because is_module_text_address() and the is_kprobe_*insn_slot() > functions require

Re: [PATCH 1/7] drm/rockchip/dsi: correct Feedback divider setting

Hi Nickey, El Mon, Sep 18, 2017 at 05:05:33PM +0800 Nickey Yang ha dit: > This patch correct Feedback divider setting: > 1、Set Feedback divider [8:5] when HIGH_PROGRAM_EN > 2、Due to the use of a "by 2 pre-scaler," the range of the > feedback multiplication Feedback divider is limited to even >

[GIT PULL] ACPI fixes for v4.14-rc2

Hi Linus, Please pull from the tag git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ acpi-4.14-rc2 with top-most commit 672d0e4502a22364b298f9307f651c1b8313514b Merge branches 'acpi-pmic', 'acpi-bus', 'acpi-wdat' and 'acpi-properties' on top of commit

Re: [PATCH v2 1/6] gpu: host1x: Enable Tegra186 syncpoint protection

On 22.09.2017 17:02, Mikko Perttunen wrote: > On 09/05/2017 04:33 PM, Dmitry Osipenko wrote: >> On 05.09.2017 11:10, Mikko Perttunen wrote: >>> ... >> diff --git a/drivers/gpu/host1x/hw/channel_hw.c > b/drivers/gpu/host1x/hw/channel_hw.c >>> index 8447a56c41ca..0161da331702 100644 >>> ---

Re: [PATCH] lib/lz4: make arrays static const, reduces object code size

On Fri, Sep 22, 2017 at 7:21 PM, Joe Perches wrote: > On Fri, 2017-09-22 at 09:48 +0200, Arnd Bergmann wrote: >> On Fri, Sep 22, 2017 at 1:11 AM, Colin Ian King >>textdata bss dec hex filename >> 18220 176 0 1839647dc >>

Re: [PATCH] lib/lz4: make arrays static const, reduces object code size

On Fri, Sep 22, 2017 at 9:17 PM, Arnd Bergmann wrote: > afterbefore > gcc-3.4.6 10855 12977 > gcc-4.0.4 11088 11088 > gcc-4.1.3 10973 10973 > gcc-4.2.5 11183 11183 > gcc-4.3.6 15501 17724 > gcc-4.4.7 13337 15693 > gcc-4.5.4 13162 15491 > gcc-4.6.4 14846 17302 >

[PATCH] staging: rtl8192u: Check some memory allocation failure

If one of these memory allocations fail, a NULL pointer dereference will occur later on. Return -ENOMEM instead. There is no need to free the resources already allocated, this is done by the caller (i.e. 'rtl8192_usb_probe()') which calls 'rtl8192_usb_deleteendpoints()'. The calling graph is:

[PATCH v3 18/33] tracing: Add hist_field 'type' field

Future support for synthetic events requires hist_field 'type' information, so add a field for that. Also, make other hist_field attribute usage consistent (size, is_signed, etc). Signed-off-by: Tom Zanussi --- kernel/trace/trace_events_hist.c | 33

[PATCH v3 17/33] tracing: Pass tracing_map_elt to hist_field accessor functions

Some accessor functions, such as for variable references, require access to a corrsponding tracing_map_elt. Add a tracing_map_elt param to the function signature and update the accessor functions accordingly. Signed-off-by: Tom Zanussi ---

Re: [PATCH net-next v2 1/3] net: dsa: use slave device phydev

On Fri, Sep 22, 2017 at 03:40:43PM -0400, Vivien Didelot wrote: > There is no need to store a phy_device in dsa_slave_priv since > net_device already provides one. Simply s/p->phy/dev->phydev/. > > While at it, return -ENODEV when it is NULL instead of -EOPNOTSUPP. I just did a quick poll for

[PATCH v3 19/33] tracing: Add variable reference handling to hist triggers

Add the necessary infrastructure to allow the variables defined on one event to be referenced in another. This allows variables set by a previous event to be referenced and used in expressions combining the variable values saved by that previous event and the event fields of the current event.

[PATCH v3 10/33] tracing: Add hist_data member to hist_field

Allow hist_data access via hist_field. Some users of hist_fields require or will require more access to the associated hist_data. Signed-off-by: Tom Zanussi --- kernel/trace/trace_events_hist.c | 14 +- 1 file changed, 9 insertions(+), 5 deletions(-)

[PATCH v3 12/33] tracing: Add variable support to hist triggers

Add support for saving the value of a current event's event field by assigning it to a variable that can be read by a subsequent event. The basic syntax for saving a variable is to simply prefix a unique variable name not corresponding to any keyword along with an '=' sign to any event field.

[PATCH v3 11/33] tracing: Add usecs modifier for hist trigger timestamps

Appending .usecs onto a common_timestamp field will cause the timestamp value to be in microseconds instead of the default nanoseconds. A typical latency histogram using usecs would look like this: # echo 'hist:keys=pid,prio:ts0=$common_timestamp.usecs ... # echo

[PATCH v3 15/33] tracing: Add simple expression support to hist triggers

Add support for simple addition, subtraction, and unary expressions (-(expr) and expr, where expr = b-a, a+b, a+b+c) to hist triggers, in order to support a minimal set of useful inter-event calculations. These operations are needed for calculating latencies between events (timestamp1-timestamp0)

[PATCH v3 14/33] tracing: Move get_hist_field_flags()

Move get_hist_field_flags() to make it more easily accessible for new code (and keep the move separate from new functionality). Signed-off-by: Tom Zanussi --- kernel/trace/trace_events_hist.c | 44 1 file changed, 22

[PATCH v3 13/33] tracing: Account for variables in named trigger compatibility

Named triggers must also have the same set of variables in order to be considered compatible - update the trigger match test to account for that. The reason for this requirement is that named triggers with variables are meant to allow one or more events to set the same variable. Signed-off-by:

Re: [PATCH] mm/device-public-memory: Enable move_pages() to stat device memory

On Fri, Sep 22, 2017 at 08:31:57PM +, Reza Arbab wrote: On Fri, Sep 22, 2017 at 08:13:56PM +, Reza Arbab wrote: The move_pages() syscall can be used to find the numa node where a page currently resides. This is not working for device public memory pages, which erroneously report -EFAULT

[PATCH v4 4/9] em28xx: fix em28xx_dvb_init for KASAN

With CONFIG_KASAN, the init function uses a large amount of kernel stack: drivers/media/usb/em28xx/em28xx-dvb.c: In function 'em28xx_dvb_init.part.4': drivers/media/usb/em28xx/em28xx-dvb.c:2061:1: error: the frame size of 3232 bytes is larger than 2048 bytes [-Werror=frame-larger-than=] It

[PATCH v4 7/9] rocker: fix rocker_tlv_put_* functions for KASAN

Inlining these functions creates lots of stack variables that each take 64 bytes when KASAN is enabled, leading to this warning about potential stack overflow: drivers/net/ethernet/rocker/rocker_ofdpa.c: In function 'ofdpa_cmd_flow_tbl_add': drivers/net/ethernet/rocker/rocker_ofdpa.c:621:1:

[PATCH v4 6/9] dvb-frontends: fix i2c access helpers for KASAN

A typical code fragment was copied across many dvb-frontend drivers and causes large stack frames when built with with CONFIG_KASAN on gcc-5/6/7: drivers/media/dvb-frontends/cxd2841er.c:3225:1: error: the frame size of 3992 bytes is larger than 3072 bytes [-Werror=frame-larger-than=]

Build failure of kernel v4.14-rc due to error in tools/perf

Hi, The build of kernel v4.14-rc1 for i686 fails on RHEL 6 with the error in tools/perf: util/syscalltbl.c:157: error: expected ';', ',' or ')' before '__maybe_unused' mv: cannot stat `util/.syscalltbl.o.tmp': No such file or directory This is fixed by placing/moving #include outside of

[PATCH 0/4] rcu/tracing/extable: Fix stack dump when RCU is not watching

I'm currently running this through my test suite, but wanted to get review or acks, so that I can send this right off to Linus before rc2. I need these to base my new work on. Basically if a stack trace happens (say from a WARN()) when RCU is not watching (like going to or coming from idle, or

Re: [Part2 PATCH v4 29/29] KVM: X86: Add CONFIG_KVM_AMD_SEV

Hi Brijesh, [auto build test ERROR on kvm/linux-next] [also build test ERROR on v4.14-rc1 next-20170922] [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/Brijesh-Singh/x86-Secure-Encrypted

[PATCH 4/4] tracing: Remove RCU work arounds from stack tracer

From: "Steven Rostedt (VMware)" While debugging some RCU issues with the stack tracer, it was discovered that the problem was much more than with the stack tracer itself, but with the saving of the stack trace, which could happen from any WARN() as well. The problem was

[GIT PULL] Power management fixes for v4.14-rc2

Hi Linus, Please pull from the tag git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ pm-4.14-rc2 with top-most commit d84c97f8f77bc4124256e76864f125f45ad53744 Merge branches 'pm-cpufreq' and 'pm-cpuidle' on top of commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e Linux

Re: [PATCH] mm: madvise: add description for MADV_WIPEONFORK and MADV_KEEPONFORK

On Sat, 2017-09-23 at 05:55 +0800, Yang Shi wrote: > mm/madvise.c has the brief description about all MADV_ flags, added > the > description for the newly added MADV_WIPEONFORK and MADV_KEEPONFORK. > > Although man page has the similar information, but it'd better to > keep the > consistency with

[PATCH] r8152: add Linksys USB3GIGV1 id

This Linksys dongle by default comes up in cdc_ether mode. This patch allows r8152 to claim the device: Bus 002 Device 002: ID 13b1:0041 Linksys Signed-off-by: Grant Grundler --- drivers/net/usb/r8152.c | 2 ++ 1 file changed, 2 insertions(+) This was tested on

[PATCH 1/2] tools: slabinfo: add "-U" option to show unreclaimable slabs only

Add "-U" option to show unreclaimable slabs only. "-U" and "-S" together can tell us what unreclaimable slabs use the most memory to help debug huge unreclaimable slabs issue. Signed-off-by: Yang Shi Acked-by: Christoph Lameter Acked-by: David Rientjes

[PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

Kernel may panic when oom happens without killable process sometimes it is caused by huge unreclaimable slabs used by kernel. Although kdump could help debug such problem, however, kdump is not available on all architectures and it might be malfunction sometime. And, since kernel already panic it

[PATCH 0/2 v6] oom: capture unreclaimable slab info in oom message when kernel panic

Recently we ran into a oom issue, kernel panic due to no killable process. The dmesg shows huge unreclaimable slabs used almost 100% memory, but kdump doesn't capture vmcore due to some reason. So, it may sound better to capture unreclaimable slab info in oom message when kernel panic to aid

Re: [PATCH] auxdisplay: fix broken menus

On 09/22/17 12:46, Geert Uytterhoeven wrote: > Hi Randy, > > On Fri, Sep 22, 2017 at 8:23 PM, Randy Dunlap wrote: >> On 09/22/17 11:15, Geert Uytterhoeven wrote: >>> On Fri, Sep 22, 2017 at 6:24 PM, Randy Dunlap wrote: From: Randy Dunlap

[PATCH v3 16/33] tracing: Generalize per-element hist trigger data

Up until now, hist triggers only needed per-element support for saving 'comm' data, which was saved directly as a private data pointer. In anticipation of the need to save other data besides 'comm', add a new hist_elt_data struct for the purpose, and switch the current 'comm'-related code over to

Re: [PATCH net-next 2/2] net: dsa: lan9303: Add basic offloading of unicast traffic

> >I'm wondering how this is supposed to work. Please add a good comment > >here, since the hardware is forcing you to do something odd. > > > >Maybe it would be a good idea to save the STP state in chip. And then > >when chip->is_bridged is set true, change the state in the hardware to > >the

[PATCH v6 1/2] iio: dac: ds4422/ds4424 dac driver

This patch provides an iio device driver for DS4422/DS4424 chips that support two/four channel 7-bit Sink/Source Current DAC. Signed-off-by: Ismail H. Kose Signed-off-by: Ismail H. Kose --- v6: * Removed reference resistor parsing v5:

[PATCH v6 2/2] iio:dac: Add DT binding documentation for ds4424

Signed-off-by: Ismail H. Kose Signed-off-by: Ismail H. Kose --- v6: * Removed reference resistors property * Fixed regulator property v3: * Removed iio-map v2: * Removed min/max rfs, ifs-scale, etc values

[PATCH] auxdisplay: change PANEL to menuconfig

From: Randy Dunlap This change makes xconfig present the PANEL drivers immediately following the AUXDISPLAY drivers instead of under the major menu item "Device Drivers". It also unclutters the Device Drivers menu in nconfig and menuconfig by moving the PANEL drivers to a

Re: [v8 0/4] cgroup-aware OOM killer

On Fri, 22 Sep 2017, Tejun Heo wrote: > > It doesn't have anything to do with my particular usecase, but rather the > > ability of userspace to influence the decisions of the kernel. Previous > > to this patchset, when selection is done based on process size, userspace > > has full control

Re: [PATCH v2 3/4] fw_cfg: write vmcoreinfo details

Hi Marc-André, [auto build test ERROR on linus/master] [also build test ERROR on v4.14-rc1 next-20170922] [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/marcandre-lureau-redhat-com/fw_cfg-add

Re: [PATCH] auxdisplay: fix broken menus

On 09/22/17 13:17, Geert Uytterhoeven wrote: > Hi Randy, > > On Fri, Sep 22, 2017 at 10:08 PM, Randy Dunlap wrote: >> On 09/22/17 12:46, Geert Uytterhoeven wrote: >>> On Fri, Sep 22, 2017 at 8:23 PM, Randy Dunlap wrote: On 09/22/17 11:15, Geert

Re: Memory-ordering recipes

On Fri, Sep 22, 2017 at 11:29:18AM +0200, Peter Zijlstra wrote: > On Thu, Sep 21, 2017 at 09:40:46AM -0700, Paul E. McKenney wrote: > > > Also, none of these cover 'simple' stuff like a ring-buffer. > > > > Control dependencies are now 'simple'? ;-) > > They're not particularly harder than any

[PATCH v3 6/6] drivers: fsi: occ: Add in-kernel API

From: "Edward A. James" Add an in-kernel read/write API with exported functions. This is necessary for other drivers which want to directly interact with the OCC. Also add a child platform device node for the associated hwmon device. Signed-off-by: Edward A. James

[PATCH v3 2/6] drivers: fsi: Add SBEFIFO FSI client device driver

From: "Edward A. James" IBM POWER9 processors contain some embedded hardware and software bits collectively referred to as the self boot engine (SBE). One role of the SBE is to act as a proxy that provides access to the registers of the POWER chip from other (embedded)

[PATCH v3 5/6] drivers: fsi: Add On-Chip Controller (OCC) driver

From: "Edward A. James" The OCC is a device embedded on a POWER processor that collects and aggregates sensor data from the processor and system. The OCC can provide the raw sensor data as well as perform thermal and power management on the system. This driver provides an

[PATCH v3 0/6] drivers: fsi: Add SBEFIFO and OCC drivers

From: "Edward A. James" This series adds two FSI-based device drivers. The OCC driver is dependent on the SBEFIFO driver, as a user of it's in-kernel API. The in-kernel API provided by the OCC driver will be used by a hwmon driver (on the lkml as "Add On-Chip Controller (OCC)

[PATCH v3 1/6] dt-bindings: fsi: Add SBEFIFO documentation

From: "Edward A. James" Document the bindings for the SBE CFAM device. SBE devices are located on a CFAM off an FSI bus. Signed-off-by: Edward A. James --- .../devicetree/bindings/fsi/ibm,p9-sbefifo.txt | 20 1 file changed,

Re: [PATCH] lib/lz4: make arrays static const, reduces object code size

On 22/09/17 22:39, Arnd Bergmann wrote: > On Fri, Sep 22, 2017 at 9:17 PM, Arnd Bergmann wrote: >> On Fri, Sep 22, 2017 at 7:21 PM, Joe Perches wrote: >>> On Fri, 2017-09-22 at 09:48 +0200, Arnd Bergmann wrote: On Fri, Sep 22, 2017 at 1:11 AM, Colin Ian King

Re: [PATCH] ARM: unaligned.h: Use an arch-specific version

On Fri, Sep 22, 2017 at 11:36 PM, Ard Biesheuvel wrote: > On 20 September 2017 at 13:35, Arnd Bergmann wrote: >> The architectures that do use include/asm-generic/unaligned.h and >> also set HAVE_EFFICIENT_UNALIGNED_ACCESS in some configurations >> are

Re: [PATCH v4 09/13] xen/pvcalls: implement sendmsg

> +static bool pvcalls_front_write_todo(struct sock_mapping *map) > +{ > + struct pvcalls_data_intf *intf = map->active.ring; > + RING_IDX cons, prod, size = XEN_FLEX_RING_SIZE(PVCALLS_RING_ORDER); > + int32_t error; > + > + cons = intf->out_cons; > + prod = intf->out_prod; >

Re: [PATCH v3] drivers:platform/x86:Use ARRAY_SIZE() for the size calculation of the array.

On Wed, Sep 13, 2017 at 04:29:31PM +0530, Allen Pais wrote: > Use ARRAY_SIZE() macro instead of TELEM_EVT_LEN(). > > v3: Replace TELEM_EVT_LEN() with ARRAY_SIZE(). > > Signed-off-by: Allen Pais Thanks Allen, queued for testing with minor changelog changes. > --- Note:

Re: [PATCH v4 10/13] xen/pvcalls: implement recvmsg

> > +static bool pvcalls_front_read_todo(struct sock_mapping *map) > +{ > + struct pvcalls_data_intf *intf = map->active.ring; > + RING_IDX cons, prod; > + int32_t error; > + > + cons = intf->in_cons; > + prod = intf->in_prod; > + error = intf->in_error; > + return

[PATCH 1/4] MAINTAINERS: add entry for NXP TDA1997x driver

Signed-off-by: Tim Harvey --- MAINTAINERS | 8 1 file changed, 8 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 2093060..de7124e 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -13019,6 +13019,14 @@ T: git git://linuxtv.org/mkrufky/tuners.git S:

[PATCH 3/4] media: i2c: Add TDA1997x HDMI receiver driver

Add support for the TDA1997x HDMI receivers. Signed-off-by: Tim Harvey --- drivers/media/i2c/Kconfig|9 + drivers/media/i2c/Makefile |1 + drivers/media/i2c/tda1997x.c | 3065 ++

[PATCH 2/4] media: dt-bindings: Add bindings for TDA1997X

Signed-off-by: Tim Harvey --- .../devicetree/bindings/media/i2c/tda1997x.txt | 159 + 1 file changed, 159 insertions(+) create mode 100644 Documentation/devicetree/bindings/media/i2c/tda1997x.txt diff --git

[PATCH 0/4] RFC: TDA1997x HDMI video receiver

This is an RFC for a driver supporting the TDA1997x HDMI video receiver. I've tested this on a Gateworks GW54xx with an IMX6Q which uses the TDA19971 with 16bits connected to the IMX6 CSI. For this configuration I've tested both 16bit YUV422 and 8bit BT656 mode. While the driver should support

[PATCH 4/4] ARM: DTS: imx: ventana: add TDA19971 HDMI Receiver to GW54xx

The GW54xx has a front-panel microHDMI connector routed to a TDA19971 which is connected the the IPU CSI when using IMX6Q. Signed-off-by: Tim Harvey --- arch/arm/boot/dts/imx6q-gw54xx.dts | 85 ++ 1 file changed, 85 insertions(+) diff

[PATCH v3 30/33] tracing: Make tracing_set_clock() non-static

Allow tracing code outside of trace.c to access tracing_set_clock(). Some applications may require a particular clock in order to function properly, such as latency calculations. Also, add an accessor returning the current clock string. Signed-off-by: Tom Zanussi

[PATCH RFC tip/core/rcu] Make rcu_irq_{enter,exit} check for NMI

Hello, Steve, Yet another attempt to allow safe initiation of RCU voyeurism... Untested at the moment. Thanx, Paul diff --git a/kernel/rcu/tree.c

[PATCH] mm/device-public-memory: Enable move_pages() to stat device memory

The move_pages() syscall can be used to find the numa node where a page currently resides. This is not working for device public memory pages, which erroneously report -EFAULT (unmapped or zero page). Enable by adding a FOLL_DEVICE flag for follow_page(), which move_pages() will use. This could

Re: [PATCH] lib: zstd: make const array rtbTable static, reduces object code size

On 22/09/17 20:14, Nick Terrell wrote: > On 9/22/17, 8:00 AM, "linux-kernel-ow...@vger.kernel.org on behalf of Colin > King" colin.k...@canonical.com> wrote: >> From: Colin Ian King >> >> Don't populate const array

Re: [PATCH v2 07/10] dmaengine: sun6i: Retrieve channel count/max request from devicetree

On Tue, Sep 19, 2017 at 04:17:59PM +, Brüns, Stefan wrote: > On Dienstag, 19. September 2017 16:25:08 CEST Maxime Ripard wrote: > > On Mon, Sep 18, 2017 at 02:09:43PM +, Brüns, Stefan wrote: > > > On Montag, 18. September 2017 10:18:24 CEST you wrote: > > > > Hi, > > > > > > > > On Sun,

Hello Dear

Good day I am Peter Cheng, from United States. I browsed through the internet and came across your mail. I would like us to be friends. Do you mind being my friend? Regards, Peter Cheng.

[PATCH 1/5] Squashfs: remove the FILE_CACHE option

From: Adrien Schildknecht FILE_DIRECT is working fine and offers faster results and lower memory footprint. Removing FILE_CACHE makes our life easier because we don't have to maintain 2 differents function that does the same thing. Signed-off-by: Adrien Schildknecht

[PATCH] mm: madvise: add description for MADV_WIPEONFORK and MADV_KEEPONFORK

mm/madvise.c has the brief description about all MADV_ flags, added the description for the newly added MADV_WIPEONFORK and MADV_KEEPONFORK. Although man page has the similar information, but it'd better to keep the consistency with other flags. Signed-off-by: Yang Shi

Re: [PATCH v4 11/13] xen/pvcalls: implement poll command

> > +static unsigned int pvcalls_front_poll_passive(struct file *file, > +struct pvcalls_bedata *bedata, > +struct sock_mapping *map, > +poll_table *wait) > +{ > +

Re: [PATCH] PM: Document rules on using pm_runtime_resume() in system suspend callbacks

On Friday, September 22, 2017 9:22:47 AM CEST Ulf Hansson wrote: > [...] > > >>> Second, leaving devices in runtime suspend in the "suspend" phase of > >>> system > >>> suspend is fishy even when their runtime PM is disabled, because that > >>> doesn't > >>> guarantee anything regarding their

Re: [PATCH v4 12/13] xen/pvcalls: implement release command

>> + */ >> +map->active.ring->in_error = -EBADF; >> +wake_up_interruptible(>active.inflight_conn_req); >> + >> +/* >> + * Wait until there are no more waiters on the mutexes. >> + * We know that no new waiters can be added

Re: Contribution to Linux Kernel.

On Thu, 21 Sep 2017 18:16:12 -0300 Javier Romero wrote: > My name is Javier, live in Argentina, and work as a Linux Server admin > in the Network Operations Center of an ISP. > > Would like to know, how can I start contributing to the Linux kernel. A good

[PATCH v3 22/33] tracing: Add support for 'field variables'

Users should be able to directly specify event fields in hist trigger 'actions' rather than being forced to explicitly create a variable for that purpose. Add support allowing fields to be used directly in actions, which essentially does just that - creates 'invisible' variables for each bare

[PATCH v3 21/33] tracing: Add support for 'synthetic' events

Synthetic events are user-defined events generated from hist trigger variables saved from one or more other events. To define a synthetic event, the user writes a simple specification consisting of the name of the new event along with one or more variables and their type(s), to the

[PATCH v3 24/33] tracing: Add 'onmax' hist trigger action support

Add an 'onmax(var).save(field,...)' hist trigger action which is invoked whenever an event exceeds the current maximum. The end result is that the trace event fields or variables specified as the onmax.save() params will be saved if 'var' exceeds the current maximum for that hist trigger entry.

[PATCH v3 25/33] tracing: Allow whitespace to surround hist trigger filter

The existing code only allows for one space before and after the 'if' specifying the filter for a hist trigger. Add code to make that more permissive as far as whitespace goes. Specifically, we want to allow spaces in the trigger itself now that we have additional syntax (onmatch/onmax) where

[PATCH v3 23/33] tracing: Add 'onmatch' hist trigger action support

Add an 'onmatch(matching.event).(param list)' hist trigger action which is invoked with the set of variables or event fields named in the 'param list'. The result is the generation of a synthetic event that consists of the values contained in those variables and/or fields at the time the invoking

[PATCH v3 26/33] tracing: Add cpu field for hist triggers

A common key to use in a histogram is the cpuid - add a new cpu 'synthetic' field for that purpose. This field is named cpu rather than $cpu or $common_cpu because 'cpu' already exists as a special filter field and it makes more sense to match that rather than add another name for the same thing.

[PATCH v3 20/33] tracing: Add hist trigger action hook

Add a hook for executing extra actions whenever a histogram entry is added or updated. The default 'action' when a hist entry is added to a histogram is to update the set of values associated with it. Some applications may want to perform additional actions at that point, such as generate

[PATCH v3 01/33] tracing: Add support to detect and avoid duplicates

From: Vedang Patel A duplicate in the tracing_map hash table is when 2 different entries have the same key and, as a result, the key_hash. This is possible due to a race condition in the algorithm. This race condition is inherent to the algorithm and not a bug. This was

[PATCH v3 4/6] dt-bindings: fsi: Add OCC documentation

From: "Edward A. James" Document the bindings for the P9 OCC device. OCC devices are accessed through the SBEFIFO. Signed-off-by: Edward A. James --- Documentation/devicetree/bindings/fsi/ibm,p9-occ.txt | 15 +++ 1 file changed, 15

[PATCH v3 3/6] drivers: fsi: sbefifo: Add in-kernel API

From: "Edward A. James" Refactor the user interface of the SBEFIFO driver to allow for an in-kernel read/write API. Add exported functions for other drivers to call, and add an include file with those functions. Also parse the device tree for child nodes and create child

[PATCH v4 8/9] netlink: fix nla_put_{u8,u16,u32} for KASAN

When CONFIG_KASAN is enabled, the "--param asan-stack=1" causes rather large stack frames in some functions. This goes unnoticed normally because CONFIG_FRAME_WARN is disabled with CONFIG_KASAN by default as of commit 3f181b4d8652 ("lib/Kconfig.debug: disable -Wframe-larger-than warnings with

[PATCH v4 9/9] kasan: rework Kconfig settings

We get a lot of very large stack frames using gcc-7.0.1 with the default -fsanitize-address-use-after-scope --param asan-stack=1 options, which can easily cause an overflow of the kernel stack, e.g. drivers/gpu/drm/i915/gvt/handlers.c:2407:1: error: the frame size of 31216 bytes is larger than

[GIT PULL] arch/tile bugfixes for 4.14-rc2

Linus, Please pull the following two changes for 4.14-rc2 from: git://git.kernel.org/pub/scm/linux/kernel/git/cmetcalf/linux-tile.git master These are a code cleanup and config cleanup, respectively. Dan Carpenter (1): tile: array underflow in setup_maxnodemem() Krzysztof Kozlowski

[PATCH v3 29/33] tracing: Add inter-event hist trigger Documentation

Add background and details on inter-event hist triggers, including hist variables, synthetic events, and actions. Signed-off-by: Tom Zanussi Signed-off-by: Baohong Liu --- Documentation/trace/events.txt | 385

[PATCH v3 31/33] tracing: Add a clock attribute for hist triggers

The default clock if timestamps are used in a histogram is "global". If timestamps aren't used, the clock is irrelevant. Use the "clock=" param only if you want to override the default "global" clock for a histogram with timestamps. Signed-off-by: Tom Zanussi

[PATCH v3 28/33] tracing: Add 'last error' error facility for hist triggers

With the addition of variables and actions, it's become necessary to provide more detailed error information to users about syntax errors. Add a 'last error' facility accessible via the erroring event's 'hist' file. Reading the hist file after an error will display more detailed information

[PATCH v3 27/33] tracing: Add hist trigger support for variable reference aliases

Add support for alias=$somevar where alias can be used as onmatch($alias). Aliases are a way of creating a new name for an existing variable, for flexibly in making naming more clear in certain cases. For example in the below the user perhaps feels that using $new_lat in the synthetic event

[PATCH v3 32/33] tracing: Increase trace_recursive_lock() limit for synthetic events

Synthetic event generation needs to happen while the current event is still in progress, so add 1 to the trace_recursive_lock() recursion limit to account for that. Because we also want to allow for the possibility of a synthetic event being generated from another synthetic event, add an

[PATCH v3 33/33] tracing: Add inter-event blurb to HIST_TRIGGERS config option

So that users know that inter-event tracing is supported as part of the HIST_TRIGGERS option, include text to that effect in the help text. Signed-off-by: Tom Zanussi --- kernel/trace/Kconfig | 3 +++ 1 file changed, 3 insertions(+) diff --git

  1   2   3   4   5   6   7   8   9   10   >