Hi, Shawn
Can you pick up this patch series if no additional comments? We need
this feature to support many modules IRQ function including suspend/resume,
thanks.
Best Regards!
Anson Huang
> -Original Message-
> From: Anson Huang
> Sent: 2019年4月9日 13:00
> To:
Add output line for NUMA remote node defrag ratio.
Signed-off-by: Tobin C. Harding
---
tools/vm/slabinfo.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/tools/vm/slabinfo.c b/tools/vm/slabinfo.c
index cbfc56c44c2f..d2c22f9ee2d8 100644
--- a/tools/vm/slabinfo.c
+++
We just implemented movable objects for the XArray. Let's test it
intree.
Add test module for the XArray's movable objects implementation.
Functionality of the XArray Slab Movable Object implementation can
usually be seen by simply by using `slabinfo` on a running machine since
the radix tree
We just implemented slab movable objects for the SLUB allocator. We
should test that code. In order to do so we need to be able to do a
number of things
- Create a cache
- Enable Slab Movable Objects for the cache
- Allocate objects to the cache
- Free objects from within specific slabs of
On Mon, Mar 11, 2019 at 03:20:12PM +0800, Peng Ma wrote:
> Add ls1028a compatible to bindings documentation.
>
> Signed-off-by: Peng Ma
I assume that the bindings will be picked up by Axboe. Otherwise,
please let me know.
Shawn
Implement functions to migrate objects. This is based on initial code by
Matthew Wilcox and was modified to work with slab object migration.
This patch can not be merged until all radix tree & IDR users are
converted to the XArray because xa_nodes and radix tree nodes share the
same slab cache
We have just implemented Slab Movable Objects (SMO). On NUMA systems
slabs can become unbalanced i.e. many slabs on one node while other
nodes have few slabs. Using SMO we can balance the slabs across all
the nodes.
The algorithm used is as follows:
1. Move all objects to node 0 (this has the
We have just implemented Slab Movable Objects (object migration).
Currently object migration is used to defrag a cache. On NUMA systems
it would be nice to be able to control the source and destination nodes
when moving objects.
Add CONFIG_SMO_NODE to guard this feature. CONFIG_SMO_NODE depends
Add output for the newly added defrag_used_ratio sysfs knob.
Signed-off-by: Tobin C. Harding
---
tools/vm/slabinfo.c | 4
1 file changed, 4 insertions(+)
diff --git a/tools/vm/slabinfo.c b/tools/vm/slabinfo.c
index d2c22f9ee2d8..ef4ff93df4cc 100644
--- a/tools/vm/slabinfo.c
+++
It is advantageous to have all defragmentable slabs together at the
beginning of the list of slabs so that there is no need to scan the
complete list. Put defragmentable caches first when adding a slab cache
and others last.
Co-developed-by: Christoph Lameter
Signed-off-by: Tobin C. Harding
---
Hi,
Another iteration of the SMO patch set implementing suggestions from Al
and Willy on the last version as well as some feedback from comments on
the recent LWN article.
Applies on top of Linus' tree (tag: v5.1-rc4).
This is a patch set implementing movable objects within the SLUB
allocator.
-C lists caches that use a ctor.
-M lists caches that support object migration.
Add command line options to show caches with a constructor and caches
that are movable (i.e. have migrate function).
Co-developed-by: Christoph Lameter
Signed-off-by: Tobin C. Harding
---
tools/vm/slabinfo.c | 40
On Mon, Mar 11, 2019 at 03:20:13PM +0800, Peng Ma wrote:
> Ls1028a SATA ecc address with more than 32 bit, so we should corrrect the
> address.
>
> Signed-off-by: Peng Ma
Applied, thanks.
Add the two methods needed for moving objects and enable the display of
the callbacks via the /sys/kernel/slab interface.
Add documentation explaining the use of these methods and the prototypes
for slab.h. Add functions to setup the callbacks method for a slab
cache.
Add empty functions for
Internal fragmentation can occur within pages used by the slub
allocator. Under some workloads large numbers of pages can be used by
partial slab pages. This under-utilisation is bad simply because it
wastes memory but also because if the system is under memory pressure
higher order allocations
On Tue, Mar 12, 2019 at 09:50:18AM +0800, Peng Ma wrote:
> Add SATA device nodes for fsl-lx2160a and enable support
> for QDS and RDB boards.
>
> Signed-off-by: Peng Ma
Applied, thanks.
hi,
在 2019/4/11 上午7:37, Doug Anderson 写道:
Hi,
On Wed, Apr 10, 2019 at 11:38 AM Jonas Karlman wrote:
On 2019-04-10 17:45, Doug Anderson wrote:
Hi,
On Fri, Mar 29, 2019 at 2:55 PM Douglas Anderson wrote:
It appears that there is a typo in the rk3288 TRM. For
GRF_SOC_CON0[7] it says that 0
On Wed, Apr 10, 2019 at 09:01:52AM +0200, Peter Zijlstra wrote:
> On Tue, Apr 09, 2019 at 06:19:57PM -0700, Ricardo Neri wrote:
> > On Tue, Apr 09, 2019 at 01:28:17PM +0200, Peter Zijlstra wrote:
> > > > @@ -147,6 +161,14 @@ static void set_periodic(struct hpet_hld_data
> > > > *hdata)
> > > >
On Wed, 2019-04-10 at 19:59 +0200, Martin Blumenstingl wrote:
> On Wed, Apr 10, 2019 at 8:13 AM Chunfeng Yun
> wrote:
> >
> > Use devm_clk_get_optional() to get optional clock
> >
> > Cc: Martin Blumenstingl
> > Signed-off-by: Chunfeng Yun
> > Acked-by: Martin Blumenstingl
> now also:
>
On 2019/4/10 22:54, Andy Lutomirski wrote:
> On Tue, Apr 9, 2019 at 8:40 PM Li, Aubrey wrote:
>>
>> On 2019/4/10 10:36, Li, Aubrey wrote:
>>> On 2019/4/10 10:25, Andy Lutomirski wrote:
On Tue, Apr 9, 2019 at 7:20 PM Li, Aubrey
wrote:
>
> On 2019/4/10 9:58, Andy Lutomirski
We can't seem to have a kernel with CONFIG_EXPERT set but
CONFIG_DEBUG_KERNEL unset these days.
While some of the features under the CONFIG_EXPERT require
CONFIG_DEBUG_KERNEL, it doesn't apply for all features.
It looks like CONFIG_KALLSYMS_ALL is the only feature that
requires
On Wed, 2019-04-10 at 14:41 +0200, Dmitry Vyukov wrote:
> On Wed, Apr 10, 2019 at 2:12 PM Al Viro wrote:
> >
> > On Wed, Apr 10, 2019 at 08:07:15PM +0800, Ian Kent wrote:
> >
> > > > I'm unable to find a branch matching the line numbers.
> > > >
> > > > Given that, on the face of it, the
On Wed, 10 Apr 2019 16:29:02 -0400
Joel Fernandes wrote:
> The srcu structure pointer array is modified at module load time because the
> array is fixed up by the module loader at load-time with the final locations
> of the tracepoints right? Basically relocation fixups. At compile time, I
>
Add code to instantiate the pmc_core platform device and thus attach to
the driver, if the ACPI device for the same ("INT33A1") is not present
in a system where it should be. This was discussed here:
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1966991.html
Signed-off-by: Rajat
Convert the intel_pmc_core driver to a platform driver, and attach using
the ACPI enumeration method (via the ACPI device "INT33A1").
Signed-off-by: Rajat Jain
---
v5: Remove the gerrit ID from commit log
v4: put back the x86_match_cpu() method.
v3: Don't instantiate the platform_device. Use
Add a module parameter which when enabled, will check on resume, if the
last S0ix attempt was successful. If not, the driver would warn and provide
helpful debug information (which gets latched during the failed suspend
attempt) to debug the S0ix failure.
This information is very useful to debug
On Thu, Apr 11, 2019 at 12:52 AM Joe Lawrence wrote:
>
> From: Josh Poimboeuf
>
> Define klp prefixes in include/uapi/linux/livepatch.h, and use them for
> replacing hard-coded values in kernel/livepatch/core.c.
>
> Update MAINTAINERS.
>
> Note: Add defines to uapi as these are also to be used
Add a module parameter which when enabled, will check on resume, if the
last S0ix attempt was successful. If not, the driver would warn and provide
helpful debug information (which gets latched during the failed suspend
attempt) to debug the S0ix failure.
This information is very useful to debug
Convert the intel_pmc_core driver to a platform driver, and attach using
the ACPI enumeration method (via the ACPI device "INT33A1").
Change-Id: I2c2c9bbff48a6548f5c96e18d766ffc4633762c0
Signed-off-by: Rajat Jain
---
v4: put back the x86_match_cpu() method.
v3: Don't instantiate the
Add code to instantiate the pmc_core platform device and thus attach to
the driver, if the ACPI device for the same ("INT33A1") is not present
in a system where it should be. This was discussed here:
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1966991.html
Change-Id:
On Wed, Apr 10, 2019 at 08:47:03AM -0400, Steven Rostedt wrote:
> On Wed, 10 Apr 2019 12:28:11 +0200
> Thomas Gleixner wrote:
>
> > It's only used in the source file where it is defined and it's using the
> > stack_trace_ namespace. Rename it to free it up for stack trace related
> > functions.
On 4/9/19 11:38 AM, Julien Desfossez wrote:
We found the source of the major performance regression we discussed
previously. It turns out there was a pattern where a task (a kworker in this
case) could be woken up, but the core could still end up idle before that
task had a chance to run.
Thanks for trying it both ways.
On Wed, Apr 10, 2019 at 4:43 PM Christian Brauner wrote:
>
> Hey Linus,
>
> This is an RFC for adding a new CLONE_PIDFD flag to clone() as
> previously discussed.
> While implementing this Jann and I ran into additional complexity that
> prompted us to send out an
Thanks for providing this example. A new nits below.
On Wed, Apr 10, 2019 at 4:43 PM Christian Brauner wrote:
>
> This is an sample program to show userspace how to get race-free access to
> process metadata from a pidfd.
> It is really not that difficult and instead of burdening the kernel with
On Wed, Apr 10, 2019 at 01:33:02PM -0700, Paul E. McKenney wrote:
> On Wed, Apr 10, 2019 at 09:19:18PM +0200, Sebastian Andrzej Siewior wrote:
> > On 2019-04-10 11:41:05 [-0700], Paul E. McKenney wrote:
> > > On Wed, Apr 10, 2019 at 08:15:38PM +0200, Sebastian Andrzej Siewior wrote:
> > > > On
Hi,
On Wed, Apr 10, 2019 at 11:30 AM Matthias Kaehlcke wrote:
>
> Some veyron devices have a Bluetooth controller connected on UART0.
> The UART needs to operate at a high speed, however setting the clock
> rate at initialization has no practical effect. During initialization
> user space
From: David Howells
Make the anon_inodes facility unconditional so that it can be used by core
VFS code and the pidfd_open() syscall.
Signed-off-by: David Howells
Signed-off-by: Al Viro
[christ...@brauner.io: adapt commit message to mention pidfd_open()]
Signed-off-by: Christian Brauner
---
This patchset makes it possible to retrieve pid file descriptors at process
creation time by introducing a new flag CLONE_PIDFD. As spotted by Linus,
there is exactly one bit left.
In this version of CLONE_PIDFD anonymous inode file descriptors are used.
They serve as a simple opaque handle on
Let pidfd_send_signal() use pidfds retrieved via CLONE_PIDFD. With this
patch pidfd_send_signal() becomes independent of procfs. This fullfils the
request made when we merged the pidfd_send_signal() patchset. The
pidfd_send_signal() syscall is now always available allowing for it to be
used by
Hey Linus,
This is an RFC for adding a new CLONE_PIDFD flag to clone() as
previously discussed.
While implementing this Jann and I ran into additional complexity that
prompted us to send out an initial RFC patchset to make sure we still
think going forward with the current implementation is a
Hi,
On Wed, Apr 10, 2019 at 11:38 AM Jonas Karlman wrote:
>
> On 2019-04-10 17:45, Doug Anderson wrote:
> > Hi,
> >
> > On Fri, Mar 29, 2019 at 2:55 PM Douglas Anderson
> > wrote:
> >> It appears that there is a typo in the rk3288 TRM. For
> >> GRF_SOC_CON0[7] it says that 0 means "vepu" and
This is an sample program to show userspace how to get race-free access to
process metadata from a pidfd.
It is really not that difficult and instead of burdening the kernel with
this task by using fds to /proc/ we can simply add a helper to libc
that does it for the user.
Signed-off-by:
This is an RFC for the implementation of pidfds as /proc/ file
descriptors. They can be retrieved through the clone() with the addition of
the CLONE_PIDFD flag.
The tricky part here is that we need to retrieve a file descriptor for
/proc/ before clone's point of no return. Otherwise, we need to
On 04/10/2019 02:55 AM, Paolo Bonzini wrote:
This check will soon be done on every nested vmentry and vmexit,
"parallelize" it using bitwise operations.
Signed-off-by: Paolo Bonzini
---
arch/x86/kvm/mtrr.c| 10 +-
arch/x86/kvm/vmx/vmx.c | 2 +-
arch/x86/kvm/x86.h | 8
On Wed, Apr 10, 2019 at 4:22 PM Josh Triplett wrote:
>
> On April 10, 2019 3:58:55 PM PDT, Kees Cook wrote:
> >On Wed, Apr 10, 2019 at 3:42 PM Sinan Kaya wrote:
> >>
> >> We can't seem to have a kernel with CONFIG_EXPERT set but
> >> CONFIG_DEBUG_KERNEL unset these days.
> >>
> >> While some of
On April 10, 2019 3:58:55 PM PDT, Kees Cook wrote:
>On Wed, Apr 10, 2019 at 3:42 PM Sinan Kaya wrote:
>>
>> We can't seem to have a kernel with CONFIG_EXPERT set but
>> CONFIG_DEBUG_KERNEL unset these days.
>>
>> While some of the features under the CONFIG_EXPERT require
>> CONFIG_DEBUG_KERNEL,
(*)(struct vm_fault *)'
[-Werror=incompatible-pointer-types]
.page_mkwrite = orangefs_page_mkwrite,
^
Caused by commit
c32607e8fc3b ("orangefs: write range tracking")
I have used the orangefs tree from next-20190410 for today.
--
Cheer
Arm64 machines should be displaying a human readable
vulnerability status to speculative execution attacks in
/sys/devices/system/cpu/vulnerabilities
This series enables that behavior by providing the expected
functions. Those functions expose the cpu errata and feature
states, as well as
Display the system vulnerability status. This means that
while its possible to have the mitigation enabled, the
sysfs entry won't indicate that status. This is because
the core ABI doesn't express the concept of mitigation
when the system isn't vulnerable.
Signed-off-by: Jeremy Linton
From: Mian Yousaf Kaukab
spectre v1, has been mitigated, and the mitigation is
always active.
Signed-off-by: Mian Yousaf Kaukab
Signed-off-by: Jeremy Linton
Reviewed-by: Andre Przywara
Reviewed-by: Catalin Marinas
Tested-by: Stefan Wahren
Acked-by: Suzuki K Poulose
---
The sysfs patches need to display machine vulnerability
status regardless of kernel config. Prepare for that
by breaking out the vulnerability/mitigation detection
code from the logic which implements the mitigation.
Signed-off-by: Jeremy Linton
Reviewed-by: Andre Przywara
Reviewed-by: Catalin
There are various reasons, including bencmarking, to disable spectrev2
mitigation on a machine. Provide a command-line to do so.
Signed-off-by: Jeremy Linton
Reviewed-by: Suzuki K Poulose
Reviewed-by: Andre Przywara
Reviewed-by: Catalin Marinas
Tested-by: Stefan Wahren
Cc: Jonathan Corbet
Add code to track whether all the cores in the machine are
vulnerable, and whether all the vulnerable cores have been
mitigated.
Once we have that information we can add the sysfs stub and
provide an accurate view of what is known about the machine.
Signed-off-by: Jeremy Linton
Reviewed-by:
The common ARM architecture code provides a generic function to exit
coherency called v7_exit_coherency_flush(). Replace the machine
specific implementation using the generic function.
Tested on a i.MX 6Dual by hotplugging the secondary CPU under load
through sysfs several 1000 times.
Tested-by:
From: Marc Zyngier
We currently have a list of CPUs affected by Spectre-v2, for which
we check that the firmware implements ARCH_WORKAROUND_1. It turns
out that not all firmwares do implement the required mitigation,
and that we fail to let the user know about it.
Instead, let's slightly revamp
The ssb detection logic is necessary regardless of whether
the vulnerability mitigation code is built into the kernel.
Break it out so that the CONFIG option only controls the
mitigation logic and not the vulnerability detection.
Signed-off-by: Jeremy Linton
Reviewed-by: Andre Przywara
From: Marc Zyngier
The SMCCC ARCH_WORKAROUND_1 service can indicate that although the
firmware knows about the Spectre-v2 mitigation, this particular
CPU is not vulnerable, and it is thus not necessary to call
the firmware on this CPU.
Let's use this information to our benefit.
Signed-off-by:
From: Mian Yousaf Kaukab
Enable CPU vulnerabilty show functions for spectre_v1, spectre_v2,
meltdown and store-bypass.
Signed-off-by: Mian Yousaf Kaukab
Signed-off-by: Jeremy Linton
Reviewed-by: Andre Przywara
Reviewed-by: Catalin Marinas
Tested-by: Stefan Wahren
---
arch/arm64/Kconfig |
Return status based on ssbd_state and the arm64 SSBS feature. If
the mitigation is disabled, or the firmware isn't responding then
return the expected machine state based on a whitelist of known
good cores.
Given a heterogeneous machine, the overall machine vulnerability
must be a tristate to
On Wed, Apr 10, 2019 at 03:12:05PM -0700, sathyanarayanan kuppuswamy wrote:
> On 4/10/19 11:41 AM, Bjorn Helgaas wrote:
> > On Tue, Mar 19, 2019 at 01:47:29PM -0700,
> > sathyanarayanan.kuppusw...@linux.intel.com wrote:
> > > From: Kuppuswamy Sathyanarayanan
> > >
> > >
> > > As per PCI
On Wed, Apr 10, 2019 at 3:42 PM Sinan Kaya wrote:
>
> We can't seem to have a kernel with CONFIG_EXPERT set but
> CONFIG_DEBUG_KERNEL unset these days.
>
> While some of the features under the CONFIG_EXPERT require
> CONFIG_DEBUG_KERNEL, it doesn't apply for all features.
>
> It looks like
Assorted command line option fixes for RISC-V.
Changes from v1->v2.
1. Update pr_err string in patch (4/4) as per review.
Atish Patra (4):
RISC-V: Add RISC-V specific arch_match_cpu_phys_id
RISC-V: Fix of_get_cpu_node usage
RISC-V: Implement nosmp commandline option.
RISC-V: Support nr_cpus
of_get_cpu_node expects a logical cpu id not a hartid.
Signed-off-by: Atish Patra
---
arch/riscv/kernel/cpu.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/riscv/kernel/cpu.c b/arch/riscv/kernel/cpu.c
index cf2fca12414a..c8d2a3223099 100644
---
nosmp command line option sets max_cpus to zero. No secondary harts
will boot if this is enabled. But present cpu mask will still point to
all possible masks.
Fix present cpu mask for nosmp usecase.
Signed-off-by: Atish Patra
---
arch/riscv/kernel/smpboot.c | 12 +++-
1 file changed,
If nr_cpus command line option is set, maximum possible cpu should be
set to that value.
Signed-off-by: Atish Patra
---
arch/riscv/kernel/smpboot. | 0
arch/riscv/kernel/smpboot.c | 10 +-
2 files changed, 9 insertions(+), 1 deletion(-)
create mode 100644 arch/riscv/kernel/smpboot.
OF/DT core has a hook for architecture specific logical cpuid to hartid
mapping. By implementing this, we can pass the logical cpu id to cpu
node parsing functions.
Signed-off-by: Atish Patra
---
arch/riscv/kernel/smp.c | 5 +
1 file changed, 5 insertions(+)
diff --git
LKML
http://chanathleticassociationbaseball.assn.la/Goto.asp?URL=https://bit.ly/2KAzcan=12781
Mark Underwood
--
Importance is one of the most important of our illusions. - Herbert Salzer
On Wed, 2019-04-10 at 23:03 +0100, Louis Taylor wrote:
> When compiling with -Wformat, clang warns:
>
> fs/afs/flock.c:632:29: warning: format specifies type 'short' but the
> argument has type
> 'unsigned char' [-Wformat]
> _leave(" = %d [%hd]", ret, fl->fl_type);
I really think
On Thu, Mar 7, 2019 at 7:43 AM Dan Williams wrote:
>
> On Thu, Mar 7, 2019 at 1:17 AM Guillaume Tucker
> wrote:
> >
> > On 06/03/2019 14:05, Mike Rapoport wrote:
> > > On Wed, Mar 06, 2019 at 10:14:47AM +, Guillaume Tucker wrote:
> > >> On 01/03/2019 23:23, Dan Williams wrote:
> > >>> On
On Wed, Apr 10, 2019 at 3:54 PM Matteo Croce wrote:
>
> On Thu, Apr 11, 2019 at 12:34 AM Kees Cook wrote:
> >
> > On Wed, Apr 10, 2019 at 3:30 PM Matteo Croce wrote:
> > >
> > > FYI, this are the stats from my local repo, just to let you the size
> > > of a series with all the changes in it:
>
On Thu, Mar 14, 2019 at 04:04:52PM -0400, Kimberly Brown wrote:
This patchset fixes a race condition in the "_show" functions that
access the channel ring buffers.
Changes in v3:
Patch 1: Drivers: hv: vmbus: Refactor chan->state if statement
- Added the “reviewed-by” line from v2.
Patch 2:
On Thu, Apr 11, 2019 at 12:34 AM Kees Cook wrote:
>
> On Wed, Apr 10, 2019 at 3:30 PM Matteo Croce wrote:
> >
> > FYI, this are the stats from my local repo, just to let you the size
> > of a series with all the changes in it:
> >
> > $ git --no-pager log --stat --oneline linus/master
> > 2
Quoting Nicholas Mc Guire (2019-04-06 20:13:24)
> Providing a range for usleep_range() allows the hrtimer subsystem to
> coalesce timers - the delay is runtime configurable so a factor 2
> is taken to provide the range.
>
> Signed-off-by: Nicholas Mc Guire
> ---
I think this driver is in
USB PowerShare is a policy which affects charging via the special
USB PowerShare port (marked with a small lightning bolt or battery icon)
when in low power states:
- In S0, the port will always provide power.
- In S0ix, if power_share is enabled, then power will be supplied to
the port when on
On Wed, Apr 10, 2019 at 3:41 PM Louis Taylor wrote:
>
> When compiling with -Wformat, clang warns:
>
> fs/afs/flock.c:632:29: warning: format specifies type 'short' but the
> argument has type
> 'unsigned char' [-Wformat]
> _leave(" = %d [%hd]", ret, fl->fl_type);
>
On Mon, Mar 11, 2019 at 04:23:55PM +, Nicholas Johnson wrote:
> Add new kernel parameters:
> - hp_io_size=nn
> - hp_mmio_size=nnM
> - hp_mmio_pref_size=nnM
>
> Depreciate old kernel parameters and print warning when used:
> - hpiosize=nn
> -
Boot on AC is a policy which makes the device boot from S5 when AC
power is connected. This is useful for users who want to run their
device headless or with a dock.
v2 changes:
- Move documentation to Documentation/ABI/testing/sysfs-platform-wilco-ec
Signed-off-by: Nick Crews
---
On 3/20/19 4:48 PM, Atish Patra wrote:
The cpu-map DT entry in ARM can describe the CPU topology in much better
way compared to other existing approaches. RISC-V can easily adopt this
binding to represent its own CPU topology. Thus, both cpu-map DT
binding and topology parsing code can be moved
The TLB flush counters under vmstat seems to be very helpful while
debugging TLB flush performance in RISC-V.
Add the Kconfig option only for debug kernels.
Signed-off-by: Atish Patra
---
arch/riscv/Kconfig.debug | 12
1 file changed, 12 insertions(+)
diff --git
CONFIG_DEBUG_TLBFLUSH was added in 'commit 3df3212f9722 ("x86/tlb: add
tlb_flushall_shift knob into debugfs")' to support tlb_flushall_shift
knob. The knob was removed in 'commit e9f4e0a9fe27 ("x86/mm: Rip out
complicated, out-of-date, buggy TLB flushing")'. However, the debug
option was never
The RISC-V patch (2/3) is based on Gary's TLB flush patch series
https://patchwork.kernel.org/project/linux-riscv/list/?series=97315
The x86 kconfig fix patch(1/3) can be applied separately.
Atish Patra (3):
x86: Update DEBUG_TLBFLUSH options description.
RISC-V: Update tlb flush counters
The TLB flush counters under vmstat seems to be very helpful while
debugging TLB flush performance in RISC-V.
Update the counters in every TLB flush methods respectively.
Signed-off-by: Atish Patra
---
arch/riscv/include/asm/tlbflush.h | 5 +
arch/riscv/mm/tlbflush.c | 12
We can't seem to have a kernel with CONFIG_EXPERT set but
CONFIG_DEBUG_KERNEL unset these days.
While some of the features under the CONFIG_EXPERT require
CONFIG_DEBUG_KERNEL, it doesn't apply for all features.
It looks like CONFIG_KALLSYMS_ALL is the only feature that
requires
When compiling with -Wformat, clang warns:
fs/afs/flock.c:632:29: warning: format specifies type 'short' but the argument
has type
'unsigned char' [-Wformat]
_leave(" = %d [%hd]", ret, fl->fl_type);
~~~ ^~~
fs/afs/dir.c:138:11: warning:
On Wed, Apr 10, 2019 at 3:30 PM Matteo Croce wrote:
>
> On Wed, Apr 10, 2019 at 11:51 PM Kees Cook wrote:
> >
> > On Wed, Apr 10, 2019 at 12:24 PM Matteo Croce wrote:
> > >
> > > On Wed, Apr 10, 2019 at 8:46 PM Kees Cook wrote:
> > > >
> > > > On Mon, Apr 8, 2019 at 3:09 PM Matteo Croce
On Wed, Apr 10, 2019 at 11:51 PM Kees Cook wrote:
>
> On Wed, Apr 10, 2019 at 12:24 PM Matteo Croce wrote:
> >
> > On Wed, Apr 10, 2019 at 8:46 PM Kees Cook wrote:
> > >
> > > On Mon, Apr 8, 2019 at 3:09 PM Matteo Croce wrote:
> > > >
> > > > Use the shared variables for range check, instead
On 4/10/2019 6:28 PM, Kees Cook wrote:
diff --git a/init/Kconfig b/init/Kconfig
index c9386a365eea..7ce4a60ab3e9 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -1188,8 +1188,6 @@ config BPF
menuconfig EXPERT
bool "Configure standard kernel features (expert users)"
- # Unhide
On Wed, Apr 10, 2019 at 3:25 PM Sinan Kaya wrote:
>
> On 4/10/2019 6:21 PM, Kees Cook wrote:
> >> I can go after individual enables if you agree assuming Mathieu will
> >> go after the changes in the other email. Let me know otherwise.
> > How about you split it, but make DEBUG_KERNEL be "default
On Wed, Apr 10, 2019 at 3:03 PM Louis Taylor wrote:
>
> When compiling with -Wformat, clang warns:
>
> fs/afs/flock.c:632:29: warning: format specifies type 'short' but the
> argument has type
> 'unsigned char' [-Wformat]
> _leave(" = %d [%hd]", ret, fl->fl_type);
>
On 4/10/2019 6:21 PM, Kees Cook wrote:
I can go after individual enables if you agree assuming Mathieu will
go after the changes in the other email. Let me know otherwise.
How about you split it, but make DEBUG_KERNEL be "default EXPERT" that
way enabling EXPERT will enable DEBUG_KERNEL still
On Wed, Apr 10, 2019 at 12:14:55PM +0200, David Hildenbrand wrote:
>While current node handling is probably terribly broken for memory block
>devices that span several nodes (only possible when added during boot,
>and something like that should be blocked completely), properly put the
>device
On Wed, Apr 10, 2019 at 3:18 PM Sinan Kaya wrote:
>
> On 4/10/2019 6:04 PM, Kees Cook wrote:
>
> >> I don't want any of the debug features in my kernel but still
> >> need all the expert features. My kernel is considered a production
> >> kernel. I don't really want to ship all the good debug
It has been observed, that highly-threaded, non-cpu-bound applications
running under cpu.cfs_quota_us constraints can hit a high percentage of
periods throttled while simultaneously not consuming the allocated
amount of quota. This use case is typical of user-interactive non-cpu
bound web
The following patch is an implementation of option 2 from my earlier e-mail.
Option #2 was the removal of all runtime_expires and related slice expiration
logic.
This is a very early iteration of this patch, and testing/comments are very
appreciated.
Thanks,
Dave.
On Wed, Apr 10, 2019 at 1:13 PM Arnd Bergmann wrote:
>
> llvm does does not understand -march=z9-109 and older target
Please file bugs for these in LLVM's issue tracker. It might be
possible to enable these additional architecture variants if they're
similar to existing ones and simply
On Mon, Apr 8, 2019 at 3:09 PM Matteo Croce wrote:
>
> In the sysctl code the proc_dointvec_minmax() function is often used to
> validate the user supplied value between an allowed range. This function
> uses the extra1 and extra2 members from struct ctl_table as minimum and
> maximum allowed
On 4/10/2019 6:04 PM, Kees Cook wrote:
I don't want any of the debug features in my kernel but still
need all the expert features. My kernel is considered a production
kernel. I don't really want to ship all the good debug enables.
Production kernels enable it. e.g. Ubuntu:
$ grep
On 4/10/2019 3:45 PM, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-04-10 12:39:16)
On 4/10/2019 10:53 AM, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-04-08 14:46:11)
On 4/4/2019 3:53 PM, Stephen Boyd wrote:
In some circumstances drivers register clks early and don't have access
to a
Stop enabling the oscillator and removing the oscillator failure flags in
probe. Instead, return -EINVAL in .read_time when the oscillaotr is not
start or when it failed at some point. The oscillator gets enabled on the
first .set_time after failure and the failure flags are cleared.
This also
Hi Joe,
On Wed, Apr 10, 2019 at 03:10:09PM -0700, Joe Perches wrote:
> On Wed, 2019-04-10 at 12:54 -0700, Guenter Roeck wrote:
> > A checkpatch rule suggesting that multiple extension lines can be merged
> > might be useful to help finding such situations. Just a thought.
>
> You are welcome to
101 - 200 of 880 matches
Mail list logo
