Re: [RFC PATCH 3/3] of: fix node traversing in of_dma_get_range

Hi Rob, On 27/03/17 15:34, Rob Herring wrote: > On Sat, Mar 25, 2017 at 12:31 AM, Oza Pawandeep wrote: >> it jumps to the parent node without examining the child node. >> also with that, it throws "no dma-ranges found for node" >> for pci dma-ranges. >> >> this patch fixes

[PATCH v3 07/19] HID: logitech-hidpp: retrieve the HID++ device name when available

hidpp->name can't be null. Only HID++ 2.0 and above device supports the query. Signed-off-by: Benjamin Tissoires --- changes in v3: - moved up in the series new in v2 --- drivers/hid/hid-logitech-hidpp.c | 14 +++--- 1 file changed, 7 insertions(+), 7

[PATCH v3 12/19] HID: logitech-hidpp: return an error if the queried feature is not present

Or the device just answers a valid feature '0'. Signed-off-by: Benjamin Tissoires --- changes in v3: - moved up in the series no changes in v2 --- drivers/hid/hid-logitech-hidpp.c | 3 +++ 1 file changed, 3 insertions(+) diff --git

Re: [RFC PATCH v0.2] PCI: Add support for tango PCIe host bridge

On 24/03/2017 19:47, Marc Zyngier wrote: > On 23/03/17 17:03, Mason wrote: > >> On 23/03/2017 15:22, Marc Zyngier wrote: >> >>> On 23/03/17 13:05, Mason wrote: >>> + writel_relaxed(status, pcie->msi_status); /* clear IRQs */ >>> >>> Why isn't this your irq_ack method instead of open-coding

[PATCH V2 2/2] perf/x86: add sysfs entry to freeze counter on SMI

From: Kan Liang Currently, the SMIs are visible to all performance counters. Because many users want to measure everything including SMIs. But in some cases, the SMI cycles should not be count. For example, to calculate the cost of SMI itself. So a knob is needed. When

Re: [kernel-hardening] [PATCH v5 1/4] gcc-plugins: Add the initify gcc plugin

On Mon, Mar 27, 2017 at 12:38 AM, Andrew Donnellan wrote: > On 01/02/17 07:24, Kees Cook wrote: >> >> From: Emese Revfy >> >> The kernel already has a mechanism to free up code and data memory that >> is only used during kernel or module

Re: [PATCH] usb-musb: keep VBUS on when device is disconnected

> Il giorno 27 mar 2017, alle ore 16:30, Tony Lindgren ha > scritto: > > […] > I wonder if the following test patch allows the mode changing > devices to been properly found? Of course it's just for testing, > and scanning for devices takes now 5 seconds.. But it might >

Re: [RFC PATCH v0.2] PCI: Add support for tango PCIe host bridge

On Mon, 27 Mar 2017, Mason wrote: > On 24/03/2017 19:22, Marc Zyngier wrote: > > > You cannot directly use a pointer to a u32 in any of the bitmap > > operations. You need to copy the value to an unsigned long, and > > apply the bitmap op on that. > > On my platform, find_first_zero_bit()

kvm: use-after-free in srcu_reschedule

Hello, I've got the following use-after-free report on linux-next/65b2dc38291f9f27e5ec3b804d6eb3b5f79a3ce4. == BUG: KASAN: use-after-free in debug_spin_unlock kernel/locking/spinlock_debug.c:97 [inline] BUG: KASAN: use-after-free in

Re: kvm: use-after-free in srcu_reschedule

On 27/03/2017 16:46, Dmitry Vyukov wrote: > > Paul McKenney writes: > > === > Hmmm... I am not seeing a call to cleanup_srcu_struct() for the > ->track_srcu field of the kvm_page_track_notifier_head structure. > Or is this structure immortal, so that it is never cleaned up? > Or am I just

Re: [PATCH v9 15/15] irqchip: mbigen: Add ACPI support

[+Al,Darren to comment on _DSD review process] On Mon, Mar 27, 2017 at 12:24:45PM +, Gabriele Paoloni wrote: > Hi Marc Many thanks for your comments > > > -Original Message- > > From: linuxarm-boun...@huawei.com [mailto:linuxarm-boun...@huawei.com] > > On Behalf Of Marc Zyngier > >

Re: [RESEND PATCH v2 21/53] mtd: nand: denali: move multi device fixup code to a helper function

On Thu, 23 Mar 2017 05:07:20 +0900 Masahiro Yamada wrote: > Collect multi NAND fixups into a helper function instead of > scattering them in denali_init(). > > I am rewording the comment block to clearly explain what is called > "multi device". I will take the

Re: [PATCH v8 3/3] printk: fix double printing with earlycon

