Hi Krzysztof,
Thank you for the update.
Patch set looks good to me.
Now we're missing only ack from Rob for this patch.
Best regards,
Jacek Anaszewski
On 1/9/19 3:44 PM, Krzysztof Kozlowski wrote:
Document new led-pattern property for initialization of LED triggers.
The property format is tr
On 1/9/19 11:32 AM, Johannes Weiner wrote:
On Thu, Jan 10, 2019 at 03:14:40AM +0800, Yang Shi wrote:
We have some usecases which create and remove memcgs very frequently,
and the tasks in the memcg may just access the files which are unlikely
accessed by anyone else. So, we prefer force_empt
This patch implements sparsemem support for risc-v which helps pave the
way for memory hotplug and eventually P2P support.
We introduce Kconfig options for virtual and physical address bits which
are used to calculate the size of the vmemmap and set the
MAX_PHYSMEM_BITS.
The vmemmap is located di
Cleanup the open coded for_each_memblock() loop that is equivalent
to the new memblocks_present() helper.
Signed-off-by: Logan Gunthorpe
Cc: Yoshinori Sato
Cc: Rich Felker
Cc: Dan Williams
Cc: Rob Herring
---
arch/sh/mm/init.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff
This patchset implements sparsemem on RISC-V. The first couple patches
from the previous version have been merged into v4.20 and the ARM patches
have been sent separately to the ARM maintainers. These are the RISC-V
patches only.
This is the first small step in supporting P2P on RISC-V.
--
Chang
On Wed, Jan 09, 2019 at 05:52:20PM +0100, Paul Kocialkowski wrote:
> Hi Daniel,
>
> On Tue, 2019-01-08 at 19:21 +0100, Daniel Vetter wrote:
> > On Tue, Jan 8, 2019 at 3:51 PM Paul Kocialkowski
> > wrote:
> > > During an atomic commit, the HVS is configured with a display list
> > > for the channe
While replacing idr_alloc_cyclic(), I've come across a situation in
which being able to depend on -fplan9-extensions is going to lead to
nicer code in the users.
For cyclic allocations, we need to keep a 'next' value somewhere.
The IDR had a moderately large root, so they didn't mind the cost to
Commit 8c8c10b90d88 ("powerpc/8xx: fix handling of early NULL pointer
dereference") moved the loading of r6 earlier in the code. As some
functions are called inbetween, r6 needs to be loaded again with the
address of swapper_pg_dir in order to set PTE pointers for
the Abatron BDI.
Fixes: 8c8c10b90
Cleanup the arm_memory_present() function seeing it's very
similar to other arches.
The new memblocks_present() helper checks for node ids which the
arm version did not. However, this is equivalent seeing
HAVE_MEMBLOCK_NODE_MAP should be false in this arch and therefore
memblock_get_region_node()
Hey,
We've recently added a new memblocks_present() helper macro to clean
up some common code with ARM and code we are adding in RISC-V. The
commit that added the helper is:
9def36e0fa9a ("mm/sparse: add common helper to mark all memblocks present")
This series includes two patches to switch ARM
Cleanup the arm64_memory_present() function seeing it's very
similar to other arches.
memblocks_present() is a direct replacement of arm64_memory_present()
Signed-off-by: Logan Gunthorpe
Acked-by: Catalin Marinas
Cc: Will Deacon
---
arch/arm64/mm/init.c | 20 +---
1 file chang
GFP_KERNEL is one of the most used constant but on archs like arm
with fixed length instruction some constants are more equal than
the others. Constants with tightly packed bits can be injected directly
into instruction stream:
0: e3a00d33mov r0, #3264 ; 0xcc0
Other
On 01/09/2019 02:59 PM, Matthew Wilcox wrote:
> On Wed, Jan 09, 2019 at 01:54:36PM -0500, Waiman Long wrote:
>> If you read patch 4, you can see that quite a bit of CPU cycles was
>> spent looking up the radix tree to locate the IRQ descriptor for each of
>> the interrupts. Those overhead will stil
On Wed, Jan 9, 2019 at 11:46 AM James Bottomley
wrote:
>
> On Wed, 2019-01-09 at 10:34 -0800, Andy Lutomirski wrote:
> > > > On Jan 8, 2019, at 10:49 PM, James Bottomley > > > senpartnership.com> wrote:
> > > >
> > If so, then a signature that the kernel would have prevented user
> > code from
Hi Greg,
Please pull these lkdtm changes for next (into, I assume, your
drivers-misc tree).
Thanks!
-Kees
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
https://git.kernel.org/
Hi Dan,
On 1/8/19 10:22 PM, Dan Murphy wrote:
On 1/8/19 3:16 PM, Jacek Anaszewski wrote:
On 1/8/19 9:53 PM, Dan Murphy wrote:
Jacek
On 1/8/19 2:33 PM, Jacek Anaszewski wrote:
Dan,
On 12/19/18 5:26 PM, Dan Murphy wrote:
Introduce the bindings for the Texas Instruments LP5024 and the LP5018
On Wed, Jan 9, 2019 at 7:16 AM Kees Cook wrote:
>
> On Tue, Jan 8, 2019 at 10:31 PM Christophe Leroy
> wrote:
> >
> >
> >
> > Le 09/01/2019 à 02:14, Kees Cook a écrit :
> > > On Fri, Dec 14, 2018 at 7:26 AM Christophe Leroy
> > > wrote:
> > >>
> > >> Introduce lkdtm tests for NULL pointer derefe
On Wed, Jan 09, 2019 at 10:40:20AM -0800, Linus Torvalds wrote:
> Side note: I do wish people would use the proper _public_ access.
I'm wondering if this largely happens due to people's insteadOf rules.
We've established that git-request-pull will quietly substitute URLs in
the emails it generates
On Wed, Jan 09, 2019 at 01:54:36PM -0500, Waiman Long wrote:
> If you read patch 4, you can see that quite a bit of CPU cycles was
> spent looking up the radix tree to locate the IRQ descriptor for each of
> the interrupts. Those overhead will still be there even if I use percpu
> counters. So usin
Add reference to scaling document into main table of contents in network
documentation.
Signed-off-by: Otto Sabart
---
Documentation/networking/index.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/networking/index.rst
b/Documentation/networking/index.rst
index 6a47629ef8e
Add markups which are necessary for successful conversion into
reStructuredText.
There are no semantic changes.
Signed-off-by: Otto Sabart
---
Documentation/networking/scaling.txt | 131 +--
1 file changed, 85 insertions(+), 46 deletions(-)
diff --git a/Documentation/ne
P010 is a planar 4:2:0 YUV with interleaved UV plane, 10 bits per
channel video format.
P012 is a planar 4:2:0 YUV 12 bits per channel
P016 is a planar 4:2:0 YUV with interleaved UV plane, 16 bits per
channel video format.
V3: Added P012 and fixed cpp for P010.
V4: format definition refined per
As the requirement from:
P010 fourcc format support - Was: Re: Kernel error "Unknown pixelformat
0x" occurs when I start capture video
I don't know which device would support the P010, P012, P016 video pixel
format, but Rockchip would support that NV12_10LE40 and a patch for that
driver is
Just rename the scaling file to be found by Sphinx.
There are no references to "scaling.txt" file. Whole kernel tree was
checked using:
$ grep -r "scaling\.txt"
Signed-off-by: Otto Sabart
---
Documentation/networking/{scaling.txt => scaling.rst} | 0
1 file changed, 0 insertions(+), 0 deletions
This pixel format is a fully packed and 10bits variant of NV12.
A luma pixel would take 10bits in memory, without any
filled bits between pixels in a stride.
Signed-off-by: Randy Li
---
drivers/gpu/drm/drm_fourcc.c | 4
include/uapi/drm/drm_fourcc.h | 8
2 files changed, 12 insert
These patches integrate scaling document into documentation tree.
There are no semantic changes.
Otto Sabart (3):
doc: networking: prepare scaling document for conversion into RST
doc: networking: convert scaling doc into RST
doc: networking: add scaling doc into index file
Documentation/
From: Tom Zanussi
The action refactor code allowed actions and handlers to be separated,
but the existing onmax handler and save action code is still not
flexible enough to handle arbitrary coupling. This change generalizes
them and in the process makes additional handlers and actions easier
to
From: Tom Zanussi
The action/handler code refactoring didn't change the action/handler
syntax, but did generalize it - the Documentation should reflect that.
Signed-off-by: Tom Zanussi
---
Documentation/trace/histogram.rst | 56 ++-
1 file changed, 43 insert
From: Tom Zanussi
Add Documentation for the hist:handlerXXX($var).snapshot() action.
Signed-off-by: Tom Zanussi
---
Documentation/trace/histogram.rst | 110 ++
1 file changed, 110 insertions(+)
diff --git a/Documentation/trace/histogram.rst
b/Documentation
Do you have photos for editing? We asked this because we see your photos on
your website.
We mainly supply service for photos cut out , clipping path, and
retouching.
You may just send us a photo, we can provide you test editing to check
quality.
Thanks,
Jane
From: Tom Zanussi
Currently, tracing snapshots are context-free - they capture the ring
buffer contents at the time the tracing_snapshot() function was
invoked, and nothing else. Additionally, they're always taken
unconditionally - the calling code can decide whether or not to take a
snapshot, b
From: Tom Zanussi
Add a 'trace(synthetic_event_name, params)' alternative to
synthetic_event_name(params).
Currently, the syntax used for generating synthetic events is to
invoke synthetic_event_name(params) i.e. use the synthetic event name
as a function call.
Users requested a new form that m
From: Tom Zanussi
Add support for a hist:onchange($var) handler, similar to the onmax()
handler but triggering whenever there's any change in $var, not just a
max.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace.c | 3 ++-
kernel/trace/trace_events_hist.c | 58 ++
Do you have photos for editing? We asked this because we see your photos on
your website.
We mainly supply service for photos cut out , clipping path, and
retouching.
You may just send us a photo, we can provide you test editing to check
quality.
Thanks,
Jane
From: Tom Zanussi
Add a test case verifying the basic functionality of the
hist:snapshot() action.
Signed-off-by: Tom Zanussi
Acked-by: Masami Hiramatsu
---
.../inter-event/trigger-snapshot-action-hist.tc| 43 ++
1 file changed, 43 insertions(+)
create mode 100644
to
From: Tom Zanussi
Add a test case verifying that basic action combinations fail as
expected.
Signed-off-by: Tom Zanussi
---
.../inter-event/trigger-action-hist-xfail.tc | 30 ++
1 file changed, 30 insertions(+)
create mode 100644
tools/testing/selftests/ftrace/test.
From: Tom Zanussi
Add a test case verifying the basic functionality of the
hist:onchange($var) handler.
Signed-off-by: Tom Zanussi
Acked-by: Masami Hiramatsu
---
.../inter-event/trigger-onchange-action-hist.tc| 28 ++
1 file changed, 28 insertions(+)
create mode 10064
From: Tom Zanussi
Apparently this directory was missed in the license cleanup process -
add the missing identifiers to the trigger/inter-event test cases.
Signed-off-by: Tom Zanussi
---
.../ftrace/test.d/trigger/inter-event/trigger-extended-error-support.tc | 1 +
.../ftrace/test.d/trigger/in
From: Tom Zanussi
Add a test case for the alternative trace(
---
.../inter-event/trigger-trace-action-hist.tc | 42 ++
1 file changed, 42 insertions(+)
create mode 100644
tools/testing/selftests/ftrace/test.d/trigger/inter-event/trigger-trace-action-hist.tc
diff --gi
From: Tom Zanussi
Currently, the onmatch action data binds the onmatch action to data
related to synthetic event generation. Since we want to allow the
onmatch handler to potentially invoke a different action, and because
we expect other handlers to generate synthetic events, we need to
separate
From: Tom Zanussi
Add support for hist:handlerXXX($var).snapshot(), which will take a
snapshot of the current trace buffer whenever handlerXXX is hit.
As a first user, this also adds snapshot() action support for the
onmax() handler i.e. hist:onmax($var).snapshot().
Also, the hist trigger key p
From: Tom Zanussi
Add Documentation for the hist:onchange($var) handler.
Signed-off-by: Tom Zanussi
---
Documentation/trace/histogram.rst | 98 +++
1 file changed, 98 insertions(+)
diff --git a/Documentation/trace/histogram.rst
b/Documentation/trace/histog
From: Tom Zanussi
The hist trigger action code currently implements two essentially
hard-coded pairs of 'actions' - onmax(), which tracks a variable and
saves some event fields when a max is hit, and onmatch(), which is
hard-coded to generate a synthetic event.
These hardcoded pairs (track max/s
From: Tom Zanussi
Hi,
This is v11 of the hist trigger snapshot and onchange additions
patchset.
It doesn't add anything new - it's just a rebase of v10 on top of the
latest ftrace/core with conflicts due to the new str_has_prefix()
fixed.
Thanks,
Tom
v10->v11 changes:
- Updated to use st
Quoting Jeffrey Hugo (2018-12-17 18:15:36)
> Add rpm smd clocks, PMIC and bus clocks which are required on MSM8998
> for clients to vote on.
>
> Signed-off-by: Jeffrey Hugo
> ---
Applied to clk-next
On Wed, 2019-01-09 at 10:34 -0800, Andy Lutomirski wrote:
> > > On Jan 8, 2019, at 10:49 PM, James Bottomley > > senpartnership.com> wrote:
> > >
> > > On Tue, 2019-01-08 at 17:43 -0800, Andy Lutomirski wrote:
> > > [Adding Jarkko because this stuff relates to the TPM.]
> > > Anyway, if we're tal
On Wed, 9 Jan 2019 18:07:19 +0100
Pierre Morel wrote:
> On 09/01/2019 16:37, Alex Williamson wrote:
> > On Wed, 9 Jan 2019 13:41:53 +0100
> > Pierre Morel wrote:
> >
> >> We add a new flag, VFIO_IOMMU_INFO_CAPABILITIES, inside the
> >> vfio_iommu_type1_info to specify the support for capabil
Quoting Jan Kotas (2018-12-13 04:49:29)
> This patch adds a driver for Fixed MMIO clock.
> The driver reads a clock frequency value from a single 32-bit memory
> mapped register and registers it as a fixed rate clock.
>
> It can be enabled with COMMON_CLK_FIXED_MMIO Kconfig option.
>
> Signed-off
Quoting Jan Kotas (2018-12-13 04:49:29)
> This patch adds a driver for Fixed MMIO clock.
> The driver reads a clock frequency value from a single 32-bit memory
> mapped register and registers it as a fixed rate clock.
>
> It can be enabled with COMMON_CLK_FIXED_MMIO Kconfig option.
>
> Signed-off
Quoting Jan Kotas (2018-12-13 04:49:28)
> This patch adds a DT binding documentation for Fixed
> Memory Mapped IO clocks.
>
> Signed-off-by: Jan Kotas
> ---
Applied to clk-next
On Wed, Jan 09, 2019 at 03:38:11PM +0100, Greg Kroah-Hartman wrote:
> On Tue, Jan 08, 2019 at 03:07:31PM -0800, Guenter Roeck wrote:
> > On Mon, Jan 07, 2019 at 01:30:27PM +0100, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 4.19.14 release.
> > > There are 17
On Wed, Jan 9, 2019 at 1:02 PM H. Nikolaus Schaller wrote:
>
> From: Tony Lindgren
>
> We're currently getting a warning with make dtbs:
>
> arch/arm/boot/dts/omap3-gta04.dtsi:720.7-727.4: Warning (graph_port):
> /ocp@6800/dss@4805/encoder@48050c0 0/port: graph node unit
> address error,
On Wed, Jan 9, 2019 at 11:31 AM Lina Iyer wrote:
>
> On Tue, Jan 08 2019 at 07:49 -0700, Rob Herring wrote:
> >On Mon, Jan 7, 2019 at 12:51 PM Lina Iyer wrote:
> >>
> >> On Fri, Dec 28 2018 at 17:07 -0700, Rob Herring wrote:
> >> >On Wed, Dec 19, 2018 at 03:11:02PM -0700, Lina Iyer wrote:
> >> >>
On Wed, 2019-01-09 at 20:09 +0100, Otto Sabart wrote:
> There is no `samsung,exynos5250-trng.txt` file in the documentation and
> I do not think it ever existed.
There was a patch for this
https://patchwork.kernel.org/patch/10623153/
But is is still unapplied...
> diff --git a/MAINTAINERS b/MAI
The patch
regulator: provide rdev_get_regmap()
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
On 2019-01-09 12:32 p.m., Dave Jiang wrote:
>> I'm resending this because I've recently found out that the change we
>> made to use the NTB struct device in DMA allocations is wrong and
>> needs to be reverted. Turns out that, when running with an IOMMU,
>> dma_alloc_coherent() will always fail
Since we now have a str_has_prefix() that returns the length, we can
use that instead of explicitly calculating it.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace_events_hist.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/kernel/trace/trace_events_hist.c b/kernel/trac
On Thu, Jan 10, 2019 at 03:14:40AM +0800, Yang Shi wrote:
>
> We have some usecases which create and remove memcgs very frequently,
> and the tasks in the memcg may just access the files which are unlikely
> accessed by anyone else. So, we prefer force_empty the memcg before
> rmdir'ing it to rec
On 1/9/19 12:22 PM, Logan Gunthorpe wrote:
> Hey,
>
> I'm resending this because I've recently found out that the change we
> made to use the NTB struct device in DMA allocations is wrong and
> needs to be reverted. Turns out that, when running with an IOMMU,
> dma_alloc_coherent() will always
On 1/9/2019 11:59 AM, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-01-04 08:50:15)
The gcc_usb3_phy_pipe_clk is generated by the phy, but is also used by
the phy during init. The clock needs to be enabled during the init
sequence, but may not be fully active until after the init sequence is
c
Quoting David Dai (2018-12-13 18:35:04)
> The current clk-rpmh driver only supports on and off RPMh clock resources,
> let's extend the current driver by add support for clocks that are managed
> by a different type of RPMh resource known as Bus Clock Manager(BCM).
> The BCM is a configurable share
On 09.01.2019 20:06, Tony Lindgren wrote:
> Hi all,
>
> Commit 6e2d85ec0559 ("net: phy: Stop with excessive soft reset") caused
> a regression where suspend resume cycle fails to bring up Ethernet on at
> least cpsw on am437x-sk-evm.
>
What kind of PHY and which PHY driver is used with this board
On Wed, 9 Jan 2019 11:13:44 + Mel Gorman
wrote:
> Full compaction of a node passes in negative orders which can lead to array
> boundary issues. While it could be addressed in the control flow of the
> primary loop, it would be fragile so explicitly check for the condition.
> This is a fix f
On Wed, Jan 09, 2019 at 04:03:16PM +0100, Mike Galbraith wrote:
> On Wed, 2019-01-09 at 15:42 +0100, Adam Borowski wrote:
> > On Wed, Jan 09, 2019 at 06:38:58AM +0100, Mike Galbraith wrote:
> > > KVM seems to be busted in master ATM. All I have to do to have host
> > > start screaming and maybe ex
Hi Sebastian,
>>> +static int ll_register_fm(struct ll_device *lldev)
>>> +{
>>> + struct device *dev = &lldev->serdev->dev;
>>> + int err;
>>> +
>>> + if (!of_device_is_compatible(dev->of_node, "ti,wl1281-st") &&
>>> + !of_device_is_compatible(dev->of_node, "ti,wl1283-st") &&
>>> +
For better performance analysis of dynamically JITed and loaded kernel
functions, such as BPF programs, this patch introduces
PERF_RECORD_KSYMBOL, a new perf_event_type that exposes kernel symbol
register/unregister information to user space.
The following data structure is used for PERF_RECORD_KS
This patch synthesize PERF_RECORD_KSYMBOL and PERF_RECORD_BPF_EVENT for
BPF programs loaded before perf-record. This is achieved by gathering
information about all BPF programs via sys_bpf.
Signed-off-by: Song Liu
---
tools/perf/builtin-record.c | 6 ++
tools/perf/util/bpf-event.c | 205 ++
Commit 417cf39cfea9 ("NTB: Set dma mask and dma coherent mask to NTB
devices") started using the NTB device for DMA allocations which was
turns out was wrong. If the IOMMU is enabled, such alloctanions will
always fail with messages such as:
DMAR: Allocating domain for :02:00.1 failed
This
This commit fixes pingpong support for existing drivers that do not
implement ntb_default_port_number() and ntb_default_peer_port_number().
This is required for hardware (like the crosslink topology of
switchtec) which cannot assign reasonable port numbers to each port due
to its perfect symmetry.
This set catches symbol for all bpf programs loaded/unloaded
before/during/after perf-record run PERF_RECORD_KSYMBOL and
PERF_RECORD_BPF_EVENT.
PERF_RECORD_KSYMBOL and PERF_RECORD_BPF_EVENT includes key information
of a bpf program load and unload. They are sent through perf ringbuffer,
and stored
Hey,
I'm resending this because I've recently found out that the change we
made to use the NTB struct device in DMA allocations is wrong and
needs to be reverted. Turns out that, when running with an IOMMU,
dma_alloc_coherent() will always fail if you pass it the NTB struct
device. This is because
When running ntb_test this warning is issued:
./ntb_test.sh: line 200: warning: command substitution: ignored null
byte in input
This is caused by the kernel returning one more byte than is necessary
when reading the link file.
Reduce the number of bytes read back to 2 as it was before the
commi
When remote files are counted in get_files_count, without using SSH,
the code returns 0 because there is a colon prepended to $LOC. $VPATH
should have been used instead of $LOC.
Fixes: 06bd0407d06c ("NTB: ntb_test: Update ntb_tool Scratchpad tests")
Signed-off-by: Logan Gunthorpe
Acked-by: Allen
When running ntb_test, the script tries to run the ntb_perf test
immediately after probing the modules. Since adding multi-port support,
this fails seeing the new initialization procedure in ntb_perf
can not complete instantly.
To fix this we add a completion which is waited on when a test is
star
On Thu, 2019-01-10 at 00:48 +0800, Kairui Song wrote:
> Currently kexec_file_load will verify the kernel image being loaded
> against .builtin_trusted_keys or .secondary_trusted_keys, but the
> image could be signed with third part keys which will be provided by
> platform or firmware and the keys
Legacy drivers do not have port numbers (but is reliably only two ports)
and was broken by the recent commit that added mult-port support to
ntb_perf. This is especially important to support the cross link
topology which is perfectly symmetric and cannot assign unique port
numbers easily.
Hardware
When the commit adding ntb_default_port_number() and
ntb_default_peer_port_number() entered the kernel there was no
users of it so it was impossible to tell what the API needed.
When a user finally landed a year later (ntb_pingpong) there were
more NTB topologies were created and no consideration
sync changes for PERF_RECORD_KSYMBOL
Signed-off-by: Song Liu
---
tools/include/uapi/linux/perf_event.h | 26 +-
1 file changed, 25 insertions(+), 1 deletion(-)
diff --git a/tools/include/uapi/linux/perf_event.h
b/tools/include/uapi/linux/perf_event.h
index 9de8780ac8d9.
ntb_perf should not require more than one memory window per peer. This
was probably an off-by-one error.
Fixes: 5648e56d03fa ("NTB: ntb_perf: Add full multi-port NTB API support")
Signed-off-by: Logan Gunthorpe
Acked-by: Allen Hubbe
Tested-by: Alexander Fomichev
---
drivers/ntb/test/ntb_perf.c
This patch adds basic handling of PERF_RECORD_BPF_EVENT.
Tracking of PERF_RECORD_BPF_EVENT is OFF by default. Option --bpf-event
is added to turn it on.
Signed-off-by: Song Liu
---
tools/perf/builtin-record.c | 1 +
tools/perf/perf.h | 1 +
tools/perf/util/Build | 2 ++
tools/
This patch handles PERF_RECORD_KSYMBOL in perf record/report.
Specifically, map and symbol are created for ksymbol register, and
removed for ksymbol unregister.
This patch also set perf_event_attr.ksymbol properly. The flag is
ON by default.
Signed-off-by: Song Liu
---
tools/perf/util/event.c
For better performance analysis of BPF programs, this patch introduces
PERF_RECORD_BPF_EVENT, a new perf_event_type that exposes BPF program
load/unload information to user space.
Each BPF program may contain up to BPF_MAX_SUBPROGS (256) sub programs.
The following example shows kernel symbols for
sync for PERF_RECORD_BPF_EVENT
Signed-off-by: Song Liu
---
tools/include/uapi/linux/perf_event.h | 29 ++-
1 file changed, 28 insertions(+), 1 deletion(-)
diff --git a/tools/include/uapi/linux/perf_event.h
b/tools/include/uapi/linux/perf_event.h
index 68c4da0227c5..8bd7
We have some usecases which create and remove memcgs very frequently,
and the tasks in the memcg may just access the files which are unlikely
accessed by anyone else. So, we prefer force_empty the memcg before
rmdir'ing it to reclaim the page cache so that they don't get
accumulated to incur unn
After skipping the percpu summation of non-active IRQs on a 4-socket
Broadwell system with about 3k IRQs, about half of the CPU cycles were
spent in the kstat_irqs() call. The majority of which were used to look
up the IRQ descriptors for the corresponding IRQ numbers.
We can recoup a lot of those
mem_cgroup_force_empty() will be reused by the following patch which
does memory reclaim when offlining. It is unnecessary to do swap in that
path, but force_empty still needs keep intact since it is also used by
other usecases per Shakeel.
So, introduce may_swap parameter to mem_cgroup_force_emp
v1: https://lkml.org/lkml/2019/1/7/899
v2: Fix a minor bug in patch 4 & update the cover-letter.
As newer systems have more and more IRQs and CPUs available in their
system, the performance of reading /proc/stat frequently is getting
worse and worse.
It appears that the idea of caching the IRQ
A new atomic variable nr_active_irqs is added to track the number of
active IRQs that have one or more interrupts serviced.
Signed-off-by: Waiman Long
---
kernel/irq/internals.h | 7 +--
kernel/irq/irqdesc.c | 5 +
2 files changed, 10 insertions(+), 2 deletions(-)
diff --git a/kernel/
Recent computer systems may have hundreds or even thousands of IRQs
available. However, most of them may not be active and their IRQ counts
are zero. It is just a waste of CPU cycles to do percpu summation of
those zero counts.
In order to find out if an IRQ is active, we track the transition of t
The code that generates the "intr" line of /proc/stat is now moved
from show_stat() into a new function - show_stat_irqs(). There is no
functional change.
Signed-off-by: Waiman Long
Reviewed-by: Kees Cook
---
fs/proc/stat.c | 39 +--
1 file changed, 29 insert
The default hierarchy doesn't support force_empty, but there are some
usecases which create and remove memcgs very frequently, and the
tasks in the memcg may just access the files which are unlikely
accessed by anyone else. So, we prefer force_empty the memcg before
rmdir'ing it to reclaim the page
On Wed, Jan 09, 2019 at 09:44:28AM -0800, Shakeel Butt wrote:
> Hi Johannes,
>
> On Wed, Jan 9, 2019 at 8:45 AM Johannes Weiner wrote:
> >
> > On Wed, Jan 09, 2019 at 03:20:18PM +0300, Kirill Tkhai wrote:
> > > On nodes without memory overcommit, it's common a situation,
> > > when memcg exceeds
Add desprition of wipe_on_offline interface in cgroup documents.
Cc: Michal Hocko
Cc: Johannes Weiner
Cc: Shakeel Butt
Signed-off-by: Yang Shi
---
Documentation/admin-guide/cgroup-v2.rst | 9 +
Documentation/cgroup-v1/memory.txt | 10 ++
2 files changed, 19 insertions(+)
We don't do page cache reparent anymore when offlining memcg, so update
force empty related content accordingly.
Reviewed-by: Shakeel Butt
Acked-by: Michal Hocko
Cc: Johannes Weiner
Signed-off-by: Yang Shi
---
Documentation/cgroup-v1/memory.txt | 7 ---
1 file changed, 4 insertions(+), 3
We have some usecases which create and remove memcgs very frequently,
and the tasks in the memcg may just access the files which are unlikely
accessed by anyone else. So, we prefer force_empty the memcg before
rmdir'ing it to reclaim the page cache so that they don't get
accumulated to incur unnec
Hello RT Folks!
I'm pleased to announce the 3.18.129-rt111 stable release.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
branch: v3.18-rt
Head SHA1: abae91683efc5c482d2fbbad07010decde532360
Or to build 3.18.129-rt111 di
On Wed, Jan 09, 2019 at 08:17:36PM +0530, Pankaj Gupta wrote:
> Virtio pmem provides asynchronous host page cache flush
> mechanism. we don't support 'MAP_SYNC' with virtio pmem
> and xfs.
>
> Signed-off-by: Pankaj Gupta
> ---
> fs/xfs/xfs_file.c | 8
> 1 file changed, 8 insertions(+)
On Thu, Jan 10, 2019 at 12:21:24AM +0530, b-ak wrote:
> > Note that the reason we've not done that already for everything is that
> > the DAPM graph needs updating for the new routing in machine drivers as
> > the two widgets are wired differently. However this is fine here as
> > there aren't an
--
I solicit your cooperation to transfer $7 million to your bank account
and you will be entitled to 40% of this fund, respond urgent if you
are capable for more details.
There is no `samsung,exynos5250-trng.txt` file in the documentation and
I do not think it ever existed.
Signed-off-by: Otto Sabart
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 32d76a90..609451bf2b1a 100644
--- a/MAINTAINERS
+++ b/MAINTAIN
401 - 500 of 1253 matches
Mail list logo
