[PATCH 21/25] objtool: Rewrite alt->skip_orig

Really skip the original instruction flow, instead of letting it continue with NOPs. Since the alternative code flow already continues after the original instructions, only the alt-original is skipped. Signed-off-by: Peter Zijlstra (Intel) --- tools/objtool/check.c | 16 ++-- 1 fi

[PATCH 09/25] x86/uaccess: Always inline user_access_begin()

If GCC out-of-lines it, the STAC and CLAC are in different fuctions and objtool gets upset. Signed-off-by: Peter Zijlstra (Intel) --- arch/x86/include/asm/uaccess.h |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/arch/x86/include/asm/uaccess.h +++ b/arch/x86/include/asm/uaccess.h

[PATCH 15/25] x86/uaccess,ftrace: Fix ftrace_likely_update() vs SMAP

For CONFIG_TRACE_BRANCH_PROFILING the likely/unlikely things get overloaded and generate callouts to this code, and thus also when AC=1. Make it safe. Cc: Steven Rostedt Signed-off-by: Peter Zijlstra (Intel) --- kernel/trace/trace_branch.c |4 1 file changed, 4 insertions(+) --- a/ke

[PATCH 02/25] tracing: Improve "if" macro code generation

With CONFIG_PROFILE_ALL_BRANCHES, the "if" macro converts the conditional to an array index. This can cause GCC to create horrible code. When there are nested ifs, the generated code uses register values to encode branching decisions. Make it easier for GCC to optimize by keeping the conditional

[PATCH 20/25] objtool: Add --backtrace support

For when you want to know the path that reached your fail state. $ ./objtool check --no-fp --backtrace arch/x86/lib/usercopy_64.o arch/x86/lib/usercopy_64.o: warning: objtool: .altinstr_replacement+0x3: UACCESS disable without MEMOPs: __clear_user() arch/x86/lib/usercopy_64.o: warning: objtool:

[PATCH 08/25] x86/uaccess,xen: Suppress SMAP warnings

drivers/xen/privcmd.o: warning: objtool: privcmd_ioctl()+0x1414: call to hypercall_page() with UACCESS enabled Some Xen hypercalls allow parameter buffers in user land, so they need to set AC=1. Avoid the warning for those cases. Cc: andrew.coop...@citrix.com Reviewed-by: Juergen Gross Signed-o

[PATCH 13/25] x86/uaccess,kasan: Fix KASAN vs SMAP

KASAN inserts extra code for every LOAD/STORE emitted by te compiler. Much of this code is simple and safe to run with AC=1, however the kasan_report() function, called on error, is most certainly not safe to call with AC=1. Therefore wrap kasan_report() in user_access_{save,restore}; which for x8

[PATCH 22/25] objtool: Fix sibling call detection

It turned out that we failed to detect some sibling calls; specifically those without relocation records; like: $ ./objdump-func.sh defconfig-build/mm/kasan/generic.o __asan_loadN 0840 <__asan_loadN>: 840: 48 8b 0c 24 mov(%rsp),%rcx 0004 844: 31 d2

[PATCH] regulator: core: fix error path for regulator_set_voltage_unlocked

During several error paths in the function regulator_set_voltage_unlocked() the value of 'ret' can take on negative error values. However, in calls that go through the 'goto out' statement, this return value is lost and return 0 is used instead, indicating a 'pass'. There are several cases where t

Re: [RFC][PATCH 03/16] sched: Wrap rq::lock access

The case where we try to acquire the lock on 2 runqueues belonging to 2 different cores requires the rq_lockp wrapper as well otherwise we frequently deadlock in there. This fixes the crash reported in 1552577311-8218-1-git-send-email-jdesfos...@digitalocean.com diff --git a/kernel/sched/sched.h

Re: [PATCH v3 1/6] list: Don't use WRITE_ONCE() in hlist_add_behind()

On Sun, Mar 17, 2019 at 02:22:53PM +0200, Nikos Tsironis wrote: > Commit 1c97be677f72b3 ("list: Use WRITE_ONCE() when adding to lists and > hlists") introduced the use of WRITE_ONCE() to atomically write the list > head's ->next pointer. > > hlist_add_behind() doesn't touch the hlist head's ->firs

[PATCH v1] dmaengine: idma64: Use actual device for DMA transfers

Intel IOMMU, when enabled, tries to find the domain of the device, assuming it's a PCI one, during DMA operations, such as mapping or unmapping. Since we are splitting the actual PCI device to couple of children via MFD framework (see drivers/mfd/intel-lpss.c for details), the DMA device appears to

Re: [PATCH v4 06/10] dt-bindings: sdm845-pinctrl: add wakeup interrupt parent for GPIO

