Hi all,
Today's linux-next merge of the kvm tree got a conflict in:
arch/powerpc/kernel/exceptions-64s.S
between commit:
1a6822d194c3 ("powerpc/64s: Use (start, size) rather than (start, end) for
exception handlers")
from the powerpc tree and commit:
bc3551257af8 ("powerpc/64: Allow
Hi all,
Today's linux-next merge of the kvm tree got a conflict in:
arch/powerpc/kernel/exceptions-64s.S
between commit:
1a6822d194c3 ("powerpc/64s: Use (start, size) rather than (start, end) for
exception handlers")
from the powerpc tree and commit:
bc3551257af8 ("powerpc/64: Allow
On Thu, Feb 09, 2017 at 11:17:23PM +0100, Philippe Reynes wrote:
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> As I don't have the hardware, I'd be very pleased if
> someone may test this patch.
Tested using a 2-port NIC. Works
On Thu, Feb 09, 2017 at 11:17:23PM +0100, Philippe Reynes wrote:
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> As I don't have the hardware, I'd be very pleased if
> someone may test this patch.
Tested using a 2-port NIC. Works
"Naveen N. Rao" writes:
> kprobe_exceptions_notify() is not used on some of the architectures such
> as arm[64] and powerpc anymore. Introduce a weak variant for such
> architectures.
I'll merge patch 1 & 3 via the powerpc tree for v4.11.
You can then send
"Naveen N. Rao" writes:
> kprobe_exceptions_notify() is not used on some of the architectures such
> as arm[64] and powerpc anymore. Introduce a weak variant for such
> architectures.
I'll merge patch 1 & 3 via the powerpc tree for v4.11.
You can then send patch 2 to the arm guys after -rc1,
Hi all,
Today's linux-next merge of the kvm tree got a conflict in:
arch/powerpc/include/asm/head-64.h
between commit:
852e5da99d15 ("powerpc/64s: Tidy up after exception handler rework")
from the powerpc tree and commit:
7ede531773ea ("KVM: PPC: Book3S: Move 64-bit KVM interrupt
Hi all,
Today's linux-next merge of the kvm tree got a conflict in:
arch/powerpc/include/asm/head-64.h
between commit:
852e5da99d15 ("powerpc/64s: Tidy up after exception handler rework")
from the powerpc tree and commit:
7ede531773ea ("KVM: PPC: Book3S: Move 64-bit KVM interrupt
From: Andi Kleen
This is not a full uncore event list, but a short list of useful
and understandable metrics.
Signed-off-by: Andi Kleen
Cc: Jiri Olsa
Link: http://lkml.kernel.org/n/tip-c0cix4eprbldfrx5zf60s...@git.kernel.org
From: Andi Kleen
This is not a full uncore event list, but a short list of useful
and understandable metrics.
Signed-off-by: Andi Kleen
Cc: Jiri Olsa
Link: http://lkml.kernel.org/n/tip-c0cix4eprbldfrx5zf60s...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
---
The GR8, like other sun5i SoCs, has only 1 pin option for PWM0 output.
Other SoCs had named the pingroup "pwm0_pins" in their dtsi files, while
GR8 named it "pwm0_pins_a". When we switched to the new common sun5i
dtsi file, we forgot to rename the pingroup references in the GR8 board
dts files.
The GR8, like other sun5i SoCs, has only 1 pin option for PWM0 output.
Other SoCs had named the pingroup "pwm0_pins" in their dtsi files, while
GR8 named it "pwm0_pins_a". When we switched to the new common sun5i
dtsi file, we forgot to rename the pingroup references in the GR8 board
dts files.
On 02/09/2017 09:50 AM, Grzegorz Andrejczuk wrote:
> Application allocating overcommitted hugepages behave differently when
> its mempolicy is set to bind with NUMA nodes containing CPUs and not
> containing CPUs. When memory is allocated on node with CPUs everything
> work as expected, when
On 02/09/2017 09:50 AM, Grzegorz Andrejczuk wrote:
> Application allocating overcommitted hugepages behave differently when
> its mempolicy is set to bind with NUMA nodes containing CPUs and not
> containing CPUs. When memory is allocated on node with CPUs everything
> work as expected, when
On (02/09/17 19:19), Eric Dumazet wrote:
>
> More likely the bug is in fanout_add(), with a buggy sequence in error
> case, and not correct locking.
>
> kfree(po->rollover);
> po->rollover = NULL;
>
> Two cpus entering fanout_add() (using the same af_packet socket,
> syzkaller courtesy...)
On (02/09/17 19:19), Eric Dumazet wrote:
>
> More likely the bug is in fanout_add(), with a buggy sequence in error
> case, and not correct locking.
>
> kfree(po->rollover);
> po->rollover = NULL;
>
> Two cpus entering fanout_add() (using the same af_packet socket,
> syzkaller courtesy...)
From: Netanel Belgazal
Date: Thu, 9 Feb 2017 15:21:26 +0200
> Changes from V3:
> * Rebase patchset to master and solve merge conflicts.
> * Remove redundant bug fix (fix error handling when probe fails)
Series applied, thank you.
From: Netanel Belgazal
Date: Thu, 9 Feb 2017 15:21:26 +0200
> Changes from V3:
> * Rebase patchset to master and solve merge conflicts.
> * Remove redundant bug fix (fix error handling when probe fails)
Series applied, thank you.
On Thu, Feb 9, 2017 at 10:14 PM, Dan Williams wrote:
> On Thu, Feb 9, 2017 at 1:29 AM, Anup Patel wrote:
>> On Wed, Feb 8, 2017 at 9:54 PM, Dan Williams
>> wrote:
>>> On Wed, Feb 8, 2017 at 12:57 AM, Anup Patel
On Thu, Feb 9, 2017 at 10:14 PM, Dan Williams wrote:
> On Thu, Feb 9, 2017 at 1:29 AM, Anup Patel wrote:
>> On Wed, Feb 8, 2017 at 9:54 PM, Dan Williams
>> wrote:
>>> On Wed, Feb 8, 2017 at 12:57 AM, Anup Patel wrote:
On Tue, Feb 7, 2017 at 11:46 PM, Dan Williams
wrote:
> On
On Thu, 2017-02-09 at 19:19 -0800, Eric Dumazet wrote:
> More likely the bug is in fanout_add(), with a buggy sequence in error
> case, and not correct locking.
>
> kfree(po->rollover);
> po->rollover = NULL;
>
> Two cpus entering fanout_add() (using the same af_packet socket,
> syzkaller
On Thu, 2017-02-09 at 19:19 -0800, Eric Dumazet wrote:
> More likely the bug is in fanout_add(), with a buggy sequence in error
> case, and not correct locking.
>
> kfree(po->rollover);
> po->rollover = NULL;
>
> Two cpus entering fanout_add() (using the same af_packet socket,
> syzkaller
On Wed, Feb 8, 2017 at 4:08 PM, James Bottomley
wrote:
> On Mon, 2017-02-06 at 21:42 -0800, Dan Williams wrote:
[..]
>> ...but it reproduces on current mainline with the same config. I
>> haven't spotted what makes scsi_debug behave like this.
>
> Looking at
On Wed, Feb 8, 2017 at 4:08 PM, James Bottomley
wrote:
> On Mon, 2017-02-06 at 21:42 -0800, Dan Williams wrote:
[..]
>> ...but it reproduces on current mainline with the same config. I
>> haven't spotted what makes scsi_debug behave like this.
>
> Looking at the config, it's a static debug with
Hi Herbert,
On Mon, 6 Feb 2017 17:03:40 +0800 Herbert Xu
wrote:
>
> On Mon, Feb 06, 2017 at 12:28:37PM +1100, Stephen Rothwell wrote:
> >
> > After merging the crypto tree, today's linux-next build (x86_64
> > allmodconfig) produced these warnings:
> >
> >
On Thu, 2017-02-09 at 17:24 -0800, Cong Wang wrote:
> On Thu, Feb 9, 2017 at 5:14 AM, Dmitry Vyukov wrote:
> > Hello,
> >
> > I've got the following use-after-free report in packet_rcv_fanout
> > while running syzkaller fuzzer on linux-next
> >
Hi Herbert,
On Mon, 6 Feb 2017 17:03:40 +0800 Herbert Xu
wrote:
>
> On Mon, Feb 06, 2017 at 12:28:37PM +1100, Stephen Rothwell wrote:
> >
> > After merging the crypto tree, today's linux-next build (x86_64
> > allmodconfig) produced these warnings:
> >
> > warning: (CRYPTO_DEV_ATMEL_AUTHENC)
On Thu, 2017-02-09 at 17:24 -0800, Cong Wang wrote:
> On Thu, Feb 9, 2017 at 5:14 AM, Dmitry Vyukov wrote:
> > Hello,
> >
> > I've got the following use-after-free report in packet_rcv_fanout
> > while running syzkaller fuzzer on linux-next
> > e3e6c5f3544c5d05c6b3b309a34f4f2c3537e993. So far it
Resend this series to involve device tree maintainer and add 'Reviewed-by' tag
for driver.
The Current default dwc2 just handle one clock named otg, however, it may have
two or more clock need to manage for some new SoCs(such as RK3328), so this
adds change clk to clk's array of dwc2_hsotg to
Move 'clocks' to optional properties since not every platform
is going to need to specify it and add pmu/utmi/ulpi/utmifs
optional clocks into 'clock-names' list.
Signed-off-by: Frank Wang
---
Documentation/devicetree/bindings/usb/dwc2.txt | 13 ++---
1 file
Resend this series to involve device tree maintainer and add 'Reviewed-by' tag
for driver.
The Current default dwc2 just handle one clock named otg, however, it may have
two or more clock need to manage for some new SoCs(such as RK3328), so this
adds change clk to clk's array of dwc2_hsotg to
Move 'clocks' to optional properties since not every platform
is going to need to specify it and add pmu/utmi/ulpi/utmifs
optional clocks into 'clock-names' list.
Signed-off-by: Frank Wang
---
Documentation/devicetree/bindings/usb/dwc2.txt | 13 ++---
1 file changed, 10 insertions(+), 3
Since dwc2 may have one or more input clocks need to manage for some
platform, so this adds change clk to clk's array of struct dwc2_hsotg
to handle more clocks operation.
Signed-off-by: Frank Wang
Reviewed-by: Heiko Stuebner
---
Since dwc2 may have one or more input clocks need to manage for some
platform, so this adds change clk to clk's array of struct dwc2_hsotg
to handle more clocks operation.
Signed-off-by: Frank Wang
Reviewed-by: Heiko Stuebner
---
drivers/usb/dwc2/core.h | 5 -
Synaptics add new TP firmware ID: 0x2 and 0x3, for now both lower 2 bits
are indicated as TP. Change the constant to bitwise values.
Signed-off-by: Aaron Ma
Cc: sta...@vger.kernel.org
---
drivers/input/mouse/trackpoint.c | 3 ++-
drivers/input/mouse/trackpoint.h | 3 ++-
On Thu, 2017-02-09 at 22:39 -0300, Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo
>
> For cases where implicit fall through case labels are intended,
> to let us inform that to gcc >= 7:
I believe this should be added to compiler_gcc.h
> diff --git
Synaptics add new TP firmware ID: 0x2 and 0x3, for now both lower 2 bits
are indicated as TP. Change the constant to bitwise values.
Signed-off-by: Aaron Ma
Cc: sta...@vger.kernel.org
---
drivers/input/mouse/trackpoint.c | 3 ++-
drivers/input/mouse/trackpoint.h | 3 ++-
2 files changed, 4
On Thu, 2017-02-09 at 22:39 -0300, Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo
>
> For cases where implicit fall through case labels are intended,
> to let us inform that to gcc >= 7:
I believe this should be added to compiler_gcc.h
> diff --git
From: Arnaldo Carvalho de Melo
Addressing this warning from gcc 7:
CC /tmp/build/perf/bench/numa.o
bench/numa.c: In function '__bench_numa':
bench/numa.c:1582:42: error: '%d' directive output may be truncated writing
between 1 and 10 bytes into a region of size
From: Arnaldo Carvalho de Melo
Addressing this warning from gcc 7:
CC /tmp/build/perf/bench/numa.o
bench/numa.c: In function '__bench_numa':
bench/numa.c:1582:42: error: '%d' directive output may be truncated writing
between 1 and 10 bytes into a region of size between 8 and 17
Hi all,
On Tue, 10 Jan 2017 12:27:03 +1100 Stephen Rothwell
wrote:
>
> After merging the selinux tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> In file included from /home/sfr/next/next/security/selinux/avc.c:35:0:
>
Hi all,
On Tue, 10 Jan 2017 12:27:03 +1100 Stephen Rothwell
wrote:
>
> After merging the selinux tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> In file included from /home/sfr/next/next/security/selinux/avc.c:35:0:
>
On 2017/2/10 10:25, Wangnan (F) wrote:
On 2017/2/10 7:21, Mickaël Salaün wrote:
Replace bpf_prog_load() with bpf_load_program() calls.
Signed-off-by: Mickaël Salaün
Cc: Alexei Starovoitov
Cc: Daniel Borkmann
Cc: Shuah Khan
On 2017/2/10 10:25, Wangnan (F) wrote:
On 2017/2/10 7:21, Mickaël Salaün wrote:
Replace bpf_prog_load() with bpf_load_program() calls.
Signed-off-by: Mickaël Salaün
Cc: Alexei Starovoitov
Cc: Daniel Borkmann
Cc: Shuah Khan
---
tools/lib/bpf/bpf.c | 6 +++---
Add the device tree node for the ir-spi driver which enable the
ir led for remote controlling.
This patch sets first the GPR3[3] gpio line as a regulator-fixed
for enabling an external regulator which powers the IR LED.
Removes also the default assignment of GPG3[7] related to the
MOSI line of
Add the device tree node for the ir-spi driver which enable the
ir led for remote controlling.
This patch sets first the GPR3[3] gpio line as a regulator-fixed
for enabling an external regulator which powers the IR LED.
Removes also the default assignment of GPG3[7] related to the
MOSI line of
> ker...@vger.kernel.org
> Subject: [PATCH 4/4] cxgb4: Convert PDBG to pr_debug
>
> Use a more typical logging style.
>
> Miscellanea:
>
> o Obsolete the c4iw_debug module parameter
> o Coalesce formats
> o Realign arguments
>
> Signed-off-by: Joe Perches
> ---
>
> ker...@vger.kernel.org
> Subject: [PATCH 4/4] cxgb4: Convert PDBG to pr_debug
>
> Use a more typical logging style.
>
> Miscellanea:
>
> o Obsolete the c4iw_debug module parameter
> o Coalesce formats
> o Realign arguments
>
> Signed-off-by: Joe Perches
> ---
>
From: Andi Kleen
This is not a full uncore event list, but a short list of useful
and understandable metrics.
Signed-off-by: Andi Kleen
Cc: Jiri Olsa
Link: http://lkml.kernel.org/n/tip-c0cix4eprbldfrx5zf60s...@git.kernel.org
From: Andi Kleen
This is not a full uncore event list, but a short list of useful
and understandable metrics.
Signed-off-by: Andi Kleen
Cc: Jiri Olsa
Link: http://lkml.kernel.org/n/tip-c0cix4eprbldfrx5zf60s...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
---
From: Arnaldo Carvalho de Melo
For cases where implicit fall through case labels are intended,
to let us inform that to gcc >= 7:
CC /tmp/build/perf/util/string.o
util/string.c: In function 'perf_atoll':
util/string.c:22:7: error: this statement may fall through
From: Arnaldo Carvalho de Melo
For cases where implicit fall through case labels are intended,
to let us inform that to gcc >= 7:
CC /tmp/build/perf/util/string.o
util/string.c: In function 'perf_atoll':
util/string.c:22:7: error: this statement may fall through
From: He Kuang
These two debug messages are missing the trailing newline.
Signed-off-by: He Kuang
Cc: Alexander Shishkin
Cc: Bintian Wang
Cc: Jiri Olsa
Cc: Masami Hiramatsu
From: He Kuang
These two debug messages are missing the trailing newline.
Signed-off-by: He Kuang
Cc: Alexander Shishkin
Cc: Bintian Wang
Cc: Jiri Olsa
Cc: Masami Hiramatsu
Cc: Peter Zijlstra
Cc: Wang Nan
Cc: Will Deacon
Cc: linux-arm-ker...@lists.infradead.org
Link:
From: Andi Kleen
This is not a full uncore event list, but a short list of useful
and understandable metrics.
Signed-off-by: Andi Kleen
Cc: Jiri Olsa
Link: http://lkml.kernel.org/n/tip-c0cix4eprbldfrx5zf60s...@git.kernel.org
From: Andi Kleen
This is not a full uncore event list, but a short list of useful
and understandable metrics.
Signed-off-by: Andi Kleen
Cc: Jiri Olsa
Link: http://lkml.kernel.org/n/tip-c0cix4eprbldfrx5zf60s...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
---
From: Andi Kleen
This is not a full uncore event list, but a short list of useful
and understandable metrics.
Signed-off-by: Andi Kleen
Cc: Jiri Olsa
Link: http://lkml.kernel.org/n/tip-c0cix4eprbldfrx5zf60s...@git.kernel.org
From: Arnaldo Carvalho de Melo
To address new warnings emmited by gcc 7, e.g.::
CC /tmp/build/perf/util/intel-pt-decoder/intel-pt-pkt-decoder.o
CC /tmp/build/perf/tests/parse-events.o
util/intel-pt-decoder/intel-pt-pkt-decoder.c: In function
From: Andi Kleen
This is not a full uncore event list, but a short list of useful
and understandable metrics.
Signed-off-by: Andi Kleen
Cc: Jiri Olsa
Link: http://lkml.kernel.org/n/tip-c0cix4eprbldfrx5zf60s...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
---
From: Arnaldo Carvalho de Melo
To address new warnings emmited by gcc 7, e.g.::
CC /tmp/build/perf/util/intel-pt-decoder/intel-pt-pkt-decoder.o
CC /tmp/build/perf/tests/parse-events.o
util/intel-pt-decoder/intel-pt-pkt-decoder.c: In function 'intel_pt_pkt_desc':
From: Taeung Song
Signed-off-by: Taeung Song
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc: Wang Nan
Link:
From: Taeung Song
Signed-off-by: Taeung Song
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc: Wang Nan
Link:
http://lkml.kernel.org/r/1485952447-7013-2-git-send-email-treeze.tae...@gmail.com
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/util/parse-events.c | 3 ++-
1 file
From: Taeung Song
We have zfree() for this very common pattern:
free(ptr);
ptr = NULL;
So use it in a few more places.
Signed-off-by: Taeung Song
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Peter Zijlstra
From: Andi Kleen
The next patch needs to modify event code. Previously eventcode was just
passed through as a string. Now parse it as a number.
v2: Don't special case 0
Signed-off-by: Andi Kleen
Acked-by: Jiri Olsa
Link:
From: Taeung Song
We have zfree() for this very common pattern:
free(ptr);
ptr = NULL;
So use it in a few more places.
Signed-off-by: Taeung Song
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc: Wang Nan
Link:
From: Andi Kleen
The next patch needs to modify event code. Previously eventcode was just
passed through as a string. Now parse it as a number.
v2: Don't special case 0
Signed-off-by: Andi Kleen
Acked-by: Jiri Olsa
Link: http://lkml.kernel.org/r/20170128020345.19007-2-a...@firstfloor.org
From: Taeung Song
The cases changed in this patch are for when we free but keep the
pointer to the freed area, which is not always a good idea.
Be more defensive and zero the pointer to avoid possible use after
free bugs to take more time to be detected.
Signed-off-by:
From: Taeung Song
Signed-off-by: Taeung Song
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc: Wang Nan
Link:
From: Andi Kleen
Add support for registering json aliases per PMU. Any alias with an unit
matching the prefix is registered to the PMU. Uncore has multiple
instances of most units, so all these aliases get registered for each
individual PMU (this is important later to run
From: Taeung Song
The cases changed in this patch are for when we free but keep the
pointer to the freed area, which is not always a good idea.
Be more defensive and zero the pointer to avoid possible use after
free bugs to take more time to be detected.
Signed-off-by: Taeung Song
Cc: Jiri
From: Taeung Song
Signed-off-by: Taeung Song
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc: Wang Nan
Link:
http://lkml.kernel.org/r/1485952447-7013-3-git-send-email-treeze.tae...@gmail.com
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/util/parse-events.c | 2 ++
1 file
From: Andi Kleen
Add support for registering json aliases per PMU. Any alias with an unit
matching the prefix is registered to the PMU. Uncore has multiple
instances of most units, so all these aliases get registered for each
individual PMU (this is important later to run the event on every
From: Arnaldo Carvalho de Melo
In commit daeecbc0c431 ("perf tools: Add event_update event scale type"), the
handling of PERF_EVENT_UPDATE__SCALE cast struct event_update_event->data to a
pointer to event_update_event_scale, uses some field from this casted struct
and then ends
From: Arnaldo Carvalho de Melo
In commit daeecbc0c431 ("perf tools: Add event_update event scale type"), the
handling of PERF_EVENT_UPDATE__SCALE cast struct event_update_event->data to a
pointer to event_update_event_scale, uses some field from this casted struct
and then ends up falling
Le jeudi 09 février 2017 à 15:10 -0700, Shuah Khan a écrit :
> Fix s5p_mfc_set_dec_frame_buffer_v6() to print buffer size in hex to
> be
> consistent with the rest of the messages in the routine.
Short and long descriptions are miss-leading. This patch will print the
buffer pointer as hex and
Le jeudi 09 février 2017 à 15:10 -0700, Shuah Khan a écrit :
> Fix s5p_mfc_set_dec_frame_buffer_v6() to print buffer size in hex to
> be
> consistent with the rest of the messages in the routine.
Short and long descriptions are miss-leading. This patch will print the
buffer pointer as hex and
On Thu, 9 Feb 2017 16:49:00 +
Russell King - ARM Linux wrote:
> On Fri, Feb 10, 2017 at 01:32:22AM +0900, Masami Hiramatsu wrote:
> > Fix a possibility of deadlock case in kretprobe on arm
> > implementation. There may be a chance that the kretprobe
> > hash table lock
On Thu, 9 Feb 2017 16:49:00 +
Russell King - ARM Linux wrote:
> On Fri, Feb 10, 2017 at 01:32:22AM +0900, Masami Hiramatsu wrote:
> > Fix a possibility of deadlock case in kretprobe on arm
> > implementation. There may be a chance that the kretprobe
> > hash table lock can cause a dead lock.
From: He Kuang
Since HAVE_KPROBES can be enabled in arm64, this patch introduces
regs_query_register_offset() to convert register name to offset for
arm64, so the BPF prologue feature is ready to use.
Signed-off-by: He Kuang
Reviewed-by: Will Deacon
From: He Kuang
Since HAVE_KPROBES can be enabled in arm64, this patch introduces
regs_query_register_offset() to convert register name to offset for
arm64, so the BPF prologue feature is ready to use.
Signed-off-by: He Kuang
Reviewed-by: Will Deacon
Acked-by: Masami Hiramatsu
Cc: Alexander
From: Andi Kleen
The code for handling pmu aliases without specifying the PMU hardcoded
only supported the cpu PMU.
This patch extends it to work for all PMUs. We always duplicate the
event for all PMUs that have an matching alias. This allows to
automatically expand an
FYI, we noticed the following commit:
commit: cf6c467d67d319e239aec57d7ba31cb9946f29bf ("drm/ttm: add BO priorities
for the LRUs")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
in testcase: trinity
with following parameters:
runtime: 300s
test-description:
From: Andi Kleen
Handle the "Unit" field, which is needed to find the right PMU for an
event. We call it "pmu" and convert it to the perf pmu name with an
uncore prefix.
Handle the "ExtSel" field, which just extends the event mask with an
additional bit.
Handle the
From: Andi Kleen
The code for handling pmu aliases without specifying the PMU hardcoded
only supported the cpu PMU.
This patch extends it to work for all PMUs. We always duplicate the
event for all PMUs that have an matching alias. This allows to
automatically expand an alias for all instances
FYI, we noticed the following commit:
commit: cf6c467d67d319e239aec57d7ba31cb9946f29bf ("drm/ttm: add BO priorities
for the LRUs")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
in testcase: trinity
with following parameters:
runtime: 300s
test-description:
From: Andi Kleen
Handle the "Unit" field, which is needed to find the right PMU for an
event. We call it "pmu" and convert it to the perf pmu name with an
uncore prefix.
Handle the "ExtSel" field, which just extends the event mask with an
additional bit.
Handle the "Filter" field which adds
From: Ravi Bangoria
All events from 'perf list', except SDT events, can be directly recorded
with 'perf record'. But, the flow is little different for SDT events.
Probe points for SDT event needs to be created using 'perf probe' before
recording it using 'perf
From: Ravi Bangoria
All events from 'perf list', except SDT events, can be directly recorded
with 'perf record'. But, the flow is little different for SDT events.
Probe points for SDT event needs to be created using 'perf probe' before
recording it using 'perf record'.
Perf shows misleading
On 2017/2/10 7:21, Mickaël Salaün wrote:
Add require dependency headers.
Signed-off-by: Mickaël Salaün
Cc: Alexei Starovoitov
Cc: Daniel Borkmann
Cc: Shuah Khan
---
tools/lib/bpf/bpf.c | 6
On 2017/2/10 7:21, Mickaël Salaün wrote:
Add require dependency headers.
Signed-off-by: Mickaël Salaün
Cc: Alexei Starovoitov
Cc: Daniel Borkmann
Cc: Shuah Khan
---
tools/lib/bpf/bpf.c | 6 ++
tools/testing/selftests/bpf/bpf_sys.h | 27
From: Andi Kleen
For debugging and testing it is useful to see the converted alias
string. Add support to perf stat/record and perf list to print the alias
conversion. The text string is saved in the alias structure. For perf
stat/record it is folded into the normal -v.
From: Andi Kleen
For debugging and testing it is useful to see the converted alias
string. Add support to perf stat/record and perf list to print the alias
conversion. The text string is saved in the alias structure. For perf
stat/record it is folded into the normal -v. For perf list -v was
On 2017/2/10 7:21, Mickaël Salaün wrote:
Replace bpf_prog_load() with bpf_load_program() calls.
Signed-off-by: Mickaël Salaün
Cc: Alexei Starovoitov
Cc: Daniel Borkmann
Cc: Shuah Khan
---
tools/lib/bpf/bpf.c
On 2017/2/10 7:21, Mickaël Salaün wrote:
Replace bpf_prog_load() with bpf_load_program() calls.
Signed-off-by: Mickaël Salaün
Cc: Alexei Starovoitov
Cc: Daniel Borkmann
Cc: Shuah Khan
---
tools/lib/bpf/bpf.c | 6 +++---
tools/lib/bpf/bpf.h
On Thu, 9 Feb 2017, Davidlohr Bueso wrote:
> We do not support prefaulting functionality in sysv shm,
> nor MAP_NONBLOCK for that matter. Drop the pointless check
> for populate in do_shmat().
I haven't checked, but are you sure that "populated" does nothing
when the attacher had previously
On Thu, 9 Feb 2017, Davidlohr Bueso wrote:
> We do not support prefaulting functionality in sysv shm,
> nor MAP_NONBLOCK for that matter. Drop the pointless check
> for populate in do_shmat().
I haven't checked, but are you sure that "populated" does nothing
when the attacher had previously
Commit a92e7c3d82a1 ("spi: s3c64xx: consider the case when the CS
line is not connected") introduced an inconsistency between the
binding, where the disconnected CS line was marked as
'no-cs-readback', and the driver.
The driver is erroneously checking for that attribute with
property name of
Commit a92e7c3d82a1 ("spi: s3c64xx: consider the case when the CS
line is not connected") introduced an inconsistency between the
binding, where the disconnected CS line was marked as
'no-cs-readback', and the driver.
The driver is erroneously checking for that attribute with
property name of
Hi,
this patchset provides support for the ST-Microelectronics
FingerTip S device driver and enables it in the tm2 and tm2e
devices.
It's tested on top of next-20170210 kernel and applies on
Krzysztof's for-next branch.
Thanks,
Andi
Changelog V1-V2
===
V1:
Hi,
this patchset provides support for the ST-Microelectronics
FingerTip S device driver and enables it in the tm2 and tm2e
devices.
It's tested on top of next-20170210 kernel and applies on
Krzysztof's for-next branch.
Thanks,
Andi
Changelog V1-V2
===
V1:
201 - 300 of 1850 matches
Mail list logo