From: Wanpeng Li
Expose the per-vCPU advancement information to the user via per-vCPU debugfs
entry. wait_lapic_expire() call was moved above guest_enter_irqoff() because
of its tracepoint, which violated the RCU extended quiescent state invoked
by guest_enter_irqoff()[1][2]. This patch simply
From: Wanpeng Li
Advance lapic timer tries to hidden the hypervisor overhead between the
host emulated timer fires and the guest awares the timer is fired. However,
it just hidden the time between apic_timer_fn/handle_preemption_timer ->
wait_lapic_expire, instead of the real position of vment
From: Wanpeng Li
Extract adaptive tune timer advancement logic to a single function.
Cc: Paolo Bonzini
Cc: Radim Krčmář
Cc: Sean Christopherson
Cc: Liran Alon
Signed-off-by: Wanpeng Li
---
arch/x86/kvm/lapic.c | 57 ++--
1 file changed, 33 in
Advance lapic timer tries to hidden the hypervisor overhead between the
host emulated timer fires and the guest awares the timer is fired. However,
it just hidden the time between apic_timer_fn/handle_preemption_timer ->
wait_lapic_expire, instead of the real position of vmentry which is
mentio
merged both patches into cifs-2.6.git for-next
On Mon, May 13, 2019 at 11:02 PM wrote:
>
> From: Long Li
>
> When sending data, use the DMA_TO_DEVICE to map buffers. Also log the number
> of requests in a compounding request from upper layer.
>
> Signed-off-by: Long Li
> ---
> fs/cifs/smbdirec
On Mon, May 13, 2019 at 3:48 PM Doug Anderson wrote:
>
> Hi,
>
> On Thu, May 9, 2019 at 11:44 AM Rob Clark wrote:
>
> > From: Douglas Anderson
> >
> > Let's fixup the reserved memory to re-add the things we deleted in
> > ("CHROMIUM: arm64: dts: qcom: sdm845-cheza: Temporarily delete
> > reserve
Advance lapic timer tries to hidden the hypervisor overhead between the
host emulated timer fires and the guest awares the timer is fired. However,
it just hidden the time between apic_timer_fn/handle_preemption_timer ->
wait_lapic_expire, instead of the real position of vmentry which is
mentio
[v2]
* Update KCONFIG to select RATIONAL
* Clean up redundant code from dp_set_rate/dp_set_rate_and_parent
* Update the disp_cc_mdss_dp_link_clk_src to use the byte2_ops instead
of defining the frequencies in KHz.
* Clean up CLK_GET_RATE_NOCACHE from various RCGs of DP.
[v1]
SDM845 dispcc supports RCG and CBCRs for display port, so add support for
the same.
Signed-off-by: Taniya Das
---
drivers/clk/qcom/dispcc-sdm845.c | 216 -
include/dt-bindings/clock/qcom,dispcc-sdm845.h | 13 +-
2 files changed, 227 insertions(+), 2 deletio
New display port clock ops supported for display port clocks.
Signed-off-by: Taniya Das
---
drivers/clk/qcom/Kconfig| 1 +
drivers/clk/qcom/clk-rcg.h | 1 +
drivers/clk/qcom/clk-rcg2.c | 81 -
3 files changed, 82 insertions(+), 1 deletion(-)
di
Hi all,
Please do not add any v5.3 material to your linux-next included
trees/branches until after v5.2-rc1 has been released.
Changes since 20190514:
The thermal-soc tree lost its build failure but gained conflicts against
Linus' tree.
The akpm-current tree gained a conflict against the
On 05/15/2019 05:21 AM, Roman Gushchin wrote:
> __vunmap() calls find_vm_area() twice without an obvious reason:
> first directly to get the area pointer, second indirectly by calling
> vm_remove_mappings()->remove_vm_area(), which is again searching
> for the area.
>
> To remove this redundanc
Hi,
Am 14.05.2019 um 13:22 schrieb Michael Schmitz:
Stephen,
I wasn't aware of the other asix module when submitting the phy driver.
The phy module gets autoloaded based on the PHY ID, so there's no reason
why it couldn't be renamed.
May I suggest ax88796b for the new module name?
I've got a
The top level Makefile adds -Wall globally:
KBUILD_CFLAGS := -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs \
For riscv, I see two "-Wall" added for compiling each object.
Signed-off-by: Masahiro Yamada
---
arch/riscv/Makefile | 2 --
1 file changed, 2 deletions(-)
diff --git a/a
This fixes a build break introduced in with the recent round of CPU
bug patches.
arch/powerpc/kernel/security.c: In function ‘setup_barrier_nospec’:
arch/powerpc/kernel/security.c:59:21: error: implicit declaration of
function ‘cpu_mitigations_off’ [-Werror=implicit-function-declaration]
Ah, I think I see the problem. Sorry, this one was my fault. Does
this fix things for you?
- Ted
>From 0c72924ef346d54e8627440e6d71257aa5b56105 Mon Sep 17 00:00:00 2001
From: Theodore Ts'o
Date: Wed, 15 May 2019 00:51:19 -0400
Subject: [PATCH] ex
On Wed, May 15, 2019 at 12:34:00AM +, Jason Gunthorpe wrote:
> On Tue, May 14, 2019 at 12:45:10PM -0700, Nathan Chancellor wrote:
> > DIV_ROUND_UP is u64 / u32 in this case. I think DIV_ROUND_UP_ULL is
> > needed but I am not sure if that has any unintended side effects so I
> > didn't want to
On Tue, 14 May 2019 16:58:24 -0500, Xing, Cedric
wrote:
Hi Everyone,
I think we are talking about 2 different kinds of criteria for
determining the sanity of an enclave.
The first kind determines an enclave's sanity by generally accepted good
practices. For example, no executable pages
Hi Florian,
On 5/14/19 7:38 PM, Florian Fainelli wrote:
> When building on a 64-bit host, we will get warnings like those:
>
> drivers/firmware/broadcom/bcm47xx_nvram.c:103:3: note: in expansion of macro
> 'pr_err'
>pr_err("nvram on flash (%i bytes) is bigger than the reserved space in
> me
On Wed, May 15, 2019 at 02:22:06PM +0930, Joel Stanley wrote:
> This fixes a build break introduced in with the recent round of CPU
> bug patches.
>
> arch/powerpc/kernel/security.c: In function ‘setup_barrier_nospec’:
> arch/powerpc/kernel/security.c:59:21: error: implicit declaration of
>
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
This patch aims to suppress 3 missing-break-in-switch false positives
on some architectures.
Acked-by: Arnd Bergmann
Cc: Deepa Dinamani
Cc: Gustavo A. R. Silva
Cc: Kees Cook
Cc: Jann H
Hi Kairui,
On 5/13/19 5:02 PM, Baoquan He wrote:
> On 05/13/19 at 09:50am, Borislav Petkov wrote:
>> On Mon, May 13, 2019 at 03:32:54PM +0800, Baoquan He wrote:
>> So we're going to try it again this cycle and if there's no fallout, it
>> will go upstream. If not, it will have to be fixed. The usu
Hi,
Here is the v9 series of probe-event to support user-space access.
Previous version is here.
https://lkml.kernel.org/r/155741476971.28419.15837024173365724167.stgit@devnote2
In this version, I fixed more typos/style issues.
Changes in v9:
[3/6]
- Fix other style & coding issues (Than
WARN_ON_IN_IRQ() assumes that the access_ok() and following
user memory access can sleep. But this assumption is not
always correct; when the pagefault is disabled, following
memory access will just returns -EFAULT and never sleep.
Add pagefault_disabled() check in WARN_ON_ONCE() so that
it can ig
Support user-space dereference syntax for probe event arguments
to dereference the data-structure or array in user-space.
The syntax is just adding 'u' before an offset value.
+|-u()
e.g. +u8(%ax), +u0(+0(%si))
For example, if you probe do_sched_setscheduler(pid, policy,
param) and record para
Add a user-memory access syntax testcase which checks
new user-memory access syntax and ustring type.
Signed-off-by: Masami Hiramatsu
Acked-by: Steven Rostedt (VMware)
---
Changes in v6:
- Add $argN availability check
---
.../ftrace/test.d/kprobe/kprobe_args_user.tc | 32
Add probe_user_read(), strncpy_from_unsafe_user() and
strnlen_unsafe_user() which allows caller to access user-space
in IRQ context.
Current probe_kernel_read() and strncpy_from_unsafe() are
not available for user-space memory, because it sets
KERNEL_DS while accessing data. On some arch, user add
Add "ustring" type for fetching user-space string from kprobe event.
User can specify ustring type at uprobe event, and it is same as
"string" for uprobe.
Note that probe-event provides this option but it doesn't choose the
correct type automatically since we have not way to decide the address
is
Add user memory access attribute for kprobe event arguments.
If a given 'local variable' is in user-space, User can
specify memory access method by '@user' suffix. This is
not only for string but also for data structure.
If we access a field of data structure in user memory from
kernel on some arc
On 14.05.2019 23:04, Arnaldo Carvalho de Melo wrote:
> Em Mon, Mar 18, 2019 at 08:44:42PM +0300, Alexey Budankov escreveu:
>>
>> Implemented -z,--compression_level[=] option that enables compression
>> of mmaped kernel data buffers content in runtime during perf record
>> mode collection. Default o
Since commit 350e88bad496 ("mm: memblock: make keeping memblock memory
opt-in rather than opt-out") the default behaviour is to discard memblock
data after init and the ARCH_DISCARD_MEMBLOCK is obsolete.
Remove it.
Signed-off-by: Mike Rapoport
---
arch/parisc/Kconfig | 1 -
1 file changed, 1 de
Hi Jones,
> > +
> > +struct rpc_spi {
> > + struct rpc_mfd *mfd;
>
> The term MFD isn't a real thing. What you're obtaining below is
> driver data and is normally articulated as 'ddata' in drivers.
yes, it's just imply that data is from MFD.
Should I rename "mfd" ?
>
> > + u32 cur_speed
* Masami Hiramatsu wrote:
> Hi,
>
> Here is the v9 series of probe-event to support user-space access.
> Previous version is here.
>
> https://lkml.kernel.org/r/155741476971.28419.15837024173365724167.stgit@devnote2
>
> In this version, I fixed more typos/style issues.
>
> Changes in v9:
>
Commit-ID: 2decec48b0fd28ffdbf4cc684bd04e735f0839dd
Gitweb: https://git.kernel.org/tip/2decec48b0fd28ffdbf4cc684bd04e735f0839dd
Author: Raphael Gault
AuthorDate: Tue, 14 May 2019 17:47:46 -0500
Committer: Ingo Molnar
CommitDate: Wed, 15 May 2019 07:57:50 +0200
objtool: Fix whitelist do
Enable USB3 HW LPM feature for lx2160a and active patch for
snps erratum A-010131. It will disable U1/U2 temperary when
initiate U3 request.
Signed-off-by: Ran Wang
---
Depend on: https://lore.kernel.org/patchwork/patch/870134/
arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi |4
1 files
On Wed, May 15, 2019 at 07:18:30AM +0200, Greg Kroah-Hartman wrote:
> On Wed, May 15, 2019 at 02:22:06PM +0930, Joel Stanley wrote:
> > This fixes a build break introduced in with the recent round of CPU
> > bug patches.
> >
> > arch/powerpc/kernel/security.c: In function ‘setup_barrier_nospec’:
On 5/14/19 11:53 PM, Jeff Kletsky wrote:
> From: Jeff Kletsky
That #define in $subject is called a macro.
Seems this patch adds a lot of almost duplicate code, can it be somehow
de-duplicated ?
> The GigaDevice GD5F1GQ4UFxxG SPI NAND utilizes three-byte addresses
> for its page-read ops.
>
> h
Strict module RWX is just like strict kernel RWX, but for modules - so
loadable modules aren't marked both writable and executable at the same
time. This is handled by the generic code in kernel/module.c, and
simply requires the architecture to implement the set_memory() set of
functions, declared
On (05/14/19 21:13), Geert Uytterhoeven wrote:
> I would immediately understand there's a missing IS_ERR() check in a
> function that can return -EINVAL, without having to add a new printk()
> to find out what kind of bogus value has been received, and without
> having to reboot, and trying to rep
Hi.
On Tue, May 14, 2019 at 04:51:22PM +0200, Michal Hocko wrote:
> [Forgot Hugh]
>
> On Tue 14-05-19 16:41:05, Michal Hocko wrote:
> > [This is adding a new user visible interface so you should be CCing
> > linux-api mailing list. Also CC Hugh for KSM in general. Done now]
Right, thanks for tak
Hi.
On Wed, May 15, 2019 at 03:53:55AM +0300, Timofey Titovets wrote:
> LGTM for whole series
>
> Reviewed-by: Timofey Titovets
>
> вт, 14 мая 2019 г. в 16:17, Oleksandr Natalenko :
> >
> > Document respective sysfs knob.
> >
> > Signed-off-by: Oleksandr Natalenko
> > ---
> > Documentation/ad
This patch enables NO_HZ_IDLE (idle dynamic ticks) and HIGH_RES_TIMERS
(hrtimers) in RV32 and RV64 defconfigs.
Both of the above options are enabled by default for architectures
such as x86, ARM, and ARM64.
The idle dynamic ticks helps use save power by stopping timer ticks
when the system is idl
When the output sample rate is [8kHz, 30kHz], the limitation
of the supported ratio range is [1/24, 8]. In the driver
we use (8kHz, 30kHz) instead of [8kHz, 30kHz].
So this patch is to fix this issue and the potential rounding
issue with divider.
Fixes: fff6e03c7b65 ("ASoC: fsl_asrc: add support f
Support more sample rate in asrc
Shengjiu Wang (3):
ASoC: fsl_asrc: Fix the issue about unsupported rate
ASoC: fsl_asrc: replace the process_option table with function
ASoC: fsl_asrc: Unify the supported input and output rate
Changes in RESEND V6
- change the Content-Transfer-Encoding to "q
> +static int change_page_ro(pte_t *ptep, pgtable_t token, unsigned long addr,
> void *data)
There are a couple way too long lines like this in the patch.
Unify the supported input and output rate, add the
12kHz/24kHz/128kHz to the support list
Signed-off-by: Shengjiu Wang
Acked-by: Nicolin Chen
---
sound/soc/fsl/fsl_asrc.c | 32 +++-
1 file changed, 19 insertions(+), 13 deletions(-)
diff --git a/sound/soc/fsl/fsl_asr
Oops, forgot to tell it's for 4.9. Resending with proper subject.
Le 15/05/2019 à 08:39, Christophe Leroy a écrit :
[Backport of upstream commit b45ba4a51cde29b2939365ef0c07ad34c8321789]
On powerpc32, patch_instruction() is called by apply_feature_fixups()
which is called from early_init()
The
When we want to support more sample rate, for example 12kHz/24kHz
we need update the process_option table, if we want to support more
sample rate next time, the table need to be updated again. which
is not flexible.
We got a function fsl_asrc_sel_proc to replace the table, which can
give the pre-p
A test for the basic NAT functionality uses ip command which
needs veth device.There is a condition where the kernel support
for veth is not compiled into the kernel and the test script
breaks.This patch contains code for reasonable error display
and correct code exit.
Signed-off-by: Jeffrin Jose
Pointer s is allocated with kmem_cache_zalloc(). And s is used in the
follwoing codes. However, when kmem_cache_zalloc fails, using s will
cause null pointer dereference and the kernel will go wrong. Thus we
check whether the kmem_cache_zalloc fails.
Signed-off-by: Gen Zhang
---
--- mm/slub.c
Le 15/05/2019 à 08:42, Christoph Hellwig a écrit :
+static int change_page_ro(pte_t *ptep, pgtable_t token, unsigned long addr,
void *data)
There are a couple way too long lines like this in the patch.
powerpc arch accepts 90 chars per line, see arch/powerpc/tools/checkpatch.pl
Christop
Hi Miquel,
> > Add a driver for Macronix MX25F0A multifunction device controller.
> >
> > Signed-off-by: Mason Yang
> > ---
> > drivers/mfd/Kconfig | 9 ++
> > drivers/mfd/Makefile | 1 +
> > drivers/mfd/mxic-mx25f0a.c | 84 +++
> > includ
On 15.05.19 08:17, Marek Vasut wrote:
> On 5/14/19 11:53 PM, Jeff Kletsky wrote:
>> From: Jeff Kletsky
>
> That #define in $subject is called a macro.
>
> Seems this patch adds a lot of almost duplicate code, can it be somehow
> de-duplicated ?
We could add another parameter naddr or addrlen to
On 5/15/19 1:49 AM, kan.li...@linux.intel.com wrote:
> From: Kan Liang
>
> The available registers for --int-regs and --user-regs may be different,
> e.g. XMM registers.
>
> Split parse_regs into two dedicated functions for --int-regs and
> --user-regs respectively.
>
> Modify the warning mes
Yabin Cui writes:
> diff --git a/kernel/events/ring_buffer.c b/kernel/events/ring_buffer.c
> index 674b35383491..0b9aefe13b04 100644
> --- a/kernel/events/ring_buffer.c
> +++ b/kernel/events/ring_buffer.c
> @@ -54,8 +54,10 @@ static void perf_output_put_handle(struct
> perf_output_handle *handle
On 14.05.19 23:53, Jeff Kletsky wrote:
> From: Jeff Kletsky
>
> The GigaDevice GD5F1GQ4UFxxG SPI NAND utilizes three-byte addresses
> for its page-read ops.
>
> http://www.gigadevice.com/datasheet/gd5f1gq4xfxxg/
>
> Signed-off-by: Jeff Kletsky
Reviewed-by: Frieder Schrempf
> ---
> include
On 14.05.19 23:53, Jeff Kletsky wrote:
> From: Jeff Kletsky
>
> The GigaDevice GD5F1GQ4UFxxG SPI NAND utilizes two-byte device IDs.
>
> http://www.gigadevice.com/datasheet/gd5f1gq4xfxxg/
>
> Signed-off-by: Jeff Kletsky
Reviewed-by: Frieder Schrempf
> ---
> drivers/mtd/nand/spi/core.c | 2
On Mon, May 13, 2019 at 2:04 PM Christoph Hellwig wrote:
>
> On Mon, May 13, 2019 at 01:50:19PM +0200, Dmitry Vyukov wrote:
> > > We did have some bugs in the past (~1-2 y/ago) but AFAIK they are all
> > > fixed now. These days I build most of my kernels with a bi-endian 64-bit
> > > toolchain, an
On 14.05.19 23:53, Jeff Kletsky wrote:
> From: Jeff Kletsky
>
> The GigaDevice GD5F1GQ4UFxxG SPI NAND is in current production devices
> and, while it has the same logical layout as the E-series devices,
> it differs in the SPI interfacing in significant ways.
>
> This support is contingent on p
On Wed 15-05-19 08:25:23, Oleksandr Natalenko wrote:
[...]
> > > Please make sure to describe a usecase that warrants adding a new
> > > interface we have to maintain for ever.
>
> I think of two major consumers of this interface:
>
> 1) hosts, that run containers, especially similar ones and esp
Since commit 7d5905dc14a8 ("x86 / CPU: Always show current CPU frequency
in /proc/cpuinfo") open and read of /proc/cpuinfo sends IPI to all CPUs.
Many applications read /proc/cpuinfo at the start for trivial reasons like
counting cores or detecting cpu features. While sensitive workloads like
DPDK
601 - 661 of 661 matches
Mail list logo