Thanks for the review Rob. On Fri, Mar 15 2019 at 17:37 -0600, Rob Herring wrote: On Wed, Mar 13, 2019 at 03:18:40PM -0600, Lina Iyer wrote: SDM845 SoC has an always-on interrupt controller (PDC) with select GPIO routed to the PDC as interrupts that can be used to wake the system up from deep l

Re: [PATCH 2/2] Revert "x86/hpet: Reduce HPET counter read contention"

On 03/18/2019 04:44 AM, Zhenzhong Duan wrote: > > On 2019/3/15 22:17, Waiman Long wrote: >> On 03/15/2019 05:25 AM, Peter Zijlstra wrote: >>> On Thu, Mar 14, 2019 at 04:42:12PM +0800, Zhenzhong Duan wrote: This reverts commit f99fd22e4d4bc84880a8a3117311bbf0e3a6a9dc. It's unnecessory

Re: [PATCH V5 2/5] pwm: Add i.MX TPM PWM driver support

On Mon, Mar 18, 2019 at 11:33:33AM +, Anson Huang wrote: > Hi, Thierry > > Best Regards! > Anson Huang > > > -Original Message- > > From: Thierry Reding [mailto:thierry.red...@gmail.com] > > Sent: 2019年3月18日 18:28 > > To: Anson Huang > > Cc: robh...@kernel.org; mark.rutl...@arm.com;

Re: [PATCH v3] mfd: cros_ec: instantiate properly CrOS ISH MCU device

On Fri, Mar 01, 2019 at 01:50:54PM +0530, Rushikesh S Kadam wrote: > Integrated Sensor Hub (ISH) is also a MCU running EC > having feature bit EC_FEATURE_ISH. Instantiate it as > a special CrOS EC device with device name 'cros_ish'. FWIW, Reviewed-by: Andy Shevchenko > > Signed-off-by: Rushikes

Re: [PATCH 2/2] platform/x86: intel_pmc_core: Allow to dump debug registers on S0ix failure

On Mon, Mar 18, 2019 at 2:31 AM Somayaji, Vishwanath wrote: > > > > >-Original Message- > >From: Rajat Jain > >Sent: Thursday, March 14, 2019 3:51 AM > >To: Bhardwaj, Rajneesh ; Somayaji, Vishwanath > >; Darren Hart ; Andy > >Shevchenko ; platform-driver-...@vger.kernel.org; linux- > >ker

Re: [PATCH v7 10/15] sched/fair: uclamp: Add uclamp support to energy_compute()

On 06-Mar 17:21, Quentin Perret wrote: [...] > > Since we are at that: > > - rename schedutil_freq_util() into schedutil_cpu_util(), > >since it's not only used for frequency selection. > > - use "unsigned int" instead of "unsigned long" whenever the tracked > >utilization value is not

Re: [PATCH] perf: extend total_ref_count usage to protect perf_trace_buf access

On Mon, Mar 18, 2019 at 11:02:50AM -0400, Steven Rostedt wrote: > On Mon, 18 Mar 2019 16:17:45 +0530 > Prateek Sood wrote: > > > A potential race exists between access of perf_trace_buf[i] from > > perf_trace_buf_alloc() and perf_trace_event_unreg(). This can > > result in perf_trace_buf[i] being

[PATCH 2/2] dt-bindings: iio: add Bosch BMG160 gyroscope sensor

Define bindings for "bosch,bmg160" and "bosch,bmi055_gyro". Signed-off-by: H. Nikolaus Schaller --- .../bindings/iio/gyroscope/bmg160.txt | 20 +++ 1 file changed, 20 insertions(+) create mode 100644 Documentation/devicetree/bindings/iio/gyroscope/bmg160.txt diff --git

[PATCH 0/2] iio: gyro: bmg160 add device tree support

There is no device tree support since the of_device_id table is missing. H. Nikolaus Schaller (2): iio: gyro: bmg160: add device tree compatibility table dt-bindings: iio: add Bosch BMG160 gyroscope sensor .../bindings/iio/gyroscope/bmg160.txt | 20 +++ drivers/iio/gy

[PATCH 1/2] iio: gyro: bmg160: add device tree compatibility table

Add of_match_table. Signed-off-by: H. Nikolaus Schaller --- drivers/iio/gyro/bmg160_i2c.c | 9 + 1 file changed, 9 insertions(+) diff --git a/drivers/iio/gyro/bmg160_i2c.c b/drivers/iio/gyro/bmg160_i2c.c index 90126a5a7663..934a092134f0 100644 --- a/drivers/iio/gyro/bmg160_i2c.c +++ b/d