On 03/27/2017 05:14 PM, Petr Mladek wrote: On Mon 2017-03-20 13:03:00, Aleksey Makarov wrote: [..] diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c index fd752f0c8ef1..462036e7a767 100644 --- a/kernel/printk/printk.c +++ b/kernel/printk/printk.c @@ -1909,8 +1909,28 @@ static

Re: [PATCH v5 6/9] coresight: add support for CPU debug module

On 25/03/17 18:23, Leo Yan wrote: Coresight includes debug module and usually the module connects with CPU debug logic. ARMv8 architecture reference manual (ARM DDI 0487A.k) has description for related info in "Part H: External Debug". Chapter H7 "The Sample-based Profiling Extension"

[PATCH v3 04/19] HID: logitech-hidpp: do not query the name through HID++ for 1.0 devices

Unless they are connected through unifying, they don't support it, so remove one error in the logs. Signed-off-by: Benjamin Tissoires --- changes in v3: - moved up in the series no changes in v2 --- drivers/hid/hid-logitech-hidpp.c | 2 ++ 1 file changed, 2

[PATCH v3 01/19] HID: logitech-dj: allow devices to request full pairing information

Register 0xB5 should be handled specially no matter what function is used. This allows to retrieve the serial and the Quad ID from hid-logitech-hidpp directly. Signed-off-by: Benjamin Tissoires --- changes in v3: - fixed 0xb5 to handle any incoming parameters no

[PATCH v3 06/19] HID: logitech-hidpp: rework probe path for unifying devices

Unifying devices are different from others because they can probed while not connected. So we need to talk to the receiver to get some extra information like the device name and the serial. Instead of having conditionals while attempting to read the device name from HID++ 2.0, have a special init

[PATCH v3 19/19] HID: logitech-hidpp: add a sysfs file to tell we support power_supply

This way, upower can add a simple udev rule to decide whether or not it should use the internal unifying support or just the generic kernel one. Signed-off-by: Benjamin Tissoires --- no changes in v3 no changes in v2 --- drivers/hid/hid-logitech-hidpp.c | 20

RE: [PATCH] net: netfilter: Remove multiple assignment.

From: Pablo Neira Ayuso > Sent: 27 March 2017 13:08 > On Sat, Mar 25, 2017 at 06:19:47PM +0530, Arushi Singhal wrote: > > This patch removes multiple assignments. > > Done using coccinelle. > > @@ > > identifier i1,i2; > > constant c; > > @@ > > - i1=i2=c; > > + i1=c; > > + i2=c; > > You have to

Re: [PATCH] virtio-blk: add DISCARD support to virtio-blk driver

On Tue, Mar 28, 2017 at 04:39:25PM +0800, Changpeng Liu wrote: > Currently virtio-blk driver does not provide discard feature flag, so the > filesystems which built on top of the block device will not send discard > command. This is okay for HDD backend, but it will impact the performance > for

Re: [x86/mm/gup] 2947ba054a [ 71.329069] kernel BUG at include/linux/pagemap.h:151!

On Fri, Mar 24, 2017 at 02:47:09PM +0300, Kirill A. Shutemov wrote: > > From d2f416a3ee3e5dbb10e59d0b374d382fdc4ba082 Mon Sep 17 00:00:00 2001 > From: "Kirill A. Shutemov" > Date: Fri, 24 Mar 2017 14:13:05 +0300 > Subject: [PATCH] mm: Fix false-positive

Re: Getting the way a SIGSEGV append when catching a SIGSEGV from within

On Mon, Mar 27, 2017 at 4:45 PM, none wrote: > Hello, > > There’s three way to perform an invalid memory access : > > The attempt to execute/jump at an invalid address. > The attempt to read at an invalid address. > The attempt to write at an invalid address. > > Determining

[PATCH V2 1/2] x86/msr: add msr_set/clear_bit_on_cpu/cpus access functions

From: Kan Liang Having msr_set/clear_bit on many cpus or given CPU can avoid extra unnecessory IPIs and simplify MSR content manipulation, when it only needs to flip a bit. There is already msr_set/clear_bit, but missing the _on_cpu and _on_cpus version. Signed-off-by: Kan

[PATCH V2 0/2] measure SMI cost (kernel)

From: Kan Liang Currently, there is no way to measure the time cost in System management mode (SMM) by perf. Intel perfmon supports FREEZE_WHILE_SMM bit in IA32_DEBUGCTL. Once it sets, the PMU core counters will freeze on SMI handler. But it will not have an effect on free

Re: [RFC v5 8/9] sched/deadline: base GRUB reclaiming on the inactive utilization

