[PATCH v10 23/26] KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2

From: Pierre Morel When the guest schedules a SIE with a FORMAT-0 CRYCB, we are able to schedule it in the host with a FORMAT-2 CRYCB if the host uses FORMAT-2 Signed-off-by: Pierre Morel Signed-off-by: Tony Krowiak --- arch/s390/kvm/vsie.c |4 +++- 1 files changed, 3 insertions(+), 1 del

[PATCH v10 24/26] KVM: s390: device attrs to enable/disable AP interpretation

From: Tony Krowiak Introduces two new VM crypto device attributes (KVM_S390_VM_CRYPTO) to enable or disable AP instruction interpretation from userspace via the KVM_SET_DEVICE_ATTR ioctl: * The KVM_S390_VM_CRYPTO_ENABLE_APIE attribute enables hardware interpretation of AP instructions executed

[PATCH v10 26/26] s390: doc: detailed specifications for AP virtualization

From: Tony Krowiak This patch provides documentation describing the AP architecture and design concepts behind the virtualization of AP devices. It also includes an example of how to configure AP devices for exclusive use of KVM guests. Signed-off-by: Tony Krowiak Reviewed-by: Halil Pasic Sign

[PATCH v10 25/26] KVM: s390: CPU model support for AP virtualization

From: Tony Krowiak Introduces a new CPU model feature and two CPU model facilities to support AP virtualization for KVM guests. CPU model feature: The KVM_S390_VM_CPU_FEAT_AP feature indicates that AP instructions are available on the guest. This feature will be enabled by the kernel only if th

[PATCH v10 21/26] KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1

From: Pierre Morel When the guest schedules a SIE with a FORMAT-0 CRYCB, we are able to schedule it in the host with a FORMAT-1 CRYCB if the host uses FORMAT-1 or FORMAT-0. Signed-off-by: Pierre Morel Signed-off-by: Tony Krowiak --- arch/s390/kvm/vsie.c | 14 ++ 1 files changed,

[PATCH v3 2/3] ASoC: enable interrupt after dma buffer initialization

In snd_hdac_bus_init_chip(), we enable interrupt before snd_hdac_bus_init_cmd_io() initializing dma buffers. If irq has been acquired and irq handler uses the dma buffer, kernel may crash when interrupt comes in. Fix the problem by postponing enabling irq after dma buffer initialization. And warn

[PATCH v10 20/26] KVM: s390: vsie: allow CRYCB FORMAT-0

From: Pierre Morel When the host and the guest both use a FORMAT-0 CRYCB, we copy the guest's FORMAT-0 APCB to a shadow CRYCB for use by vSIE. Signed-off-by: Pierre Morel Signed-off-by: Tony Krowiak --- arch/s390/kvm/vsie.c | 20 +--- 1 files changed, 17 insertions(+), 3 del

[PATCH v10 18/26] KVM: s390: vsie: Allow CRYCB FORMAT-2

From: Pierre Morel When the guest and the host both use CRYCB FORMAT-2, we copy the guest's FORMAT-1 APCB to a FORMAT-1 shadow APCB. This patch also cleans up the shadow_crycb() function. Signed-off-by: Pierre Morel Signed-off-by: Tony Krowiak --- arch/s390/kvm/vsie.c | 114

[PATCH v10 19/26] KVM: s390: vsie: allow CRYCB FORMAT-1

From: Pierre Morel When the host and guest both use a FORMAT-1 CRYCB, we copy the guest's FORMAT-0 APCB to a shadow CRYCB for use by vSIE. Signed-off-by: Pierre Morel Signed-off-by: Tony Krowiak --- arch/s390/kvm/vsie.c | 19 +++ 1 files changed, 19 insertions(+), 0 deletion

[PATCH v10 17/26] KVM: s390: vsie: Make use of CRYCB FORMAT2 clear

From: Pierre Morel The comment preceding the shadow_crycb function is misleading, we effectively accept FORMAT2 CRYCB in the guest. When using FORMAT2 in the host we do not need to or with FORMAT1. Signed-off-by: Pierre Morel Signed-off-by: Tony Krowiak Reviewed-by: Janosch Frank Reviewed-by

[PATCH v10 11/26] s390: vfio-ap: implement mediated device open callback

From: Tony Krowiak Implements the open callback on the mediated matrix device. The function registers a group notifier to receive notification of the VFIO_GROUP_NOTIFY_SET_KVM event. When notified, the vfio_ap device driver will get access to the guest's kvm structure. The open callback must ensu

[PATCH v10 12/26] s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl

From: Tony Krowiak Introduces ioctl access to the VFIO AP Matrix device driver by implementing the VFIO_DEVICE_GET_INFO ioctl. This ioctl provides the VFIO AP Matrix device driver information to the guest machine. Signed-off-by: Tony Krowiak Reviewed-by: Pierre Morel Acked-by: Halil Pasic Tes

[PATCH v10 13/26] s390: vfio-ap: zeroize the AP queues

From: Tony Krowiak Let's call PAPQ(ZAPQ) to zeroize a queue for each queue configured for a mediated matrix device when it is released. Zeroizing a queue resets the queue, clears all pending messages for the queue entries and disables adapter interruptions associated with the queue. Signed-off-