Re: [PATCH 2/2] platform/x86: intel_pmc_core: Allow to dump debug registers on S0ix failure

On Sat, Mar 16, 2019 at 1:43 AM Rajneesh Bhardwaj wrote: > > On Wed, Mar 13, 2019 at 03:21:24PM -0700, Rajat Jain wrote: > > Add a module parameter which when enabled, will check on resume, if the > > last S0ix attempt was successful. If not, the driver would provide > > helpful debug information

Re: [PATCH v1] lib/test_printf: Switch to bitmap_zalloc()

On Fri, Mar 08, 2019 at 10:37:29AM +0100, Petr Mladek wrote: > On Mon 2019-03-04 12:00:09, Andy Shevchenko wrote: > > Switch to bitmap_zalloc() to show clearly what we are allocating. > > Besides that it returns pointer of bitmap type instead of opaque void *. > Reviewed-by: Petr Mladek Thanks!

Re: [PATCH 1/2] platform/x86: intel_pmc_core: Convert to a platform_driver

On Sat, Mar 16, 2019 at 1:30 AM Rajneesh Bhardwaj wrote: > > On Wed, Mar 13, 2019 at 03:21:23PM -0700, Rajat Jain wrote: > > Convert the intel_pmc_core driver to a platform driver. There is no > > functional change. Some code that tries to determine what kind of > > CPU this is, has been moved cod

Re: [PATCH] perf: extend total_ref_count usage to protect perf_trace_buf access

On Mon, 18 Mar 2019 16:17:45 +0530 Prateek Sood wrote: > A potential race exists between access of perf_trace_buf[i] from > perf_trace_buf_alloc() and perf_trace_event_unreg(). This can > result in perf_trace_buf[i] being NULL during access from memset() > in perf_trace_buf_alloc(). > > Signed-o

Re: [PATCH] arm64: zynqmp: dt: Add TI PHY quirk

On 09. 03. 19 12:16, Harini Katakam wrote: > Add TI PHY strap ctrl quirk for all the HW where applicable. > > Signed-off-by: Harini Katakam > --- > arch/arm64/boot/dts/xilinx/zynqmp-zc1751-xm016-dc2.dts | 1 + > arch/arm64/boot/dts/xilinx/zynqmp-zcu102-revA.dts | 1 + > arch/arm64/boot/dts/

Cgroup cpu throttling with low cpu usage of multi-threaded applications on high-core count machines

We are seeing a high amount of cgroup cpu throttling, as measured by nr_throttled/nr_periods, while also seeing low cpu usage when running highly threaded applications on high core-count machines. In particular we are seeing this on "thread pool" design pattern applications that are being run on ku

Re: [PATCH 2/2] tty/serial: atmel: RS485 HD w/DMA: enable RX after TX is stopped

