From: Adrian Hunter
Add an option to select PERF_RECORD_SWITCH events.
Signed-off-by: Adrian Hunter
Acked-by: Peter Zijlstra (Intel)
Tested-by: Arnaldo Carvalho de Melo
Tested-by: Jiri Olsa
Cc: Andi Kleen
Cc: Mathieu Poirier
Cc: Pawel Moll
Cc: Stephane Eranian
Link:
From: Arnaldo Carvalho de Melo
That provides the function signature expected by libtraceevent's
pevent_set_function_resolver().
Acked-by: David Ahern
Cc: Adrian Hunter
Cc: Borislav Petkov
Cc: Frederic Weisbecker
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Stephane Eranian
Cc: Steven Rostedt
From: Arnaldo Carvalho de Melo
So that beautifiers wanting to resolve kernel function addresses to
names can do its work, now, for instance, the 'timer' tracepoints
beautifiers works with 'perf trace', see the "function=tick..." part:
# perf trace --event timer:hrtimer_start
0.000
From: Arnaldo Carvalho de Melo
The perf tools have a symbol resolver that includes solving kernel
symbols using either kallsyms or ELF symtabs, and it also is using
libtraceevent to format the trace events fields, including via
subsystem specific plugins, like the "timer" one.
To solve fields
Hi Ingo,
Please consider pulling,
- Arnaldo
The following changes since commit a11c51acc52822754d66a11c15f6f6edd4d23c55:
Merge tag 'perf-core-for-mingo' of
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core
(2015-07-21 07:58:06 +0200)
are available in the git
From: Jiri Olsa
Checking also for refcnt in thread_map test.
Signed-off-by: Jiri Olsa
Cc: David Ahern
Cc: Namhyung Kim
Cc: Peter Zijlstra
Link:
http://lkml.kernel.org/r/1437481927-29538-2-git-send-email-jo...@kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
---
From: Jiri Olsa
Forcing perf_evlist__set_maps to propagate maps through events, so
cpu/thread maps get set within evlist.
Signed-off-by: Jiri Olsa
Cc: David Ahern
Cc: Namhyung Kim
Cc: Peter Zijlstra
Link:
http://lkml.kernel.org/r/1437481927-29538-11-git-send-email-jo...@kernel.org
From: Jiri Olsa
Tolerating NULL maps in perf_evlist__propagate_maps, so we dont need to
pass evlist with both cpus and threads maps defined.
Signed-off-by: Jiri Olsa
Cc: David Ahern
Cc: Namhyung Kim
Cc: Peter Zijlstra
Link:
于 2015/7/24 6:56, Alexei Starovoitov 写道:
> On 7/23/15 2:42 AM, Kaixu Xia wrote:
>> According to the perf_event_map_fd and index, the function
>> bpf_perf_event_read() can convert the corresponding map
>> value to the pointer to struct perf_event and return the
>> Hardware PMU counter value.
>>
>>
于 2015/7/24 6:59, Alexei Starovoitov 写道:
> On 7/23/15 2:42 AM, Kaixu Xia wrote:
>> This is a simple example and shows how to use the new ability
>> to get the selected Hardware PMU counter value.
>>
>> Signed-off-by: Kaixu Xia
> ...
>> +struct bpf_map_def SEC("maps") my_map = {
>> +.type =
)
pdata->wakeup = of_property_read_bool(pp, "wakeup-source") ||
^
Caused by commit
7e324dd6cc21 ("Input: samsung-keypad - change name of wakeup property")
Please at least build test these changes :-(
I have used the input tree from
On Thu, 23 Jul 2015 22:34:48 -0300
Arnaldo Carvalho de Melo wrote:
> > > One more try:
>
> > Third time's a charm, or was this the forth?
>
> As many as needed would be put forth!
And the Lord said unto John, "Come forth and you will receive eternal life"
But John came fifth, and won a
On Fri, Jul 24, 2015 at 09:52:18AM +0900, KOBAYASHI Yoshitake wrote:
> This patch enables support for Toshiba BENAND. BENAND is a SLC NAND
> solution that automatically generates ECC inside NAND chip.
>
> I considered to use the patch of on-die ECC, but I believe reading twice
> the same page
On Sun, Jul 12, 2015 at 10:49:08PM -0400, Peter Hurley wrote:
> Introduce tty_debug() macro to output uniform debug information for
> tty core debug messages (function name and tty name).
>
> Note: printk(KERN_DEBUG) is retained here over pr_debug() since
> messages can be enabled in non-DEBUG
Em Thu, Jul 23, 2015 at 06:07:30PM -0400, Steven Rostedt escreveu:
> On Thu, 23 Jul 2015 18:58:36 -0300
> Arnaldo Carvalho de Melo wrote:
>
> > Em Thu, Jul 23, 2015 at 06:52:46PM -0300, Arnaldo Carvalho de Melo escreveu:
> > > Em Thu, Jul 23, 2015 at 05:35:24PM -0400, Steven Rostedt escreveu:
>
As the original patch has not been in upstream, I'd prefer a refreshed patch,
rather than an incremental fix.
Thanks,
rui
> -Original Message-
> From: Sascha Hauer [mailto:s.ha...@pengutronix.de]
> Sent: Thursday, July 23, 2015 6:38 PM
> To: Zhang, Rui
> Cc: Punit Agrawal;
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org
> [mailto:linux-kernel-ow...@vger.kernel.org] On Behalf Of Eric Auger
> Sent: Monday, July 06, 2015 8:11 PM
> To: eric.au...@st.com; eric.au...@linaro.org;
> linux-arm-ker...@lists.infradead.org;
On 07/23/15 at 01:07pm, Josh Poimboeuf wrote:
> On Thu, Jul 23, 2015 at 12:02:06PM +0800, Minfei Huang wrote:
> > On 07/22/15 at 09:40am, Josh Poimboeuf wrote:
> > > Is it really safe to assume that there are no dependencies between
> > > patches which patch different objects?
> > >
> >
> > I
This patch fixes one of the problems reported by Daniel Walker
(https://lkml.org/lkml/2015/6/24/44).
If "crash_kexec_post_notifiers" boot option is specified,
other cpus are stopped by smp_send_stop() before entering
crash_kexec(), while usually machine_crash_shutdown() called by
crash_kexec()
This is a bugfix patch for crash_kexec_post_notifiers boot option
which allows users to call panic notifiers and kmsg dumpers before
kdump.
This fixes one of the problems reported by Daniel Walker
(https://lkml.org/lkml/2015/6/24/44).
Problem 1:
If crash_kexec_post_notifiers boot option is
Peter Zijlstra [pet...@infradead.org] wrote:
| On Wed, Jul 22, 2015 at 04:19:16PM -0700, Sukadev Bhattiprolu wrote:
| > Peter Zijlstra [pet...@infradead.org] wrote:
| > | I've not woken up yet, and not actually fully read the email, but can
| > | you stuff the entire above chunk inside the IPI?
|
Since this wheel is now available, and the USBID is listed on their website,
this patch adds it to allow the hid-lg4ff force feedback driver to find it.
I do not have this wheel to test with, but this should at least get it working
in emulation mode.
Note: There is probably more work required
Now that minor LSMs can cleanly stack with major LSMs, remove the unneeded
config for Yama to be made to explicitly stack. Just selecting the main
Yama CONFIG will allow it to work, regardless of the major LSM. Since
distros using Yama are already forcing it to stack, this is effectively
a no-op
This LSM enforces that kernel-loaded modules and firmware must all come
from the same filesystem, with the expectation that such a filesystem
is backed by a read-only device such as dm-verity or CDROM. This allows
systems that have a verified and/or unchangeable filesystem to enforce
module and
This patch enables support for Toshiba BENAND. BENAND is a SLC NAND
solution that automatically generates ECC inside NAND chip.
I considered to use the patch of on-die ECC, but I believe reading twice
the same page approach will affect read performance. Additionally, BENAND
does not support
Quoting Bartlomiej Zolnierkiewicz (2015-07-01 06:10:35)
> From: Thomas Abraham
>
> With the addition of the new Samsung specific cpu-clock type, the
> arm clock can be represented as a cpu-clock type. Add the CPU clock
> configuration data and instantiate the CPU clock type for Exynos5250.
>
>
Quoting Kukjin Kim (2015-07-07 07:43:31)
> Bartlomiej Zolnierkiewicz wrote:
> >
> > Hi,
> >
> Hi,
>
> > On Thursday, July 02, 2015 09:42:38 AM Chanwoo Choi wrote:
> > > This patchset use cpufreq-dt driver to support Exynos3250 cpufreq and
> > > tested it
> > > on Exynos3250-based Rinato board.
On Thu, Jul 23, 2015 at 12:28:33PM -0400, Stephen Smalley wrote:
> The shm implementation internally uses shmem or hugetlbfs inodes
> for shm segments. As these inodes are never directly exposed to
> userspace and only accessed through the shm operations which are
> already hooked by security
Hi Russel,
On Thu, Jul 23, 2015 at 01:35:53PM +0100, Russell King - ARM Linux wrote:
> On Thu, Jul 23, 2015 at 02:48:03AM +0200, Sebastian Reichel wrote:
> > Having the !ARCH_MULTIPLATFORM dependency in the Kconfig file results
> > in one option less to think about when configuring the kernel.
>
On Thu, Jul 23, 2015 at 4:58 PM, Willy Tarreau wrote:
> On Thu, Jul 23, 2015 at 04:40:14PM -0700, Andy Lutomirski wrote:
>> On Thu, Jul 23, 2015 at 4:36 PM, Kees Cook wrote:
>> > I've been pondering something like this that is even MORE generic, for
>> > any syscall. Something like a "syscalls"
On Thu, Jul 23, 2015 at 04:40:14PM -0700, Andy Lutomirski wrote:
> On Thu, Jul 23, 2015 at 4:36 PM, Kees Cook wrote:
> > I've been pondering something like this that is even MORE generic, for
> > any syscall. Something like a "syscalls" directory under
> > /proc/sys/kernel, with 1 entry per
On Thu, Jul 23, 2015 at 09:19:28AM -0400, J. Bruce Fields wrote:
> On Thu, Jul 23, 2015 at 11:51:35AM +1000, Dave Chinner wrote:
> > On Wed, Jul 22, 2015 at 01:41:00PM -0400, J. Bruce Fields wrote:
> > > On Wed, Jul 22, 2015 at 12:52:58PM -0400, Austin S Hemmelgarn wrote:
> > > > On 2015-07-22
On Thu, Jul 23, 2015 at 4:36 PM, Kees Cook wrote:
> On Thu, Jul 23, 2015 at 3:24 AM, Willy Tarreau wrote:
>> #ifdef CONFIG_SMP
>> static void flush_ldt(void *current_mm)
>> {
>> @@ -254,6 +260,9 @@ asmlinkage int sys_modify_ldt(int func, void __user *ptr,
>> {
>> int ret = -ENOSYS;
On Thu, Jul 23, 2015 at 3:24 AM, Willy Tarreau wrote:
> Hi Andy,
>
> On Wed, Jul 22, 2015 at 12:23:47PM -0700, Andy Lutomirski wrote:
>> The modify_ldt syscall exposes a large attack surface and is
>> unnecessary for modern userspace. Make it optional.
>
> Wouldn't you prefer something like this
On 07/22/2015 10:09 AM, Kaixu Xia wrote:
Previous patch v1 url:
https://lkml.org/lkml/2015/7/17/287
[ Sorry to chime in late, just noticed this series now as I wasn't in Cc for
the core BPF changes. More below ... ]
This patchset allows user read PMU events in the following way:
1. Open
On Thu, 2015-07-23 at 14:54 -0700, Spencer Baugh wrote:
> From: Joern Engel
>
> Mapping large memory spaces can be slow and prevent high-priority
> realtime threads from preempting lower-priority threads for a long time.
Yes, and one of the goals of large page ioremap support is to address such
On Thu, Jul 23, 2015 at 01:37:02PM -0700, Andrew Morton wrote:
> On Thu, 16 Jul 2015 01:41:56 + Naoya Horiguchi
> wrote:
>
> > The race condition addressed in commit add05cecef80 ("mm: soft-offline:
> > don't
> > free target page in successful page migration") was not closed completely,
>
The esc argument is used to reduce which characters will be escaped.
For example, using " " with ESCAPE_SPACE will not produce any escaped
spaces.
Signed-off-by: Kees Cook
---
lib/string_helpers.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git
Irina Tirdea schrieb am 23.07.2015 um 19:22:
> Running generic_buffer without enabling any channel of the
> sensor will fail without printing any error message.
>
> Add an error message that indicates buffer enable failed.
Hi,
please make use of the error code stored in ret (with negative sign),
Hi,
Sure - sorry, my description was a little .. basic.
So, I have a client who was having problems with machines hanging in
the field. Very rare, associated with a h/w change that introduced
more cores. Kernel dumps implied that the timer list was getting
corrupted.
This configuration of
On Thu, Jul 23, 2015 at 03:54:43PM -0700, David Rientjes wrote:
> On Thu, 23 Jul 2015, Jörn Engel wrote:
>
> > > This is wrong, you'd want to do any cond_resched() before the page
> > > allocation to avoid racing with an update to h->nr_huge_pages or
> > > h->surplus_huge_pages while
Irina Tirdea schrieb am 23.07.2015 um 19:22:
> When the the sensor data uses 32 bits out of 32, generic_buffer prints
> the value 0 for all data read.
>
> In this case, the mask is shifted 32 bits, which is beyond the size of
> an integer. This will lead to the mask always being 0. Before
On Thu, Jul 23, 2015 at 01:08:36PM -0400, Mikulas Patocka wrote:
> On Wed, 22 Jul 2015, Dave Chinner wrote:
> > On Wed, Jul 22, 2015 at 10:09:23AM +1000, Dave Chinner wrote:
> > > On Tue, Jul 21, 2015 at 01:47:53PM -0400, Mike Snitzer wrote:
> > > | $ cat
> > > |
Instead of creating wakealarm attribute manually, after the device has been
registered, let's rely on facilities provided by the attribute groups to
control which attributes are visible and which are not. This allows to to
create all needed attributes at once, at the same time that we register RTC
Instead of using older style DEVICE_ATTR for wakealarm attribute let's
switch to using DEVICE_ATTR_RW that ensures consistent across the kernel
permissions on the attribute.
Signed-off-by: Dmitry Torokhov
---
drivers/rtc/rtc-sysfs.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
Users of rtc_does_wakealarm() return value treat it as boolean so let's
change the signature accordingly.
Signed-off-by: Dmitry Torokhov
---
drivers/rtc/rtc-sysfs.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/rtc/rtc-sysfs.c b/drivers/rtc/rtc-sysfs.c
index
On Thu, Jul 23, 2015 at 12:43:58PM -0400, Vivek Goyal wrote:
> On Thu, Jul 23, 2015 at 03:10:43PM +1000, Dave Chinner wrote:
>
> [..]
> > I don't think knowing the bdev timeout is necessary because the
> > default is most likely to be "fail fast" in this case. i.e. no
> > retries, just shut down.
On 7/23/15 2:42 AM, Kaixu Xia wrote:
This is a simple example and shows how to use the new ability
to get the selected Hardware PMU counter value.
Signed-off-by: Kaixu Xia
...
+struct bpf_map_def SEC("maps") my_map = {
+ .type = BPF_MAP_TYPE_PERF_EVENT_ARRAY,
+ .key_size =
Hi,
I've an offer for you.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On 7/23/15 2:42 AM, Kaixu Xia wrote:
According to the perf_event_map_fd and index, the function
bpf_perf_event_read() can convert the corresponding map
value to the pointer to struct perf_event and return the
Hardware PMU counter value.
Signed-off-by: Kaixu Xia
...
+static u64
On Thu, Jul 23, 2015 at 1:50 PM, Andy Shevchenko
wrote:
> On Thu, 2015-07-23 at 13:36 -0700, Kees Cook wrote:
>> On Thu, Jul 23, 2015 at 1:27 PM, Andy Shevchenko
>> wrote:
>> > On Thu, 2015-07-23 at 12:59 -0700, Kees Cook wrote:
>> > > Hi,
>> > >
>> > > I'm curious why ESCAPE_SPACE doesn't
On Thu, 23 Jul 2015, Jörn Engel wrote:
> > This is wrong, you'd want to do any cond_resched() before the page
> > allocation to avoid racing with an update to h->nr_huge_pages or
> > h->surplus_huge_pages while hugetlb_lock was dropped that would result in
> > the page having been uselessly
On 7/23/15 2:42 AM, Kaixu Xia wrote:
Introduce a new bpf map type 'BPF_MAP_TYPE_PERF_EVENT_ARRAY'.
This map only stores the pointer to struct perf_event. The
user space event FDs from perf_event_open() syscall are converted
to the pointer to struct perf_event and stored in map.
...
+static
On Thu, Jul 23, 2015 at 12:54:42PM -0700, Davidlohr Bueso wrote:
> On Wed, 2015-07-22 at 17:13 -0700, Paul E. McKenney wrote:
> > I need to see something more than what I am seeing for me to be able
> > to accept this, cute though it unarguably is.
>
> heh I didn't consider copyright for this
Our irq-bcm7120-l2 interrupt controller driver utilizes the same handler
function for the different parent interrupts it services: UPG_MAIN, UPG_BSC for
instance.
The problem is that function reads the IRQSTAT register which can combine
interrupt causes for different parent interrupts, such that
Signed-off-by: Moritz Fischer
---
arch/arm/boot/dts/zynq-7000.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/zynq-7000.dtsi b/arch/arm/boot/dts/zynq-7000.dtsi
index b429e1d..a56fe11 100644
--- a/arch/arm/boot/dts/zynq-7000.dtsi
+++
Signed-off-by: Moritz Fischer
---
Documentation/devicetree/bindings/reset/zynq-reset-pl.txt | 13 +
1 file changed, 13 insertions(+)
create mode 100644 Documentation/devicetree/bindings/reset/zynq-reset-pl.txt
diff --git a/Documentation/devicetree/bindings/reset/zynq-reset-pl.txt
Hi all,
while trying to get the devicetree overlays working using Alan's
simple-fpga-bus I couldn't find a way to independently reset
parts of the PL logic. I might have missed something and this
exists already somewhere, in that case, oh well ...
If Sören or Michael could take a look at this to
The Zynq PL reset controller allows to control the 4
FCLK{0..3}_RESETN signals that can be used to reset custom IP in
the PL.
Signed-off-by: Moritz Fischer
---
drivers/reset/Makefile| 1 +
drivers/reset/reset-zynq-pl.c | 142 ++
2 files changed,
Hi all,
I started to test linux 4.1 series with rc6. However, I was never able
to boot that kernel in i686 architecture. Trying it again with
VirtualBox gave me more conclusions. Using one core it simply boots up.
Using more than one CPU core it crashes with:
Failed to access perfctr msr (MSR
On Thu, Jul 23, 2015 at 3:37 PM, Andy Lutomirski wrote:
> int3 uses IST and the paranoid gsbase path. Neither is necessary,
> although the IST stack may currently be necessary to avoid stack
> overruns.
>
> Clean up IRQ stacks, make them NMI safe, teach idtentry to use
> irqstacks if requested,
This will allow IRQ stacks to nest inside NMIs or similar entries
that can happen during IRQ stack setup or teardown.
The Xen code here has a confusing comment.
Signed-off-by: Andy Lutomirski
---
arch/x86/entry/entry_64.S| 72 ++--
There's nothing IST-worthy about #BP/int3. We don't allow kprobes
in the small handful of places in the kernel that run at CPL0 with
an invalid stack, and 32-bit kernels have used normal interrupt
gates for #BP forever.
Furthermore, we don't allow kprobes in places that have usergs while
in
We don't specifically need IST for things like kprobes, but we do
want to avoid rare, surprising extra stack usage if a kprobe hits
with a deep stack.
Teach idtentry to use the IRQ stack for selected entries.
This implementation uses the IRQ stack even if we entered from user
mode. This
int3 uses IST and the paranoid gsbase path. Neither is necessary,
although the IST stack may currently be necessary to avoid stack
overruns.
Clean up IRQ stacks, make them NMI safe, teach idtentry to use
irqstacks if requested, and move int3 to the IRQ stack.
This prepares us to return from
On Thu, Jul 23, 2015 at 03:08:58PM -0700, David Rientjes wrote:
> On Thu, 23 Jul 2015, Spencer Baugh wrote:
> > From: Joern Engel
> >
> > ~150ms scheduler latency for both observed in the wild.
> >
> > Signed-off-by: Joern Engel
> > Signed-off-by: Spencer Baugh
> > ---
> > mm/hugetlb.c | 2
On Fri, Jun 05, 2015 at 09:57:40AM +, Taichi Kageyama wrote:
> The following race conditions can happen if a serial is used as console.
> Case1. CPU_B handles an interrupt from a serial
> autoconfig_irq() fails whether the interrupt is raised or not
> if CPU_B is disabled to handle
Currently, the warning for missing device_caps gives a backtrace like so:
[] dump_stack+0x45/0x57
[] warn_slowpath_common+0x8a/0xc0
[] warn_slowpath_null+0x1a/0x20
[] v4l_querycap+0x43/0x80 [videodev]
[] __video_do_ioctl+0x2a4/0x320 [videodev]
[] ? do_last+0x195/0x1210
[]
From: Brian Bunker
AIX servers using VIOS servers that virtualize FC cards will have a
problem booting without support for START_STOP_UNIT.
v2: Cite sb3r36 exactly, clean up if conditions
Signed-off-by: Brian Bunker
Signed-off-by: Spencer Baugh
---
drivers/target/target_core_sbc.c | 36
On Tue, Jul 21, 2015 at 01:34:52PM -0700, Guenter Roeck wrote:
> Commit b17d1bf16cc7 ("gpio: make flags mandatory for gpiod_get functions")
> makes the flags argument to devm_gpiod_get_optional mandatory but does not
> update all users. This results in the following build error.
>
>
On Mon, Jun 08, 2015 at 11:17:11AM -0700, Bin Gao wrote:
> On some Intel Atom SoCs, the legacy IO port UART(0x3F8) is not available.
> Instead, a 8250 compatible PCI uart can be used as early console.
> This patch adds pci support to the 8250 early console driver uart8250.
> For example, to enable
On Thu, Jul 23, 2015 at 11:10:30AM -0700, Jörn Engel wrote:
> On Thu, Jul 23, 2015 at 11:02:55AM -0700, Jörn Engel wrote:
> > Spencer spotted something nasty in the round_up macro. We were
> > wondering why round_up() worked differently from ALIGN. The only real
> > difference between the two
From: Alexei Potashnik
If command didn't match a LUN and we're sending check condition, the
target_cmd_complete ftrace point will crash because it assumes that
cmd->t_task_cdb has been set.
The fix will temporarily set t_task_cdb to the se_cmd buffer
and copy first 6 bytes of cdb in there as
On Thu, Jul 23, 2015 at 02:55:52PM -0700, Moritz Fischer wrote:
> Hi Alan,
>
> I saw that your socfpga driver doesn't support the partial reconfig
> use case (not a big deal).
> What I currently do for Zynq is if I'm doing a non-partial reconfig is
> that I disable input
> level shifters and
On Tue, Jun 09, 2015 at 03:11:36PM +0900, Hyuk Myeong wrote:
> This patch fix a spelling typo in the comment in synclink.c and
> synclinkmp.c.
>
> Signed-off-by: Hyuk Myeong
> ---
> drivers/tty/synclink.c | 4 ++--
> drivers/tty/synclinkmp.c | 4 ++--
> 2 files changed, 4 insertions(+), 4
On Tue, May 19, 2015 at 04:06:53PM +0100, Richard Watts wrote:
> Avoid usb reset crashes by making tty_io cdevs truly dynamic
What USB reset crashes are you referring to here?
>
> Signed-off-by: Richard Watts
> Reported-by: Duncan Mackintosh
> ---
> drivers/tty/tty_io.c | 24
On Thu, 23 Jul 2015, Spencer Baugh wrote:
> From: Joern Engel
>
> ~150ms scheduler latency for both observed in the wild.
>
> Signed-off-by: Joern Engel
> Signed-off-by: Spencer Baugh
> ---
> mm/hugetlb.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/mm/hugetlb.c
On Thu, 23 Jul 2015 18:58:36 -0300
Arnaldo Carvalho de Melo wrote:
> Em Thu, Jul 23, 2015 at 06:52:46PM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Thu, Jul 23, 2015 at 05:35:24PM -0400, Steven Rostedt escreveu:
> > > On Thu, 23 Jul 2015 18:25:36 -0300
> > > Arnaldo Carvalho de Melo wrote:
On Thu, Jul 23, 2015 at 2:59 PM, Andy Lutomirski wrote:
> OK, new proposal:
>
> In do_debug, if we trip an instruction breakpoint while
> !user_mode(regs) && ((regs->flags & X86_EFLAGS_IF) == 0), then disarm
> *that breakpoint*.
Ack. The more targeted we can make this while still guaranteeing
On Thu, Jul 23, 2015 at 2:54 PM, Linus Torvalds
wrote:
> On Thu, Jul 23, 2015 at 2:45 PM, Andy Lutomirski wrote:
>>
>> Or we just re-enable them on the way out of NMI (i.e. the very last
>> thing we do in the NMI handler). I don't want to break regular
>> userspace gdb when perf is running.
>
>
On Thu, Jul 23, 2015 at 2:50 PM, Andy Lutomirski wrote:
>
> What if we relax it slightly: "if the breakpoint happened during that
> interrupts-off region, I will clear all *kernel breakpoints* in %dr7
> to guarantee forward progress"?
>
> Watchpoints don't need RF to make forward progress, and,
On Thu, Jul 23, 2015 at 12:28 PM, Stephen Smalley wrote:
> The shm implementation internally uses shmem or hugetlbfs inodes
> for shm segments. As these inodes are never directly exposed to
> userspace and only accessed through the shm operations which are
> already hooked by security modules,
On Tue, Jul 14, 2015 at 06:12:03PM +0300, Andy Shevchenko wrote:
> We have couple of standard but rare used baudrates which are not supported by
> 1,8432MHz reference frequency. Besides that user can potentially ask for any
> baudrate (via BOTHER flag) and we currently don't fully support that.
Em Thu, Jul 23, 2015 at 06:52:46PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Thu, Jul 23, 2015 at 05:35:24PM -0400, Steven Rostedt escreveu:
> > On Thu, 23 Jul 2015 18:25:36 -0300
> > Arnaldo Carvalho de Melo wrote:
> > > + if (resolver == NULL) {
> > > + errno = ENOMEM;
> >
> > Why
From: Joern Engel
Code was responsible for ~150ms scheduler latencies.
Signed-off-by: Joern Engel
Signed-off-by: Spencer Baugh
---
drivers/net/ethernet/intel/e1000/e1000_hw.c | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git
Hi Bastien,
On Thu, Jul 23, 2015 at 04:13:28PM +0200, Bastien Nocera wrote:
> The touchscreen on the WinBook TW100 and TW700 don't match the default
> display, with 0,0 touches being reported when touching at the bottom
> right of the screen.
>
> 1280,800 0,800
>
From: Joern Engel
Users can request timeouts as low as 1s. However, whatever the request
timeout happens to be, we always round it up by up to 1s. So at the
lower end the rounding doubles the user-requested timeout.
Reduce the impact of rounding for small timeout values.
Curious side note:
Hi Alan,
I saw that your socfpga driver doesn't support the partial reconfig
use case (not a big deal).
What I currently do for Zynq is if I'm doing a non-partial reconfig is
that I disable input
level shifters and assert *all* resets while reprogramming in my FPGA
manager .write_init() and
From: Joern Engel
Mapping large memory spaces can be slow and prevent high-priority
realtime threads from preempting lower-priority threads for a long time.
In my case it was a 256GB mapping causing at least 950ms scheduler
delay. Problem detection is ratelimited and depends on interrupts
From: Joern Engel
Multiple nested loops. I have observed 590ms scheduler latency caused
by this loop and interrupts. Interrupts were responsible for 190ms, the
rest could have been avoided with a cond_resched.
Signed-off-by: Joern Engel
Signed-off-by: Spencer Baugh
---
From: Joern Engel
~150ms scheduler latency for both observed in the wild.
Signed-off-by: Joern Engel
Signed-off-by: Spencer Baugh
---
mm/hugetlb.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/mm/hugetlb.c b/mm/hugetlb.c
index a8c3087..2eb6919 100644
--- a/mm/hugetlb.c
+++
On Thu, Jul 23, 2015 at 2:45 PM, Andy Lutomirski wrote:
>
> Or we just re-enable them on the way out of NMI (i.e. the very last
> thing we do in the NMI handler). I don't want to break regular
> userspace gdb when perf is running.
I'd really prefer it if we don't touch NMI code in those kinds
For all of these, you need a better subject line that shows what part of
the kernel you are modifying.
For example, this one would be:
Subject: [PATCH 1/5] staging: lustre: cl_page.c: add blank line after
variable definition
On Thu, Jul 23, 2015 at 02:21:10PM +0800, Incarnation P. Lee
From: Roland Dreier
In a performance profile, taking a mutex in iscsit_increment_maxcmdsn()
shows up very high. However taking a mutex around "sess->max_cmd_sn += 1"
seems pretty silly: we're not serializing against other contexts in
any useful way.
I did a quick audit and there don't appear
Em Thu, Jul 23, 2015 at 05:35:24PM -0400, Steven Rostedt escreveu:
> On Thu, 23 Jul 2015 18:25:36 -0300
> Arnaldo Carvalho de Melo wrote:
>
> > Like this?
>
> Yep, but some comments.
>
> > +int pevent_set_function_resolver(struct pevent *pevent,
> > +
On Thu, Jul 23, 2015 at 02:46:49PM -0700, Andy Lutomirski wrote:
> On Thu, Jul 23, 2015 at 2:46 PM, Willy Tarreau wrote:
> > Can't the back link of the TSS tell us where we come from ? At least
> > it should not be manipulable from user-space.
>
> Not on 64-bit -- there are no tasks :)
Ah crap,
On Thu, Jul 23, 2015 at 2:48 PM, Linus Torvalds
wrote:
> On Thu, Jul 23, 2015 at 2:31 PM, Steven Rostedt wrote:
>>
>> Let me get this straight. The idea is in the #DB handler to detect that
>> it was triggered in NMI context, and if so, simply disarm that
>> breakpoint permanently, right?
>
>
On 7/22/2015 5:15 PM, Eric W. Biederman wrote:
> Casey Schaufler writes:
>
>> On 7/22/2015 12:32 PM, Seth Forshee wrote:
>>> On Wed, Jul 22, 2015 at 11:10:46AM -0700, Casey Schaufler wrote:
On 7/22/2015 8:56 AM, Seth Forshee wrote:
> On Tue, Jul 21, 2015 at 06:52:31PM -0700, Casey
On Thu, Jul 23, 2015 at 2:31 PM, Steven Rostedt wrote:
>
> Let me get this straight. The idea is in the #DB handler to detect that
> it was triggered in NMI context, and if so, simply disarm that
> breakpoint permanently, right?
No, for simplicity, I'd make it cover not just NMI code, but any
On Thu, Jul 23, 2015 at 2:20 PM, Steven Rostedt wrote:
> On Thu, 23 Jul 2015 13:21:16 -0700
> Andy Lutomirski wrote:
>
>> 3. Forbid faults (other than MCE) inside NMI.
>>
>> Option 3 is almost easy. There are really only two kinds of faults
>> that can legitimately nest inside NMI: #PF and #DB.
101 - 200 of 1842 matches
Mail list logo