[PATCH v10 16/26] KVM: s390: vsie: Do the CRYCB validation first

From: Pierre Morel We need to handle the validity checks for the crycb, no matter what the settings for the keywrappings are. So lets move the keywrapping checks after we have done the validy checks. Signed-off-by: Pierre Morel Signed-off-by: Tony Krowiak Reviewed-by: Janosch Frank Reviewed-b

[PATCH v10 04/26] s390: vfio-ap: base implementation of VFIO AP device driver

From: Tony Krowiak Introduces a new AP device driver. This device driver is built on the VFIO mediated device framework. The framework provides sysfs interfaces that facilitate passthrough access by guests to devices installed on the linux host. The VFIO AP device driver will serve two purposes:

[PATCH v10 14/26] s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl

From: Tony Krowiak Implements the VFIO_DEVICE_RESET ioctl. This ioctl zeroizes all of the AP queues assigned to the guest. Signed-off-by: Tony Krowiak Reviewed-by: Halil Pasic Tested-by: Michael Mueller Tested-by: Farhan Ali Reviewed-by: Pierre Morel Tested-by: Pierre Morel Signed-off-by:

[PATCH v10 15/26] KVM: s390: Clear Crypto Control Block when using vSIE

From: Pierre Morel When we clear the Crypto Control Block (CRYCB) used by a guest level 2, the vSIE shadow CRYCB for guest level 3 must be updated before the guest uses it. We achieve this by using the KVM_REQ_VSIE_RESTART synchronous request for each vCPU belonging to the guest to force the rel

[PATCH v10 09/26] s390: vfio-ap: sysfs interface to view matrix mdev matrix

From: Tony Krowiak Provides a sysfs interface to view the AP matrix configured for the mediated matrix device. The relevant sysfs structures are: /sys/devices/vfio_ap/matrix/ .. [mdev_supported_types] . [vfio_ap-passthrough] [devices] ...[$uuid]

[PATCH v10 07/26] s390: vfio-ap: sysfs interfaces to configure domains

From: Tony Krowiak Introduces two new sysfs attributes for the VFIO mediated matrix device for assigning AP domains to and unassigning AP domains from a mediated matrix device. The IDs of the AP domains assigned to the mediated matrix device will be stored in an AP queue mask (AQM). The bits in

[PATCH v10 08/26] s390: vfio-ap: sysfs interfaces to configure control domains

From: Tony Krowiak Provides the sysfs interfaces for: 1. Assigning AP control domains to the mediated matrix device 2. Unassigning AP control domains from a mediated matrix device 3. Displaying the control domains assigned to a mediated matrix device The IDs of the AP control domains assig

[PATCH v10 10/26] KVM: s390: interfaces to clear CRYCB masks

From: Tony Krowiak Introduces two new KVM interface to clear the APM, AQM and ADM masks in the guest's CRYCB. The VCPUs are taken out of SIE to ensure the VCPUs do not get out of sync. Signed-off-by: Tony Krowiak Acked-by: Halil Pasic Tested-by: Michael Mueller Tested-by: Farhan Ali Tested-

[PATCH v10 06/26] s390: vfio-ap: sysfs interfaces to configure adapters

From: Tony Krowiak Introduces two new sysfs attributes for the VFIO mediated matrix device for assigning AP adapters to and unassigning AP adapters from a mediated matrix device. The IDs of the AP adapters assigned to the mediated matrix device will be stored in an AP mask (APM). The bits in the

[PATCH v10 03/26] KVM: s390: refactor crypto initialization

From: Tony Krowiak This patch refactors the code that initializes and sets up the crypto configuration for a guest. The following changes are implemented via this patch: 1. Prior to the introduction of AP device virtualization, it was not necessary to provide guest access to the CRYCB unle

[PATCH v10 05/26] s390: vfio-ap: register matrix device with VFIO mdev framework

From: Tony Krowiak Registers the matrix device created by the VFIO AP device driver with the VFIO mediated device framework. Registering the matrix device will create the sysfs structures needed to create mediated matrix devices each of which will be used to configure the AP matrix for a guest an

[PATCH v10 02/26] KVM: s390: introduce and use KVM_REQ_VSIE_RESTART