On 18/03/2019 16:30, Richard Genoud wrote: >> +/* Start RX if flag was set and FIFO is empty */ >> +if (atmel_port->hd_start_rx) { >> +if (atmel_uart_readl(port, ATMEL_US_CSR) >> +& ATMEL_US_TXEMPTY) { >> +

Re: [PATCH] lib: Add shared copy of __lshrti3 from libgcc

On Mon, Mar 18, 2019 at 02:43:41PM +, David Laight wrote: > From: Peter Zijlstra > > Sent: 18 March 2019 09:14 > > On Fri, Mar 15, 2019 at 03:06:37PM -0700, Nick Desaulniers wrote: > > > On Fri, Mar 15, 2019 at 1:54 PM Matthias Kaehlcke > > > wrote: > > > > > > > > The compiler may emit calls

Re: [PATCH v2 2/6] ptrace: introduce ptrace_syscall_enter to consolidate PTRACE_SYSEMU handling

On Mon, Mar 18, 2019 at 05:31:47PM +0300, Dmitry V. Levin wrote: > On Mon, Mar 18, 2019 at 10:49:21AM +, Sudeep Holla wrote: > > Currently each architecture handles PTRACE_SYSEMU in very similar way. > > It's completely arch independent and can be handled in the code helping > > to consolidate

Applied "spi: lpspi: Code cleanup" to the spi tree

The patch spi: lpspi: Code cleanup has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next m

Applied "spi: spi-fsl-spi: support use of the SPISEL_BOOT signal on MPC8309" to the spi tree

The patch spi: spi-fsl-spi: support use of the SPISEL_BOOT signal on MPC8309 has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "regulator: mt6397: Use unsigned int for volt_tables" to the regulator tree

The patch regulator: mt6397: Use unsigned int for volt_tables has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hou

Applied "spi: lpspi: add dma mode support" to the spi tree

The patch spi: lpspi: add dma mode support has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during th

Applied "regulator: mt6323: Use unsigned int for volt_tables" to the regulator tree

The patch regulator: mt6323: Use unsigned int for volt_tables has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hou

Applied "regulator: mt6380: Use unsigned int for volt_tables" to the regulator tree

The patch regulator: mt6380: Use unsigned int for volt_tables has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hou

Applied "spi : spi-topcliff-pch: Fix to handle empty DMA buffers" to the spi tree

The patch spi : spi-topcliff-pch: Fix to handle empty DMA buffers has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Applied "spi: lpspi: Add the missing NULL check" to the spi tree

The patch spi: lpspi: Add the missing NULL check has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus dur

Applied "regulator: da9063: Convert to use regulator_set/get_current_limit_regmap" to the regulator tree

The patch regulator: da9063: Convert to use regulator_set/get_current_limit_regmap has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually someti

Applied "regulator: da9062: Convert to use regulator_set/get_current_limit_regmap" to the regulator tree

The patch regulator: da9062: Convert to use regulator_set/get_current_limit_regmap has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually someti

Applied "spi: lpspi: use the core way to implement cs-gpio function" to the spi tree

The patch spi: lpspi: use the core way to implement cs-gpio function has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) a

Applied "doc: lpspi: Document DT bindings for LPSPI clocks" to the spi tree

The patch doc: lpspi: Document DT bindings for LPSPI clocks has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent t

Applied "regulator: cpcap: Convert to use of_device_get_match_data" to the regulator tree

The patch regulator: cpcap: Convert to use of_device_get_match_data has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

Applied "regulator: cpcap: Remove unneeded init_data setting" to the regulator tree

The patch regulator: cpcap: Remove unneeded init_data setting has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hou

Applied "regulator: as3711: Remove struct as3711_regulator_info and as3711_regulator" to the regulator tree

The patch regulator: as3711: Remove struct as3711_regulator_info and as3711_regulator has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually som

Applied "regulator: lp87565: Fix missing register for LP87565_BUCK_0" to the regulator tree

The patch regulator: lp87565: Fix missing register for LP87565_BUCK_0 has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the nex

Applied "regulator: as3722: Remove *rdevs[] from struct as3722_regulators" to the regulator tree

The patch regulator: as3722: Remove *rdevs[] from struct as3722_regulators has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in th

Applied "regulator: da9052: Include linux/of.h to fix build warning for of_match_ptr" to the regulator tree

The patch regulator: da9052: Include linux/of.h to fix build warning for of_match_ptr has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually som

Applied "regulator: max77650: Use unsigned int for max77651_sbb1_regulator_volt_table" to the regulator tree

The patch regulator: max77650: Use unsigned int for max77651_sbb1_regulator_volt_table has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually so

Applied "regulator: lp87565: Convert to use regulator_set/get_current_limit_regmap" to the regulator tree

The patch regulator: lp87565: Convert to use regulator_set/get_current_limit_regmap has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually somet

Applied "ASoC: stm32: spdifrx: add power management" to the asoc tree

The patch ASoC: stm32: spdifrx: add power management has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Li

Commit seems to prevent use of GNUmakefile wrappers

Hi Mashiro, commit 2b50f7ab63685cd247e32ad321f7338ed130d3d5 Author: Masahiro Yamada kbuild: add workaround for Debian make-kpkg seems to prevent the use of GNUmakefile wrappers to set the ARCH and CROSS_COMPILE make variables. With this commit, I now see: make:

RE: [PATCH] lib: Add shared copy of __lshrti3 from libgcc

From: Peter Zijlstra > Sent: 18 March 2019 09:14 > On Fri, Mar 15, 2019 at 03:06:37PM -0700, Nick Desaulniers wrote: > > On Fri, Mar 15, 2019 at 1:54 PM Matthias Kaehlcke wrote: > > > > > > The compiler may emit calls to __lshrti3 from the compiler runtime > > > library, which results in undefined

RE: [PATCH V4 2/5] pwm: Add i.MX TPM PWM driver support

Hi, Uwe Yes, I will post a V6, but before sending V6, can you help confirm if you agree my 2 answers for your last comments, such as the counter disable for changing prescale and the mutex lock in .apply function? Best Regards! Anson Huang > -Original Message- > From: Uwe Kleine

Re: [PATCH v3] PCI: qcom: Use default config space read function

On 18/03/2019 14:28, Marc Gonzalez wrote: We don't need to fudge the device class in qcom_pcie_rd_own_conf() because dw_pcie_setup_rc() already does the right thing: /* Program correct class for RC */ dw_pcie_wr_own_conf(pp, PCI_CLASS_DEVICE, 2, PCI_CLASS_BRIDGE_PCI); However

Re: [PATCH v5 0/3] Add PM support to STM32 LP Timer drivers

On 2/20/19 2:07 PM, Fabrice Gasnier wrote: > This patch series adds power management support for STM32 LP Timer: > - PWM driver > - Document the pinctrl states for sleep mode > > It also adds device link between the PWM consumer and the PWM provider. > This allows proper sequencing for suspend/res

Re: [PATCH] printk: Remove no longer used console_silent().

On (03/18/19 23:05), Tetsuo Handa wrote: > console_silent() is no longer used after the removal of > arch/mn10300/kernel/mn10300-watchdog.c in Linux 4.17-rc1. [..] > -static inline void console_silent(void) > -{ > - console_loglevel = CONSOLE_LOGLEVEL_SILENT; > -} I would keep it, I guess, a

Re: [PATCH 2/2] tty/serial: atmel: RS485 HD w/DMA: enable RX after TX is stopped

[ adding Gil Weber in Cc: ] Le 15/03/2019 à 10:23, Razvan Stefanescu a écrit : > In half-duplex operation, RX should be started after TX completes. > > If DMA is used, there is a case when the DMA transfer completes but the > TX FIFO is not emptied, so the RX cannot be restarted just yet. > > Use

Re: [PATCH v7 03/15] sched/core: uclamp: Add system default clamps

On Mon, Mar 18, 2019 at 02:21:52PM +, Patrick Bellasi wrote: > On 18-Mar 14:10, Peter Zijlstra wrote: > > On Mon, Mar 18, 2019 at 12:18:04PM +, Patrick Bellasi wrote: > > > On 13-Mar 21:18, Peter Zijlstra wrote: > > > > On Fri, Feb 08, 2019 at 10:05:42AM +, Patrick Bellasi wrote: > > >

Re: [External] Re: mm/cma.c: High latency for cma allocation

On Mon 18-03-19 14:02:09, Pankaj Suryawanshi wrote: >> > I have the system(vanilla kernel) with 2GB of RAM, reserved 1GB for CMA. >> > No swap or zram. >> > Sorry, I don't have information where the time is spent. >> > time is calculated in between cma_alloc call. >> > I have just cma_alloc trace

[PATCH v3] PCI: qcom: Use default config space read function

We don't need to fudge the device class in qcom_pcie_rd_own_conf() because dw_pcie_setup_rc() already does the right thing: /* Program correct class for RC */ dw_pcie_wr_own_conf(pp, PCI_CLASS_DEVICE, 2, PCI_CLASS_BRIDGE_PCI); However, the above has no effect on 8064, thus a fixup

Re: [PATCH] percpu/module resevation: change resevation size iff X86_VSMP is set

On Mon, Mar 18, 2019 at 10:18:48AM +0200, Eial Czerwacki wrote: > Greetings Paul, > > On 3/15/19 12:19 AM, Paul E. McKenney wrote: > > On Thu, Mar 14, 2019 at 10:36:19AM -0700, Tejun Heo wrote: > >> On Wed, Mar 13, 2019 at 04:11:55PM -0700, Paul E. McKenney wrote: > >>> commit 34f67df09cc0c6bf082a

Re: [PATCH 2/2] regulator: da9055: Convert to regulator core's simplified DT parsing code

On Mon, Mar 18, 2019 at 01:56:21PM +, Steve Twiss wrote: > But it does seem that around 97% of this driver has not has not changed since > 2014, so we are happy here at Dialog to remove our support from this DA9055 > device. > Is there a Linux device driver retirement plan for obsoleted produ

Re: [PATCH v6 00/14] KVM/X86: Introduce a new guest mapping interface

On Mon, Mar 18, 2019 at 01:10:24PM +, Raslan, KarimAllah wrote: > I guess this patch series missed the 5.1 merge window? :) Were there any outstanding fixes that had to be addressed? > > On Thu, 2019-01-31 at 21:24 +0100, KarimAllah Ahmed wrote: > > Guest memory can either be directly manage

