Re: [RFC PATCH 01/13] arm: Fix mutual exclusion in arch_gettimeoffset

2018-11-13 Thread Russell King - ARM Linux
On Wed, Nov 14, 2018 at 02:35:29PM +1300, Michael Schmitz wrote: > So we'd still have to use jiffies + interpolation from the current timer > rundown counter as clocksource (since that will be monotonous and won't > wrap)? > > The way Finn did the clocksource for m68k, the clocksource counter

Re: [PATCH 2/8] pstore: Do not use crash buffer for decompression

2018-11-13 Thread Kees Cook
On Fri, Nov 2, 2018 at 1:24 PM, Joel Fernandes wrote: > On Thu, Nov 01, 2018 at 04:51:54PM -0700, Kees Cook wrote: >> static void decompress_record(struct pstore_record *record) >> { >> + int ret; >> int unzipped_len; > > nit: We could get rid of the unzipped_len variable now I think.

Re: [PATCH 1/1] Bluetooth: make the balance of judgement condition to fix a false report

2018-11-13 Thread Marcel Holtmann
Hi Zumeng, > This patch is to balance the condition scope between hci_get_cmd_complete and > hci_event_packet about orig_skb as follows: > >if (req_complete_skb || event == HCI_EV_CMD_STATUS || >event == HCI_EV_CMD_COMPLETE) >orig_skb = skb_clone(skb,

Re: [Letux-kernel] [PATCH RFC] bluetooth: add uart h4 devices via serdev/devicetree

2018-11-13 Thread Marcel Holtmann
Hi Andreas, > Am 12.11.2018 um 21:59 schrieb Andreas Kemnade : > On Sun, 11 Nov 2018 03:46:48 +0100 > Sebastian Reichel wrote: >> On Sun, Nov 11, 2018 at 12:20:34AM +0100, Andreas Kemnade wrote: >>> This is a first try to be able to use h4 devices specified in >>> the

Re: [PATCH v1 3/4] Bluetooth: hci_qca: clear HCI_QUIRK_RESET_ON_CLOSE flag

2018-11-13 Thread Marcel Holtmann
Hi Balakrishna, >> During hci down we are sending reset command to chip, which >> is not required for wcn3990, as hdev->shutdown() will turn off the >> regulators. >> Signed-off-by: Balakrishna Godavarthi >> --- >> drivers/bluetooth/hci_qca.c | 1 + >> 1 file changed,

[PATCH v3 0/2] Add device driver for APU2/APU3 GPIOs

2018-11-13 Thread Florian Eckert
Changes v2: - Update SPDX short identifier - Remove gpio-keys-polled device moved to arch/x86/platform - Fix styling - Use spinnlock only there where it is useful - Removed useless output on driver load - Do bit manipulation later not on IO - Add additional GPIOs handling mpci2_reset and

[PATCH v3 1/2] gpio: Add driver for PC Engines APU2/APU3 GPIOs

2018-11-13 Thread Florian Eckert
Add a new device driver "gpio-apu" which will handle the GPIOs onAPU2 and APU3 devices from PC Engines. APU2 (https://pcengines.ch/schema/apu2c.pdf page 7): - G32 is "button_reset" connected to the smd-button on the frontpanel - G50 is "mpcie2_reset" connected to mPCIe2 reset line - G51 is

[PATCH v3 2/2] kernel: Add reset button platform device for APU2/APU3

2018-11-13 Thread Florian Eckert
This will add a x86 platform device "gpio-keys-polled" which uses the new gpio-apu drive for APU2 and APU3 boards from PC Engines. Signed-off-by: Florian Eckert --- arch/x86/Kconfig | 14 arch/x86/platform/Makefile | 1 + arch/x86/platform/amd/Makefile | 1 +

Re: [PATCH] l1tf: drop the swap storage limit restriction when l1tf=off

2018-11-13 Thread Michal Hocko
On Tue 13-11-18 20:56:54, Jiri Kosina wrote: > On Tue, 13 Nov 2018, Michal Hocko wrote: > > > From: Michal Hocko > > > > Swap storage is restricted to max_swapfile_size (~16TB on x86_64) > > whenever the system is deemed affected by L1TF vulnerability. Even > > though the limit is quite high

Re: [PATCH 1/2] Makefile: Fix distcc compilation with x86 macros

2018-11-13 Thread Logan Gunthorpe
On 13/11/18 11:34 AM, Nadav Amit wrote: > Just one question before I send v2, since I have second thoughts. Does it > make sense to require the “DISTCC” make parameter, or should it be set in > the Kconfig? It can be detected automatically, the same way gcc/clang are > detected or manually

RE: [PATCH v3] thermal: qoriq: add multiple sensors support

2018-11-13 Thread Andy Tang
PING. BR, Andy > -Original Message- > From: andy.t...@nxp.com > Sent: 2018年10月30日 9:00 > To: rui.zh...@intel.com; daniel.lezc...@linaro.org > Cc: edubez...@gmail.com; linux...@vger.kernel.org; > linux-kernel@vger.kernel.org; Andy Tang > Subject: [PATCH v3] thermal: qoriq: add multiple

Re: [PATCH v2] UAPI: move RENAME_* definitions to separated file

2018-11-13 Thread Yury Norov
Hi all, It seems that I forgot to rename guards in v2. This is the correct version. My apologize for noise. Yury >From 61215b1cb559e69fb57f2a82864e72e3a1ef4b12 Mon Sep 17 00:00:00 2001 From: Yury Norov Date: Wed, 14 Nov 2018 09:51:49 +0300 To: Andrew Morton , Alexander Viro ,

[PATCH] HID: i2c-hid: Disable runtime PM for LG touchscreen

2018-11-13 Thread Kai-Heng Feng
LG touchscreen (1fd2:8001) stops working after reboot: [ 4.859153] i2c_hid i2c-SAPS2101:00: i2c_hid_get_input: incomplete report (64/66) [ 4.936070] i2c_hid i2c-SAPS2101:00: i2c_hid_get_input: incomplete report (64/66) [ 9.948224] i2c_hid i2c-SAPS2101:00: failed to reset device. The device in

kernel BUG at mm/slab.c:LINE! (3)

2018-11-13 Thread syzbot
Hello, syzbot found the following crash on: HEAD commit:3e536cff3424 net: phy: check if advertising is zero using .. git tree: net-next console output: https://syzkaller.appspot.com/x/log.txt?x=16f95b8340 kernel config: https://syzkaller.appspot.com/x/.config?x=4a0a89f12ca9b0f5

Re: [PATCH RFC v2 0/3] cleanups for pstore and ramoops

2018-11-13 Thread Kees Cook
On Sat, Nov 3, 2018 at 6:38 PM, Joel Fernandes (Google) wrote: > Here are some simple cleanups and fixes for ramoops in pstore. Let me know > what you think, thanks. I took these and slightly tweaked code locations for the first one. I'll send out the series for review when I'm back from

Re: [RFC PATCH] mm, memory_hotplug: do not clear numa_node association after hot_remove

2018-11-13 Thread Michal Hocko
It seems there were no objections here. So can we have it in linux-next for a wider testing a possibly target the next merge window? On Thu 08-11-18 11:04:13, Michal Hocko wrote: > From: Michal Hocko > > Per-cpu numa_node provides a default node for each possible cpu. The > association gets

[PATCH v2] UAPI: move RENAME_* definitions to separated file

2018-11-13 Thread Yury Norov
Discussion: https://lore.kernel.org/lkml/20180702084622.GA15274@yury-thinkpad/ Although RENAME_* macros are exposed in kernel headers, they are not used by glibc. That's because linux/fs.h which hosts RENAME_* is considered unsuitable by glibc developers: As Florian Weimer wrote: > undefines

Re: Applied "ASoC: pcm3060: Add DT property for single-ended output" to the asoc tree

2018-11-13 Thread Kirill Marinushkin
Hello Mark, Thank you for applying this patch series. I think you forgot one patch in the series: patch [1] is a documentation for patch [2]. It has a different naming scheme, because that's how the document [3] recommends. That's why it was not obvious that they relate to each other. Document

Re: UBSAN: Undefined behaviour in mm/page_alloc.c

2018-11-13 Thread Michal Hocko
On Tue 13-11-18 15:29:41, Andrew Morton wrote: [...] > But do we really need to do this? Are there any other known potential > callsites? The main point is that the code as it stands is quite fragile, isn't it? Fixing up all the callers is possible but can you actually think of a reason why this

Re: [PATCH] zram: close udev startup race condition as default groups

2018-11-13 Thread Hannes Reinecke
On 11/14/18 6:52 AM, Minchan Kim wrote: commit fef912bf860e upstream. commit 98af4d4df889 upstream. I got a report from Howard Chen that he saw zram and sysfs race(ie, zram block device file is created but sysfs for it isn't yet) when he tried to create new zram devices via hotadd knob. v4.20

Re: [PATCH v1 3/4] Bluetooth: hci_qca: clear HCI_QUIRK_RESET_ON_CLOSE flag

2018-11-13 Thread Balakrishna Godavarthi
Hi Matthias, On 2018-11-14 07:44, Matthias Kaehlcke wrote: On Tue, Nov 06, 2018 at 06:44:07PM +0530, Balakrishna Godavarthi wrote: Hi Marcel, On 2018-11-06 18:32, Marcel Holtmann wrote: > Hi Balakrishna, > > > > > During hci down we are sending reset command to chip, which > > > > is not

Re: [PATCH v6 0/2] mtd: rawnand: meson: add Amlogic NAND driver support

2018-11-13 Thread Jianxin Pan
Hi Miquel, I sorry to miss you in the CC list before, I will CC you in the next version. Thank you very much. On 2018/11/12 4:57, Miquel Raynal wrote: > Hi Jianxin, > > Jianxin Pan wrote on Fri, 2 Nov 2018 00:42:19 > +0800: > >> These two patches try to add initial NAND driver support for

Re: [PATCH v1 2/4] Bluetooth: hci_qca: Pull RTS line high for baudrate change command

2018-11-13 Thread Balakrishna Godavarthi
Hi Matthias, On 2018-11-14 07:25, Matthias Kaehlcke wrote: On Tue, Nov 06, 2018 at 05:35:26PM +0530, Balakrishna Godavarthi wrote: This patch will pull the RTS line high instead of turning off the flow control, while changing baudrate of host and chip. Please don't only describe what is

Re: [PATCH v1 1/4] Bluetooth: hci_qca: use wait_until_sent() for power pulses

2018-11-13 Thread Balakrishna Godavarthi
Hi Matthias, On 2018-11-14 05:47, Matthias Kaehlcke wrote: On Tue, Nov 06, 2018 at 05:35:25PM +0530, Balakrishna Godavarthi wrote: wcn3990 requires a power pulse to turn ON/OFF along with regulators. Sometimes we are observing the power pulses are sent out with some time delay, due to queuing

RE: [RFC/RFT][PATCH v3] cpuidle: New timer events oriented governor for tickless systems

2018-11-13 Thread Doug Smythies
On 2018.11.08 00:00 Rafael J. Wysocki wrote: > On Wednesday, November 7, 2018 6:04:12 PM CET Doug Smythies wrote: >> On 2018.11.04 08:31 Rafael J. Wysocki wrote: ...[snip]... >> The results are: >> http://fast.smythies.com/linux-pm/k420/k420-dbench-teo3.htm >>

Re: [PATCH v1 08/11] clk: mediatek: Add MT8183 clock support

2018-11-13 Thread Nicolas Boichat
On Mon, Nov 5, 2018 at 10:42 PM Weiyi Lu wrote: > > Add MT8183 clock support, include topckgen, apmixedsys, > infracfg, mcucfg and subsystem clocks. > > Signed-off-by: Weiyi Lu > --- > drivers/clk/mediatek/Kconfig | 75 ++ > drivers/clk/mediatek/Makefile | 12 + >

[GIT PULL] PCI fixes for v4.20

2018-11-13 Thread Bjorn Helgaas
PCI fixes: - Revert a _PXM change that causes silent early boot failure on some AMD ThreadRipper systems (Bjorn Helgaas) The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a: Linux 4.20-rc1 (2018-11-04 15:37:52 -0800) are available in the Git repository at:

[PATCH -next] i3c: master: Remove set but not used variable 'old_i3c_scl_lim'

2018-11-13 Thread YueHaibing
Fixes gcc '-Wunused-but-set-variable' warning: drivers/i3c/master/i3c-master-cdns.c: In function 'cdns_i3c_master_do_daa': drivers/i3c/master/i3c-master-cdns.c:1137:16: warning: variable 'old_i3c_scl_lim' set but not used [-Wunused-but-set-variable] It never used since introdution in commit

Re: [PATCH 4/6] autofs - use struct for mount params

2018-11-13 Thread Ian Kent
On Wed, 2018-11-14 at 09:54 +0800, kbuild test robot wrote: > Hi Ian, > > I love your patch! Yet something to improve: > > [auto build test ERROR on linus/master] > [also build test ERROR on v4.20-rc2] > [cannot apply to next-20181113] > [if your patch is applied to th

[PATCH] zram: close udev startup race condition as default groups

2018-11-13 Thread Minchan Kim
commit fef912bf860e upstream. commit 98af4d4df889 upstream. I got a report from Howard Chen that he saw zram and sysfs race(ie, zram block device file is created but sysfs for it isn't yet) when he tried to create new zram devices via hotadd knob. v4.20 kernel fixes it by [1, 2] but it's too

[PATCH] HID: multitouch: Add pointstick support for Cirque Touchpad

2018-11-13 Thread Kai-Heng Feng
Cirque Touchpad/Pointstick combo is similar to Alps devices, it requires MT_CLS_WIN_8_DUAL to expose its pointstick as a mouse. Signed-off-by: Kai-Heng Feng --- drivers/hid/hid-ids.h| 3 +++ drivers/hid/hid-multitouch.c | 6 ++ 2 files changed, 9 insertions(+) diff --git

Re: [PATCH v2 2/2] platform/chrome: don't report EC_MKBP_EVENT_SENSOR_FIFO as wakeup

2018-11-13 Thread Benson Leung
Hi Brian, On Wed, Nov 07, 2018 at 06:49:39PM -0800, Brian Norris wrote: > EC_MKBP_EVENT_SENSOR_FIFO events can be triggered for a variety of > reasons, and there are very few cases in which they should be treated as > wakeup interrupts (particularly, when a certain > MOTIONSENSE_MODULE_FLAG_* is

Re: [PATCH v2 1/2] platform/chrome: straighten out cros_ec_get_{next,host}_event() error codes

2018-11-13 Thread Benson Leung
Hi Brian, On Wed, Nov 07, 2018 at 06:49:38PM -0800, Brian Norris wrote: > cros_ec_get_next_event() is documented to return 0 for success and > negative for errors. It currently returns negative for some errors, and > non-negative (number of bytes received) for success (including some "no > data

linux-next: Tree for Nov 14

2018-11-13 Thread Stephen Rothwell
Hi all, Changes since 20181113: The tip tree still had its build failure for which I applied a fix patch. Non-merge commits (relative to Linus' tree): 2696 2835 files changed, 114088 insertions(+), 98851 deletions

Re: [PATCH] ideapad-laptop: Add Lenovo Yoga 2 13 to the no_hw_rfkill DMI list

2018-11-13 Thread Darren Hart
On Tue, Nov 13, 2018 at 06:22:45PM -0800, Loic WEI YU NENG wrote: > Some Lenovo ideapad models lack a physical rfkill switch. > On Lenovo models Yoga 2 13, ideapad-laptop would wrongly report all > radios as blocked by hardware which caused wireless network connections > to fail. > Add these

Re: [PATCH v3] mm: Create the new vm_fault_t type

2018-11-13 Thread Souptick Joarder
On Tue, Nov 6, 2018 at 5:33 PM Souptick Joarder wrote: > > Page fault handlers are supposed to return VM_FAULT codes, > but some drivers/file systems mistakenly return error > numbers. Now that all drivers/file systems have been converted > to use the vm_fault_t return type, change the type

Re: [PATCH] nvme: utilize two queue maps, one for reads and one for writes

2018-11-13 Thread Guenter Roeck
On Tue, Nov 13, 2018 at 05:51:08PM -0700, Jens Axboe wrote: > On 11/13/18 5:41 PM, Guenter Roeck wrote: > > Hi, > > > > On Wed, Oct 31, 2018 at 08:36:31AM -0600, Jens Axboe wrote: > >> NVMe does round-robin between queues by default, which means that > >> sharing a queue map for both reads and

[PATCH v2] fork: Fix some -Wmissing-prototypes warnings

2018-11-13 Thread Yi Wang
We get a warning when building kernel with W=1: kernel/fork.c:167:13: warning: no previous prototype for ‘arch_release_thread_stack’ [-Wmissing-prototypes] kernel/fork.c:779:13: warning: no previous prototype for ‘fork_init’ [-Wmissing-prototypes] Add the missing declaration in head file to fix

Re: [PATCH v4] cpufreq: ti-cpufreq: Only register platform_device when supported

2018-11-13 Thread Viresh Kumar
On 13-11-18, 13:30, Dave Gerlach wrote: > Currently the ti-cpufreq driver blindly registers a 'ti-cpufreq' to force > the driver to probe on any platforms where the driver is built in. > However, this should only happen on platforms that actually can make use > of the driver. There is already

Re: [RFC PATCH 01/13] arm: Fix mutual exclusion in arch_gettimeoffset

2018-11-13 Thread Finn Thain
On Tue, 13 Nov 2018, Russell King - ARM Linux wrote: > > A clocksource provides a cycle counter that monotonically changes and > does not wrap between clockevent events. > > A clock event is responsible for providing events to the system when > some work is needing to be done, limited by the

Re: [PATCH] ARM: dts: i.MX25: add the clocks for the EPIT blocks

2018-11-13 Thread Shawn Guo
On Thu, Nov 01, 2018 at 06:32:47PM +0100, Martin Kaiser wrote: > The i.MX25 contains two EPIT (Enhanced Periodic Interrupt Timer) > function blocks. Add their ipg and per clocks to the device tree. > > Signed-off-by: Martin Kaiser Applied, thanks.

Re: [RFC PATCH 06/13] m68k: Drop ARCH_USES_GETTIMEOFFSET

2018-11-13 Thread Michael Schmitz
Hi Finn, Am 14.11.2018 um 14:08 schrieb Michael Schmitz: Can you also test tree fbf8405cd982 please? My tests were on c606b5cf902 in case it wasn't clear. I've now seen fbf8405cd982, one moment please ... That one does appear to work - different versions of ARAnyM, and different userland

BUG: KASAN: slab-out-of-bounds in try_to_unmap_one+0x1c4/0x1af0

2018-11-13 Thread Qian Cai
Compiling kernel on an aarch64 server with the latest mainline (rc2) triggered this, [ 1463.931841] BUG: KASAN: slab-out-of-bounds in try_to_unmap_one+0x1c4/0x1af0 [ 1463.938969] Write of size 32 at addr 80897ce87b58 by task kworker/u513:0/5209 [ 1463.946678] [ 1463.948656] CPU: 38 PID:

[PATCH 16/25] sched/cputime: Allow to pass cputime index on user/guest accounting

2018-11-13 Thread Frederic Weisbecker
When we account user or guest cputime, we decide to add the delta either to the nice fields or the normal fields of kcpustat and this depends on the nice value for the task passed in parameter. Since we are going to track the nice-ness from vtime instead, we'll need to be able to use a different

RE: scsi_set_medium_removal timeout issue

2018-11-13 Thread Zengtao (B)
Hi Alan: >-Original Message- >From: Alan Stern [mailto:st...@rowland.harvard.edu] >Sent: Monday, November 12, 2018 11:33 PM >To: Zengtao (B) >Cc: j...@linux.vnet.ibm.com; martin.peter...@oracle.com; >gre...@linuxfoundation.org; linux-s...@vger.kernel.org; >linux-kernel@vger.kernel.org;

[PATCH 23/25] leds: Use vtime aware kcpustat accessors

2018-11-13 Thread Frederic Weisbecker
Now that we have a vtime safe kcpustat accessor, use it to fix frozen kcpustat values on nohz_full CPUs. Reported-by: Yauheni Kaliuta Signed-off-by: Frederic Weisbecker Cc: Yauheni Kaliuta Cc: Thomas Gleixner Cc: Rik van Riel Cc: Peter Zijlstra Cc: Wanpeng Li Cc: Ingo Molnar ---

[PATCH 24/25] rackmeter: Use vtime aware kcpustat accessors

2018-11-13 Thread Frederic Weisbecker
Now that we have a vtime safe kcpustat accessor, use it to fix frozen kcpustat values on nohz_full CPUs. Reported-by: Yauheni Kaliuta Signed-off-by: Frederic Weisbecker Cc: Yauheni Kaliuta Cc: Thomas Gleixner Cc: Rik van Riel Cc: Peter Zijlstra Cc: Wanpeng Li Cc: Ingo Molnar ---

[PATCH 25/25] sched/vtime: Clarify vtime_task_switch() argument layout

2018-11-13 Thread Frederic Weisbecker
This function deals with the previous and next tasks during a context switch. But only the previous is passed as an argument, the next task being deduced from current. Make the code clearer by passing both previous and next as arguments. Signed-off-by: Frederic Weisbecker Cc: Yauheni Kaliuta

[PATCH 22/25] cpufreq: Use vtime aware kcpustat accessor

2018-11-13 Thread Frederic Weisbecker
Now that we have a vtime safe kcpustat accessor, use it to fix frozen kcpustat values on nohz_full CPUs. Reported-by: Yauheni Kaliuta Signed-off-by: Frederic Weisbecker Cc: Yauheni Kaliuta Cc: Thomas Gleixner Cc: Rik van Riel Cc: Peter Zijlstra Cc: Wanpeng Li Cc: Ingo Molnar ---

[PATCH 13/25] context_tracking: Introduce context_tracking_enabled_cpu()

2018-11-13 Thread Frederic Weisbecker
This allows us to check if a remote CPU runs context tracking (ie: is nohz_full). We'll need that to reliably support "nice" accounting on kcpustat. Signed-off-by: Frederic Weisbecker Cc: Yauheni Kaliuta Cc: Thomas Gleixner Cc: Rik van Riel Cc: Peter Zijlstra Cc: Wanpeng Li Cc: Ingo Molnar

[PATCH 17/25] sched/cputime: Standardize the kcpustat index based accounting functions

2018-11-13 Thread Frederic Weisbecker
Sanitize a bit the functions that do cputime accounting with custom kcpustat indexes: * Rename account_system_index_time() to account_system_time_index() to comply with account_guest/user_time_index() * Use proper enum cpu_usage_stat type in account_system_time() * Reorder

[PATCH 11/25] context_tracking: s/context_tracking_is_enabled/context_tracking_enabled()

2018-11-13 Thread Frederic Weisbecker
Remove the superfluous "is" in the middle of the name. We want to standardize the naming so that it can be expanded through suffixes: context_tracking_enabled() context_tracking_enabled_cpu() context_tracking_enabled_this_cpu() Signed-off-by: Frederic Weisbecker Cc:

[PATCH 20/25] sched/kcpustat: Introduce vtime-aware kcpustat accessor

2018-11-13 Thread Frederic Weisbecker
Kcpustat is not correctly supported on nohz_full CPUs. The tick doesn't fire and the cputime therefore doesn't move forward. The issue has shown up after the vanishing of the remaining 1Hz which has made the issue visible. We are solving that with tracking the task running on a CPU through RCU

[PATCH 07/25] sched/cputime: Add vtime guest task state

2018-11-13 Thread Frederic Weisbecker
Record guest as a VTIME state instead of guessing it from VTIME_SYS and PF_VCPU. This is going to simplify the cputime read side especially as its state machine is going to further expand in order to fully support kcpustat on nohz_full. Signed-off-by: Frederic Weisbecker Cc: Yauheni Kaliuta Cc:

[PATCH 21/25] procfs: Use vtime aware kcpustat accessor

2018-11-13 Thread Frederic Weisbecker
Now that we have a vtime safe kcpustat accessor, use it to fix frozen kcpustat values on nohz_full CPUs. Reported-by: Yauheni Kaliuta Signed-off-by: Frederic Weisbecker Cc: Yauheni Kaliuta Cc: Thomas Gleixner Cc: Rik van Riel Cc: Peter Zijlstra Cc: Wanpeng Li Cc: Ingo Molnar ---

[PATCH 14/25] sched/vtime: Rename vtime_accounting_cpu_enabled() to vtime_accounting_enabled_this_cpu()

2018-11-13 Thread Frederic Weisbecker
Standardize the naming on top of the vtime_accounting_enabled_*() base. Also make it clear we are checking the vtime state of the *current* CPU with this function. We'll need to add an API to check that state on remote CPUs as well, so we must disambiguate the naming. Signed-off-by: Frederic

[PATCH 19/25] sched/vite: Handle nice updates under vtime

2018-11-13 Thread Frederic Weisbecker
On the vtime level, nice updates are currently handled on context switches. When a task's nice value gets updated while it is sleeping, the context switch takes into account the new nice value in order to later record the vtime delta to the appropriate kcpustat index. We have yet to handle live

[PATCH 15/25] sched/vtime: Introduce vtime_accounting_enabled_cpu()

2018-11-13 Thread Frederic Weisbecker
This allows us to check if a remote CPU runs vtime accounting (ie: is nohz_full). We'll need that to reliably support "nice" accounting on kcpustat. Signed-off-by: Frederic Weisbecker Cc: Yauheni Kaliuta Cc: Thomas Gleixner Cc: Rik van Riel Cc: Peter Zijlstra Cc: Wanpeng Li Cc: Ingo Molnar

[PATCH 10/25] context_tracking: Remove context_tracking_active()

2018-11-13 Thread Frederic Weisbecker
This function is a leftover from old removal or rename. We can drop it. Signed-off-by: Frederic Weisbecker Cc: Yauheni Kaliuta Cc: Thomas Gleixner Cc: Rik van Riel Cc: Peter Zijlstra Cc: Wanpeng Li Cc: Ingo Molnar --- include/linux/context_tracking_state.h | 1 - 1 file changed, 1

[PATCH 09/25] kcpustat: Track running task following vtime sequences

2018-11-13 Thread Frederic Weisbecker
In order to make kcpustat vtime aware (ie: work on nohz_full without freezing), we need to track the task running on the CPU in order to fetch its vtime delta and add it to the relevant kcpustat field. The most efficient way to track this task is to use RCU. The task is assigned on context switch

[PATCH 08/25] vtime: Exit vtime before exit_notify()

2018-11-13 Thread Frederic Weisbecker
In order to correctly implement kcpustat under nohz_full, we need to track the task running on a given CPU and read its vtime state safely, reliably and locklessly. This leaves us with tracking and fetching that task under RCU. This will be done in a further patch. Until then we need to prepare

[PATCH 18/25] vtime: Track nice-ness on top of context switch

2018-11-13 Thread Frederic Weisbecker
We need to read the nice value of the task running on any CPU, possibly remotely, in order to correctly support kcpustat on nohz_full. Unfortunately we can't just read task_nice(tsk) when tsk runs on another CPU because its nice value may be concurrently changed. There could be a risk that a

[PATCH 12/25] context_tracking: Rename context_tracking_is_cpu_enabled() to context_tracking_enabled_this_cpu()

2018-11-13 Thread Frederic Weisbecker
Standardize the naming on top of the context_tracking_enabled_*() base. Also make it clear we are checking the context tracking state of the *current* CPU with this function. We'll need to add an API to check that state on remote CPUs as well, so we must disambiguate the naming. Signed-off-by:

[PATCH 06/25] sched/cputime: Add vtime idle task state

2018-11-13 Thread Frederic Weisbecker
Record idle as a VTIME state instead of guessing it from VTIME_SYS and is_idle_task(). This is going to simplify the cputime read side especially as its state machine is going to further expand in order to fully support kcpustat on nohz_full. Signed-off-by: Frederic Weisbecker Cc: Yauheni

[PATCH 00/25] sched/nohz: Make kcpustat vtime aware (Fix kcpustat on nohz_full)

2018-11-13 Thread Frederic Weisbecker
Kcpustat (the stats you see for each CPU on /proc/stat) is partly maintained by the tick, updated by TICK_NSEC every jiffy, the same way we account the cputime for tasks. Now in the case of nohz_full, kcpustat doesn't get accounted anymore while the tick is stopped. Vtime maintains the task

[PATCH 01/25] sched/vtime: Fix guest/system mis-accounting on task switch

2018-11-13 Thread Frederic Weisbecker
vtime_account_system() assumes that the target task to account cputime to is always the current task. This is most often true indeed except on task switch where we call: vtime_common_task_switch(prev) vtime_account_system(prev) Here prev is the scheduling-out task where

[PATCH 03/25] vtime: Rename vtime_account_system() to vtime_account_kernel()

2018-11-13 Thread Frederic Weisbecker
vtime_account_system() decides if we need to account the time to the system (__vtime_account_system()) or to the guest (vtime_account_guest()). So this function is a misnommer as we are on a higher level than "system". All we know when we call that function is that we are accounting kernel

[PATCH 04/25] vtime: Spare a seqcount lock/unlock cycle on context switch

2018-11-13 Thread Frederic Weisbecker
On context switch we are locking the vtime seqcount of the scheduling-out task twice: * On vtime_task_switch_common(), when we flush the pending vtime through vtime_account_system() / vtime_account_idle() * On arch_vtime_task_switch() to reset the vtime state. This is pointless as these

[PATCH 05/25] sched/vtime: Record CPU under seqcount for kcpustat needs

2018-11-13 Thread Frederic Weisbecker
In order to compute the kcpustat delta on a nohz CPU, we'll need to fetch the task running on that target. Checking that its vtime state snapshot actually refers to the relevant target involves recording that CPU under the seqcount locked on task switch. This is a step toward making kcpustat

[PATCH 02/25] sched/vtime: Protect idle accounting under vtime seqcount

2018-11-13 Thread Frederic Weisbecker
Locking the seqcount on idle vtime accounting wasn't thought to be necessary because the readers of idle cputime don't use vtime (yet). Now updating vtime expect the related seqcount to be locked so do it for locking coherency purposes. Also idle cputime updates use vtime, but idle cputime

WARNING: possible circular locking dependency detected

2018-11-13 Thread Qian Cai
Compiling kernel on an aarch64 server with the latest mainline (rc2) generated this, [ 910.263839] WARNING: possible circular locking dependency detected [ 910.263841] 4.20.0-rc2+ #4 Tainted: GWL [ 910.263843] -- [

Re: kmemleak: Early log buffer exceeded (525980) during boot

2018-11-13 Thread Qian Cai
> On Nov 10, 2018, at 12:42 PM, Qian Cai wrote: > > > On 11/10/18 at 11:59 AM, Catalin Marinas wrote: > >> On Sat, Nov 10, 2018 at 10:08:10AM -0500, Qian Cai wrote: >>> On Nov 8, 2018, at 4:23 PM, Qian Cai wrote: The maximum value for DEBUG_KMEMLEAK_EARLY_LOG_SIZE is only 4, so it

Re: [PATCH] openrisc: make function cache_loop() inline

2018-11-13 Thread Changbin Du
On Wed, Nov 14, 2018 at 05:49:53AM +0900, Stafford Horne wrote: > On Mon, Nov 12, 2018 at 11:55:44PM +0800, Changbin Du wrote: > > The third operand of mtspr instruction must be a constraint. To guarantee > > this condition, function cache_loop() which uses macro mtspr() must be > > inlined. So

linux-next: build warning after merge of the spi tree

2018-11-13 Thread Stephen Rothwell
Hi Mark, After merging the spi tree, today's linux-next build (x86_64 allmodconfig) produced this warning: drivers/spi/spi-npcm-pspi.c: In function 'npcm_pspi_recv': drivers/spi/spi-npcm-pspi.c:226:17: warning: 'val' may be used uninitialized in this function [-Wmaybe-uninitialized]

Re: [PATCH v1 3/4] Bluetooth: hci_qca: clear HCI_QUIRK_RESET_ON_CLOSE flag

2018-11-13 Thread Matthias Kaehlcke
On Tue, Nov 06, 2018 at 06:44:07PM +0530, Balakrishna Godavarthi wrote: > Hi Marcel, > > On 2018-11-06 18:32, Marcel Holtmann wrote: > > Hi Balakrishna, > > > > > > > During hci down we are sending reset command to chip, which > > > > > is not required for wcn3990, as hdev->shutdown() will turn

Re: [PATCH cgroup/for-4.21 1/2] cpuset: Minor cgroup2 interface updates

2018-11-13 Thread Waiman Long
On 11/13/2018 12:13 PM, Tejun Heo wrote: > From b1e3aeb11c5e86ee0988a038c4e7682d6beaa977 Mon Sep 17 00:00:00 2001 > From: Tejun Heo > Date: Tue, 13 Nov 2018 12:03:33 -0800 > > * Rename the partition file from "cpuset.sched.partition" to > "cpuset.cpus.partition". > > * When writing to the

Re: [PATCH v7 15/17] tpm: introduce tpm_chip_start() and tpm_chip_stop()

2018-11-13 Thread Stefan Berger
On 11/13/18 5:34 PM, Stefan Berger wrote: On 11/13/18 1:36 PM, Jarkko Sakkinen wrote: Encapsulate power gating and locality functionality to tpm_chip_start() and tpm_chip_stop() in order to clean up the branching mess in tpm_transmit(). I ran the vtpm proxy test suite on this series and got

Re: [PATCH v1 2/4] Bluetooth: hci_qca: Pull RTS line high for baudrate change command

2018-11-13 Thread Matthias Kaehlcke
On Tue, Nov 06, 2018 at 05:35:26PM +0530, Balakrishna Godavarthi wrote: > This patch will pull the RTS line high instead of turning off the > flow control, while changing baudrate of host and chip. Please don't only describe what is changed, but also why this change is necessary. IIUC the BT

Re: [PATCH v11 3/5] x86/boot: Add get_acpi_rsdp() to parse RSDP in cmdlien from kexec

2018-11-13 Thread Chao Fan
On Tue, Nov 13, 2018 at 06:51:50PM +0100, Borislav Petkov wrote: >On Mon, Nov 12, 2018 at 05:46:43PM +0800, Chao Fan wrote: >> Imitate setup_acpi_rsdp() for the early_param of 'acpi_rsdp'. >> KEXEC writes the RSDP pointer to cmdline for EFI booting. >> So if 'acpi_rsdp' found in cmdline, use it

Re: [PATCH 4/6] autofs - use struct for mount params

2018-11-13 Thread kbuild test robot
Hi Ian, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.20-rc2] [cannot apply to next-20181113] [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

Re: [PATCH v7 15/17] tpm: introduce tpm_chip_start() and tpm_chip_stop()

2018-11-13 Thread Stefan Berger
On 11/13/18 1:36 PM, Jarkko Sakkinen wrote: Encapsulate power gating and locality functionality to tpm_chip_start() and tpm_chip_stop() in order to clean up the branching mess in tpm_transmit(). Signed-off-by: Jarkko Sakkinen --- drivers/char/tpm/tpm-chip.c | 110

[PATCH -next] misc: mic/scif: fix copy-paste error in scif_create_remote_lookup

2018-11-13 Thread YueHaibing
gcc '-Wunused-but-set-variable' warning: drivers/misc/mic/scif/scif_rma.c: In function 'scif_create_remote_lookup': drivers/misc/mic/scif/scif_rma.c:373:25: warning: variable 'vmalloc_num_pages' set but not used [-Wunused-but-set-variable] 'vmalloc_num_pages' should be used to determine if the

Re: nvme: utilize two queue maps, one for reads and one for writes

2018-11-13 Thread Mike Snitzer
On Tue, Nov 13 2018 at 8:28pm -0500, Mike Snitzer wrote: > On Tue, Nov 13 2018 at 7:51pm -0500, > Jens Axboe wrote: > > > On 11/13/18 5:41 PM, Guenter Roeck wrote: > > > Hi, > > > > > > On Wed, Oct 31, 2018 at 08:36:31AM -0600, Jens Axboe wrote: > > >> NVMe does round-robin between queues

Re: [RFC PATCH 01/13] arm: Fix mutual exclusion in arch_gettimeoffset

2018-11-13 Thread Michael Schmitz
On 14/11/18 12:43 PM, Russell King - ARM Linux wrote: On Wed, Nov 14, 2018 at 08:55:37AM +1100, Finn Thain wrote: On Tue, 13 Nov 2018, Russell King - ARM Linux wrote: On Tue, Nov 13, 2018 at 02:39:00PM +1100, Finn Thain wrote: You could remove the old arch_gettimeoffset API without

Re: nvme: utilize two queue maps, one for reads and one for writes

2018-11-13 Thread Mike Snitzer
On Tue, Nov 13 2018 at 7:51pm -0500, Jens Axboe wrote: > On 11/13/18 5:41 PM, Guenter Roeck wrote: > > Hi, > > > > On Wed, Oct 31, 2018 at 08:36:31AM -0600, Jens Axboe wrote: > >> NVMe does round-robin between queues by default, which means that > >> sharing a queue map for both reads and

RE,

2018-11-13 Thread Miss Juliet Muhammad
Hello, I need your help to invest in your region.

RE,

2018-11-13 Thread Miss Juliet Muhammad
Hello, I need your help to invest in your region.

RE,

2018-11-13 Thread Miss Juliet Muhammad
Hello, I need your help to invest in your region.

Re: [RFC PATCH 06/13] m68k: Drop ARCH_USES_GETTIMEOFFSET

2018-11-13 Thread Michael Schmitz
Hi Finn, On 14/11/18 11:11 AM, Finn Thain wrote: On Tue, 13 Nov 2018, Michael Schmitz wrote: Running a recent kernel under ARAnyM shows 40 ns resolution so the Atari hardware emulation is a little more complete. You mean, 40 us resolution, right? Sorry, typo. Should have been us of

Re: [GIT PULL] namespace fixes for v4.20-rc2

2018-11-13 Thread Konstantin Ryabitsev
On Wed, Nov 14, 2018 at 12:55:45AM +, pr-tracker-...@kernel.org wrote: > The pull request you sent on Sat, 10 Nov 2018 12:12:12 -0600: > > > git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git > > for-linus > > has been merged into torvalds/linux.git: >

Re: [GIT PULL] Ceph fixes for 4.20-rc2

2018-11-13 Thread pr-tracker-bot
The pull request you sent on Fri, 9 Nov 2018 17:47:55 +0100: > https://github.com/ceph/ceph-client.git tags/ceph-for-4.20-rc2 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/d757a3b01e72368176c5ee580ea17f8c2d185cd7 Thank you! -- Deet-doot-dot, I am a bot.

Re: ODEBUG: Out of memory. ODEBUG disabled

2018-11-13 Thread Qian Cai
> On Nov 12, 2018, at 11:33 PM, Qian Cai wrote: > > > >> On Nov 10, 2018, at 9:11 AM, Qian Cai wrote: >> >> On 11/10/18 at 8:59 AM, Waiman Long wrote: >> >>> On 11/09/2018 08:45 PM, Qian Cai wrote: > Sent: Friday, November 09, 2018 at 5:08 PM > From: "Waiman Long" > To:

Re: [GIT PULL] Devicetree fixes for 4.20-rc, round 2

2018-11-13 Thread pr-tracker-bot
The pull request you sent on Fri, 9 Nov 2018 15:39:43 -0600: > git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git > tags/devicetree-fixes-for-4.20-2 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/aa4330e15c26c5ef8dd184f515c0655db8c6df3a Thank you! --

Re: [GIT PULL] clk fixes for v4.20-rc1

2018-11-13 Thread pr-tracker-bot
The pull request you sent on Sat, 10 Nov 2018 10:04:23 -0800: > https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git > tags/clk-fixes-for-linus has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/a1aa42f1d8c00a0767afee28d17caafd2a4dd8ff Thank you! --

Re: [GIT PULL] arm64 fixes for 4.20-rc2

2018-11-13 Thread pr-tracker-bot
The pull request you sent on Sat, 10 Nov 2018 11:44:54 +: > git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/35c55685fc807fb536067602418f4a12dde23987 Thank you! -- Deet-doot-dot, I am a

Re: [GIT PULL] namespace fixes for v4.20-rc2

2018-11-13 Thread pr-tracker-bot
The pull request you sent on Sat, 10 Nov 2018 12:12:12 -0600: > git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git > for-linus has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/1de4f2ef216dade3b5bd5f5247c4c750a953f51c Thank you! --

Re: [PATCH] nvme: utilize two queue maps, one for reads and one for writes

2018-11-13 Thread Jens Axboe
On 11/13/18 5:41 PM, Guenter Roeck wrote: > Hi, > > On Wed, Oct 31, 2018 at 08:36:31AM -0600, Jens Axboe wrote: >> NVMe does round-robin between queues by default, which means that >> sharing a queue map for both reads and writes can be problematic >> in terms of read servicing. It's much easier

[PATCH] mm/usercopy: Use memory range to be accessed for wraparound check

2018-11-13 Thread Isaac J. Manjarres
Currently, when checking to see if accessing n bytes starting at address "ptr" will cause a wraparound in the memory addresses, the check in check_bogus_address() adds an extra byte, which is incorrect, as the range of addresses that will be accessed is [ptr, ptr + (n - 1)]. This can lead to

Re: [PATCH] nvme: utilize two queue maps, one for reads and one for writes

2018-11-13 Thread Guenter Roeck
rate poll queue map" fixes the problem. Guenter --- # bad: [220dcf1c6fc97f8873b6d9fe121b80decd4b71a8] Add linux-next specific files for 20181113 # good: [ccda4af0f4b92f7b4c308d3acc262f4a7e3affad] Linux 4.20-rc2 git bisect start 'HEAD' 'v4.20-rc2' # good: [b5ae1d7e1bd7cf5dfdef94da5cb69c60c91

Applied "regulator: bd718x7: Change next state after poweroff to ready" to the regulator tree

2018-11-13 Thread Mark Brown
The patch regulator: bd718x7: Change next state after poweroff to ready 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

  1   2   3   4   5   6   7   >