From: David Hildenbrand When we change the crycb (or execution controls), we also have to make sure that the vSIE shadow datastructures properly consider the changed values before rerunning the vSIE. We can achieve that by simply using a VCPU request now. This has to be a synchronous request (==

Re: [PATCH v2 00/14] coresight: Implement device claim protocol

On Thu, 6 Sep 2018 at 03:08, Suzuki K Poulose wrote: > > Coresight architecture defines CLAIM tags for a device to negotiate > control of the components (external agent vs self-hosted). Each device > has a pair of registers (CLAIMSET & CLAIMCLR) for managing the CLAIM > tags. However, the protocol

[PATCH v12 4/6] firmware: xilinx: Add clock APIs

From: Rajan Vaja Add clock APIs to control clocks through firmware interface. Signed-off-by: Rajan Vaja Signed-off-by: Jolly Shah --- drivers/firmware/xilinx/zynqmp.c | 186 ++- include/linux/firmware/xlnx-zynqmp.h | 30 ++ 2 files changed, 214 inserti

[PATCH v12 1/6] dt-bindings: firmware: Add bindings for ZynqMP firmware

From: Rajan Vaja Add documentation to describe Xilinx ZynqMP firmware driver bindings. Firmware driver provides an interface to firmware APIs. Interface APIs can be used by any driver to communicate to PMUFW (Platform Management Unit). Signed-off-by: Rajan Vaja Signed-off-by: Jolly Shah Review

[PATCH v12 6/6] firmware: xilinx: Add debugfs for query data API

From: Rajan Vaja Add debugfs file to query platform specific data from firmware using debugfs interface. Signed-off-by: Rajan Vaja Signed-off-by: Jolly Shah --- drivers/firmware/xilinx/zynqmp-debug.c | 28 1 file changed, 28 insertions(+) diff --git a/drivers/fir

[PATCH v12 0/6] drivers: Introduce firmware driver for ZynqMP core

Firmware driver enables APU to communicate to PMUFW(Platform Management Unit) via ATF by using SMC instructions. This patchset is adding support for base firmware driver with query and clock control APIs. More API support will be added with incremental patchsets along with their user driver.

[PATCH v12 5/6] firmware: xilinx: Add debugfs interface

From: Rajan Vaja Firmware-debug provides debugfs interface to all APIs. Debugfs can be used to call firmware APIs with required parameters. Usage: * Calling firmware API through debugfs: # echo " .. " > /sys/.../zynqmp-firmware/pm * Read output of last called firmware API: # cat /sys/.../z

[PATCH v12 2/6] firmware: xilinx: Add Zynqmp firmware driver

From: Rajan Vaja This patch is adding communication layer with firmware. Firmware driver provides an interface to firmware APIs. Interface APIs can be used by any driver to communicate to PMUFW(Platform Management Unit). All requests go through ATF. Signed-off-by: Rajan Vaja Signed-off-by: Joll

[PATCH v12 3/6] firmware: xilinx: Add query data API

From: Rajan Vaja Add ZynqMP firmware query data API to query platform specific information(clocks, pins) from firmware. Signed-off-by: Rajan Vaja Signed-off-by: Jolly Shah --- drivers/firmware/xilinx/zynqmp.c | 14 ++ include/linux/firmware/xlnx-zynqmp.h | 20 +

Re: [stable PATCH 2/2] arm64: Handle mismatched cache type

On Tue, Sep 04, 2018 at 10:10:10AM +0100, Suzuki K Poulose wrote: > commit 314d53d297980676011e6fd83dac60db4a01dc70 upstream > > Track mismatches in the cache type register (CTR_EL0), other > than the D/I min line sizes and trap user accesses if there are any. > > Fixes: be68a8aaf925 ("arm64: cpu

Re: [stable PATCH 1/2] arm64: Fix mismatched cache line size detection

On Tue, Sep 04, 2018 at 10:10:09AM +0100, Suzuki K Poulose wrote: > commit 4c4a39dd5fe2d13e2d2fa5fceb8ef95d19fc389a upstream > > If there is a mismatch in the I/D min line size, we must > always use the system wide safe value both in applications > and in the kernel, while performing cache operati

[tip:x86/pti] x86/pti/64: Remove the SYSCALL64 entry trampoline

Commit-ID: bf904d2762ee6fc1e4acfcb0772bbfb4a27ad8a6 Gitweb: https://git.kernel.org/tip/bf904d2762ee6fc1e4acfcb0772bbfb4a27ad8a6 Author: Andy Lutomirski AuthorDate: Mon, 3 Sep 2018 15:59:44 -0700 Committer: Thomas Gleixner CommitDate: Wed, 12 Sep 2018 21:33:53 +0200 x86/pti/64: Remove t

Re: [PATCH v12 0/6] Driver for at91 usart in spi mode

On Wed, 2018-09-12 at 14:12 +0100, Lee Jones wrote: > On Wed, 12 Sep 2018, Alexandre Belloni wrote: > > > On 12/09/2018 12:43:52+0100, Lee Jones wrote: > > > > > But ... we can't have it both ways. *Either* it's a true > > > > > MFD, in > > > > > which case it can/should have 2 separate compatibl

Re: linux-next: build warning after merge of the tip tree

On Tue, 11 Sep 2018, Stephen Rothwell wrote: > After merging the tip tree, today's linux-next build (x86_64 allnoconfig) > produced this warning: > > arch/x86/kernel/cpu/common.c: In function 'syscall_init': > arch/x86/kernel/cpu/common.c:1534:6: warning: unused variable 'cpu' > [-Wunused-variabl

[tip:x86/pti] x86/pti/64: Remove the SYSCALL64 entry trampoline

Commit-ID: e536a56190d412b0f98dbd4dde608f9f7081bb6d Gitweb: https://git.kernel.org/tip/e536a56190d412b0f98dbd4dde608f9f7081bb6d Author: Andy Lutomirski AuthorDate: Mon, 3 Sep 2018 15:59:44 -0700 Committer: Thomas Gleixner CommitDate: Wed, 12 Sep 2018 21:29:09 +0200 x86/pti/64: Remove t

Re: [RFC 00/60] Coscheduling for Linux

On 09/12/2018 02:24 AM, Nishanth Aravamudan wrote: > [ I am not subscribed to LKML, please keep me CC'd on replies ] > > I tried a simple test with several VMs (in my initial test, I have 48 > idle 1-cpu 512-mb VMs and 2 idle 2-cpu, 2-gb VMs) using libvirt, none > pinned to any CPUs. When I tried

[PATCH] perf: Prevent recursion in ring buffer

Some of the scheduling tracepoints allow the perf_tp_event code to write to ring buffer under different cpu than the code is running on. This results in corrupted ring buffer data demonstrated in following perf commands: # perf record -e 'sched:sched_switch,sched:sched_wakeup' perf bench sched

Re: [PATCH v2 1/3] Revert "ASoC: Intel: Skylake: Acquire irq after RIRB allocation"

On Wed, Sep 12, 2018 at 11:20:20AM +0100, Mark Brown wrote: > On Tue, Sep 11, 2018 at 03:12:46PM -0600, Yu Zhao wrote: > > This reverts commit 12eeeb4f4733bbc4481d01df35933fc15beb8b19. > > > > The patch doesn't fix accessing memory with null pointer in > > skl_interrupt(). > > Please use normal s

[PATCH v9 1/5] lib/dlock-list: Distributed and lock-protected lists

Linked list is used everywhere in the Linux kernel. However, if many threads are trying to add or delete entries into the same linked list, it can create a performance bottleneck. This patch introduces a new list APIs that provide a set of distributed lists (one per CPU), each of which is protecte

[PATCH v9 0/5] vfs: Use dlock list for SB's s_inodes list

v8->v9: - The last 2 patches in v8 were dropped because there is no more user that can use them. - Include Davidlohr's dlock_lists_empty() scaling patch. - Rebase the code to 4.19-rc3. v8 patch: https://lkml.org/lkml/2017/10/31/776 This patchset has been dormant for almost a year. Now

[PATCH v9 5/5] lib/dlock-list: Scale dlock_lists_empty()

From: Davidlohr Bueso Instead of the current O(N) implementation, at the cost of adding an atomic counter, we can convert the call to an atomic_read(). The counter only serves for accounting empty to non-empty transitions, and vice versa; therefore only modified twice for each of the lists during

[PATCH v9 3/5] vfs: Use dlock list for superblock's inode list

When many threads are trying to add or delete inode to or from a superblock's s_inodes list, spinlock contention on the list can become a performance bottleneck. This patch changes the s_inodes field to become a dlock list which is a distributed set of lists with per-list spinlocks. As a result,

[PATCH v9 4/5] lib/dlock-list: Make sibling CPUs share the same linked list

The dlock list needs one list for each of the CPUs available. However, for sibling CPUs, they are sharing the L2 and probably L1 caches too. As a result, there is not much to gain in term of avoiding cacheline contention while increasing the cacheline footprint of the L1/L2 caches as separate lists

[PATCH v9 2/5] vfs: Remove unnecessary list_for_each_entry_safe() variants

From: Jan Kara evict_inodes() and invalidate_inodes() use list_for_each_entry_safe() to iterate sb->s_inodes list. However, since we use i_lru list entry for our local temporary list of inodes to destroy, the inode is guaranteed to stay in sb->s_inodes list while we hold sb->s_inode_list_lock. So

Re: [PATCH 1/2] introduce for_each_process_thread_break() and for_each_process_thread_continue()

On Wed, 12 Sep 2018 18:33:35 +0200 Oleg Nesterov wrote: > Usage: > > rcu_read_lock(); > for_each_process_thread(p, t) { > do_something_slow(p, t); > > if (SPENT_TOO_MUCH_TIME) { > for_each_process_thread_break(p, t); >

[tip:x86/urgent] x86/xen: Disable CPU0 hotplug for Xen PV

Commit-ID: 999696752db1099aba595aac4f8d881f8c7cf4e6 Gitweb: https://git.kernel.org/tip/999696752db1099aba595aac4f8d881f8c7cf4e6 Author: Juergen Gross AuthorDate: Wed, 12 Sep 2018 19:41:22 +0200 Committer: Ingo Molnar CommitDate: Wed, 12 Sep 2018 21:15:02 +0200 x86/xen: Disable CPU0 hot

[tip:perf/urgent] tools headers uapi: Update tools's copy of linux/if_link.h

Commit-ID: 5db48a8d01319620d390bf6d9da5410be14f98e3 Gitweb: https://git.kernel.org/tip/5db48a8d01319620d390bf6d9da5410be14f98e3 Author: Arnaldo Carvalho de Melo AuthorDate: Tue, 11 Sep 2018 14:10:52 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 11 Sep 2018 14:10:52 -0300 t

[tip:perf/urgent] perf tools: Fix maps__find_symbol_by_name()

Commit-ID: 03db8b583d1c3c84963e08e2abf6c79081da5c31 Gitweb: https://git.kernel.org/tip/03db8b583d1c3c84963e08e2abf6c79081da5c31 Author: Adrian Hunter AuthorDate: Fri, 7 Sep 2018 11:51:16 +0300 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 11 Sep 2018 14:12:51 -0300 perf tools: F

Re: [PATCH] tools: Remove conflicting BITS_PER_LONG define

Em Wed, Sep 12, 2018 at 04:01:07PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Wed, Sep 12, 2018 at 07:02:32PM +0200, Alexander Sverdlin escreveu: > > CC .../tools/objtool/builtin-check.o > > ... > > In file included from > > .../tools/arch/x86/include/uapi/asm/bitsperlong.h:11:0, > >

[tip:perf/urgent] tools headers uapi: Update tools's copy of linux/vhost.h

Commit-ID: 7f28785c41f4d5635e69c183b3de8ea19093ccef Gitweb: https://git.kernel.org/tip/7f28785c41f4d5635e69c183b3de8ea19093ccef Author: Arnaldo Carvalho de Melo AuthorDate: Tue, 11 Sep 2018 13:12:40 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 11 Sep 2018 13:12:40 -0300 t

[tip:perf/urgent] tools headers uapi: Update tools's copy of drm/drm.h

Commit-ID: 434ea1bfbfc707f5fed9292df6a9b91dfb8e41f2 Gitweb: https://git.kernel.org/tip/434ea1bfbfc707f5fed9292df6a9b91dfb8e41f2 Author: Arnaldo Carvalho de Melo AuthorDate: Tue, 11 Sep 2018 11:07:56 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 11 Sep 2018 11:07:56 -0300 t

[tip:perf/urgent] tools headers uapi: Update tools's copy of asm-generic/unistd.h

Commit-ID: f9e6e4351e0bb0811a8b3696679cc6050e4f5947 Gitweb: https://git.kernel.org/tip/f9e6e4351e0bb0811a8b3696679cc6050e4f5947 Author: Arnaldo Carvalho de Melo AuthorDate: Tue, 11 Sep 2018 11:00:54 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 11 Sep 2018 11:04:43 -0300 t

[tip:perf/urgent] tools headers uapi: Update tools's copy of linux/perf_event.h

Commit-ID: 0ee03d936cbb300309ed6154ac1cc12b63e9785f Gitweb: https://git.kernel.org/tip/0ee03d936cbb300309ed6154ac1cc12b63e9785f Author: Arnaldo Carvalho de Melo AuthorDate: Tue, 11 Sep 2018 10:57:13 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 11 Sep 2018 10:57:13 -0300 t

Re: [PATCH v8 1/2] leds: core: Introduce LED pattern trigger

Hi! > >>> diff --git a/Documentation/ABI/testing/sysfs-class-led-trigger-pattern > >>> b/Documentation/ABI/testing/sysfs-class-led-trigger-pattern > >> [..] > >>> +What:/sys/class/leds//hw_pattern > >>> +Date:September 2018 > >>> +KernelVersion: 4.20 > >>> +Description:

Re: [PATCH v6 2/3] x86/speculation: Enable cross-hyperthread spectre v2 STIBP mitigation

On Wed, 12 Sep 2018, Thomas Gleixner wrote: > > case X86_BUG_SPECTRE_V2: > > - return sprintf(buf, "%s%s%s%s\n", > > spectre_v2_strings[spectre_v2_enabled], > > + mutex_lock(&spec_ctrl_mutex); > > + ret = sprintf(buf, "%s%s%s%s%s\n", > > spectre_v2_strings[spect

Re: [PATCH v6 2/3] x86/speculation: Enable cross-hyperthread spectre v2 STIBP mitigation

On Wed, 12 Sep 2018, Jiri Kosina wrote: > case X86_BUG_SPECTRE_V2: > - return sprintf(buf, "%s%s%s%s\n", > spectre_v2_strings[spectre_v2_enabled], > + mutex_lock(&spec_ctrl_mutex); > + ret = sprintf(buf, "%s%s%s%s%s\n", > spectre_v2_strings[spectre_v2_ena

Re: [GIT PULL 0/7] perf/urgent fixes

USER_DS when recording user stack data (2018-09-10 > 14:01:46 +0200) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git > tags/perf-urgent-for-mingo-4.19-20180912 > > for you to fetch changes up to 03db8b5

Re: [PATCH] tools: Remove conflicting BITS_PER_LONG define

Em Wed, Sep 12, 2018 at 07:02:32PM +0200, Alexander Sverdlin escreveu: > CC .../tools/objtool/builtin-check.o > ... > In file included from .../tools/arch/x86/include/uapi/asm/bitsperlong.h:11:0, > from .../tools/include/asm-generic/bitops/__ffs.h:6, > fr

Re: [BISECTED] Regression: Solidrun Clearfog Base won't boot since "PCI: mvebu: Only remap I/O space if configured"

You mean '4.19-rc3', right? Right, sorry. [1.741458] Internal error: Oops - undefined instruction: 0 [#1] SMP ARM [1.748182] CPU: 1 PID: 72 Comm: kworker/1:2 Tainted: G W 4.19.0-rc3 #1 The 'W' taint means that there was a kernel warning before. Which warning was tha

[GIT PULL 0/7] perf/urgent fixes

repository at: git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-urgent-for-mingo-4.19-20180912 for you to fetch changes up to 03db8b583d1c3c84963e08e2abf6c79081da5c31: perf tools: Fix maps__find_symbol_by_name() (2018-09-11 14:12:51 -0300

[PATCH 6/7] tools headers uapi: Update tools's copy of linux/if_link.h

From: Arnaldo Carvalho de Melo To get the changes in: 3e7a50ceb11e ("net: report min and max mtu network device settings") 2756f68c3149 ("net: bridge: add support for backup port") a25717d2b604 ("xdp: support simultaneous driver and hw XDP attachment") 4f91da26c81

[PATCH 4/7] tools headers uapi: Update tools's copies of kvm headers

From: Arnaldo Carvalho de Melo To get the changes in: a449938297e5 ("KVM: s390: Add huge page enablement control") 8fcc4b5923af ("kvm: nVMX: Introduce KVM_CAP_NESTED_STATE") be26b3a73413 ("arm64: KVM: export the capability to set guest SError syndrome") b7b27facc

[PATCH 7/7] perf tools: Fix maps__find_symbol_by_name()

From: Adrian Hunter Commit 1c5aae7710bb ("perf machine: Create maps for x86 PTI entry trampolines") revealed a problem with maps__find_symbol_by_name() that resulted in probes not being found e.g. $ sudo perf probe xsk_mmap xsk_mmap is out of .text, skip it. Probe point '

[PATCH 3/7] tools headers uapi: Update tools's copy of drm/drm.h

From: Arnaldo Carvalho de Melo To get the changes in: d67b6a206507 ("drm: writeback: Add client capability for exposing writeback connectors") This is for an argument to a DRM ioctl, which is not being prettyfied in the 'perf trace' DRM ioctl beautifier, but will now that syscalls are

[PATCH 5/7] tools headers uapi: Update tools's copy of linux/vhost.h

From: Arnaldo Carvalho de Melo To get the changes in: c48300c92ad9 ("vhost: fix VHOST_GET_BACKEND_FEATURES ioctl request definition") This makes 'perf trace' and other tools in the future using its beautifiers in a libbeauty.so library be able to translate these new ioctl to strings:

[PATCH 2/7] tools headers uapi: Update tools's copy of asm-generic/unistd.h

From: Arnaldo Carvalho de Melo To get the changes in: db7a2d1809a5 ("asm-generic: unistd.h: Wire up sys_rseq") That wires up the new 'rsec' system call, which will automagically support that syscall in the syscall table used by 'perf trace' on arm/arm64. This cures the following warnin

[PATCH 1/7] tools headers uapi: Update tools's copy of linux/perf_event.h

From: Arnaldo Carvalho de Melo To get the changes in: 09121255c784 ("perf/UAPI: Clearly mark __PERF_SAMPLE_CALLCHAIN_EARLY as internal use") This cures the following warning during perf's build: Warning: Kernel ABI header at 'tools/include/uapi/linux/perf_event.h' differs fro

Re: [BISECTED] Regression: Solidrun Clearfog Base won't boot since "PCI: mvebu: Only remap I/O space if configured"

Jan, Baruch, On Wed, 12 Sep 2018 21:49:41 +0300, Baruch Siach wrote: > Jan Kundrát writes: > > since commit ee1604381a371b3ea6aec7d5e43b6e3f5e153854 ("PCI: mvebu: Only > > remap I/O space if configured"), my board (Solidrun Clearfog Base) won't > > finish booting with 4.18-rc3 won't boot: > >

Re: [BISECTED] Regression: Solidrun Clearfog Base won't boot since "PCI: mvebu: Only remap I/O space if configured"

Hi Jan, Jan Kundrát writes: > since commit ee1604381a371b3ea6aec7d5e43b6e3f5e153854 ("PCI: mvebu: Only > remap I/O space if configured"), my board (Solidrun Clearfog Base) won't > finish booting with 4.18-rc3 won't boot: You mean '4.19-rc3', right? >> [1.741458] Internal error: Oops - undefi

Re: [PATCH stable] x86/tsc: Prevent result truncation on 32 bit

On Wed, Sep 12, 2018 at 02:42:08PM +0200, Thomas Gleixner wrote: > Subject: x86/tsc: Prevent result truncation on 32 bit > From: Chuanhua Lei > Date: Thu Sep 6 18:03:23 2018 +0800 > > From: Chuanhua Lei > > Commit 17f6bac2249356c795339e03a0742cd79be3cab8 upstream. > > Loops per jiffy is calcul

Re: [PATCH v2] tracing/Makefile: fix handling redefinition of CC_FLAGS_FTRACE

On Mon, 10 Sep 2018 10:59:56 -0700 Paulo Zanoni wrote: > As a Kernel developer, I make heavy use of "make targz-pkg" in order > to locally compile and remotely install my development Kernels. The > nice feature I rely on is that after a normal "make", "make targz-pkg" > only generates the tarball

Re: [PATCH] dmaengine: ep93xx: Return proper enum in ep93xx_dma_chan_direction

On Wed, Sep 12, 2018 at 10:00:57AM -0700, Nick Desaulniers wrote: > On Tue, Sep 11, 2018 at 4:40 PM Nathan Chancellor > wrote: > > > > Clang warns when implicitly converting from one enumerated type to > > another. Avoid this by using the equivalent value from the expected > > type. > > > > In fil

Re: [PATCH v3] iio: proximity: Add driver support for ST's VL53L0X ToF ranging sensor.

On Wed, Sep 12, 2018 at 10:20:34AM +0800, Song Qiang wrote: > This driver was originally written by ST in 2016 as a misc input device > driver, and hasn't been maintained for a long time. I grabbed some code > from it's API and reformed it into a iio proximity device driver. > This version of drive

Re: [PATCH v7 1/6] dt-bindings: ti-lmu: Remove LM3697

On 09/11/2018 10:05 PM, Pavel Machek wrote: > On Tue 2018-09-11 12:08:20, Dan Murphy wrote: >> Remove support for the LM3697 LED device >> from the ti-lmu. The LM3697 will be supported >> via a stand alone LED driver. >> >> Signed-off-by: Dan Murphy > > I'd really like to see better explanation

Re: [PATCH v4 4/5] iio: fxas21002c: add ODR/Scale support

Hello Afonso, On Wed, Sep 12, 2018 at 05:26:01PM +0800, kbuild test robot wrote: > Hi Afonso, > > Thank you for the patch! Yet something to improve: > > [auto build test ERROR on iio/togreg] > [also build test ERROR on v4.19-rc3 next-20180912] > [if your patch is applied

Re: [GIT PULL] soundwire updates for v4.19-rc1

On Wed, Sep 12, 2018 at 02:52:33PM +0530, Vinod wrote: > On 12-09-18, 09:29, Greg KH wrote: > > On Wed, Aug 08, 2018 at 09:58:50PM +0530, Vinod wrote: > > > Hey Greg, > > > > > > Please PULL to receive the soundwire update for v4.19-rc1 with a signed > > > tag as you requested last time and the no

Re: [PATCH v2 13/17] compat_ioctl: remove /dev/random commands

On Wed, Sep 12, 2018 at 05:13:05PM +0200, Arnd Bergmann wrote: > These are all handled by the random driver, so instead of listing > each ioctl, we can just use the same function to deal with both > native and compat commands. > > Signed-off-by: Arnd Bergmann > --- > drivers/char/random.c | 1 +

[PATCH v6 4/4] dt-bindings: msm: Update documentation of qcom,llcc

Add reg-names and interrupts for LLCC documentation and the usage examples. llcc broadcast base is added in addition to llcc base, which is used for llcc broadcast writes. Signed-off-by: Venkata Narendra Kumar Gutta Reviewed-by: Rob Herring --- .../devicetree/bindings/arm/msm/qcom,llcc.txt

[PATCH v6 2/4] drivers: soc: Add support to register LLCC EDAC driver

Cache error reporting controller detects and reports single and double bit errors on Last Level Cache Controller (LLCC) cache. Add required support to register LLCC EDAC driver as platform driver, from LLCC driver. Signed-off-by: Venkata Narendra Kumar Gutta Reviewed-by: Evan Green --- drivers/

[PATCH v6 3/4] drivers: edac: Add EDAC driver support for QCOM SoCs

From: Channagoud Kadabi Add error reporting driver for Single Bit Errors (SBEs) and Double Bit Errors (DBEs). As of now, this driver supports error reporting for Last Level Cache Controller (LLCC) of Tag RAM and Data RAM. Interrupts are triggered when the errors happen in the cache, the driver ha

[PATCH v6 0/4] Add EDAC driver for QCOM SoCs

This series implements EDAC driver for QCOM SoCs. As of now, this driver supports EDAC for Last Level Cache Controller (LLCC). LLCC EDAC driver is to detect and report single and double bit errors on Last Level Cache Controller (LLCC) cache. Interrupts are triggered when the errors happen in the ca

[PATCH v6 1/4] drivers: soc: Add broadcast base for Last Level Cache Controller (LLCC)

Currently, broadcast base is set to end of the LLCC banks, which may not be correct always. As the number of banks may vary for each chipset and the broadcast base could be at a different address as well. This info depends on the chipset, so get the broadcast base info from the device tree (DT). Ad

Re: loop device: print_req_error - blk_update_request I/O error

Answering to myself: It looks like ext4 lazy init does not play well with loop device. If the ext4 filesystem was previously created with lazy init there are I/O errors. Disabling lazy init fixes problem. Bug or feature? Thanks, I'm mounting an ext4 filesystem residing on an AHCI SATA disk via

Re: [PATCH v4 02/16] sched/core: uclamp: map TASK's clamp values into CPU's clamp groups

On 12-Sep 19:42, Peter Zijlstra wrote: > On Wed, Sep 12, 2018 at 06:35:15PM +0100, Patrick Bellasi wrote: > > On 12-Sep 18:12, Peter Zijlstra wrote: > > > > No idea; but if you want to go all fancy you can replace he whole > > > uclamp_map thing with something like: > > > > > > struct uclamp_map

Re: [PATCH] pstore: fix incorrect persistent ram buffer mapping

On Tue, Sep 11, 2018 at 8:36 PM, Bin Yang wrote: > persistent_ram_vmap() returns the page start vaddr. > persistent_ram_iomap() supports non-page-aligned mapping. Oh, yes, good catch. This should probably be explicitly mentioned in comments for these functions. > persistent_ram_buffer_map() alwa

Re: [PATCH v4 03/16] sched/core: uclamp: add CPU's clamp groups accounting

On 12-Sep 19:34, Peter Zijlstra wrote: > On Tue, Aug 28, 2018 at 02:53:11PM +0100, Patrick Bellasi wrote: > > diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h > > index 72df2dc779bc..513608ae4908 100644 > > --- a/kernel/sched/sched.h > > +++ b/kernel/sched/sched.h > > @@ -764,6 +764,50 @@ e

Re: [PATCH AUTOSEL 4.14 27/67] ARM: exynos: Define EINT_WAKEUP_MASK registers for S5Pv210 and Exynos5433

On Fri, Sep 07, 2018 at 08:33:22AM +0200, Krzysztof Kozlowski wrote: >On Fri, 7 Sep 2018 at 02:54, Sasha Levin wrote: >> >> From: Krzysztof Kozlowski >> >> [ Upstream commit e5cda42c16d89720c29678f51d95a119490ef7d8 ] >> >> S5Pv210 and Exynos5433/Exynos7 have different address of >> EINT_WAKEUP_MA

Re: [PATCH v9 21/22] KVM: s390: CPU model support for AP virtualization

On 08/23/2018 04:24 AM, Cornelia Huck wrote: On Thu, 23 Aug 2018 09:48:48 +0200 David Hildenbrand wrote: Migration of AP devices is not supported by this patch series, so this should not be an issue. Might not be a problem now, but could be later. As I said in a different reply, the CPU model

Re: [PATCH v4 02/16] sched/core: uclamp: map TASK's clamp values into CPU's clamp groups

On Wed, Sep 12, 2018 at 06:35:15PM +0100, Patrick Bellasi wrote: > On 12-Sep 18:12, Peter Zijlstra wrote: > > No idea; but if you want to go all fancy you can replace he whole > > uclamp_map thing with something like: > > > > struct uclamp_map { > > union { > > struct { > >

Re: [PATCH v4 02/16] sched/core: uclamp: map TASK's clamp values into CPU's clamp groups

On 12-Sep 18:24, Peter Zijlstra wrote: > On Tue, Aug 28, 2018 at 02:53:10PM +0100, Patrick Bellasi wrote: > > static inline int __setscheduler_uclamp(struct task_struct *p, > > const struct sched_attr *attr) > > But large for inline now. Yes, Suren also alread

Re: [PATCH AUTOSEL 4.18 69/88] xen-netfront: fix queue name setting

On Fri, Sep 07, 2018 at 01:33:55PM -0400, Boris Ostrovsky wrote: >On 09/06/2018 08:36 PM, Sasha Levin wrote: >> From: Vitaly Kuznetsov >> >> [ Upstream commit 2d408c0d4574b01b9ed45e02516888bf925e11a9 ] >> >> Commit f599c64fdf7d ("xen-netfront: Fix race between device setup and >> open") changed th

Re: [PATCH AUTOSEL 4.18 02/88] usb: usbtest: use irqsave() in USB's complete callback

On Fri, Sep 07, 2018 at 07:42:23AM +0200, Greg Kroah-Hartman wrote: >On Fri, Sep 07, 2018 at 12:35:52AM +, Sasha Levin wrote: >> From: Sebastian Andrzej Siewior >> >> [ Upstream commit 6f3fde684d0232e66ada3410f016a58e09a87689 ] >> >> The USB completion callback does not disable interrupts whil

Re: [PATCH v4 02/16] sched/core: uclamp: map TASK's clamp values into CPU's clamp groups

On 12-Sep 18:12, Peter Zijlstra wrote: > On Wed, Sep 12, 2018 at 04:56:19PM +0100, Patrick Bellasi wrote: > > On 12-Sep 15:49, Peter Zijlstra wrote: > > > On Tue, Aug 28, 2018 at 02:53:10PM +0100, Patrick Bellasi wrote: > > > > > +/** > > > > + * uclamp_map: reference counts a utilization "clamp v

Re: [PATCH v4 03/16] sched/core: uclamp: add CPU's clamp groups accounting

On Tue, Aug 28, 2018 at 02:53:11PM +0100, Patrick Bellasi wrote: > diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h > index 72df2dc779bc..513608ae4908 100644 > --- a/kernel/sched/sched.h > +++ b/kernel/sched/sched.h > @@ -764,6 +764,50 @@ extern void rto_push_irq_work_func(struct irq_work

Re: [PATCH 1/1] pci: Pick up the acpi numa node value if it is specified at the device level.

[+cc ACPI folks, LKML] On Wed, Sep 12, 2018 at 04:21:40PM +0100, Jonathan Cameron wrote: > The ACPI specification allows you to provide _PXM entries for devices based > on their location on a particular bus. Let us use that if it is provided > rather than just assuming it makes sense to put the d

Re: [PATCH AUTOSEL 4.14 49/89] ARM: 8783/1: NOMMU: Extend check for VBAR support

On Mon, Sep 10, 2018 at 10:42:05AM +0100, Vladimir Murzin wrote: >On 02/09/18 14:07, Sasha Levin wrote: >> From: Vladimir Murzin >> >> [ Upstream commit c803ce3f18bd93b3b4a15d1da0c5b5ebc60e0b85 ] >> >> ARMv8R adds support for VBAR and updates ID_PFR1 with the new filed >> Sec_frac (bits [23:20]):

<    1   2   3   4   5   6   7   8   >