Hi Ram, thanks for submitting this, please see some feedback inlined...
On Sun, Sep 06, 2015 at 10:53:07PM +0530, Ramakrishna Pallala wrote:
> Add new charger driver support for BQ24261 charger IC.
>
> BQ24261 charger driver relies on extcon notifications to get the
> charger cable type and based
On Fri, 2015-09-04 at 20:00 +0200, christophe leroy wrote:
> Le 04/09/2015 18:43, Scott Wood a écrit :
> > On Thu, Sep 03, 2015 at 11:27:03AM +0200, Christophe Leroy wrote:
> > > On PPC832x, perf record/report reports martian addresses
> > >
> > > 2.62% perf_reseau4 libpthread-2.18.so [.]
Peter Zijlstra writes:
> On Tue, Sep 08, 2015 at 03:31:58PM +0100, Morten Rasmussen wrote:
>> On Tue, Sep 08, 2015 at 02:52:05PM +0200, Peter Zijlstra wrote:
>> > > Tricky that, LOAD_AVG_MAX very much relies on the unit being 1<<10.
>>
>> I don't get why LOAD_AVG_MAX relies on the util_avg shift
Hello, Ingo,
This additional series contains a single fix for a regression introduced
earlier in this merge window:
1. security/device_cgroup: f78f5b90c4ff ("rcu: Rename
rcu_lockdep_assert() to RCU_LOCKDEP_WARN()") introduced a
bug by incorrectly inverting the condition when
In __request_region, if a conflict with a BUSY and MUXED resource is
detected, then the caller goes to sleep and waits for the resource to
be released. A pointer on the conflicting resource is kept. At wake-up
this pointer is used as a parent to retry to request the region. A first
problem is that
On Wed, 9 Sep 2015, Vlastimil Babka wrote:
> On 08/20/2015 10:26 AM, Naoya Horiguchi wrote:
> > Currently /proc/PID/smaps provides no usage info for vma(VM_HUGETLB), which
> > is inconvenient when we want to know per-task or per-vma base hugetlb usage.
> > To solve this, this patch adds a new line
The work performed by wmi_gtoa is equivalent to simply sprintf(out,
"%pUL", in), so one could replace its body by this. However, most
users feed the result directly as a %s argument to some other function
which also understands the %p extensions (they all ultimately use
vsnprintf), so we can elimin
From: Andi Kleen
[Note: I still need this patch to make memory bandwidth monitoring
work on my laptop. I believe all earlier review comments regarding
how to return later ignored error codes are addressed in this version.]
Several sytems, such as my laptop, don't expose the PCI devices
for the P
On Wed, Sep 9, 2015 at 2:20 PM, Arnd Bergmann wrote:
> On Wednesday 09 September 2015 13:52:39 Kees Cook wrote:
>> On Wed, Sep 9, 2015 at 1:08 PM, Arnd Bergmann wrote:
>> > On Wednesday 09 September 2015 12:30:27 Kees Cook wrote:
>
>> > If this is intentional, it at least needs a comment to expla
On Wed, 2015-09-09 at 19:59 +0530, Chaitra Basappa wrote:
> From: Sreekanth Reddy [mailto:sreekanth.re...@avagotech.com]
> Sent: Tuesday, September 08, 2015 5:26 PM
> To: Nicholas A. Bellinger
> Cc: linux-scsi; linux-kernel; James Bottomley; Calvin Owens; Christoph
> Hellwig; MPT-FusionLinux.pdl; k
On Mon, Sep 7, 2015 at 8:56 AM, Denys Vlasenko wrote:
> This new test checks that all x86 registers are preserved across
> 32-bit syscalls. It tests syscalls through VDSO (if available)
> and through INT 0x80, normally and under ptrace.
>
> If kernel is a 64-bit one, high registers (r8..r15) are p
This is preparation for using kstrdup_const to initialize that member.
Signed-off-by: Rasmus Villemoes
---
drivers/acpi/scan.c| 4 ++--
drivers/pnp/pnpacpi/core.c | 4 ++--
include/acpi/acpi_bus.h| 2 +-
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/acpi/scan
One wouldn't expect a "match" function modify the string it searches
for, and indeed the only instance of the struct
acpi_scan_handler::match callback, acpi_pnp_match, can easily be
changed. While there, update its helper matching_id().
This is also preparation for constifying struct acpi_hardware
Empirically, acpi_add_id is mostly called with string literals, so
using kstrdup_const for initializing struct acpi_hardware_id::id saves
a little run-time memory and a string copy.
Signed-off-by: Rasmus Villemoes
---
drivers/acpi/scan.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
On 06/30/2015 10:36 AM, Dave Hansen wrote:
> From: Dave Hansen
>
> The comment here says that it is checking for invalid bits. But,
> the mask is *actually* checking to ensure that _any_ valid bit
> is set, which is quite different.
>
> Add the actual check which was intended. Retain the exist
On Thu, Sep 03, 2015 at 08:05:40PM +0200, Vincent Pelletier wrote:
> Hi,
>
> On Fri, 21 Aug 2015 22:48:24 +0200, Vincent Pelletier
> wrote:
> > On Fri, 21 Aug 2015 19:52:16 +0200, Simon Guinot
> > wrote:
> > > Please, could you describe a setup (as simple as possible) allowing to
> > > reproduce
Hi Peter,
I noticed that tip/perf/core is missing the Skylake PEBS Frontend
extrareg support. At some point you had signed off on it, but then Stephane
found another issue which was fixed with an follow-on patch.
It would be good if that could be merged this cycle too, as that
would make the Skyl
From: Andi Kleen
Skylake has a new FRONTEND_LATENCY PEBS event to accurate profile
frontend problems (like ITLB or decoding issues)
The new event is configured through a separate MSR, which selects
a range of sub events.
Define the extra MSR as a extra reg and export support for it
through sysf
From: Andi Kleen
Stephane pointed out that the extrareg mask was one bit too short.
The bubble width field was truncated by one bit. Fix that here.
Also add some extra comments on the reserved bits inside the event
select code.
Reported-by: Stephane Eranian
Signed-off-by: Andi Kleen
---
arch/
Sometimes kobject_set_name_vargs is called with a format string
conaining no %, or a format string of precisely "%s", where the single
vararg happens to point to .rodata. kvasprintf_const detects these
cases for us and returns a copy of that pointer instead of duplicating
the string, thus saving so
This adds kvasprintf_const which tries to use kstrdup_const if
possible: If the format string contains no % characters, or if the
format string is exactly "%s", we delegate to
kstrdup_const. Otherwise, we fall back to kvasprintf.
Just as for kstrdup_const, the main motivation is to save memory by
From: Andi Kleen
Add support for the "frontend" extra MSR on Skylake in the JSON
conversion.
Signed-off-by: Andi Kleen
---
tools/perf/pmu-events/jevents.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/perf/pmu-events/jevents.c b/tools/perf/pmu-events/jevents.c
index 247d777..96e233
>
> From: Arnaldo Carvalho de Melo
>
> This reverts commit d49e4695077278ee3016cd242967de23072ec331.
>
> We don't need it, using machine->env seems to be enough.
The patchset to dump freq per sample need commit d49e469507.
It also needs commit 2c07144dfc which is revert by PATCH 13.
https://
Using kstrdup_const allows us to save a little runtime memory (and a
string copy) in the common case where name is a string literal.
Signed-off-by: Rasmus Villemoes
---
drivers/base/power/wakeup.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/base/power/wakeup.c
On Wed, Sep 9, 2015 at 2:40 PM, Stephen Rothwell wrote:
>
> I have not been able to fetch from that tree for the past couple of
> days. It connects and then hangs for some time
.. yup, that's what I got just when trying to pull.
Linus
--
To unsubscribe from this list: send the line
> diff --git a/tools/perf/util/header.c b/tools/perf/util/header.c index
> 151b8310ac70..d4c8aa2f4db7 100644
> --- a/tools/perf/util/header.c
> +++ b/tools/perf/util/header.c
> @@ -415,8 +415,6 @@ struct cpu_topo {
> u32 thread_sib;
> char **core_siblings;
> char **thread_sibling
Using kstrdup_const, thus reusing .rodata when possible, saves around
2 kB of runtime memory on my laptop/.config combination.
Signed-off-by: Rasmus Villemoes
---
lib/dynamic_debug.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/lib/dynamic_debug.c b/lib/dynamic_deb
Hi Wim,
On Wed, 9 Sep 2015 21:58:38 +0200 Wim Van Sebroeck wrote:
>
> Please pull from 'master' branch of
> git://www.linux-watchdog.org/linux-watchdog.git
I have not been able to fetch from that tree for the past couple of
days. It connects and then hangs for some time and then I get:
f
Hi Wim,
On 09/09/2015 at 21:58:38 +0200, Wim Van Sebroeck wrote :
> commit ab54d7f017772e89964d4040937a83cd4468562a
> Author: Alexandre Belloni
> Date: Fri Jul 31 11:39:39 2015 +0200
>
> Documentation: watchdog: at91sam9_wdt: add clocks property
>
> The watchdog has an input clock
futex_hash() references two global variables: the base pointer
futex_queues and the size of the array futex_hashsize. The latter is
marked __read_mostly, while the former is not, so they are likely to
end up very far from each other. This means that futex_hash() is
likely to encounter two cache mis
To cover the common case of sorting an array of pointers, Daniel
Wagner recently modified the library sort() to use a specific swap
function for size==8, in addition to the size==4 case which was
already handled. Since sizeof(long) is either 4 or 8,
ftrace_swap_ips() is redundant and we can just le
On Mon, 2015-09-07 at 01:57 -0500, Lu Yangbo-B47093 wrote:
> Any comments?
>
> -Yangbo Lu
Sorry, this somehow got marked as Awaiting Upstream in patchwork but not
applied to my tree. I'll take it next time.
-Scott
>
> > -Original Message-
> > From: Yangbo Lu [mailto:yangbo...@freesc
>
> pmu-events/jevents.c:247:2: error: missing initializer for field ‘name’ of
> ‘struct fixed’ [-Werror=missing-field-initializers]
Thanks.
Somehow a WERROR=0 must have slipped into the build script again.
> After this I was able to get non-zero counts for the 'inst_retired.any'
> event on m
The kernel now has kstrdup_const/kfree_const for reusing .rodata
(typically string literals) when possible; there's no reason to
duplicate that logic in the tracing system. Moreover, as the comment
above core_kernel_data states, it may not always return true for
.rodata - that is for example the ca
On Wednesday 09 September 2015 13:52:39 Kees Cook wrote:
> On Wed, Sep 9, 2015 at 1:08 PM, Arnd Bergmann wrote:
> > On Wednesday 09 September 2015 12:30:27 Kees Cook wrote:
> > If this is intentional, it at least needs a comment to explain the
> > situation, and be extended to all other architect
Den 09.09.2015 20:35, skrev Greg Kroah-Hartman:
On Sat, Sep 05, 2015 at 07:13:45PM +0530, Sudip Mukherjee wrote:
Instead of defining DRVNAME and using it in all calls to pr_* family of
macros lets start using pr_fmt.
Signed-off-by: Sudip Mukherjee
---
drivers/staging/fbtft/fbtft_device.c |
OMAP5 and DRA7 reuse the same pm44xx_erratum variable so, enable the
same, else PM features such as Suspend to ram is broken in a SoC only
build configuration.
Reported-by: Carlos Hernandez
Signed-off-by: Nishanth Menon
---
arch/arm/mach-omap2/pm.h |3 ++-
1 file changed, 2 insertions(+), 1
OMAP5 SoC has Cortex-A15 which does not use TWD timer. It uses
ARCH_TIMER instead, clean up unwanted configuration and enable
OMAP_INTERCONNECT and OPP which is necessary for expected functionality
on the SoC.
Reported-by: Carlos Hernandez
Reported-by: Felipe Balbi
Signed-off-by: Nishanth Menon
Hi,
While doing a SoC only build for DRA7, a few bugs did pop up. The
following series provides necessary fixups for the same.
Nishanth Menon (4):
ARM: OMAP4+: PM: erratum is used by OMAP5 and DRA7 as well
ARM: omap2+: board-generic: Remove stale of_irq macros
ARM: DRA7: Select missing opti
When commit c4082d499fa2 ("ARM: omap2+: board-generic: clean up the
irq data from board file") cleaned up the direct usage of gic_of_init
and omap_intc_of_init, it failed to clean up the macros properly.
Since these macros are no longer used, lets just remove them.
Fixes: c4082d499fa2 ("ARM: omap
DRA7 does use OPP, uses OMAP interconnect and also does require SCU.
These are missing in the SoC only build of DRA7 breaking various PM
features in DRA7 only build.
Reported-by: Carlos Hernandez
Signed-off-by: Nishanth Menon
---
arch/arm/mach-omap2/Kconfig |3 +++
1 file changed, 3 inserti
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=104031
Fixes: 6e85d5ad36a26debc23a9a865c029cbe242b2dc8
Based on the discussion starting at
http://www.spinics.net/lists/netdev/msg342193.html
Tested locally on RTL8168evl/8111evl with various concurrent processes
accessing /proc/net/dev while
I think this change actually doesn't do anything: __NR_fork was still
being defined either way, and on my machine fork() in comes
from libc.
That said, I don't think there's any way to determine this
automatically, so this at least quiets the checker.
Signed-off-by: Palmer Dabbelt
Reviewed-by:
This used to just be behind an #ifdef COMPAT_COMPAT, so most of
userspace wouldn't have seen the definition before. This change just
makes the __KERNEL__ part explicit to quiet the header checker.
Signed-off-by: Palmer Dabbelt
Reviewed-by: Andrew Waterman
Reviewed-by: Albert Ou
---
include/ua
This one scares me: while I can't find any system calls that directly
take this as an argument, a comment in
"
Generic ptrace interface that exports the architecture specific
regsets using the corresponding NT_* types (which are also used in
the core dump). Please note that the NT_PRS
This used to be hidden behind CONFIG_MMAP_ALLOW_UNINITIALIZED, so
userspace wouldn't actually ever see it. While I could have kept
hiding it, the man pages seem to indicate that MAP_UNINITIALIZED
should be visible:
mmap(2)
MAP_UNINITIALIZED (since Linux 2.6.33)
Don't clear anonymous pages
This doesn't make any sense to expose to userspace.
Signed-off-by: Palmer Dabbelt
Reviewed-by: Andrew Waterman
Reviewed-by: Albert Ou
---
include/uapi/linux/eventpoll.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/uapi/linux/eventpoll.h b/include/uapi/linux/eventpoll.h
index
Michael Ellerman [m...@ellerman.id.au] wrote:
| > > This looks fine to me from an arch perspective. I assume the whole series
can
| > > go via tip-something?
| >
| > Yeah, I've had it queued for a few days, there was one s390 compile
| > fail reported by the build-bot, which I've just fixed. So i
Now that we have introduced the bad_madt_entry() function, and that
function is being invoked in acpi_table_parse_madt() for us, there
is no longer any need to use the BAD_MADT_ENTRY macro, or in the case
of arm64, the BAD_MADT_GICC_ENTRY, too.
Signed-off-by: Al Stone
Acked-by: Catalin Marinas
A
I don't think this was ever intended to be exposed to userspace.
Signed-off-by: Palmer Dabbelt
Reviewed-by: Andrew Waterman
Reviewed-by: Albert Ou
---
include/uapi/linux/pktcdvd.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/uapi/linux/pktcdvd.h b/include/uapi/linux/pktcdvd.h
The existing BAD_MADT_ENTRY macro only checks that the size of the data
structure for an MADT subtable matches the length entry in the subtable.
This is, unfortunately, not reliable. Nor, as it turns out, does it have
anything to do with what the length should be in any particular table.
We intro
I think this actually isn't a good idea, but I can't find anything
outside of the kernel that's using this so I'm going to hide it.
Signed-off-by: Palmer Dabbelt
Reviewed-by: Andrew Waterman
Reviewed-by: Albert Ou
---
arch/x86/include/uapi/asm/auxvec.h | 2 ++
1 file changed, 2 insertions(+)
On Sep 9 22:23, Francois Romieu wrote:
> Corinna Vinschen :
> [...]
> > diff --git a/drivers/net/ethernet/realtek/r8169.c
> > b/drivers/net/ethernet/realtek/r8169.c
> > index 24dcbe6..630811a 100644
> > --- a/drivers/net/ethernet/realtek/r8169.c
> > +++ b/drivers/net/ethernet/realtek/r8169.c
> [
I don't think this was ever meant to be exposed to userspace.
Signed-off-by: Palmer Dabbelt
Reviewed-by: Andrew Waterman
Reviewed-by: Albert Ou
---
include/uapi/linux/raw.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/uapi/linux/raw.h b/include/uapi/linux/raw.h
index 62d543e70
Now that we have introduced the bad_madt_entry() function, and that
function is being invoked in acpi_table_parse_madt() for us, there
is no longer any need to use the BAD_MADT_ENTRY macro.
Signed-off-by: Al Stone
Cc: Rafael J. Wysocki
Cc: Len Brown
Cc: Pavel Machek
Cc: Thomas Gleixner
Cc: In
Now that we have introduced to bad_madt_entry(), and we have removed
all the usages of the BAD_MADT_ENTRY macro from all of the various
architectures that use it (arm64, ia64, x86), we can remove the macro
definition since it is no longer used.
Signed-off-by: Al Stone
Cc: Rafael J. Wysocki
Cc: L
Andi,
Andi Kleen [a...@firstfloor.org] wrote:
| From: Andi Kleen
|
| [This patch is on top of Sukadev's json patchkit]
I removed this line from the commit log...
|
| The JSON event lists use a different encoding for fixed counters
| than perf for instructions and cycles (ref-cycles is ok)
|
Now that we have introduced the bad_madt_entry() function, and that
function is being invoked in acpi_table_parse_madt() for us, there
is no longer any need to use the BAD_MADT_ENTRY macro.
Signed-off-by: Al Stone
Cc: Tony Luck
Cc: Fenghua Yu
---
arch/ia64/kernel/acpi.c | 20 --
Currently, the BAD_MADT_ENTRY macro is used to do a very simple sanity
check on the various subtables that are defined for the MADT. The check
compares the size of the subtable data structure as defined by ACPICA to
the length entry in the subtable. If they are not the same, the assumption
is tha
I recently got bit by a CONFIG_ in userspace bug. This has apparently
happened before, but the check got disabled for triggering too much.
In order to reduce false positives, I added some hueristics to avoid
detecting comments.
Since these tests all pass, I've now re-enabled them.
Signed-off-by:
I'm not sure what this is, but it doesn't feel like something that
should be exposed to userspace here. I'm assuming this file was
exposed for the structure in it, which doesn't depend on
MAX_SHARED_LIBS.
Signed-off-by: Palmer Dabbelt
Reviewed-by: Andrew Waterman
Reviewed-by: Albert Ou
---
in
I'm actually not sure what to do here: if this enum is meant to be
used by userspace, then it has to be the same regardless of kernel
configuration. One option would be to have the kernel expose all the
values to userspace and then map them internally if
CONFIG_HAVE_MIXED_BREAKPOINT_REGS isn't set
When working on the RISC-V port I noticed that F_SETLK64 was being
defined on our 64-bit platform, despite our port being so new that
we've only ever had the 64-bit file ops. Since there's not compat
layer for these, this causes fcntl to bail out.
It turns out that one of the ways in with F_SETLK
Nothing else in the kernel defines this, and this header is visible to
userspace. Rather than hiding it in an #ifdef, I think it's sane to
just make this visible to userspace.
Signed-off-by: Palmer Dabbelt
Reviewed-by: Andrew Waterman
Reviewed-by: Albert Ou
---
include/uapi/linux/fb.h | 3 ---
I cut the RISC-V stuff, but I intend to reply to it later. As you
said, it's just a different topic.
>>> However, I did see a lot of similar bugs now that you point me to it:
>>>
>>> $ grep -r \\\>> obj-tmp/usr/include/asm-generic/fcntl.h:#ifndef CONFIG_64BIT
>>> obj-tmp/usr/include/asm-generic/
Em Mon, Sep 07, 2015 at 10:38:06AM +0200, Jiri Olsa escreveu:
> Propagate error info from tp_format via ERR_PTR to get
> it all the way down to the parse-event.c tracepoint adding
> routines. Following functions now return pointer with
> encoded error:
> - tp_format
> - trace_event__tp_format
>
From: Sergei Trofimovich
Noticed by gcc-5.2.0:
net/mac80211/rate.c: In function 'rate_control_cap_mask':
net/mac80211/rate.c:719:25: warning: 'sizeof' on array function parameter
'mcs_mask' will return size of 'u8 * {aka unsigned char *}'
[-Wsizeof-array-argument]
for (i = 0; i
On 9/9/2015 4:28 PM, Greg KH wrote:
> On Wed, Sep 09, 2015 at 04:16:49PM -0400, Michael J Coss wrote:
>> On 9/9/2015 4:09 PM, Greg KH wrote:
>>> On Wed, Sep 09, 2015 at 03:05:29PM -0400, Michael J Coss wrote:
On 9/8/2015 11:54 PM, Greg KH wrote:
> On Tue, Sep 08, 2015 at 10:10:27PM -0400,
On Wed, Sep 9, 2015 at 1:08 PM, Arnd Bergmann wrote:
> On Wednesday 09 September 2015 12:30:27 Kees Cook wrote:
>> The syscall ABI is inconsistent on aarch64 compat, so at least we should
>> document it in the seccomp_bpf tests.
>>
>> Signed-off-by: Kees Cook
>
> Can you explain in what way the A
On Monday, September 07, 2015 12:58:18 PM Richard Guy Briggs wrote:
> On 15/09/07, Richard Guy Briggs wrote:
> > Nothing prevents a new auditd starting up and replacing a valid
> > audit_pid when an old auditd is still running, effectively starving out
> > the old auditd since audit_pid no longer p
On Wed, 2015-09-09 at 11:17 +0200, Baptiste Reynal wrote:
> From: Antonios Motakis
>
> Certain properties of a device are accessible as an array of unsigned
> integers, either u64, u32, u16, or u8. Let the VFIO user query this
> type of device properties.
>
> Signed-off-by: Antonios Motakis
> S
On Wed, 2015-09-09 at 11:17 +0200, Baptiste Reynal wrote:
> From: Antonios Motakis
>
> Certain device properties (e.g. the device node name, the compatible
> string), are available as a list of strings (separated by the null
> terminating character). Let the VFIO user query this type of propertie
On Wed, 2015-09-09 at 11:17 +0200, Baptiste Reynal wrote:
> From: Antonios Motakis
>
> This patch introduces an API that allows to return device properties (OF
> or ACPI) of a device bound to the vfio-platform/vfio-amba driver and the
> skeleton of the implementation for VFIO_PLATFORM. Informatio
On Monday, September 07, 2015 05:10:13 AM Richard Guy Briggs wrote:
> There are several reports of the kernel losing contact with auditd when
> it is, in fact, still running. When this happens, kernel syslogs show:
> "audit: *NO* daemon at audit_pid="
> although auditd is still running, and
On Wed, Sep 09, 2015 at 04:16:49PM -0400, Michael J Coss wrote:
> On 9/9/2015 4:09 PM, Greg KH wrote:
> > On Wed, Sep 09, 2015 at 03:05:29PM -0400, Michael J Coss wrote:
> >> On 9/8/2015 11:54 PM, Greg KH wrote:
> >>> On Tue, Sep 08, 2015 at 10:10:27PM -0400, Michael J. Coss wrote:
> Currently
Corinna Vinschen :
[...]
> diff --git a/drivers/net/ethernet/realtek/r8169.c
> b/drivers/net/ethernet/realtek/r8169.c
> index 24dcbe6..630811a 100644
> --- a/drivers/net/ethernet/realtek/r8169.c
> +++ b/drivers/net/ethernet/realtek/r8169.c
[...]
> + if (!paddr)
> + return false;
On Wednesday 09 September 2015 17:44:54 Jon Hunter wrote:
>
> On 09/09/15 16:56, Arnd Bergmann wrote:
> > On Wednesday 09 September 2015 16:06:01 Jon Hunter wrote:
> >> +
> >> + idata = kcalloc(mcci.num_of_cmds, sizeof(*idata), GFP_KERNEL);
> >> + if (!idata) {
> >> + err
On Wednesday, September 09, 2015 03:47:27 PM Lukasz Anaczkowski wrote:
> This series of patches attempts to fix how CPUs are enumerated by kernel when
> there's more than 255 of them on single processor.
> In such case, BIOS may interleave APIC/X2APIC MADT subtables, to obey
> requirements
> speci
Hi Linus,
Please pull from 'master' branch of
git://www.linux-watchdog.org/linux-watchdog.git
It contains:
* New driver for NXP LPC18xx Watchdog Timer
* New driver for SAMA5D4 watchdog timer
* (nv_tco) add support for MCP79
* Clean-up and improvement of the mpc8xxx watchdog driver
* Impro
On 9/9/2015 4:09 PM, Greg KH wrote:
> On Wed, Sep 09, 2015 at 03:05:29PM -0400, Michael J Coss wrote:
>> On 9/8/2015 11:54 PM, Greg KH wrote:
>>> On Tue, Sep 08, 2015 at 10:10:27PM -0400, Michael J. Coss wrote:
Currently when a uevent occurs, the event is replicated and sent to every
list
On Wed, Sep 9, 2015 at 1:35 PM, Rafael J. Wysocki wrote:
>
> On Wednesday, September 09, 2015 11:20:25 AM Alan Stern wrote:
> > On Wed, 9 Sep 2015, Rafael J. Wysocki wrote:
> >
> > > > The best example and actually the very specific problem we want to
> > > > solve is handling touchscreens on a ph
Hi Patrick,
On 09/03/2015 02:18 AM, Patrick Bellasi wrote:
> In my view, one of the main goals of sched-DVFS is actually that to be
> a solid and generic replacement of different CPUFreq governors.
> Being driven by the scheduler, sched-DVFS can exploit information on
> CPU demand of active tasks
On Wednesday, September 09, 2015 07:16:49 PM Suthikulpanit, Suravee wrote:
> Hi All,
>
> Are there any other concerns about this patch series?
I have none, but then it sort of missed the merge window.
I can easily queue it up for the next one unless it is super-urgent,
but in that case I need to
On Wed, Sep 09, 2015 at 03:24:12PM -0400, Michael J Coss wrote:
> On 9/8/2015 11:55 PM, Greg KH wrote:
> > On Tue, Sep 08, 2015 at 10:10:29PM -0400, Michael J. Coss wrote:
> >> Adds capability to allow userspace programs to forward a given event to
> >> a specific network namespace as determined by
On Wednesday 09 September 2015 12:30:27 Kees Cook wrote:
> The syscall ABI is inconsistent on aarch64 compat, so at least we should
> document it in the seccomp_bpf tests.
>
> Signed-off-by: Kees Cook
Can you explain in what way the ABI is inconsistent here?
> ---
> Can someone with access to n
On Wed, Sep 09, 2015 at 03:05:29PM -0400, Michael J Coss wrote:
> On 9/8/2015 11:54 PM, Greg KH wrote:
> > On Tue, Sep 08, 2015 at 10:10:27PM -0400, Michael J. Coss wrote:
> >> Currently when a uevent occurs, the event is replicated and sent to every
> >> listener on the kernel netlink socket, igno
On Wednesday, September 09, 2015 11:20:25 AM Alan Stern wrote:
> On Wed, 9 Sep 2015, Rafael J. Wysocki wrote:
>
> > > The best example and actually the very specific problem we want to
> > > solve is handling touchscreens on a phone / tablet. When the screen is
> > > turned off, it is ideal to sus
On Wed, Sep 09, 2015 at 11:03:20PM +0300, Mike Rapoport wrote:
> On Wed, Sep 09, 2015 at 11:41:20AM -0700, Greg Kroah-Hartman wrote:
> > On Sun, Sep 06, 2015 at 09:17:56AM +0300, Mike Rapoport wrote:
> > > Fix the checkpatch warning about CamelCase.
> > >
> > > Signed-off-by: Mike Rapoport
> > >
On Wed, Sep 09, 2015 at 11:41:20AM -0700, Greg Kroah-Hartman wrote:
> On Sun, Sep 06, 2015 at 09:17:56AM +0300, Mike Rapoport wrote:
> > Fix the checkpatch warning about CamelCase.
> >
> > Signed-off-by: Mike Rapoport
> > ---
> > drivers/staging/sm750fb/ddk750_sii164.c | 2 +-
> > drivers/stagin
On 09/07/2015 09:32 AM, Sudeep Holla wrote:
> Hi Al,
>
> On 19/08/15 23:07, Al Stone wrote:
>
> I finally got a chance to try this series on Juno. Well it exposed a firmware
> bug in MADT table :)
>
> [..]
>
>> acpi_tbl_entry_handler handler,
>> @@ -245,6 +484,8 @@ acpi_parse_e
On Wednesday, September 09, 2015 06:02:02 PM Octavian Purdila wrote:
> On Wed, Sep 9, 2015 at 4:55 PM, Oliver Neukum wrote:
> > On Wed, 2015-09-09 at 14:22 +0200, Rafael J. Wysocki wrote:
> >> > Note that when the screen is turned-on again, we want to resume the
> >> > touchscreen so that it can s
From: Arnaldo Carvalho de Melo
Out of the code to write the cpu topology map in the perf.data file
header.
Now if one needs the CPU topology map for the running machine, one needs
to call perf_env__read_cpu_topology_map(perf_env) and the info will be
stored in perf_env.cpu.
For now we're using
From: Arnaldo Carvalho de Melo
Move this from two globals to perf_env global, that eventually will
be just perf_header->env or something else, to ease the refactoring
series, leave it as a global and go on reading more of its fields,
not as part of the header writing process but as a perf_env ini
From: Arnaldo Carvalho de Melo
As al.cpu may be -1, i.e. no PERF_SAMPLE_CPU, and env->cpu may be NULL.
Rely instead on the work now done in perf_event__preprocess_sample(),
that does all those checks.
Reported-by: Wang Nan
Based-on-a-patch-by: Jiri Olsa
Cc: Adrian Hunter
Cc: Borislav Petkov
On Sun, Sep 06, 2015 at 09:17:52AM +0300, Mike Rapoport wrote:
> Fix the checkpatch warning about CamelCase
>
> Signed-off-by: Mike Rapoport
> ---
> drivers/staging/sm750fb/ddk750_hwi2c.c | 2 +-
> drivers/staging/sm750fb/ddk750_hwi2c.h | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
On Sat, Sep 05, 2015 at 07:13:45PM +0530, Sudip Mukherjee wrote:
> Instead of defining DRVNAME and using it in all calls to pr_* family of
> macros lets start using pr_fmt.
>
> Signed-off-by: Sudip Mukherjee
> ---
> drivers/staging/fbtft/fbtft_device.c | 79
> ---
On Sun, Sep 06, 2015 at 09:17:51AM +0300, Mike Rapoport wrote:
> Fix the checkpatch warning about CamelCase
>
> Signed-off-by: Mike Rapoport
> ---
> drivers/staging/sm750fb/ddk750_hwi2c.c | 2 +-
> drivers/staging/sm750fb/ddk750_hwi2c.h | 2 +-
> drivers/staging/sm750fb/ddk750_sii164.c | 2 +-
On Fri, Sep 04, 2015 at 06:53:18PM +0530, Sudip Mukherjee wrote:
> These variables were only assigned some values but they were never used.
>
> Signed-off-by: Sudip Mukherjee
> ---
> drivers/staging/slicoss/slicoss.c | 27 ++-
> 1 file changed, 6 insertions(+), 21 deletio
On Sun, Sep 06, 2015 at 09:17:53AM +0300, Mike Rapoport wrote:
> Fix the checkpatch warning about CamelCase
>
> Signed-off-by: Mike Rapoport
> ---
> drivers/staging/sm750fb/ddk750_hwi2c.c | 2 +-
> drivers/staging/sm750fb/ddk750_hwi2c.h | 2 +-
> drivers/staging/sm750fb/ddk750_sii164.c | 2 +-
Hi,
Please take a look at these changes to fix the problems reported by
Wang Nan wrt accesses to the cpu_topology_map information.
The fixes are present on these following two csets:
perf event: Use machine->env to find the cpu -> socket mapping
perf report: Do not blindly us
201 - 300 of 713 matches
Mail list logo
