Also eliminate duplicated debug code by moving it into the core driver.
Cc: Thomas Bogendoerfer
Cc: Chris Zankel
Signed-off-by: Finn Thain
---
Only the sonic.[ch] and macsonic.c changes have been tested. The other
changes are similar but untested.
---
drivers/net/ethernet/natsemi/jazzsonic.c |
On Fri, 6 Oct 2017 09:32:52 +0900
Masami Hiramatsu wrote:
> I think using ftrace gives you lower latency, but you need to depend on
> CONFIG_FUNCTION_TRACER instead of CONFIG_KPROBES.
Which shouldn't be an issue, since all distros now have that enabled.
-- Steve
On Thu, Oct 05, 2017 at 01:42:09PM -0500, Bjorn Helgaas wrote:
>On Thu, Oct 05, 2017 at 11:05:12PM +0800, Wei Yang wrote:
>> On Wed, Oct 4, 2017 at 5:15 AM, Bjorn Helgaas wrote:
>> > [+cc Alex, Gavin, Wei]
>> >
>> > On Fri, Sep 29, 2017 at 10:49:38PM -0700, Govindarajulu Varadarajan wrote:
>> >> C
Signed-off-by: Finn Thain
---
drivers/net/ethernet/cirrus/mac89x0.c | 31 ---
1 file changed, 31 deletions(-)
diff --git a/drivers/net/ethernet/cirrus/mac89x0.c
b/drivers/net/ethernet/cirrus/mac89x0.c
index f910f0f386d6..4fd72c1a69f5 100644
--- a/drivers/net/ethernet
This patch series fixes some logging bugs and adds some missing message
severity levels.
There are also cleanup patches for dead code and some Kconfig cruft.
Custom debug message logging is converted to netif_* calls to reduce
code duplication.
All up, about 150 lines of code are eliminated.
Th
On Mon, Oct 2, 2017 at 10:32 PM, Hannes Reinecke wrote:
> On 09/27/2017 09:33 AM, Gavin Guo wrote:
>> There is a problem in the latest upstream kernel with the device:
>>
>> $ grep -i lsi lspci
>> 03:00.0 Serial Attached SCSI controller [0107]: LSI Logic / Symbios
>> Logic SAS1068 PCI-X Fusion-MPT
The kvm slabs can consume a significant amount of system memory
and indeed in our production environment we have observed that
a lot of machines are spending significant amount of memory that
can not be left as system memory overhead. Also the allocations
from these slabs can be triggered directly
From: Bjorn Andersson
Date: Wed, 4 Oct 2017 20:51:05 -0700
> +/**
> + * struct qrtr_hdr_v2 - (I|R)PCrouter packet header later versions
> + * @version: protocol version
> + * @type: packet type; one of QRTR_TYPE_*
> + * @flags: bitmask of QRTR_FLAGS_*
> + * @optlen: length of optional header dat
In preparation of adding irqsoff and preemptsoff enable and disable trace
events, move required functions and code to make it easier to add these events
in a later patch. This patch is just code movement and no functional change.
Cc: Steven Rostedt
Cc: Peter Zijlstra
Cc: kernel-t...@android.com
Preempt and irq trace events can be used for tracing the start and
end of an atomic section which can be used by a trace viewer like
systrace to graphically view the start and end of an atomic section and
correlate them with latencies and scheduling issues.
This also serves as a prelude to using s
These patches add trace events support for preempt and irq disable/enable
events.
Here's an example of how Android's systrace will be using it to show atomic
sections as a gantt chart: http://imgur.com/download/TZplEVp
Other advantages of this initial work could be rewriting of preemptirqs off
tra
From: Stephen Hemminger
When investigating performance, it is useful to be able to look at
the number of host and guest events per-channel. This is equivalent
to per-device interrupt statistics.
Signed-off-by: Stephen Hemminger
Signed-off-by: K. Y. Srinivasan
---
Documentation/ABI/stable/sysf
From: Stephen Hemminger
Make sure and initialize reserved fields in messages to host,
rather than passing stack junk.
Signed-off-by: Stephen Hemminger
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/channel.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/hv/channel.c b/drivers/
From: "K. Y. Srinivasan"
Hyper-V allows the guest to report panic and the guest can pass additional
information. All this is logged on the host. Currently Linux is passing back
information that is not particularly useful. Make the following changes:
1. Windows uses crash MSR P0 to report bugchec
From: "K. Y. Srinivasan"
Miscellaneous enhancements and fixes.
K. Y. Srinivasan (1):
Drivers: hv: vmbus: Make pannic reporting to be more useful
Stephen Hemminger (2):
Drivers: hv: vmbus: Expose per-channel interrupts and events counters
vmbus: initialize reserved fields in messages
Doc
Abdul Haleem writes:
> Hi,
>
> linux-next kernel panic while DLPAR CPU add/remove operation in a loop.
>
> Test: CPU hot-unplug
> Machine Type: Power8 PowerVM LPAR
> kernel: 4.14.0-rc2-next-20170928
> gcc : 5.2.1
>
> trace logs
> --
> cpu 10 (hwid 10) Ready to die...
> cpu 11 (hwid 11) Re
On Thu, 5 Oct 2017 16:35:22 -0700
Kees Cook wrote:
> On Thu, Oct 5, 2017 at 4:13 PM, Masami Hiramatsu wrote:
> > Hi,
> >
> > This series abolishes jprobe APIs and remove or disable related
> > code. This is a preparation of removing all jprobe code (including
> > kprobe's break_handler.)
> > I'm
Daniel Drake :
[...]
> Also, is there a standard behaviour defined for ethernet drivers
> regarding wake-on-LAN? r8169 appears to enable wake-on-LAN by default
> if it believes the hardware is capable of it,
If so it isn't its designed behavior.
The r8169 driver does not enable specific WoL even
Hi Neil,
El Fri, Oct 06, 2017 at 10:58:59AM +1100 NeilBrown ha dit:
> On Thu, Oct 05 2017, Matthias Kaehlcke wrote:
>
> > The raid10 driver can't be built with clang since it uses a variable
> > length array in a structure (VLAIS):
> >
> > drivers/md/raid10.c:4583:17: error: fields must have a c
On Thu, Oct 5, 2017 at 4:58 PM, Steven Rostedt wrote:
> On Thu, 5 Oct 2017 16:35:22 -0700
> Kees Cook wrote:
>
>> > As far as I can see, tcp probe, dccp probe, sctp probe and lkdtm
>> > are using jprobe to probe function. Please consider to migrate.
>>
>> I'm happy to do so, but I'm quite unfamil
On Thu, Oct 05 2017, Matthias Kaehlcke wrote:
> The raid10 driver can't be built with clang since it uses a variable
> length array in a structure (VLAIS):
>
> drivers/md/raid10.c:4583:17: error: fields must have a constant size:
> 'variable length array in structure' extension will never be sup
A new feature Range Selector (RS) has been added to GIC specification
in order to support more than 16 CPUs at affinity level 0. New fields
are introduced in SGI system registers (ICC_SGI0R_EL1, ICC_SGI1R_EL1
and ICC_ASGI1R_EL1) to relax an artificial limit of 16 at level 0.
- A new RSS field in I
On Thu, 5 Oct 2017 16:35:22 -0700
Kees Cook wrote:
> > As far as I can see, tcp probe, dccp probe, sctp probe and lkdtm
> > are using jprobe to probe function. Please consider to migrate.
>
> I'm happy to do so, but I'm quite unfamiliar with how to do this (I
> didn't write lkdtm's jprobe code
On Thursday, October 05, 2017, Nicolas Pitre wrote:
> Do you have the same amount of free memory once booted in both cases?
Yes, almost exactly the same, so obvious it must be working the same for
both cases. That's enough evidence for me.
Thanks.
Chris
Removing a comment that duplicates definitions for pci_power_t
enumeration, and pointing to the relevant header file (current comment
is also missing PCI_POWER_ERROR).
Signed-off-by: Matthew Giassa
---
drivers/staging/rtlwifi/pci.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
dif
On Thu, 05 Oct 2017 18:18:54 -0500
Scott Wood wrote:
> On Thu, 2017-10-05 at 08:50 -0400, Steven Rostedt wrote:
> > On Wed, 04 Oct 2017 15:24:23 -0500
> > Scott Wood wrote:
> >
> > > It should also be noted that ktest.pl only depends on config-
> > > bisect.pl
> > > if a config bisect is bein
Explicitly casting pci_power_t types to resolve sparse warnings (shown
below).
Also fixing a related logging bug where pci_power_t is cast to unsigned
(can be negative, i.e. PCI_POWER_ERROR).
Original sparse report:
drivers/staging/irda/drivers//vlsi_ir.c:170:51: warning: cast from
restricted pc
On Thu, Oct 5, 2017 at 7:21 AM, Tejun Heo wrote:
> On Wed, Oct 04, 2017 at 05:54:17PM -0700, Kees Cook wrote:
>> In preparation for unconditionally passing the struct timer_list pointer to
>> all timer callbacks, switch to using the new timer_setup() and from_timer()
>> to pass the timer pointer e
Some CPUID features depend on other features. Currently it's
possible to to clear dependent features, but not clear the base features,
which can cause various interesting problems.
This patch implements a generic table to describe dependencies
between CPUID features, to be used by all code that cl
On Thu, Oct 5, 2017 at 4:13 PM, Masami Hiramatsu wrote:
> Hi,
>
> This series abolishes jprobe APIs and remove or disable related
> code. This is a preparation of removing all jprobe code (including
> kprobe's break_handler.)
> I'm not so sure how many jprobe users still exists, but
> please migra
On Thu, Sep 28, 2017 at 03:51:24PM -0700, Vikas Manocha wrote:
> This patch removes the extra compatibility string "st,stm32-usart" to
> avoid confusion, save some time & space.
I'm confused why you don't need it anymore. I thought the h/w blocks
were configured differently.
>
> Signed-off-by:
On Wed, Oct 04, 2017 at 08:50:49AM +0200, Laurent Dufour wrote:
> On 25/09/2017 18:27, Alexei Starovoitov wrote:
> > On Mon, Sep 18, 2017 at 12:15 AM, Laurent Dufour
> > wrote:
> >> Despite the unprovable lockdep warning raised by Sergey, I didn't get any
> >> feedback on this series.
> >>
> >> Is
Only try to clean up the svm page request irq if one has
been assigned. Also clear pr_irq in the error path if irq request
fails.
Signed-off-by: Jerry Snitselaar
---
drivers/iommu/intel-svm.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/iommu/intel-svm.c b
On Thu, Oct 05, 2017 at 01:08:20PM +0200, Wolfram Sang wrote:
> On Mon, Oct 02, 2017 at 04:23:43PM +0200, Gregory CLEMENT wrote:
> > Hi Wolfram,
> >
> > On ven., sept. 29 2017, Kalyan Kinthada
> > wrote:
> >
> > > This commit modifies the documentation for
> > > "marvell,mv78230-a0-i2c" compa
On Thu, Oct 5, 2017 at 4:28 PM, Joel Fernandes wrote:
> Hi Peter,
>
> On Wed, Oct 4, 2017 at 9:01 AM, Peter Zijlstra wrote:
>> On Fri, Sep 29, 2017 at 02:22:45PM -0700, Joel Fernandes wrote:
[...]
>>> EXPORT_SYMBOL(trace_hardirqs_off);
>>>
>>> __visible void trace_hardirqs_on_caller(unsigned lo
Hi Peter,
On Wed, Oct 4, 2017 at 9:01 AM, Peter Zijlstra wrote:
> On Fri, Sep 29, 2017 at 02:22:45PM -0700, Joel Fernandes wrote:
[...]
>> + */
>> +static DEFINE_PER_CPU(int, tracing_irq_cpu);
>> +
>> #if defined(CONFIG_TRACE_IRQFLAGS) && !defined(CONFIG_PROVE_LOCKING)
>> void trace_hardirqs_on
Added functionality to read LPIT table, which provides:
- Sysfs interface to read residency counters via
/sys/devices/system/cpu/cpuidle/low_power_idle_cpu_residency_us
/sys/devices/system/cpu/cpuidle/low_power_idle_system_residency_us
Here the count "low_power_idle_cpu_residency_us" shows the ti
On Thu, Sep 28, 2017 at 02:11:27PM +0100, Sudeep Holla wrote:
> This patch adds ARM MHU specific mailbox client bindings to support
> SCMI. Since SCMI specification just requires doorbell mechanism from
> mailbox controllers, we add mailbox data to specify the doorbell bit(s).
>
> Cc: Rob Herring
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
dev.2017.10.05a
head: 39ae2675aa536e6ef9d334fe9097d1e2c6b25fbc
commit: 7e3675cc18bbf4d84f60bfc02ff563ae3764ad35 [32/34] locking/barriers: Kill
lockless_dereference
config: h8300-h8300h-sim_defconfig (attached as .conf
On Thu, 2017-10-05 at 08:50 -0400, Steven Rostedt wrote:
> On Wed, 04 Oct 2017 15:24:23 -0500
> Scott Wood wrote:
>
> > It should also be noted that ktest.pl only depends on config-
> > bisect.pl
> > if a config bisect is being performed, so other ktest.pl functions
> > still
> > work standalone.
Remove jprobe related documentations from kprobes.txt.
It also add some migration advice for the people who still
using jprobe.
Signed-off-by: Masami Hiramatsu
---
Documentation/kprobes.txt | 153 +++--
1 file changed, 51 insertions(+), 102 deletions(-)
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
Cc: Jens Axboe
Cc: Michal Hocko
Cc: Andrew Morton
Cc: Jan Kara
Cc: Johannes Weiner
Cc: Nicholas Piggin
Remove jprobe sample module because jprobe is deprecated.
Signed-off-by: Masami Hiramatsu
---
samples/kprobes/Makefile |2 +
samples/kprobes/jprobe_example.c | 67 --
2 files changed, 1 insertion(+), 68 deletions(-)
delete mode 100644 samples/kp
Disable jprobe test code because jprobe is deprecated.
This code will be completely removed when jprobe code
is removed.
Signed-off-by: Masami Hiramatsu
---
kernel/test_kprobes.c |9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/kernel/test_kprobes.c b/kernel/test_kp
Abolish jprobe APIs and comment out the jprobe API function
code. This is a preparation of removing all jprobe related
code (including kprobe's break_handler)
Nowadays ftrace and other tracing features are enough matured
to replace jprobe use-cases. Users can safely use ftrace and
perf probe etc.
Use ENOTSUPP instead of ENOSYS because ENOSYS is reserved
only for invalid syscall number.
Signed-off-by: Masami Hiramatsu
---
include/linux/kprobes.h | 16
kernel/kprobes.c|4 ++--
2 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/include/linux/kpro
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
Cc: Jens Axboe
Cc: "Ed L. Cashin"
Cc: linux-bl...@vger.kernel.org
Cc: Thomas Gleixner
Signed-off-by: Kees
2017-10-06 2:14 GMT+08:00 Radim Krčmář :
> 2017-10-05 07:35-0700, Wanpeng Li:
>> From: Wanpeng Li
>>
>> The description in the Intel SDM of how the divide configuration
>> register is used: "The APIC timer frequency will be the processor's bus
>> clock or core crystal clock frequency divided by th
Hi,
This series abolishes jprobe APIs and remove or disable related
code. This is a preparation of removing all jprobe code (including
kprobe's break_handler.)
I'm not so sure how many jprobe users still exists, but
please migrate your tool to trace-event or perf-probe.
As we discussed this threa
On Thu, Sep 28, 2017 at 03:07:27PM +0200, Andrzej Hajda wrote:
> These bindings allows to describe most known standard USB connectors
> and it should be possible to extend it if necessary.
> USB connectors, beside USB can be used to route other protocols,
> for example UART, Audio, MHL. In such cas
On Fri, Oct 06, 2017 at 12:41:56AM +0200, Thomas Gleixner wrote:
> On Thu, 5 Oct 2017, Andi Kleen wrote:
> > +/*
> > + * Table of CPUID features that depend on others.
> > + *
> > + * This only includes dependencies that can be usefully disabled, not
> > + * features part of the base set (like FPU)
On Thu, Oct 05, 2017 at 03:31:05PM -0700, Linus Torvalds wrote:
> On Thu, Oct 5, 2017 at 1:57 PM, Al Viro wrote:
> >
> > AFAICS, the real bug here is in hugetlbfs; that's where obscene values in
> > ->f_bsize come from. IMO all that code in put_compat_statfs64() should be
> > replaced with
> >
Add Intel VT-d ops to the generic iommu_bind_pasid_table API
functions.
The primary use case is for direct assignment of SVM capable
device. Originated from emulated IOMMU in the guest, the request goes
through many layers (e.g. VFIO). Upon calling host IOMMU driver, caller
passes guest PASID tabl
Virtual IOMMU was proposed to support Shared Virtual Memory (SVM)
use in the guest:
https://lists.gnu.org/archive/html/qemu-devel/2016-11/msg05311.html
As part of the proposed architecture, when an SVM capable PCI
device is assigned to a guest, nested mode is turned on. Guest owns the
first level
DMA faults can be detected by IOMMU at device level. Adding a pointer
to struct device allows IOMMU subsystem to report relevant faults
back to the device driver for further handling.
For direct assigned device (or user space drivers), guest OS holds
responsibility to handle and respond per device
When SRIOV VF device IOTLB is invalidated, we need to provide
the PF source SID such that IOMMU hardware can gauge the depth
of invalidation queue which is shared among VFs. This is needed
when device invalidation throttle (DIT) capability is supported.
Signed-off-by: Jacob Pan
---
drivers/iommu
Hi All,
Shared virtual memory (SVM) space between devices and applications can
reduce programming complexity and enhance security. To enable SVM in
the guest, i.e. shared guest application address space and physical
device DMA address, IOMMU driver must provide some new functionalities.
This patc
Device faults detected by IOMMU can be reported outside IOMMU
subsystem. This patch intends to provide a generic device
fault data such that device drivers can communicate IOMMU faults
without model specific knowledge.
The assumption is that model specific IOMMU driver can filter and
handle most o
Signed-off-by: Jacob Pan
---
drivers/iommu/dmar.c| 53 ++---
drivers/iommu/intel-iommu.c | 3 ++-
include/linux/intel-iommu.h | 10 +++--
3 files changed, 60 insertions(+), 6 deletions(-)
diff --git a/drivers/iommu/dmar.c b/drivers/iommu/dmar.
Currently, dmar fault IRQ handler does nothing more than rate
limited printk, no critical hardware handling need to be done
in IRQ context.
Convert it to threaded IRQ would allow fault processing that
requires process context. e.g. find out offending device based
on source ID in the fault rasons.
This patch adds Intel VT-d specific function to implement
iommu passdown invalidate API.
The use case is for supporting caching structure invalidation
of assigned SVM capable devices. Emulated IOMMU exposes queue
invalidation capability and passes down all descriptors from the guest
to the physica
Allow both intel-iommu.c and dmar.c to access device_domain_info.
Prepare for additional per device arch data used in TLB flush function
Signed-off-by: Jacob Pan
---
drivers/iommu/intel-iommu.c | 18 --
include/linux/intel-iommu.h | 19 +++
2 files changed, 19 ins
Traditionally, device specific faults are detected and handled within
their own device drivers. When IOMMU is enabled, faults such as DMA
related transactions are detected by IOMMU. There is no generic
reporting mechanism to report faults back to the in-kernel device
driver or the guest OS in case
Currently, when device DMA faults are detected by IOMMU the fault
reasons are printed but the driver of the offending device is
involved in fault handling.
This patch uses per device fault reporting API to send fault event
data for further processing.
Offending device is identified by the source ID
If the source device of a page request has its PASID table pointer
bond to a guest, the first level page tables are owned by the guest.
In this case, we shall let guest OS to manage page fault.
This patch uses the IOMMU fault notification API to send notifications,
possibly via VFIO, to the guest
With the introduction of generic IOMMU device fault reporting API, we
can replace the private fault callback functions with standard function
and event data.
Signed-off-by: Jacob Pan
---
drivers/iommu/intel-svm.c | 7 +--
include/linux/intel-svm.h | 20 +++-
2 files changed,
From: "Liu, Yi L"
When an SVM capable device is assigned to a guest, the first level page
tables are owned by the guest and the guest PASID table pointer is
linked to the device context entry of the physical IOMMU.
Host IOMMU driver has no knowledge of caching structure updates unless
the guest
This patch adds page response support for Intel VT-d.
Generic response data is taken from the IOMMU API
then parsed into VT-d specific response descriptor format.
Signed-off-by: Jacob Pan
---
drivers/iommu/intel-iommu.c | 30 ++
1 file changed, 30 insertions(+)
diff
When nested translation is turned on and guest owns the
first level page tables, device page request can be forwared
to the guest for handling faults. As the page response returns
by the guest, IOMMU driver on the host need to process the
response which informs the device and completes the page req
On Thu, Jun 23, 2016 at 02:47:34PM +0100, David Howells wrote:
>
> Here's a set of patches that provides keyctl access for asymmetric keys,
> including a query function, and functions to do encryption, decryption,
> signature creation and signature verification.
>
> I've added a PKCS#8 asymmetric
On Thu, Oct 5, 2017 at 3:07 PM, Jens Axboe wrote:
> Yes, it's not impossible, I just usually prefer not to. For this case, I
> just setup a for-4.15/timer, that is the current block branch with -rc3
> pulled in. I applied the two patches for floppy and amiflop, I'm
> assuming Kees will respin the
Kees Cook writes:
> On Thu, Oct 5, 2017 at 10:21 AM, Abdul Haleem
> wrote:
>> Hi,
>>
>> CPU off on in a loop for single cpu results in kernel panic for
>> 4.14.0-rc2-next-20170929
>>
>> Machine: Power 8 PowerVM LPAR
>> Kernel: 4.14.0-rc2-next-20170929
>> gcc: 5.1.1
>> config : attached
>>
>> Ste
On Thu, 5 Oct 2017 22:19:15 + (UTC)
Mathieu Desnoyers wrote:
> AFAIU the scheduler rq->lock is held while preemption is disabled.
> synchronize_sched() is used here to ensure that all pre-existing
> preempt-off critical sections have completed.
>
> So saying that we use synchronize_sched() t
From: Rafael J. Wysocki
Commit 7aa7a0360a66 (PM: docs: Delete the obsolete states.txt
document) forgot to update kernel-parameters.txt with a reference
to the new sleep-states.rst document and it still points to
states.txt that was dropped, so fix it now.
Fixes: 7aa7a0360a66 (PM: docs: Delete th
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm-4.14-rc4
with top-most commit ca935f8e769c3e36e1b6339cc527a25c49f4d624
Merge branch 'pm-sleep'
on top of commit 9e66317d3c92ddaab330c125dfe9d06eee268aff
Linux 4.14-rc3
to receive a p
On Thu, 5 Oct 2017, Andi Kleen wrote:
> +/*
> + * Table of CPUID features that depend on others.
> + *
> + * This only includes dependencies that can be usefully disabled, not
> + * features part of the base set (like FPU).
> + */
> +const static struct cpuid_dep cpuid_deps[] = {
> + { X86_FEAT
Threads targeting the same VM but which belong to different thread
groups is a tricky case. It has a few consequences:
It turns out that we cannot rely on get_nr_threads(p) to count the
number of threads using a VM. We can use
(atomic_read(&mm->mm_users) == 1 && get_nr_threads(p) == 1)
instead to
On Thu, Sep 28, 2017 at 03:49:28AM +0200, Stefan Brüns wrote:
> Unit-names must not start with a leading 0.
>
> Signed-off-by: Stefan Brüns
>
> ---
>
> Changes in v4:
> - Split minor fix in devicetree example from patch 6/10
>
> Changes in v3: None
> Changes in v2: None
>
> Documentation/dev
Architectures without membarrier hooks don't need to emit the
empty membarrier_arch_switch_mm() static inline when
CONFIG_MEMBARRIER=y.
Adapt the CONFIG_MEMBARRIER=n counterpart to only emit the empty
membarrier_arch_switch_mm() for architectures with membarrier hooks.
Reported-by: Nicholas Piggi
On Thu, Sep 28, 2017 at 08:17:20AM +0800, Chunfeng Yun wrote:
> Remove optional pinctrls due to using FORCE/RG_IDDIG to implement
> manual switch function.
Another not backwards compatible change. Please explain why that is
okay.
>
> Signed-off-by: Chunfeng Yun
> ---
> .../devicetree/bindings
- On Oct 5, 2017, at 5:40 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> Threads targeting the same VM but which belong to different thread
> groups is a tricky case. It has a few consequences:
>
> It turns out that we cannot rely on get_nr_threads(p) to count the
> number of
On Thu, Sep 28, 2017 at 08:17:18AM +0800, Chunfeng Yun wrote:
> Add a new optional property to disable u3ports
>
> Signed-off-by: Chunfeng Yun
> ---
> .../devicetree/bindings/usb/mediatek,mtu3.txt |2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindin
On Thu, Oct 5, 2017 at 1:57 PM, Al Viro wrote:
>
> AFAICS, the real bug here is in hugetlbfs; that's where obscene values in
> ->f_bsize come from. IMO all that code in put_compat_statfs64() should be
> replaced with
> if (kbuf->bsize != (u32)kbuf->bsize)
> return -EOVERFL
On Wed, Sep 27, 2017 at 04:03:39PM +0200, Alexandre Belloni wrote:
> Document currently undocumented bindings.
>
> Rob, as discussed, all of this can probably go through your tree.
>
> Changes in v2:
> - made a proper series
> - fixed sirf2 example
> - listed the ds1307 compatible that support
On Wed, Sep 27, 2017 at 06:44:05PM +0800, Chen Zhong wrote:
> This patch adds the device tree binding documentation for the MediaTek
> pmic keys found on PMIC MT6397/MT6323.
>
> Signed-off-by: Chen Zhong
> ---
> .../devicetree/bindings/input/mtk-pmic-keys.txt| 43
>
>
On Fri, Oct 6, 2017 at 6:03 AM, Kees Cook wrote:
> When available, CONFIG_KERNEL_RWX should be default-enabled for PPC64.
> On PPC32, there is a performance trade-off.
>
> Cc: Benjamin Herrenschmidt
> Cc: Paul Mackerras
> Cc: Michael Ellerman
> Cc: Christophe LEROY
> Cc: Balbir Singh
> Cc: li
On Wed, Sep 27, 2017 at 06:44:04PM +0800, Chen Zhong wrote:
> This patch adds the device tree binding documentation for common
> keyboard.
>
> Signed-off-by: Chen Zhong
> ---
> Documentation/devicetree/bindings/input/keys.txt |8
> 1 file changed, 8 insertions(+)
> create mode 1006
The allocations from filp and names kmem caches can be directly
triggered by user space applications. A buggy application can
consume a significant amount of unaccounted system memory. Though
we have not noticed such buggy applications in our production
but upon close inspection, we found that a lo
> Looking at this some more, why can't mdio-mux-mmio be used?
Hi Rob
That was my first thought. And then i dug into the details. The mux is
more than just a couple of bits in an address space. Clocks needs to
be enabled/disabled, and the MAC needs a reset, when the mux changes.
So the mux needs i
On Wed, Sep 27, 2017 at 05:23:05PM +0800, Chunfeng Yun wrote:
> Remove dummy clocks for usb wakeup and add optional ones for
> MCU_BUS_CK and DMA_BUS_CK.
>
> Signed-off-by: Chunfeng Yun
> ---
> .../devicetree/bindings/usb/mediatek,mtk-xhci.txt | 18 --
> 1 file changed, 8 inse
- On Oct 5, 2017, at 6:02 PM, Andrea Parri parri.and...@gmail.com wrote:
> On Thu, Oct 05, 2017 at 04:02:06PM +, Mathieu Desnoyers wrote:
>> - On Oct 5, 2017, at 8:12 AM, Peter Zijlstra pet...@infradead.org wrote:
>>
>> > On Wed, Oct 04, 2017 at 02:37:53PM -0700, Paul E. McKenney wrot
On Wed, Sep 27, 2017 at 05:23:04PM +0800, Chunfeng Yun wrote:
> Add a new optional property to disable u3ports
>
> Signed-off-by: Chunfeng Yun
> ---
> .../devicetree/bindings/usb/mediatek,mtk-xhci.txt |2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindin
On Wed, Sep 27, 2017 at 02:29:08PM +0530, Manu Gautam wrote:
> Update compatible string and clock names for QMP version V3
> USB PHY.
>
> Signed-off-by: Manu Gautam
> ---
> Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt | 6 +-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> di
Hi,
On 10/05/2017 07:54 AM, Will Deacon wrote:
Hi all,
This patch series reworks bits of the qrwlock code that it can be used
to replace the asm rwlocks currently implemented for arm64. The structure
of the series is:
Patches 1-3 : Work WFE into qrwlock using atomic_cond_read_acquire so
On Thu, Oct 5, 2017 at 11:48 PM, Srinivas Pandruvada
wrote:
> On Thu, 2017-10-05 at 22:56 +0200, Rafael J. Wysocki wrote:
>> On Thursday, October 5, 2017 10:43:33 PM CEST Srinivas Pandruvada
>> wrote:
>> >
>> > On Thu, 2017-10-05 at 21:39 +0300, Andy Shevchenko wrote:
>> > >
>> > > On Thu, Oct 5,
On Wed, Sep 27, 2017 at 02:29:04PM +0530, Manu Gautam wrote:
> Update generic compatible string for QUSB2 V2 PHY. This will allow
> all targets using QUSB2 V2 use same string.
>
> Signed-off-by: Manu Gautam
> ---
> Documentation/devicetree/bindings/phy/qcom-qusb2-phy.txt | 5 -
> 1 file chan
On Wed, Sep 27, 2017 at 09:50:46PM -0700, Florian Fainelli wrote:
>
>
> On 09/27/2017 07:12 AM, Andrew Lunn wrote:
> > On Wed, Sep 27, 2017 at 09:34:14AM +0200, Corentin Labbe wrote:
> >> Each child node of an MDIO node is scanned as a PHY when calling
> >> of_mdiobus_register() givint the follow
On 10/05/2017 03:53 PM, Thomas Gleixner wrote:
> Jens,
>
> On Thu, 5 Oct 2017, Jens Axboe wrote:
>> On 10/05/2017 01:23 PM, Thomas Gleixner wrote:
>>> Come on. You know very well that a prerequisite for global changes which is
>>> not yet used in Linus tree can get merged post merge windew in orde
Linus,
please consider to pull the latest core-watchdog-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
core-watchdog-for-linus
The watchdog (hard/softlockup detector) code is pretty much broken in its
current state. The patch series addresses this by remov
On Thu, Oct 05, 2017 at 11:28:47AM -0700, Matthias Kaehlcke wrote:
> The raid10 driver can't be built with clang since it uses a variable
> length array in a structure (VLAIS):
>
> drivers/md/raid10.c:4583:17: error: fields must have a constant size:
> 'variable length array in structure' extens
101 - 200 of 958 matches
Mail list logo