On Mon, Mar 27, 2017 at 04:56:51PM +0200, Luca Abeni wrote: > > > +u64 grub_reclaim(u64 delta, struct rq *rq, u64 u) > > > { > > > + u64 u_act; > > > + > > > + if (rq->dl.this_bw - rq->dl.running_bw > (1 << 20) - u) > > > + u_act = u; > > > + else > > > + u_act = (1 << 20) -

Re: [PATCH 4.10 012/167] mmc: sdhci-acpi: support deferred probe

On Mon, Mar 27, 2017 at 10:40:23AM +0800, Zhang Rui wrote: > On Sun, 2017-03-26 at 12:26 +0100, Andrey Utkin wrote: > > On Fri, Mar 10, 2017 at 10:07:35AM +0100, Greg Kroah-Hartman wrote: > > > > > > 4.10-stable review patch.  If anyone has any objections, please let > > > me know. > > > > > >

Re: [PATCH] trace: Make trace_hwlat timestamp y2038 safe

> > >> > [auto build test WARNING on tip/perf/core] >> > [also build test WARNING on v4.11-rc4 next-20170327] >> > [if your patch is applied to the wrong git tree, please drop us a note to >> > help improve the system] >> > >> > url:

[PATCH] ftrace/x86: fix x86-32 triple fault with graph tracing and suspend-to-ram

On x86-32, with CONFIG_FIRMWARE and multiple CPUs, if you enable function graph tracing and then suspend to RAM, it will triple fault and reboot when it resumes. The first fault happens when booting a secondary CPU: startup_32_smp() load_ucode_ap() prepare_ftrace_return()

Re: [PATCHv2] phy: cpcap-usb: Add CPCAP PMIC USB support

* Kishon Vijay Abraham I [170326 23:27]: > On Thursday 23 March 2017 05:16 AM, Tony Lindgren wrote: > > +static const struct phy_ops ops = { > > + .owner = THIS_MODULE, > > +}; > > Given that this phy doesn't have any phy_ops, Is there a reason for > registering > this

Re: [v2] PCI: Add an option to control probing of VFs before enabling SR-IOV

On 3/22/2017 10:53 AM, bod...@mellanox.com wrote: From: Bodong Wang Sometimes it is not desirable to probe the virtual functions after SRIOV is enabled. This can save host side resource usage by VF instances which would be eventually probed to VMs. Add a new PCI sysfs

Re: [RFC PATCH 1/3] of/pci: dma-ranges to account highest possible host bridge dma_mask

On Sat, Mar 25, 2017 at 12:31 AM, Oza Pawandeep wrote: > it is possible that PCI device supports 64-bit DMA addressing, > and thus it's driver sets device's dma_mask to DMA_BIT_MASK(64), > however PCI host bridge may have limitations on the inbound > transaction addressing.

Re: [PATCH v2 3/3] perf/sdt/powerpc: Add argument support

On Mon, 27 Mar 2017 13:28:29 +0530 Ravi Bangoria wrote: > SDT marker argument is in N@OP format. Here OP is arch dependent > component. Add powerpc logic to parse OP and convert it to uprobe > compatible format. Looks good to me. Acked-by: Masami Hiramatsu

Re: [PATCH] staging: media: atomisp: remove ifdef around HMM_BO_ION

> > 2 -- > >  1 file changed, 2 deletions(-) > > Ugh, Alan, what's going on here, I thought you fixed this? I sent you a patch that removed the arrays entirely and turned it into a single string as well as removing the define. Not quite sure what happened but I've resynched to -next and I'll

Re: [PATCH] trace: Make trace_hwlat timestamp y2038 safe

On Mon, 27 Mar 2017 16:53:09 +0200 Arnd Bergmann wrote: > > Actually, I believe that "%zd" will work. It's made to work with size_t > > which is long long on 32 and long on 64. > > size_t is always 'long', not 'long long'. We have %pad for dma_addr_t > which may be 'long' or

Re: [PATCH] trace: Make trace_hwlat timestamp y2038 safe

On Mon, Mar 27, 2017 at 5:30 PM, Steven Rostedt wrote: > On Mon, 27 Mar 2017 16:53:09 +0200 >> We could probably introduce a %pts format string for timespec64 >> and have that pretty-printed. > > Hmm, probably don't want a %p as that suggests its a pointer, which it > should

Re: [PATCH v11 00/12] uapi: export all headers under uapi directories

2017-03-27 21:20 GMT+09:00 Nicolas Dichtel : > > > Patches #1 and #2 are just cleanup: some exported headers were still under > a non-uapi directory. Patch #3 is a fix to avoid exporting a file that was > not under an uapi directory. > After these three patches, all

[PATCH v2] tpm_tis: convert to using locality callbacks

This patch converts tpm_tis to use of the new tpm class ops request_locality, and relinquish_locality. With the move to using the callbacks, release_locality is changed so that we now release the locality even if there is no request pending. This required some changes to the tpm_tis_core_init

Re: [PATCH v3 00/19] Report power supply from hid-logitech-hidpp

On Mon, 2017-03-27 at 16:59 +0200, Benjamin Tissoires wrote: > Hi, > > this is finally a rework of the series that provides kernel > power_supply > for hidpp devices. > > This will allow upower to not handle those devices anymore and to > have more > immediate reportng of the device to the

Re: [PATCH] PCI: dwc: fix crash seen due to missing ops

Às 7:19 AM de 3/23/2017, Niklas Cassel escreveu: > On 03/22/2017 04:47 PM, Joao Pinto wrote: >> Hi Niklas, >> >> Às 2:43 PM de 3/21/2017, Niklas Cassel escreveu: >>> From: Niklas Cassel >>> >>> Fix the following crash, seen in dwc/pcie-artpec6. >>> >>> Unable to handle

Re: [RFC LINUX PATCH 0/3] Allow remote to specify shared memory

Hi Wendy, On 03/24/2017 02:22 PM, Wendy Liang wrote: > This patch enables the remoteproc to specify the shared memory. > Remoteproc declared this memory as DMA memory. > It can be used for virtio, or shared buffers. You should be able to achieve this without any remoteproc core changes. You can

Re: [PATCH 1/1] ethtool : added get_phy_stats,get_strings,get_sset_count

Hello, On 03/27/2017 03:12 AM, Thomas Scariah wrote: > From: "Scariah, Thomas" > > Added functions to support ethtool to print the phy statistics and error > information along with other ethtool statistics. This will help ethtool > information to know the error is

Re: [RFC v5 9/9] sched/deadline: also reclaim bandwidth not used by dl tasks

Hi Peter, On Mon, 27 Mar 2017 16:03:41 +0200 Peter Zijlstra wrote: > On Fri, Mar 24, 2017 at 04:53:02AM +0100, luca abeni wrote: > > > +static inline > > +void __dl_update(struct dl_bw *dl_b, s64 bw) > > +{ > > + struct root_domain *rd = container_of(dl_b, struct > >

Getting the way a SIGSEGV append when catching a SIGSEGV from within

Hello, There’s three way to perform an invalid memory access : The attempt to execute/jump at an invalid address. The attempt to read at an invalid address. The attempt to write at an invalid address. Determining the execute case with rt_sigaction is easy : the last value of eip match the

[PATCH v3 14/19] HID: logitech-hidpp: battery: provide ONLINE property

When ONLINE isn't set, upower should ignore the battery capacity, so there is no need to overload it with some random values. Signed-off-by: Benjamin Tissoires --- completely reworked in v3: - store a online field in hidpp->battery to be able to fine control

[PATCH v3 16/19] HID: logitech-hidpp: battery: provide CAPACITY_LEVEL

CAPACITY LEVEL allows to forward rough information on the battery mileage. HID++ 2.0 devices will either report percentage or levels, so better forwarding this information to the user space. The M325 supports only 2 levels: 'Full' and 'Critical'. With mileage, it will report either 90% or 5%,

[PATCH v3 15/19] HID: logitech-hidpp: rename battery level into capacity

The power_supply term for the percentage is capacity. Capacity level can be given when non accurate mileage is provided by the device, so better stick to the terms used in power_supply. Signed-off-by: Benjamin Tissoires --- new in v3 ---

Re: [PATCH] kvm: arm/arm64: Rework gpa callback handlers

On 24/03/17 18:00, Christoffer Dall wrote: On Mon, Mar 20, 2017 at 06:26:42PM +, Suzuki K Poulose wrote: In order to perform an operation on a gpa range, the hyp iterates the hyp ? To be precise "the host" ? over each page in a user memory slot for the given range. This is

Re: [RFC PATCH v0.2] PCI: Add support for tango PCIe host bridge

On 27/03/2017 16:46, Thomas Gleixner wrote: > On Mon, 27 Mar 2017, Mason wrote: > >> On 24/03/2017 19:22, Marc Zyngier wrote: >> >>> You cannot directly use a pointer to a u32 in any of the bitmap >>> operations. You need to copy the value to an unsigned long, and >>> apply the bitmap op on that.

Re: [PATCH v2] usb: musb: cppi_dma.c: use DIV_ROUND_UP macro in cppi_next_(r|t)x_segment()

On Sat, Mar 25, 2017 at 12:52:58PM +0300, Ivan Safonov wrote: > DIV_ROUND_UP is bit useful than series of "/" and "%" operations. > Replace "/%" sequence with DIV_ROUND_UP macro. > > Signed-off-by: Ivan Safonov Applied. Thanks. -Bin. > --- > Changes in v2: > - little

Re: [PATCH RFC v4 06/10] net: qualcomm: make qca_common a separate kernel module

On Mon, 2017-03-27 at 15:37 +0200, Stefan Wahren wrote: > In order to share common functions between QCA7000 SPI and UART > protocol > driver the qca_common needs to be a separate kernel module. Maybe "qca_eth_common"? There are many things Qualcomm, slightly fewer things Qualcomm Atheros, and

Re: [PATCH] trace: Make trace_hwlat timestamp y2038 safe

On Mon, 27 Mar 2017 17:35:13 +0200 Arnd Bergmann wrote: > On Mon, Mar 27, 2017 at 5:30 PM, Steven Rostedt wrote: > > On Mon, 27 Mar 2017 16:53:09 +0200 > >> We could probably introduce a %pts format string for timespec64 > >> and have that pretty-printed.

Re: [PATCH 1/7] Documentation: dt: net: Update the ath9k binding for SoC devices

On Monday, March 13, 2017 10:05:09 PM CEST Alban wrote: > The current binding only cover PCI devices so extend it for SoC devices. > > Most SoC platforms use an MTD partition for the calibration data > instead of an EEPROM. The qca,no-eeprom property was added to allow > loading the EEPROM

[PATCH 7/8] x86/kasan: Extend to support 5-level paging

This patch bring support for non-folded additional page table level. Signed-off-by: Kirill A. Shutemov Cc: Dmitry Vyukov Cc: Andrey Ryabinin --- arch/x86/mm/kasan_init_64.c | 18 -- 1 file changed,

[PATCH v3 08/19] HID: logitech-hidpp: rework hidpp_connect_event()

Looks like all users don't care about a disconnect. Simplify the various variant_connect() and put the connect state check at the beginning. For delayed input devices, make sure we go through all other connect values (protocol, battery) before bailing out. Signed-off-by: Benjamin Tissoires

[PATCH v3 17/19] HID: logitech-hidpp: add support for battery status for the K750

The Solar Keyboard uses a different feature to report the battery level. Signed-off-by: Benjamin Tissoires --- changes in v3: - fixed online status changes in v2: * update state according to lux information * do not update Lux if the event does not contain lux

[PATCH v3 10/19] HID: logitech-hidpp: forward device info in power_supply

Better forwarding the device name, manufacturer and serial to upower. Note that serial is still empty, it will be filled in a later patch in this series. Signed-off-by: Benjamin Tissoires --- changes in v3: - moved up in the series changes in v2: * model

[PATCH v3 05/19] HID: logitech-hidpp: create a capabilities bits field

Do not pollute the quirks bits field which is public API with elements that are queried from the device. Move the 2 battery capabilities into the new field. Signed-off-by: Benjamin Tissoires --- new in v3 --- drivers/hid/hid-logitech-hidpp.c | 10 ++ 1

[PATCH v3 09/19] HID: logitech-hidpp: handle battery events in hidpp_raw_hidpp_event()

Battery events are reported through HID++, so we need to be sure the report ID is the HID++ one. Without this, we might receive keyboard events that looks just like battery events with wrong data and which will confuse user space. Signed-off-by: Benjamin Tissoires

[PATCH v3 00/19] Report power supply from hid-logitech-hidpp

Hi, this is finally a rework of the series that provides kernel power_supply for hidpp devices. This will allow upower to not handle those devices anymore and to have more immediate reportng of the device to the system. I have splitted the series to not support non unifying receivers here. I

Re: [PATCH v7 5/9] media: venus: vdec: add video decoder files

Le lundi 27 mars 2017 à 10:45 +0200, Hans Verkuil a écrit : > > > timestamp and sequence are only set for CAPTURE, not OUTPUT. Is > > > that correct? > > > > Correct. I can add sequence for the OUTPUT queue too, but I have no > > idea how that sequence is used by userspace. > > You set

Re: [PATCH] sd: Consider max_xfer_blocks if opt_xfer_blocks is unusable

- Original Message - > From: "Fam Zheng" > To: linux-kernel@vger.kernel.org > Cc: "Martin K. Petersen" , f...@redhat.com, > linux-s...@vger.kernel.org, "James E.J. > Bottomley" > Sent: Monday, March 27, 2017

[PATCH 1/8] x86/boot: Detect 5-level paging support

5-level paging support is required from hardware when compiled with CONFIG_X86_5LEVEL=y. We will implement boot-time switch between 4- and 5-level paging later. Signed-off-by: Kirill A. Shutemov --- arch/x86/boot/cpucheck.c | 9 +

[PATCH 4/8] x86/paravirt: Make paravirt code support 5-level paging

Add operations to allocate/release p4ds. Xen requires more work. We will need to come back to it. Signed-off-by: Kirill A. Shutemov --- arch/x86/include/asm/paravirt.h | 37 --- arch/x86/include/asm/paravirt_types.h | 7

[PATCH 2/8] x86/asm: Remove __VIRTUAL_MASK_SHIFT==47 assert

We don't need the assert anymore. 17be0aec74fb ("x86/asm/entry/64: Implement better check for canonical addresses") made canonical address check generic wrt. address width. Signed-off-by: Kirill A. Shutemov --- arch/x86/entry/entry_64.S | 7 ++- 1 file

[PATCH 8/8] x86/espfix: Add support 5-level paging

We don't need extra virtual address space for ESPFIX, so it stays within one PUD page table for both 4- and 5-level paging. Signed-off-by: Kirill A. Shutemov --- arch/x86/kernel/espfix_64.c | 12 +++- 1 file changed, 7 insertions(+), 5 deletions(-) diff

[PATCH 6/8] x86/dump_pagetables: Add support 5-level paging

Simple extension to support one more page table level. Signed-off-by: Kirill A. Shutemov --- arch/x86/mm/dump_pagetables.c | 49 --- 1 file changed, 42 insertions(+), 7 deletions(-) diff --git

[PATCH 3/8] x86/mm: Define virtual memory map for 5-level paging

The first part of memory map (up to %esp fixup) simply scales existing map for 4-level paging by factor of 9 -- number of bits addressed by additional page table level. The rest of the map is unchanged. Signed-off-by: Kirill A. Shutemov ---

[PATCH 0/8] x86: 5-level paging enabling for v4.12, Part 3

Here's the third bunch of patches of 5-level patchset. This time we prepare code to handle non-folded version of the additional page table level. Kirill A. Shutemov (8): x86/boot: Detect 5-level paging support x86/asm: Remove __VIRTUAL_MASK_SHIFT==47 assert x86/mm: Define virtual memory

[PATCH 5/8] x86/mm: Add basic defines/helpers for CONFIG_X86_5LEVEL

Extends pagetable headers to support new paging mode. Signed-off-by: Kirill A. Shutemov --- arch/x86/include/asm/pgtable_64.h | 11 +++ arch/x86/include/asm/pgtable_64_types.h | 20 +++ arch/x86/include/asm/pgtable_types.h| 10

Re: [lkp-robot] [fsnotify] 0ee0efcf7c: kernel_BUG_at_fs/notify/inotify/inotify_user.c

On Mon 27-03-17 12:36:17, kernel test robot wrote: > FYI, we noticed the following commit: > > commit: 0ee0efcf7c7968fb045454f621b5681e94b2c288 ("fsnotify: Move queueing of > mark for destruction into fsnotify_put_mark()") > https://git.kernel.org/cgit/linux/kernel/git/jack/linux-fs.git

Re: [RFC v5 8/9] sched/deadline: base GRUB reclaiming on the inactive utilization

On Mon, 27 Mar 2017 16:26:33 +0200 Peter Zijlstra wrote: > On Fri, Mar 24, 2017 at 04:53:01AM +0100, luca abeni wrote: > > From: Luca Abeni > > > > Instead of decreasing the runtime as "dq = -Uact dt" (eventually > > divided by the maximum

[PATCH v3 11/19] HID: logitech-hidpp: create the battery for all types of HID++ devices

The creation of the power_supply should not be in a HID++ 2.0 specific function. Signed-off-by: Benjamin Tissoires --- changes in v3: - moved up in the series no changes in v2 --- drivers/hid/hid-logitech-hidpp.c | 94 ++-- 1

[PATCH v3 02/19] HID: logitech-hidpp: Add scope to battery

From: Bastien Nocera Without a scope defined, UPower assumes that the battery provides power to the computer it's connected to, like a laptop battery or a UPS. Tested-by: Peter Hutterer Signed-off-by: Bastien Nocera

[PATCH] MAINTAINERS: Add memory drivers to AT91 entry

Both atmel-ebi and atmel-sdram are maintained as part of the Atmel ARM SoCs. Signed-off-by: Alexandre Belloni --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index c45c02bc6082..6531d239db6b 100644 ---

Re: [PATCH] MAINTAINERS: Add memory drivers to AT91 entry

Le 27/03/2017 à 17:21, Alexandre Belloni a écrit : > Both atmel-ebi and atmel-sdram are maintained as part of the Atmel ARM > SoCs. > > Signed-off-by: Alexandre Belloni Acked-by: Nicolas Ferre > --- > MAINTAINERS | 1 + > 1

[PATCH v2] ftrace/x86: fix x86-32 triple fault with graph tracing and suspend-to-ram

On x86-32, with CONFIG_FIRMWARE and multiple CPUs, if you enable function graph tracing and then suspend to RAM, it will triple fault and reboot when it resumes. The first fault happens when booting a secondary CPU: startup_32_smp() load_ucode_ap() prepare_ftrace_return()

Re: [PATCHv2] braille-console: Fix value returned by _braille_console_setup

On (03/26/17 22:47), Samuel Thibault wrote: > commit bbeddf52adc1 ("printk: move braille console support into > separate braille.[ch] files") introduced _braille_console_setup() > to outline the braille initialization code. There was however some > confusion over the value it was supposed to

Re: [PATCH v3 0/3] Add support for MyGica T230C DVB-T2 stick

On Montag, 6. März 2017 12:34:13 CEST Mauro Carvalho Chehab wrote: > Em Sat, 4 Mar 2017 03:23:42 +0200 > > Antti Palosaari escreveu: > > On 03/03/2017 08:35 PM, Brüns, Stefan wrote: > > > On Fr, 2017-02-17 at 01:55 +0100, Stefan Brüns wrote: > > >> The required command sequence for

Re: [PATCH 1/1] ethtool : added get_phy_stats,get_strings,get_sset_count

> > static int cpsw_get_sset_count(struct net_device *ndev, int sset) > > { > > + struct cpsw_priv *priv = netdev_priv(ndev); > > + int slave_no = cpsw_slave_index(priv); > > + int count; > > + > > switch (sset) { > > case ETH_SS_STATS: > > - return CPSW_STATS_LEN; > > +

Re: [RFD PATCH 3/5] sched/cpufreq_schedutil: make worker kthread be SCHED_DEADLINE

On Monday, March 27, 2017 06:13:36 PM Juri Lelli wrote: > On 27/03/17 19:05, Rafael J. Wysocki wrote: > > On Monday, March 27, 2017 06:01:34 PM Juri Lelli wrote: > > > On 27/03/17 18:50, Peter Zijlstra wrote: > > > > On Fri, Mar 24, 2017 at 02:08:58PM +, Juri Lelli wrote: > > > > > Worker

Re: [PATCH] regulator: core: Limit propagation of parent voltage count and list

Hello Matthias, On 03/27/2017 01:39 PM, Matthias Kaehlcke wrote: > Thanks for the reviews and testing! > You are welcome. [snip] + if (ops->get_voltage || ops->get_voltage_sel) >> >> It's valid to have a .get_voltage_sel callback without a .list_voltage? >> >> At least it seems

RE: [PATCH 2/2] pci-hyperv: Fix an atomic bug

> -Original Message- > From: devel [mailto:driverdev-devel-boun...@linuxdriverproject.org] On > Behalf Of k...@exchange.microsoft.com > Sent: Friday, March 24, 2017 11:07 AM > To: helg...@kernel.org; linux-...@vger.kernel.org; linux- > ker...@vger.kernel.org; de...@linuxdriverproject.org;

Re: [PATCH 1/4] regmap: irq: Fix lost interrupts by introducing handle_reread

On Wed, Mar 22, 2017 at 10:10:49AM -0700, Tony Lindgren wrote: > At least Motorola CPCAP PMIC needs it's device interrupts re-read > until there are no more interrupts. Otherwise the PMIC interrupt to > the SoC will eventually stop toggling. This seems to be a bug in the > CPCAP PMIC where it can

[PATCH V7 05/18] blk-throttle: configure bps/iops limit for cgroup in low limit

each queue will have a state machine. Initially queue is in LIMIT_LOW state, which means all cgroups will be throttled according to their low limit. After all cgroups with low limit cross the limit, the queue state gets upgraded to LIMIT_MAX state. For max limit, cgroup will use the limit

[PATCH v3] UBI: add debugfs file for tracking PEB state

From: Ben Shelton Add a file under debugfs to allow easy access to the erase count for each physical erase block on an UBI device. This is useful when debugging data integrity issues with UBIFS on NAND flash devices. Signed-off-by: Ben Shelton

Re: [PATCH v3 3/3] perf annotate: Fix missing number of samples

Em Mon, Mar 27, 2017 at 04:10:38PM +0900, Taeung Song escreveu: > If running 'perf annotate --stdio -l --show-total-period', > you can see a problem showing only zero '0' for number of samples. > > Before: > $ perf annotate --stdio -l --show-total-period > ... >0 :400816:

Re: Random guest crashes since 5c34d002dcc7 ("virtio_pci: use shared interrupts for virtqueues")

On Mon, 2017-03-27 at 19:05 +0200, Christoph Hellwig wrote: > Hi Mike, > > does the patch below fix that issue for you? Thanks, I'll give it a go in the A.M. BTW, WRT RT woes with $subject, I tried booting a generic kernel with threadirqs, and bingo, same deal, just a bit more painful than for

[PATCH V7 00/18] blk-throttle: add .low limit

Hi, cgroup still lacks a good iocontroller. CFQ works well for hard disk, but not much for SSD. This patch set try to add a conservative limit for blk-throttle. It isn't a proportional scheduling, but can help prioritize cgroups. There are several advantages we choose blk-throttle: - blk-throttle

Re: [PATCH] blkcg: allocate struct blkcg_gq outside request queue spinlock

On Sun, Mar 26, 2017 at 3:54 AM, Julia Lawall wrote: > Is an unlock needed before line 848? Or does blkg_lookup_check take care > of it? Unlock is not needed. On success, function returns with locks held. It is documented at line 805: "... This function returns with RCU

[PATCH V7 04/18] blk-throttle: add .low interface

Add low limit for cgroup and corresponding cgroup interface. To be consistent with memcg, we allow users configure .low limit higher than .max limit. But the internal logic always assumes .low limit is lower than .max limit. So we add extra bps/iops_conf fields in throtl_grp for userspace

Re: [PATCH 0/6] perf string handling fixes

Em Wed, Mar 22, 2017 at 03:06:18PM +0200, Tommi Rantala escreveu: > Hi, > > Some small perf fixes, mostly caught with valgrind. > > The last patch is a simplification: it is easier to open /proc/self/exe > than /proc/$pid/exe. Thanks, applied the series. - Arnaldo > Tommi Rantala (6): >

Re: [BUG nohz]: wrong user and system time accounting

On Mon, 27 Mar 2017 09:56:47 +0800 Wanpeng Li wrote: > Actually after I bisect, the first bad commit is ff9a9b4c4334 ("sched, > time: Switch VIRT_CPU_ACCOUNTING_GEN to jiffy granularity"). The bug > can be reproduced readily if CONFIG_CONTEXT_TRACKING_FORCE is true, > then

Re: [RFD PATCH 3/5] sched/cpufreq_schedutil: make worker kthread be SCHED_DEADLINE

On Fri, Mar 24, 2017 at 02:08:58PM +, Juri Lelli wrote: > Worker kthread needs to be able to change frequency for all other > threads. > > Make it special, just under STOP class. *yuck* ;-) So imagine our I2C/SPI bus is 'busy' and its mutex taken, then this 'soecial' task will need to boost

Re: [PATCH V2 1/2] x86/msr: add msr_set/clear_bit_on_cpu/cpus access functions

On Mon, Mar 27, 2017 at 08:47:37AM -0700, kan.li...@intel.com wrote: > From: Kan Liang > > Having msr_set/clear_bit on many cpus or given CPU can avoid extra > unnecessory IPIs How does that happen? You have smp_call_function_many() sending IPIs to each CPU in the mask.

[PATCH] net: ipconfig: fix ic_close_devs() use-after-free

Our chosen ic_dev may be anywhere in our list of ic_devs, and we may free it before attempting to close others. When we compare d->dev and ic_dev->dev, we're potentially dereferencing memory returned to the allocator. This causes KASAN to scream for each subsequent ic_dev we check. As there's a

Re: [RFC PATCH v0.2] PCI: Add support for tango PCIe host bridge

On 27/03/17 16:53, Mason wrote: > On 24/03/2017 19:47, Marc Zyngier wrote: > >> On 23/03/17 17:03, Mason wrote: >> >>> On 23/03/2017 15:22, Marc Zyngier wrote: >>> On 23/03/17 13:05, Mason wrote: > + writel_relaxed(status, pcie->msi_status); /* clear IRQs */ Why isn't this

Re: [PATCH] usb-musb: keep VBUS on when device is disconnected

* Moreno Bartalucci [170327 09:23]: > If I understood your patch, however, if the device (anyone, not just my one) > takes longer to switch, VBUS is deasserted anyway. Yeah some of them can take at least 10 seconds even to enumerate. So probably we need to have

[PATCH] HID: sony: remove redundant check for -ve err

From: Colin Ian King err is being checked for failure each time it is being updated so this err check is totally redundant and can be removed Detected with CoverityScan, CID#1420665 ("Logically dead code") Signed-off-by: Colin Ian King ---

[PATCH V7 12/18] blk-throttle: make bandwidth change smooth

When cgroups all reach low limit, cgroups can dispatch more IO. This could make some cgroups dispatch more IO but others not, and even some cgroups could dispatch less IO than their low limit. For example, cg1 low limit 10MB/s, cg2 limit 80MB/s, assume disk maximum bandwidth is 120M/s for the

[PATCH V7 17/18] blk-throttle: add a mechanism to estimate IO latency

User configures latency target, but the latency threshold for each request size isn't fixed. For a SSD, the IO latency highly depends on request size. To calculate latency threshold, we sample some data, eg, average latency for request size 4k, 8k, 16k, 32k .. 1M. The latency threshold of each

  1   2   3   4   5   6   7   8   9   10   >