Re: [PATCH v7 03/15] sched/core: uclamp: Add system default clamps

On 18-Mar 14:10, Peter Zijlstra wrote: > On Mon, Mar 18, 2019 at 12:18:04PM +, Patrick Bellasi wrote: > > On 13-Mar 21:18, Peter Zijlstra wrote: > > > On Fri, Feb 08, 2019 at 10:05:42AM +, Patrick Bellasi wrote: > > > > +static void uclamp_fork(struct task_struct *p) > > > > +{ > > > > +

LOANS !!!

Dial Direct Loan SA Consolidate your debts with Dial Direct Loan SA for your peace of mind at a fixed interest rate of 4.75%,personal and business loans are also welcome.For details open enclosed documents and file in your applications by sending an email to: dialdirectinfolo...@mail2consultant

Re: [PATCH 1/1] loop: access lo_backing_file only when the loop device is Lo_bound

On 3/18/19 6:23 AM, Dongli Zhang wrote: > Commit 758a58d0bc67 ("loop: set GENHD_FL_NO_PART_SCAN after > blkdev_reread_part()") separates "lo->lo_backing_file = NULL" and > "lo->lo_state = Lo_unbound" into different critical regions protected by > loop_ctl_mutex. > > However, there is below race th

Re: [PATCH 1/2] tty/serial: atmel: Add is_half_duplex helper

On 18/03/2019 15:41, Richard Genoud wrote: > [ adding Gil Weber in Cc: ] > > Le 15/03/2019 à 10:23, Razvan Stefanescu a écrit : >> Use a helper function to check that a port needs to use half duplex >> communication, replacing several occurrences of multi-line bit checking. >> >> Signed-off-by:

Re: [PATCH V4 2/5] pwm: Add i.MX TPM PWM driver support

Hello, as you got some feedback for v5 already I assume you will post a v6. I'll skip reviewing v5 then. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König| Industrial Linux Solutions | http://www.pengutronix.de/ |

Re: [PATCH] rcu: Allow to eliminate softirq processing from rcutree

On Fri, Mar 15, 2019 at 12:11:30PM +0100, Sebastian Andrzej Siewior wrote: > From: "Paul E. McKenney" > > Running RCU out of softirq is a problem for some workloads that would > like to manage RCU core processing independently of other softirq work, > for example, setting kthread priority. > This

Re: [syzbot? printk?] no WARN_ON() messages printed before "Kernel panic - not syncing: panic_on_warn set ..."

On (03/18/19 14:42), Dmitry Vyukov wrote: > > There is also SYSLOG_ACTION_CONSOLE_OFF, which disables logging. > > That one I somehow figured earlier, here is the exact check: > https://github.com/google/syzkaller/blob/61f9c92f3a465025d2b9d91f429aaec968aeaa2a/sys/linux/init.go#L152-L155 OK, cool.

[PATCH] printk: Remove no longer used console_silent().

console_silent() is no longer used after the removal of arch/mn10300/kernel/mn10300-watchdog.c in Linux 4.17-rc1. Signed-off-by: Tetsuo Handa --- include/linux/printk.h | 5 - 1 file changed, 5 deletions(-) diff --git a/include/linux/printk.h b/include/linux/printk.h index d7c77ed..65b6d4f

RE: [PATCH V4 2/5] pwm: Add i.MX TPM PWM driver support

Hi, Uwe Best Regards! Anson Huang > -Original Message- > From: Anson Huang > Sent: 2019年3月18日 18:08 > To: 'Uwe Kleine-König' > Cc: thierry.red...@gmail.com; robh...@kernel.org; mark.rutl...@arm.com; > shawn...@kernel.org; s.ha...@pengutronix.de; ker...@pengutronix.de; > feste...@gmail.co

Re: [PATCH 4.9 00/31] 4.9.164-stable review

stable-rc/linux-4.9.y boot: 94 boots: 0 failed, 94 passed (v4.9.163-32-g631b5fe18b59) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.9.y/kernel/v4.9.163-32-g631b5fe18b59/ Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.9.y/kernel/v4.9.163-3

Re: [External] Re: mm/cma.c: High latency for cma allocation

From: Michal Hocko Sent: 18 March 2019 19:12 To: Pankaj Suryawanshi Cc: linux...@kvack.org; linux-kernel@vger.kernel.org; minc...@kernel.org; Kirill Tkhai Subject: Re: [External] Re: mm/cma.c: High latency for cma allocation [Please do not use html emai

Re: [PATCH net] staging: rtl8188eu: use is_zero_ether_addr() instead of memcmp()

On 2019/3/17 19:26, Greg KH wrote: > On Sat, Mar 09, 2019 at 11:26:00AM +0800, Mao Wenan wrote: >> Using is_zero_ether_addr() instead of directly use >> memcmp() to determine if the ethernet address is all >> zeros. >> >> Signed-off-by: Mao Wenan >> --- >> drivers/staging/rtl8188eu/core/rtw_ml

RE: [PATCH 2/2] regulator: da9055: Convert to regulator core's simplified DT parsing code

Hi Mark, For the DA9055, I have spoken with the management here. Dialog Semiconductor are "no longer building the DA9055"; the device doesn't appear on the support portal or website and; I have been told, "you can remove [it] from your list of supported products". But, as always: I realise that t

RE: [PATCH v2] infiniband: i40iw: fix potential NULL pointer dereferences

>Subject: [PATCH v2] infiniband: i40iw: fix potential NULL pointer dereferences Something like "RDMA/i40iw: Handle workqueue allocation failure" is a more appropriate subject line. > >alloc_ordered_workqueue may fail and return NULL. >The fix captures the failure and handles it properly to avoid

Re: [PATCH] HID: Increase maximum report size allowed by hid_field_extract()

On Fri, 8 Mar 2019, Kai-Heng Feng wrote: > Commit 71f6fa90a353 ("HID: increase maximum global item tag report size > to 256") increases the max report size from 128 to 256. > > We also need to update the report size in hid_field_extract() otherwise > it complains and truncates now valid report si

Re: [PATCH] selinux: fix NULL dereference in policydb_destroy()

On 3/17/19 9:46 AM, Ondrej Mosnacek wrote: The conversion to kvmalloc() forgot to account for the possibility that p->type_attr_map_array might be null in policydb_destroy(). Fix this by destroying its contents only if it is not NULL. Also make sure ebitmap_init() is called on all entries befor

Re: [PATCH] HID: steam: fix deadlock with input devices.

On Fri, 15 Mar 2019, Rodrigo Rivas Costa wrote: > When using this driver with the wireless dongle and some usermode > program that monitors every input device (acpid, for example), while > another usermode client opens and closes the low-level device > repeadedly, the system eventually deadlocks.

Re: [External] Re: mm/cma.c: High latency for cma allocation

[Please do not use html emails to the mailing list and try to fix your email client to not break quoating. Fixed for this email] On Mon 18-03-19 13:28:50, Pankaj Suryawanshi wrote: > On Mon 18-03-19 12:58:28, Pankaj Suryawanshi wrote: > > > Hello, > > > > > > I am facing issue of high latency in C

Re: [syzbot? printk?] no WARN_ON() messages printed before "Kernel panic - not syncing: panic_on_warn set ..."

On Mon, Mar 18, 2019 at 1:50 PM Sergey Senozhatsky wrote: > > On (03/18/19 13:32), Dmitry Vyukov wrote: > > Wait, but isn't SYSLOG_ACTION_CONSOLE_LEVEL what we are looking for? > > syzkaller knows about the syslog syscall: > > There is also SYSLOG_ACTION_CONSOLE_OFF, which disables logging. That

Re: [PATCH 4.19 00/52] 4.19.30-stable review

stable-rc/linux-4.19.y boot: 103 boots: 0 failed, 102 passed with 1 untried/unknown (v4.19.29-53-g80fa0a60fe1b) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.19.y/kernel/v4.19.29-53-g80fa0a60fe1b/ Full Build Summary: https://kernelci.org/build/stable-rc/branch/li

Re: [PATCH 1/2] tty/serial: atmel: Add is_half_duplex helper

[ adding Gil Weber in Cc: ] Le 15/03/2019 à 10:23, Razvan Stefanescu a écrit : > Use a helper function to check that a port needs to use half duplex > communication, replacing several occurrences of multi-line bit checking. > > Signed-off-by: Razvan Stefanescu > --- > drivers/tty/serial/atmel_s

Re: [PATCH] nvme: lightnvm: expose OC devices as zero size to OS

On 3/14/19 2:56 PM, Matias Bjørling wrote: On 3/14/19 6:41 AM, Marcin Dziegielewski wrote: Open channel devices are not able to handle traditional IO requests addressed by LBA, so following current approach to exposing special nvme devices as zero size (e.g. with namespace formatted to use metad

Re: [External] Re: mm/cma.c: High latency for cma allocation

From: Michal Hocko Sent: 18 March 2019 18:37:57 To: Pankaj Suryawanshi Cc: linux...@kvack.org; linux-kernel@vger.kernel.org; minc...@kernel.org; Kirill Tkhai Subject: [External] Re: mm/cma.c: High latency for cma allocation CAUTION: This email originated from outside of the organizatio

Re: [PATCH] sched/fair: Limit sched_cfs_period_timer loop to avoid hard lockup

On Fri, Mar 15, 2019 at 05:03:47PM +0100 Peter Zijlstra wrote: > On Fri, Mar 15, 2019 at 11:30:42AM -0400, Phil Auld wrote: > > >> I'll rework the maths in the averaged version and post v2 if that makes > >> sense. > > > > It may have the extra timer fetch, although maybe I could rework it so th

Re: [PATCH 4.14 00/34] 4.14.107-stable review

stable-rc/linux-4.14.y boot: 103 boots: 1 failed, 101 passed with 1 untried/unknown (v4.14.106-35-g6fdcb56d3713) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.106-35-g6fdcb56d3713/ Full Build Summary: https://kernelci.org/build/stable-rc/branch/

Re: [PATCH] [RESEND] Do not modify perf bias performance setting by default at boot

On Monday, March 18, 2019 12:40:46 PM CET Rafael J. Wysocki wrote: > On Mon, Mar 18, 2019 at 12:15 PM Thomas Renninger wrote: ... > And who's BIOS, really? I guess you mean the OEM? Note, however, > that the user and the OEM may not agree on that, but whatever. I mean both! The OEM. And the

Re: [PATCH 3/3] RISC-V: Allow booting kernel from any 4KB aligned address

On Mon, Mar 18, 2019 at 12:48 PM Mike Rapoport wrote: > > On Sat, Mar 16, 2019 at 04:55:30AM +0530, Anup Patel wrote: > > On Fri, Mar 15, 2019 at 9:52 PM Anup Patel wrote: > > > > > > On Fri, Mar 15, 2019 at 9:28 PM Mike Rapoport wrote: > > > > > > > > I still don't get why it is that important

Re: [PATCH 2/2] pinctrl: meson: add support of drive-strength

On 14/03/2019 17:37, Jerome Brunet wrote: > From: Guillaume La Roque > > drive-strength is a new feature needed for G12A SoC. > the default DS setting after boot is usually 0.5mA and it is not enough for > many functions. We need to be able to set the drive strength to reliably > enable things li

Re: [PATCH v7 03/15] sched/core: uclamp: Add system default clamps

On Mon, Mar 18, 2019 at 12:18:04PM +, Patrick Bellasi wrote: > On 13-Mar 21:18, Peter Zijlstra wrote: > > On Fri, Feb 08, 2019 at 10:05:42AM +, Patrick Bellasi wrote: > > > +static void uclamp_fork(struct task_struct *p) > > > +{ > > > + unsigned int clamp_id; > > > + > > > + if (unlikely(!

Re: [PATCH v6 00/14] KVM/X86: Introduce a new guest mapping interface

I guess this patch series missed the 5.1 merge window? :) On Thu, 2019-01-31 at 21:24 +0100, KarimAllah Ahmed wrote: > Guest memory can either be directly managed by the kernel (i.e. have a "struct > page") or they can simply live outside kernel control (i.e. do not have a > "struct page"). KVM mo

Re: mm/cma.c: High latency for cma allocation

On Mon 18-03-19 12:58:28, Pankaj Suryawanshi wrote: > Hello, > > I am facing issue of high latency in CMA allocation of large size buffer. > > I am frequently allocating/deallocation CMA memory, latency of allocation is > very high. > > Below are the stat for allocation/deallocation latency iss

Re: [PATCH v2 2/2] ceph: quota: fix quota subdir mounts

On Tue, Mar 12, 2019 at 10:22 PM Luis Henriques wrote: > > The CephFS kernel client does not enforce quotas set in a directory that > isn't visible from the mount point. For example, given the path > '/dir1/dir2', if quotas are set in 'dir1' and the filesystem is mounted with > > mount -t ceph

Re: [PATCH v7 06/15] sched/core: uclamp: Reset uclamp values on RESET_ON_FORK

On 13-Mar 21:52, Peter Zijlstra wrote: > On Fri, Feb 08, 2019 at 10:05:45AM +, Patrick Bellasi wrote: > > diff --git a/kernel/sched/core.c b/kernel/sched/core.c > > index 070caa1f72eb..8b282616e9c9 100644 > > --- a/kernel/sched/core.c > > +++ b/kernel/sched/core.c > > @@ -1071,7 +1071,7 @@ stat

mm/cma.c: High latency for cma allocation

Hello, I am facing issue of high latency in CMA allocation of large size buffer. I am frequently allocating/deallocation CMA memory, latency of allocation is very high. Below are the stat for allocation/deallocation latency issue. (390100 kB), latency 29997 us (390100 kB), latency 22957 us (

[PATCH] ARM: dts: sun8i: a23/a33: Add R_I2C Controller

The A23 and A33 both have an I2C controller in the ARISC domain, that share the same pins with the RSB bus. Even if it's an unusual configuration, that device can be used to drive the PMIC, so let's use it. Signed-off-by: Maxime Ripard --- arch/arm/boot/dts/sun8i-a23-a33.dtsi | 20 +

<    1   2   3   4   5   6   7   8   9   10   >