On Thu, Jan 31, 2019 at 02:18:59PM -0500, Mimi Zohar wrote:
> diff --git a/kernel/module.c b/kernel/module.c
> index 2ad1b5239910..70a9709d19eb 100644
> --- a/kernel/module.c
> +++ b/kernel/module.c
> @@ -275,16 +275,23 @@ static void module_assert_mutex_or_preempt(void)
>
> static bool
On Mon, Feb 04, 2019 at 12:10:42PM -0300, Arnaldo Carvalho de Melo wrote:
> Noticed this now when building with PYTHON=python3, can you take a look?
> For now I'm reinstalling python2-devel and building with it, i.e.
> removing that PYTHON=python3 make command line variable.
>
> [root@quaco ~]#
On 2/4/2019 2:43 PM, Borislav Petkov wrote:
On Mon, Feb 04, 2019 at 01:57:49PM -0500, Liang, Kan wrote:
You mean a given microcode revision X applying to multiple stepping,
right?
Yes, the range thing. You specify a range of steppings:
kabylake mobile with steppings 9-12
kabylake desktop
2 ELF header aren't that large to allocate them on heap.
However, code is bloated by 1.5 KB (!!!) with gcc 8.2 and stack size
grows by ~340 bytes.
The problem is that 2 elf headers are only 128 bytes.
I'm shocked and the patch should not be applied probably.
Signed-off-by: Alexey Dobriyan
---
This patch adds the command buffer (CB) module, which allows the user to
create and destroy CBs and to map them to the user's process
address-space.
A command buffer is a memory blocks that reside in DMA-able address-space
and is physically contiguous so it can be accessed by the device without
This patch implements the INFO IOCTL. That IOCTL is used by the user to
query information that is relevant/needed by the user in order to submit
deep learning jobs to Goya.
The information is divided into several categories, such as H/W IP, Events
that happened, DDR usage and more.
This patch adds two modules - ASID and context.
Each user process that opens a device's file must have at least one
context before it is able to "work" with the device. Each context has its
own device address-space and contains information about its runtime state
(its active command submissions).
This patch adds support for receiving events from Goya's control CPU and
for receiving MSI-X interrupts from Goya's DMA engines and CPU.
Goya's PCI controller supports up to 8 MSI-X interrupts, which only 6 of
them are currently used. The first 5 interrupts are dedicated for Goya's
DMA engine
This patch adds debugfs support to the driver. It allows the user-space to
display information that is contained in the internal structures of the
driver, such as:
- active command submissions
- active user virtual memory mappings
- number of allocated command buffers
It also enables the user to
The habanalabs driver was written from scratch from the very first days
of Habana and is maintained by Oded Gabbay.
Signed-off-by: Oded Gabbay
---
CREDITS | 2 +-
MAINTAINERS | 9 +
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/CREDITS b/CREDITS
index
This patch adds support for doing various on-the-fly reset of Goya.
The driver supports two types of resets:
1. soft-reset
2. hard-reset
Soft-reset is done when the device detects a timeout of a command
submission that was given to the device. The soft-reset process only resets
the engines that
This patch adds the main flow for the user to submit work to the device.
Each work is described by a command submission object (CS). The CS contains
3 arrays of command buffers: One for execution, and two for context-switch
(store and restore).
For each CB, the user specifies on which queue to
From: Omer Shpigelman
This patch adds the Virtual Memory and MMU modules.
Goya has an internal MMU which provides process isolation on the internal
DDR. The internal MMU also performs translations for transactions that go
from Goya to the Host.
The driver is responsible for allocating and
This patch add the sysfs and hwmon entries that are exposed by the driver.
Goya has several sensors, from various categories such as temperature,
voltage, current, etc. The driver exposes those sensors in the standard
hwmon mechanism.
In addition, the driver exposes a couple of interfaces in
This patch adds the H/W queues module and the code to initialize Goya's
various compute and DMA engines and their queues.
Goya has 5 DMA channels, 8 TPC engines and a single MME engine. For each
channel/engine, there is a H/W queue logic which is used to pass commands
from the user to the H/W.
This patch adds a basic support for the Goya device. The code initializes
the device's PCI controller and PCI bars. It also initializes various S/W
structures and adds some basic helper functions.
Signed-off-by: Oded Gabbay
---
drivers/misc/habanalabs/Makefile| 4 +
This patch adds the habanalabs skeleton driver. The driver does nothing at
this stage except very basic operations. It contains the minimal code to
insmod and rmmod the driver and to create a /dev/hlX file per PCI device.
Signed-off-by: Oded Gabbay
---
drivers/misc/Kconfig |
Hello,
This is v3 of the Habana Labs kernel driver patch-set. It contains minor fixes
according to reviews done on v2. In addition, it is rebased on v5.0-rc5.
Link to v2 cover letter: https://lkml.org/lkml/2019/1/30/1003
Link to v1 cover letter: https://lwn.net/Articles/777342/
I would
On 01/02/19 09:55, Christoph Hellwig wrote:
> The only real user of the T10 OSD protocol, the pNFS object layout
> driver never went to the point of having shipping products, and we
> removed it 1.5 years ago. Exofs is just a simple example without
> real life users.
>
> The code has been mostly
On Mon, Feb 04, 2019 at 07:33:06PM +, Song Liu wrote:
>
>
> > On Feb 4, 2019, at 11:31 AM, Song Liu wrote:
> >
> > Synthesizing BPF events is only supported for root. Silent warning msg
> > when non-root user runs perf-record.
great, it was annoying ;-)
Tested-by: Jiri Olsa
thanks,
Signed-off-by: Alexey Dobriyan
---
fs/binfmt_elf.c |8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
--- a/fs/binfmt_elf.c
+++ b/fs/binfmt_elf.c
@@ -57,8 +57,6 @@
#endif
static int load_elf_binary(struct linux_binprm *bprm);
-static unsigned long elf_map(struct file *,
Signed-off-by: Alexey Dobriyan
---
fs/binfmt_elf.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
--- a/fs/binfmt_elf.c
+++ b/fs/binfmt_elf.c
@@ -2030,7 +2030,6 @@ static int fill_note_info(struct elfhdr *elf, int phdrs,
struct elf_note_info
On Mon, Feb 04, 2019 at 12:05:38PM -0800, Stephane Eranian wrote:
SNIP
> > > > > >
> > > > > > [jolsa@krava perf]$ ll result_1/
> > > > > > total 348
> > > > > > -rw---. 1 jolsa jolsa 27624 Feb 4 11:35 data.0
> > > > > > -rw---. 1 jolsa jolsa 56672 Feb 4 11:35 data.1
> > > > > >
On Mon, Feb 4, 2019 at 2:19 PM Jeremy Gebben wrote:
>
> The LM96000 is a temperature sensor and fan controller based
> on the LM85.
>
> Signed-off-by: Jeremy Gebben
> ---
> Documentation/devicetree/bindings/trivial-devices.yaml | 2 ++
> 1 file changed, 2 insertions(+)
Reviewed-by: Rob Herring
On Mon, 4 Feb 2019, Christoph Hellwig wrote:
On Fri, Feb 01, 2019 at 09:50:08PM +0100, David Kozub wrote:
This should make no change in functionality.
The formatting changes were triggered by checkpatch.pl.
Signed-off-by: David Kozub
Reviewed-by: Scott Bauer
---
block/sed-opal.c | 19
Number of ELF program headers is 16-bit by spec, so total size
comfortably fits into "unsigned int".
Space savings: 7 bytes!
add/remove: 0/0 grow/shrink: 0/1 up/down: 0/-7 (-7)
Function old new delta
load_elf_phdrs
On Mon 04 Feb 11:51 PST 2019, Avri Altman wrote:
>
> > This reverts commit 60f0187031c05e04cbadffb62f557d0ff3564490.
> >
> > Calling ufshcd_set_vccq_rail_unused hangs my system.
> > It seems vccq is not *not* needed.
> This patch essentially implements the UFS_DEVICE_NO_VCCQ quirk,
> Which is
Dear Friend,
3/2/2019
My beloved in Christ,
Donation of Two Million,Four Hundred Thousand British pounds forcharity Less
privileged peoples orphanages work, please reply tome.via my private email
address ( mrskathleenjaco...@yahoo.com )
Yours in Christ, Mrs. KATHLEEN JACOB
* Lukasz Luba [181113 10:22]:
> Hi Tony,
>
> On 11/8/18 5:59 PM, Tony Lindgren wrote:
> > Hi,
> >
> > * Lukasz Luba [181009 08:36]:
> >> PROVE_LOCKING enables LOCKDEP, which causes big overhead on cache and
> >> bus transactions.
> >>
> >> On some ARM big.LITTLE architecutres (Exynos 5433) the
On 2/4/2019 12:51 PM, Avri Altman wrote:
This reverts commit 60f0187031c05e04cbadffb62f557d0ff3564490.
Calling ufshcd_set_vccq_rail_unused hangs my system.
It seems vccq is not *not* needed.
This patch essentially implements the UFS_DEVICE_NO_VCCQ quirk,
Which is needed for both Samsung and
On Mon, Feb 04, 2019 at 04:14:20PM -0200, Thiago Jung Bauermann wrote:
>
> Hello Michael,
>
> Michael S. Tsirkin writes:
>
> > On Tue, Jan 29, 2019 at 03:42:44PM -0200, Thiago Jung Bauermann wrote:
> >>
> >> Fixing address of powerpc mailing list.
> >>
> >> Thiago Jung Bauermann writes:
> >>
The LM96000 is a temperature sensor and fan controller based
on the LM85.
Signed-off-by: Jeremy Gebben
---
Documentation/devicetree/bindings/trivial-devices.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/trivial-devices.yaml
It has been supported as a generic lm85 for quite some time.
Signed-off-by: Jeremy Gebben
---
Documentation/hwmon/lm85 | 6 +-
drivers/hwmon/lm85.c | 9 +++--
2 files changed, 12 insertions(+), 3 deletions(-)
diff --git a/Documentation/hwmon/lm85 b/Documentation/hwmon/lm85
index
Workspace manager init and cleanup code is open coded inside a for loop
over the compression types. This forces each compression type to rely on
the same workspace manager implementation. This patch creates helper
methods that will be the generic implementation for btrfs workspace
management.
This is in preparation for zstd compression levels. As each level will
require different sized workspaces, workspaces_list is no longer a
really fitting name.
Signed-off-by: Dennis Zhou
Reviewed-by: Nikolay Borisov
Reviewed-by: Josef Bacik
---
fs/btrfs/compression.c | 46
Hi everyone,
V2 had only a handful of changes outside of minor feedback.
0001:
- use functions over macros
0003:
- BTRFS_NR_WORKSPACE_MANAGERS is added instead of overriding
BTRFS_COMPRESS_TYPES
0011 (new):
- address monotonic memory requirement for zstd workspaces
0012:
- increase reclaim
On Mon, Feb 4, 2019 at 4:22 AM Torsten Duwe wrote:
>
> On Thu, Oct 18, 2018 at 03:33:18PM +0800, Icenowy Zheng wrote:
> > This patchset brings the support for Analogix ANX6345 RGB-(e)DP bridge,
> > which is used by some Allwinner A64 laptops, such as Pinebook and Olimex
> > TERES-I.
> >
>
> So
Make the workspace_manager own the interface operations rather than
managing index-paired arrays for the workspace_manager and compression
operations.
Signed-off-by: Dennis Zhou
Reviewed-by: Nikolay Borisov
Reviewed-by: Josef Bacik
---
fs/btrfs/compression.c | 11 +++
1 file changed,
It is very easy to miss places that rely on a certain bitshifting for
decyphering the type_level overloading. Add helpers to do this instead.
Signed-off-by: Dennis Zhou
Reviewed-by: Nikolay Borisov
Reviewed-by: Josef Bacik
Cc: Omar Sandoval
---
fs/btrfs/compression.c | 2 +-
The previous patch added generic helpers for get_workspace() and
put_workspace(). Now, we can migrate ownership of the workspace_manager
to be in the compression type code as the compression code itself
doesn't care beyond being able to get a workspace. The init/cleanup
and get/put methods are
Currently, the only user of set_level() is zlib which sets an internal
workspace parameter. As level is now plumbed into get_workspace(), this
can be handled there rather than separately.
This repurposes set_level() to bound the level passed in so it can be
used when setting the mounts
Zlib compression supports multiple levels, but doesn't require changing
in how a workspace itself is created and managed. Zstd introduces a
different memory requirement such that higher levels of compression
require more memory. This requires changes in how the alloc()/get()
methods work for zstd.
It is possible based on the level configurations that a higher level
workspace uses less memory than a lower level workspace. In order to
reuse workspaces, this must be made a monotonic relationship. This
precomputes the required memory for each level and enforces the
monotonicity between level
This patch includes the following:
1. Basic skeleton for the support
2. Enablement of x86 platform to use the same
Signed-off-by: Nitesh Narayan Lal
---
arch/x86/Kbuild | 2 +-
arch/x86/kvm/Kconfig | 8
arch/x86/kvm/Makefile| 2 ++
include/linux/gfp.h
This patch enables QEMU to recieve free page address from the guest
and to use madvise to make them available to the host.
---
hw/virtio/trace-events| 1 +
hw/virtio/virtio-balloon.c| 82 +++
hw/virtio/virtio.c
Zstd compression requires different amounts of memory for each level of
compression. The prior patches implemented indirection to allow for each
compression type to manage their workspaces independently. This patch
uses this indirection to implement compression level support for zstd.
To manage
While the heuristic workspaces aren't really compression workspaces,
they use the same interface for managing them. So rather than branching,
let's just handle them once again as the index 0 compression type.
Signed-off-by: Dennis Zhou
Reviewed-by: Nikolay Borisov
Reviewed-by: Josef Bacik
---
Zstd currently only supports the default level of compression. This
patch switches to using the level passed in for btrfs zstd
configuration.
Zstd workspaces now keep track of the requested level as this can differ
from the size of the workspace.
Signed-off-by: Dennis Zhou
Reviewed-by: Nikolay
There are two levels of workspace management. First, alloc()/free()
which are responsible for actually creating and destroy workspaces.
Second, at a higher level, get()/put() which is the compression code
asking for a workspace from a workspace_manager.
The compression code shouldn't really care
This patch enables the caller to expose a single buffers to the
other end using vring descriptor. It also allows the caller to
perform this action in synchornous manner by using virtqueue_kick_sync.
Signed-off-by: Nitesh Narayan Lal
---
drivers/virtio/virtio_ring.c | 72
This patch adds the functional skeleton for the guest implementation.
It also enables the guest to maintain the list of pages which are
freed by the guest. Once the list is full guest_free_page invokes
scan_array() which wakes up the kernel thread responsible for further
processing.
This patch enables to track the pages freed by the guest and
the pages isolated by the page hinting code through kernel
tracepoints.
Signed-off-by: Nitesh Narayan Lal
---
include/trace/events/kmem.h | 40 +
virt/kvm/page_hinting.c | 10 ++
2 files
This patch disables page poisoning if guest page hinting is enabled.
It is required to avoid possible guest memory corruption errors.
Page Poisoning is a feature in which the page is filled with a specific
pattern of (0x00 or 0xaa) after arch_free_page and the same is verified
before
This patch enables the guest free page hinting support
to enable or disable based on the STATIC key which
could be set via sysctl.
Signed-off-by: Nitesh Narayan Lal
---
include/linux/gfp.h | 2 ++
include/linux/page_hinting.h | 5 +
kernel/sysctl.c | 9 +
Allow support for chips that support more than 8 frequencies.
Signed-off-by: Jeremy Gebben
---
drivers/hwmon/lm85.c | 25 +++--
1 file changed, 15 insertions(+), 10 deletions(-)
diff --git a/drivers/hwmon/lm85.c b/drivers/hwmon/lm85.c
index 0a325878e8f5..4b15193d195c 100644
This patch enables the kernel to scan the per cpu array and
compress it by removing the repetitive/re-allocated pages.
Once the per cpu array is completely filled with pages in the
buddy it wakes up the kernel per cpu thread which re-scans the
entire per cpu array by acquiring a zone lock
The LM96000 expands the freqency field from 3 to 4 bits, to
add more frequencies in the 22.5 to 30 kHz ranges.
Signed-off-by: Jeremy Gebben
---
Documentation/hwmon/lm85 | 3 +++
drivers/hwmon/lm85.c | 9 +
2 files changed, 12 insertions(+)
diff --git a/Documentation/hwmon/lm85
The following patch-set proposes an efficient mechanism for handing freed
memory between the guest and the host. It enables the guests with no page cache
to rapidly free and reclaims memory to and from the host respectively.
Benefit:
With this patch-series, in our test-case, executed on a
Hi,
This patch set adds support for the PWM frequencies from 22.5 to 30 kHz
available on the LM96000.
It looks like this chip has been supported for a long time, but wasn't
mentioned in the docs (which I have updated).
I stumbled on to a 10 year old thread discussing a patch which looks
like an
On Wed, Jan 30, 2019 at 01:46:46PM +0100, Jiri Slaby wrote:
> Some global data in the suspend code were marked as `ENTRY'. ENTRY was
> intended for functions and shall be paired with ENDPROC. ENTRY also
> aligns symbols which creates unnecessary holes here between data. Since
> we are dropping
Hi Martin,
On Mon, 4 Feb 2019 at 19:36, Martin Blumenstingl
wrote:
>
> Hi Anand,
>
> On Tue, Jan 29, 2019 at 11:25 AM Anand Moon wrote:
> >
> > Override the dr_mode from "host" to "otg" for USB_HOST controller (usb0)
> > changes help usb_phy0->usb0 initialization of OTG bus port.
> >
> >
On Mon, Feb 4, 2019 at 11:27 AM Arnaldo Carvalho de Melo
wrote:
>
> Em Mon, Feb 04, 2019 at 10:56:05AM -0800, Stephane Eranian escreveu:
> > On Mon, Feb 4, 2019 at 3:41 AM Jiri Olsa wrote:
> > >
> > > On Mon, Feb 04, 2019 at 02:29:56PM +0300, Alexey Budankov wrote:
> > > > On 04.02.2019 13:36,
Hi Martin,
Thanks for your review comments.
On Mon, 4 Feb 2019 at 19:29, Martin Blumenstingl
wrote:
>
> Hi Anand,
>
> On Tue, Jan 29, 2019 at 11:25 AM Anand Moon wrote:
> >
> > Add missing vin-supply node 5.0V regulator setting to power
> > to usb ports, changes help fix the usb reset warning.
Currently, the jump label of a static key is transformed via the arch
specific function:
void arch_jump_label_transform(struct jump_entry *entry,
enum jump_label_type type)
The new approach (batch mode) uses two arch functions, the first has the
same
If the architecture supports the batching of jump label updates, use it!
An easy way to see the benefits of this patch is switching the
schedstats on and off. For instance:
-- %<
#!/bin/bash
while [ true ]; do
sysctl -w
text_poke_bp() updates instructions on live kernel on SMP in three steps:
1) add a int3 trap to the address that will be patched
2) update all but the first byte of the patched range
3) replace the first byte (int3) by the first byte of
This patch creates one function for each of these steps.
Currently, the patch of an address is done in three steps:
-- Pseudo-code #1 - Current implementation ---
1) add an int3 trap to the address that will be patched
sync cores (send IPI to all other CPUs)
2) update all but the first byte of the patched range
In the batching mode, entries with the same key should also be sorted by the
code, enabling a bsearch() of a code/addr when updating a key.
Signed-off-by: Daniel Bristot de Oliveira
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter Anvin"
Cc: Greg Kroah-Hartman
Cc:
Move the definition of the code to be written from
__jump_label_transform() to a specialized function.
Signed-off-by: Daniel Bristot de Oliveira
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter Anvin"
Cc: Greg Kroah-Hartman
Cc: Masami Hiramatsu
Cc: "Steven Rostedt
Move the check of the current code, before updating an entry, to specialized
functions. No changes in the method, only code relocation.
Signed-off-by: Daniel Bristot de Oliveira
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter Anvin"
Cc: Greg Kroah-Hartman
Cc: Masami
Move the check of if a jump_entry is valid to a function.
Signed-off-by: Daniel Bristot de Oliveira
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter Anvin"
Cc: Greg Kroah-Hartman
Cc: Masami Hiramatsu
Cc: "Steven Rostedt (VMware)"
Cc: Jiri Kosina
Cc: Josh Poimboeuf
Add a helper macro to make jump entry iteration code more readable.
Signed-off-by: Daniel Bristot de Oliveira
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter Anvin"
Cc: Greg Kroah-Hartman
Cc: Masami Hiramatsu
Cc: "Steven Rostedt (VMware)"
Cc: Jiri Kosina
Cc: Josh
While tuning a system with CPUs isolated as much as possible, we've
noticed that isolated CPUs were receiving bursts of 12 IPIs, periodically.
Tracing the functions that emit IPIs, we saw chronyd - an unprivileged
process - generating the IPIs when changing a static key, enabling
network
On Mon, Feb 04, 2019 at 11:05:52AM -0800, Dave Hansen wrote:
> But, we're not being very persuasive because we kinda forgot about the
> "if and only if" condition that you mentioned.
But why does it have to be a cmdline parameter instead of
being an automatic thing which sets the proper bits in
On 04.02.2019 22:27, Arnaldo Carvalho de Melo wrote:
> Em Mon, Feb 04, 2019 at 10:56:05AM -0800, Stephane Eranian escreveu:
>> On Mon, Feb 4, 2019 at 3:41 AM Jiri Olsa wrote:
>>>
>>> On Mon, Feb 04, 2019 at 02:29:56PM +0300, Alexey Budankov wrote:
On 04.02.2019 13:36, Jiri Olsa wrote:
>
> This reverts commit 60f0187031c05e04cbadffb62f557d0ff3564490.
>
> Calling ufshcd_set_vccq_rail_unused hangs my system.
> It seems vccq is not *not* needed.
This patch essentially implements the UFS_DEVICE_NO_VCCQ quirk,
Which is needed for both Samsung and Hynix devices.
Once acked by those
On Mon, 2019-02-04 at 11:40 -0800, Dave Hansen wrote:
> > +void __arch_merge_page(struct zone *zone, struct page *page,
> > + unsigned int order)
> > +{
> > + /*
> > +* The merging logic has merged a set of buddies up to the
> > +* KVM_PV_UNUSED_PAGE_HINT_MIN_ORDER.
On 04.02.2019 22:29, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jan 22, 2019 at 08:48:54PM +0300, Alexey Budankov escreveu:
>>
>> Allocate and bind AIO user space buffers to the memory nodes
>> that mmap kernel buffers are bound to.
>
> [root@quaco amazonlinux]# perf test -v python
> 18: 'import
On 2/4/19 10:15 AM, Alexander Duyck wrote:
> +#ifdef CONFIG_KVM_GUEST
> +#include
> +extern struct static_key_false pv_free_page_hint_enabled;
> +
> +#define HAVE_ARCH_FREE_PAGE
> +void __arch_free_page(struct page *page, unsigned int order);
> +static inline void arch_free_page(struct page
On Mon, Feb 04, 2019 at 01:57:49PM -0500, Liang, Kan wrote:
> You mean a given microcode revision X applying to multiple stepping,
> right?
Yes, the range thing. You specify a range of steppings:
kabylake mobile with steppings 9-12
kabylake desktop with steppings 10-13
> I don't think so. I
> +void __arch_merge_page(struct zone *zone, struct page *page,
> +unsigned int order)
> +{
> + /*
> + * The merging logic has merged a set of buddies up to the
> + * KVM_PV_UNUSED_PAGE_HINT_MIN_ORDER. Since that is the case, take
> + * advantage of this
> On Feb 4, 2019, at 11:31 AM, Song Liu wrote:
>
> Synthesizing BPF events is only supported for root. Silent warning msg
> when non-root user runs perf-record.
>
> Cc: Arnaldo Carvalho de Melo
> Cc: Jiri Olsa
> Reported-by: David Carrillo-Cisneros
> Tested-by: David Carrillo-Cisneros
>
Synthesizing BPF events is only supported for root. Silent warning msg
when non-root user runs perf-record.
Cc: Arnaldo Carvalho de Melo
Cc: Jiri Olsa
Reported-by: David Carrillo-Cisneros
Tested-by: David Carrillo-Cisneros
Signed-off-by: Song Liu
---
tools/perf/util/bpf-event.c | 4 ++--
1
On Mon, Feb 04, 2019 at 07:13:30PM +, Colin Ian King wrote:
> > drivers/regulator/axp20x-regulator.c | 8 ++--
> > 1 file changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/regulator/axp20x-regulator.c
> > b/drivers/regulator/axp20x-regulator.c
> > index
On 04.02.2019 17:42, Thierry Reding wrote:
> From: Thierry Reding
>
> If the system was booted using a device tree and if the device tree
> contains a MAC address, use it instead of reading one from the EEPROM.
> This is useful in situations where the EEPROM isn't properly programmed
> or where
Em Tue, Jan 22, 2019 at 08:48:54PM +0300, Alexey Budankov escreveu:
>
> Allocate and bind AIO user space buffers to the memory nodes
> that mmap kernel buffers are bound to.
[root@quaco amazonlinux]# perf test -v python
18: 'import perf' in python :
--- start ---
Em Mon, Feb 04, 2019 at 11:41:28AM -0700, Mathieu Poirier escreveu:
> On Tue, 29 Jan 2019 at 05:29, Leo Yan wrote:
> >
> > This patch seris adds support for sample flags so can facilitate perf
> > to print sample flags for branch instruction.
> >
> > Patch 0001 is used to save last branch
Em Mon, Feb 04, 2019 at 10:56:05AM -0800, Stephane Eranian escreveu:
> On Mon, Feb 4, 2019 at 3:41 AM Jiri Olsa wrote:
> >
> > On Mon, Feb 04, 2019 at 02:29:56PM +0300, Alexey Budankov wrote:
> > > On 04.02.2019 13:36, Jiri Olsa wrote:
> > > > On Mon, Feb 04, 2019 at 01:12:11PM +0300, Alexey
On Mon 04 Feb 10:23 PST 2019, Mark Brown wrote:
> On Mon, Feb 04, 2019 at 08:03:37AM -0800, Bjorn Andersson wrote:
>
> > We have a regulator that is described as 1.05V in the schematics for the
> > board we're working on and we have the USB block wanting 1.05V on one of
> > its pins. But the
On Mon, Feb 04, 2019 at 07:13:30PM +, Colin Ian King wrote:
> ping?
Please don't send content free pings and please allow a reasonable time
for review. People get busy, go on holiday, attend conferences and so
on so unless there is some reason for urgency (like critical bug fixes)
please
Fix looks good.
On 2019-02-04 11:21 a.m., Ray Jui wrote:
From: Rayagonda Kokatanur
RING_CONTROL reg was not written due to wrong address, hence all
the subsequent ring flush was timing out.
Fixes: a371c10ea4b3 ("mailbox: bcm-flexrm-mailbox: Fix FlexRM ring flush
sequence")
Signed-off-by:
On 2/1/19 2:21 PM, Jim Mattson wrote:
> On Mon, Dec 4, 2017 at 5:07 PM Brijesh Singh wrote:
>>
>> On AMD platforms, under certain conditions insn_len may be zero on #NPF.
>> This can happen if a guest gets a page-fault on data access but the HW
>> table walker is not able to read the
From: Rayagonda Kokatanur
RING_CONTROL reg was not written due to wrong address, hence all
the subsequent ring flush was timing out.
Fixes: a371c10ea4b3 ("mailbox: bcm-flexrm-mailbox: Fix FlexRM ring flush
sequence")
Signed-off-by: Rayagonda Kokatanur
Signed-off-by: Ray Jui
---
Looks good.
On 2019-02-04 11:07 a.m., Ray Jui wrote:
From: Qingmin Liu
When PIPEMIX=1, change the operation from 2x8 EP to 1x8 EP + 1x8 RC.
Signed-off-by: Qingmin Liu
Signed-off-by: Ray Jui
Acked-by: Scott Branden
---
drivers/phy/broadcom/phy-bcm-sr-pcie.c | 4 ++--
1 file changed, 2
Hi Shawn,
Care to have a look?
Daniel.
On Thu, Jan 31, 2019 at 10:16 AM Aisheng Dong wrote:
>
> > -Original Message-
> > From: Daniel Baluta
> > Sent: Wednesday, January 30, 2019 9:30 PM
> > To: shawn...@kernel.org
> > Cc: s.ha...@pengutronix.de; ker...@pengutronix.de;
On Mon, Feb 4, 2019 at 1:03 AM Vinod Koul wrote:
>
> On 24-01-19, 12:24, John Stultz wrote:
> > This patch series is based on recent work by Tanglei Han, and
> > adds support for hi3660 SoCs as found on the HiKey960 board,
> > along with a few patches I've been carrying.
>
> Applied and fixed the
Hi,
I notice this commit as a possible culprit of the illegal instructions my lttng
users are noticing on arm32 when using kprobes on a v4.19.13 Linux kernel
in a Yocto environment [1]. They were able to reproduce the issue with perf
as well.
commit e46daee53bb50bde38805f1823a182979724c229
ping?
On 22/12/2018 11:31, Colin King wrote:
> From: Colin Ian King
>
> Currently rdev is dereferenced when assigning desc before rdev is null
> checked, hence there is a potential null pointer dereference on rdev.
> Fix this by null checking rdev first.
>
> Detected by CoverityScan,
On 2/4/19 10:19 AM, Matthew Wilcox wrote:
> On Sun, Feb 03, 2019 at 09:21:33PM -0800, john.hubb...@gmail.com wrote:
>> +/*
>> + * GUP_PIN_COUNTING_BIAS, and the associated functions that use it, overload
>> + * the page's refcount so that two separate items are tracked: the original
>> page
>> +
On Mon, Feb 04, 2019 at 11:00:03AM -0800, Dave Hansen wrote:
> On 2/4/19 10:45 AM, Fenghua Yu wrote:
> > On Mon, Feb 04, 2019 at 10:41:40AM -0800, Dave Hansen wrote:
> >> On 2/1/19 9:14 PM, Fenghua Yu wrote:
> >>> --- a/arch/x86/include/asm/cpufeatures.h
> >>> +++
301 - 400 of 1302 matches
Mail list logo
