This patch creates maps based on 'map' section in object file using
bpf_create_map(), and store the fds into an array in 'struct bpf_obj'.
Signed-off-by: Wang Nan
---
tools/perf/util/bpf-loader.c | 53
tools/perf/util/bpf-loader.h | 2 ++
2 files
Copy print_bpf_insn() from kernel/bpf/verifier.c to bpf.c, dump the
program if called by -vv.
Signed-off-by: Wang Nan
---
tools/perf/util/bpf-loader.c | 14 +++-
tools/perf/util/bpf.c| 156 +++
tools/perf/util/bpf.h| 1 +
3 files
This patch does the final work whcih makes eBPF program actually work.
It introduces bpf_attach(), which first retrive id field of previous
created k(ret)probe events, then use PERF_EVENT_IOC_SET_BPF to attach
eBPF program to the events.
Signed-off-by: Wang Nan
---
tools/perf/util/bpf-loader.c
On Wednesday, April 29, 2015 8:50:57 PM PDT, Mike Galbraith wrote:
On Wed, 2015-04-29 at 13:40 -0700, Daniel Phillips wrote:
That order of magnitude latency difference is striking. It sounds
good, but what does it mean? I see a smaller difference here, maybe
because of running under KVM.
If an eBPF program access a map, LLVM generates a relocated load
instruction. To enable the usage of that map, relocation must be done
by replacing original instructions by map loading instructions.
This patch do that work by utilizing previous stored relocation section
information in 'struct
This patch use bpf system call to load all eBPF programs into kernel.
Their fds are stored into prog_fd field in 'struct bpf_perf_prog'.
Signed-off-by: Wang Nan
---
tools/perf/util/bpf-loader.c | 58
tools/perf/util/bpf-loader.h | 3 +++
2 files
eBPF programs are allowed to include 'config' sections, which contain
strings describe each bpf program. Config strings have identical format
as 'perf probe' defined. They describe positions and arguments used by
bpf programs.
Defining config strings separatly is allowed. For example:
#define
Code and format roughly based on Xen's vmcs_dump_vcpu.
Signed-off-by: Paolo Bonzini
---
arch/x86/kvm/vmx.c | 153 +
1 file changed, 153 insertions(+)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 31a76ab38267..a0f5952ed0e9 100644
On Tue, Apr 28, 2015 at 05:38:52PM -0700, Feng Kan wrote:
> Using the glibc cortex string work work authored by Linaro as base to
> create new copy to/from user kernel routine.
>
> Iperf performance increase:
> -l (size) 1 core result
> Optimized 64B
To speed up paravirtualized spinlock handling when running on bare
metal introduce a new pvops function "spin_unlock". This is a simple
add instruction (possibly with lock prefix) when the kernel is running
on bare metal.
As the patched instruction includes a lock prefix in some
configurations
The decision whether the slowpath flag is to be cleared for
paravirtualized spinlocks is located in
__ticket_check_and_clear_slowpath() today.
Move that decision into arch_spin_lock() and add an unlikely attribute
to it to avoid calling a function in case the compiler chooses not to
inline
To speed up paravirtualized spinlock handling when running on bare
metal introduce a new pvops function "clear_slowpath". This is a nop
when the kernel is running on bare metal.
As the clear_slowpath function is common for all users add a new
initialization function to set the pvops function
There is no need any more for a special treatment of _raw_spin_unlock()
regarding inlining compared to the other spinlock functions. Just treat
it like all the other spinlock functions.
Remove selecting UNINLINE_SPIN_UNLOCK in case of PARAVIRT_SPINLOCKS.
Signed-off-by: Juergen Gross
---
---
tools/perf/util/bpf-loader.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/tools/perf/util/bpf-loader.c b/tools/perf/util/bpf-loader.c
index 208f5e8..186a3d0 100644
--- a/tools/perf/util/bpf-loader.c
+++ b/tools/perf/util/bpf-loader.c
@@ -952,8 +952,26 @@ out:
On 13/04/15 13:41, Will Deacon wrote:
On Thu, Apr 09, 2015 at 04:36:29PM +0100, Mark Rutland wrote:
On Thu, Apr 09, 2015 at 03:57:05PM +0100, Mark Salter wrote:
Currently in validate_group(), there is a static initializer
for fake_pmu.used_mask which is based on CPU_BITS_NONE but
the used_mask
Paravirtualized spinlocks produce some overhead even if the kernel is
running on bare metal. The main reason are the more complex locking
and unlocking functions. Especially unlocking is no longer just one
instruction but so complex that it is no longer inlined.
This patch series addresses this
[cc linux-kernel]
On Thu, Apr 30, 2015 at 1:53 PM, Alexey Dobriyan wrote:
>> By default I used destination type as a reference. Maybe it's wrong and
>> we really want to read long, unsigned long from source ?
>
> long and unsigned long -- no. Always look at type of data.
> There are many places
With the paravirtualized spinlock unlock function being a pvops
function paravirt_ticketlocks_enabled is no longer needed. Remove it.
Signed-off-by: Juergen Gross
---
arch/x86/include/asm/spinlock.h | 3 ---
arch/x86/kernel/kvm.c| 14 --
For paravirtualized spinlocks setting the "slowpath" flag in
__ticket_enter_slowpath() is done via setting bit "0" in
lock->tickets.head instead of using a macro.
Change this by defining an appropriate macro.
Signed-off-by: Juergen Gross
---
arch/x86/include/asm/spinlock.h | 3 ++-
> > Obviously my patch isn't the real solution, the real solution is to
> > make the new function calls use a consistent 64-bit type, or figure
> > out what in my code path is calling these functions and check it for
> > value sanity.
I would be tempted to do both computations and print then
If maps are used by eBPF programs, corresponding object file(s) should
contain a section named 'map'. Which contains map definitions, one for
each map to describe its format. 'struct perf_bpf_map_def' is
introduced as part of protocol between perf and eBPF programs. All map
definitions are copied
Check endianess according to EHDR to support loading eBPF objects into
big endian machines. Code is taken from util/symbol-elf.c.
Signed-off-by: Wang Nan
---
tools/perf/util/bpf-loader.c | 28
tools/perf/util/bpf-loader.h | 1 +
2 files changed, 29 insertions(+)
Expand bpf_obj_elf_collect() to let it collect license and kernel
version information in eBPF object files. eBPF object file should have
a section named 'license', which contains a string. It should also
have a section named 'version', contains a u32 LINUX_VERSION_CODE.
bpf_obj_validate() is
Shell script allowing to find errno definitions and descriptions in the
kernel source.
Signed-off-by: Bartosz Golaszewski
---
This is a simple script I use when seeing messages like:
some_func() failed: -123
to find out the actual errno meaning. The usage is very simple - just
call
The util-linux release v2.26.2 is available at
ftp://ftp.kernel.org/pub/linux/utils/util-linux/v2.26/
Feedback and bug reports, as always, are welcomed.
Karel
util-linux 2.26.2 Release Notes
===
blockdev:
- fix whole-disk start sector usage
On Thursday 30 April 2015 11:41:02 Will Deacon wrote:
> Hi Arnd,
>
> On Thu, Apr 30, 2015 at 09:23:59AM +0100, Arnd Bergmann wrote:
> > On Wednesday 29 April 2015 16:53:10 Suravee Suthikulpanit wrote:
> > > As for the case where _CCA=0, I think the ACPI driver should essentially
> > >
The ARM Dual-Timer SP804 module is peripheral found not only on ARM32
platforms but also on ARM64 platforms.
This patch moves the driver out of arch/arm to driver/clocksource
so that it can be used on ARM64 platforms also.
Signed-off-by: Sudeep Holla
Cc: Russell King
Cc: Daniel Lezcano
Cc:
The header asm/hardware/arm_timer.h is included in various machine
specific files to access TIMER_CTRL and initialise to a known state.
However that's not required as the clock{source,event} driver timer-sp
initialises all the timer being used.
This patch removes the redundant code in timer_init
Since there are ARM64 platforms(e.g. Juno) with SP804 timers, we need
to move the driver out of arch/arm so that the code can be shared.
Regards,
Sudeep
Sudeep Holla (2):
ARM: simplify timer initialisation and remove arm_timer.h inclusion
ARM: move Dual-Timer SP804 driver to
Hi Arnd,
On Thu, Apr 30, 2015 at 09:23:59AM +0100, Arnd Bergmann wrote:
> On Wednesday 29 April 2015 16:53:10 Suravee Suthikulpanit wrote:
> > As for the case where _CCA=0, I think the ACPI driver should essentially
> > communicate the information as HW is non-coherent as described in the
> >
Am 30.04.2015 um 12:19 schrieb Łukasz Stelmach:
> It was <2015-04-30 czw 11:12>, when Richard Weinberger wrote:
>> Am 30.04.2015 um 11:05 schrieb Łukasz Stelmach:
>>> Regardless, of initrd issues I feel there is a need of a local IPC
>>> that is more capable than UDS. Linus Torvalds is probably
> > +struct bus_type ulpi_bus = {
>
> non-static and undeclared anywhere, adds a sparse error. I'm dropping
> the series for now :-)
>
> "
> drivers/usb/common/ulpi.c:77:17: warning: symbol 'ulpi_bus' was not
> declared. Should it be static?
> "
Need to fix that. I'll wait for your comment's to
On 28 April 2015 at 20:41, Jean Delvare wrote:
> From: Jean Delvare
> Subject: firmware: dmi_scan: Only honor end-of-table for 64-bit tables
>
> A 32-bit entry point to a DMI table says how many structures the table
> contains. The SMBIOS specification explicitly says that end-of-table
> markers
In set_node_addr, we try to lookup cached nat entry of inode and then
set flag in it.
But previously in this function, we have already grabbed nat entry with
current node id, if the node id is the same as the one of inode, we
do not need to lookup it in cache again.
So this patch adds condition
Remove f2fs_make_empty() declaration, since the main body of this function
is move into do_make_empty_dir() and the function is obsolete now.
Signed-off-by: Chao Yu
---
fs/f2fs/f2fs.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
index 8be6cab..ff1014b
Hi Felipe,
> > + case DWC3_GHWPARAMS3_HSPHY_IFC_ULPI:
> > + /* Soft reset here to sync the clocks */
> > + ret = dwc3_soft_reset(dwc);
>
> you just lost all DWC3_GUSB3PIPECTL(0) and DWC3_GUSB2PHYCFG(0)
> configurations which happened right before this switch. Essentially
>
> > -static void dwc3_phy_setup(struct dwc3 *dwc)
> > +static int dwc3_phy_setup(struct dwc3 *dwc)
> > {
> > u32 reg;
> > + int ret;
>
> unused variable
true,
--
heikki
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Thu, 30 Apr 2015 10:48:09 +0300
Eyal Reizer wrote:
> tty_hci driver exposes a /dev/hci_tty character device node, that intends
> to emulate a generic /dev/ttyX device that would be used by the user-space
> Bluetooth stacks to send/receive data to/from the WL combo-connectivity
> chipsets.
We
On Wednesday, April 29, 2015 6:46:16 PM PDT, Dave Chinner wrote:
I measured fsync performance using a 7200 RPM disk as a virtual
drive under KVM, configured with cache=none so that asynchronous
writes are cached and synchronous writes translate into direct
writes to the block device.
Yup, a
It was <2015-04-30 czw 11:12>, when Richard Weinberger wrote:
> Am 30.04.2015 um 11:05 schrieb Łukasz Stelmach:
>> Regardless, of initrd issues I feel there is a need of a local IPC
>> that is more capable than UDS. Linus Torvalds is probably right that
>> dbus-daemon is everything but effictient.
On Wed, Apr 29, 2015 at 02:44:06PM -0700, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez"
>
> ioremap_nocache() currently uses UC- by default.
> Our goal is to eventually make UC the default.
> Linux maps UC- to PCD=1, PWT=0 page attributes on
> non-PAT systems. Linux maps UC to PCD=1,
On Thu, 30 Apr 2015, Inha Song wrote:
> This patch add support for select accessory detect mode to HPDETL or HPDETR.
> Arizona provides a headphone detection circuit on the HPDETL and HPDETR pins
> to measure the impedance of an external load connected to the headphone.
>
> Depending on board
Hi Inha,
On 04/30/2015 10:37 AM, Inha Song wrote:
> This patch add support for select accessory detect mode to HPDETL or HPDETR.
> Arizona provides a headphone detection circuit on the HPDETL and HPDETR pins
> to measure the impedance of an external load connected to the headphone.
>
> Depending
ill make a hole of len bytes at offset."
This patch implements fallocate's FALLOC_FL_ZERO_RANGE for f2fs.
Signed-off-by: Chao Yu
---
v2:
* rebase to last git repository of f2fs (20150430)
fs/f2fs/file.c | 106 -
1 file changed, 105 ins
On Wednesday, April 29, 2015 at 05:36:32 PM, Gabriele Mazzotta wrote:
[...]
> > > I'm sorry, I've just noticed that I haven't changed the value of
> > > realbits in acpi_als_channels. This makes me wonder what would be the
> > > proper value, given that this is a generic driver and all the
> > >
in case of xfs and ext4.
4) Collaspe range does not work beyond i_size."
This patch implements fallocate's FALLOC_FL_COLLAPSE_RANGE for f2fs.
Signed-off-by: Chao Yu
---
v2:
* rebase to last git repository of f2fs (20150430)
* remove replace_block() introduction.
Introduce a generic function replace_block base on recover_data_page,
and export it. So wit it we can operate file's meta data which is in
CP/SSA area when we invoke fallocate with FALLOC_FL_COLLAPSE_RANGE flag.
Signed-off-by: Chao Yu
---
fs/f2fs/f2fs.h | 4 ++--
fs/f2fs/recovery.c | 2 +-
On Wed, Apr 29, 2015 at 01:21:46PM -0400, Rhyland Klein wrote:
> From: Bill Huang
>
> Add logic which (if specified for a pll) can verify that a PLL is set
> to the proper default value and if not can set it. This can be
> specified per PLL as each will have different default values.
>
Why
On Wed, Apr 29, 2015 at 01:21:43PM -0400, Rhyland Klein wrote:
> Tegra210 SoC's have 2 PLLS for memory usage. Add plumbing to register
> and handle PLLMB.
>
Seems my comments to v1 never made it to the list :/ trying again:
I think this would be better rephrased as:
'Tegra210 SoC's have 2 PLLs
On Thu, 30 Apr 2015, Inha Song wrote:
> This patch add device tree bindings for the pdata needed to configure
> the Accessory Detect Mode select when Headphone detection.
>
> Signed-off-by: Inha Song
> ---
> Documentation/devicetree/bindings/mfd/arizona.txt | 6 ++
> 1 file changed, 6
On Thu, 30 Apr 2015, Charles Keepax wrote:
> On the wm5110 it is important the reset line is held for slightly longer
> to ensure the device starts up well. This patch adds a 5mS delay for
> this.
>
> Signed-off-by: Charles Keepax
> ---
> drivers/mfd/arizona-core.c | 10 ++
> 1 files
Minor spell fix, s/intialised/initialised.
Signed-off-by: Viresh Kumar
---
Documentation/devicetree/bindings/regulator/regulator.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/regulator/regulator.txt
Let's group some values together. This avoids a too detailed
histogram. Some sort of logarythmic scale could be useful
for latency plots.
Now we can write something like:
'hist:key=latency.bucket:val=hitcount:sort=latency'
latency: 0 hitcount: 166440
latency:256 hitcount:
From: Tom Zanussi
Hi Daniel,
On Mon, 2015-04-20 at 14:52 +0200, Daniel Wagner wrote:
> Hi Tom,
>
> On 04/10/2015 06:05 PM, Tom Zanussi wrote:
> > This is v4 of the 'hist triggers' patchset, following feedback from
> > v3.
> >
> > This version fixes the race in tracing_map_insert() noted in v3,
The hist patch allows sorting on values only. By allowing to
sort also on the key we can do something like this:
'hist:key=latency:val=hitcount:sort=latency'
latency: 16 hitcount: 3
latency: 17 hitcount:171
latency: 18 hitcount:626
latency:
Finally we place a few tracepoint at the end of critical section. With
the hist trigger in place we can generate the plots.
There are a few drawbacks compared to the latency_hist.patch [1]
The latency plots contain the values from all CPUs. In theory you
can also filter with something like
The tracepoint can't be used in code section where we are in the
middle of a state transition.
For example if we place a tracepoint inside start/stop_critical_section(),
lockdep complains with
[0.035589] WARNING: CPU: 0 PID: 3 at kernel/locking/lockdep.c:3560
On Wed, 29 Apr 2015, Andrew Bresticker wrote:
> On Wed, Apr 29, 2015 at 11:34 AM, Lee Jones wrote:
> > On Wed, 29 Apr 2015, Andrew Bresticker wrote:
> >
> >> Lee,
> >>
> >> On Wed, Apr 29, 2015 at 2:25 AM, Lee Jones wrote:
> >> > On Mon, 27 Apr 2015, Andrew Bresticker wrote:
> >> >
> >> >> Add
Hi,
I would like to discuss a possible way of getting the feature of the
latecy_hist.patch [1] added to mainline.
"Latency histograms are primarily relevant in the context of real-time
enabled kernels (CONFIG_PREEMPT/CONFIG_PREEMPT_RT)and are used in the
quality management of the Linux real-time
The former duplicates the functionality of the latter but is neither
documented nor arch-independent.
Signed-off-by: Bartosz Golaszewski
---
drivers/hwmon/coretemp.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/hwmon/coretemp.c b/drivers/hwmon/coretemp.c
index
The former duplicates the functionality of the latter but is neither
documented nor arch-independent.
Signed-off-by: Bartosz Golaszewski
---
drivers/cpufreq/powernow-k8.c | 13 +++--
1 file changed, 3 insertions(+), 10 deletions(-)
diff --git a/drivers/cpufreq/powernow-k8.c
The former duplicate the functionalities of the latter but are neither
documented nor arch-independent.
Signed-off-by: Bartosz Golaszewski
---
drivers/cpufreq/acpi-cpufreq.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/cpufreq/acpi-cpufreq.c
These functions are arch-specific and duplicate the functionality
of macros defined in linux/include/topology.h.
Remove them as all the callers in x86 have now switched to using
the topology_**_cpumask() family.
Signed-off-by: Bartosz Golaszewski
---
arch/x86/include/asm/smp.h | 10 --
The former duplicate the functionalities of the latter but are neither
documented nor arch-independent.
Signed-off-by: Bartosz Golaszewski
---
arch/x86/kernel/cpu/proc.c | 5 +++--
arch/x86/kernel/smpboot.c | 40
arch/x86/kernel/tsc_sync.c | 3 +--
3
The former duplicates the functionality of the latter but is neither
documented nor arch-independent.
Signed-off-by: Bartosz Golaszewski
---
drivers/cpufreq/p4-clockmod.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/p4-clockmod.c
Two functions defined in asm/smp.h: cpu_sibling_mask() and cpu_core_mask(),
have the same functionality as macros defined in linux/topology.h:
topology_thread_cpumask() and topology_core_cpumask() respectively.
They are not documented and are architecture specific. Also: different
naming for the
On Thu, Apr 30, 2015 at 7:04 AM, Marcel Holtmann wrote:
> Hi Laura,
>
We've received a number of reports of warnings when coming
out of suspend with certain bluetooth firmware configurations:
WARNING: CPU: 3 PID: 3280 at drivers/base/firmware_class.c:1126
This patch adds functions for enabling and disabling the physical reset
line. This will be helpful in future refactoring.
Signed-off-by: Charles Keepax
Acked-by: Lee Jones
---
drivers/mfd/arizona-core.c | 25 +
1 files changed, 17 insertions(+), 8 deletions(-)
diff
The wm5102 uses a custom boot sequence and the standard boot sequence is
disabled. However, the standard boot sequence must be run at least once
after a cold boot (caused by either a hard reset or removal of AVDD).
Unfortunately the register WRITE_SEQUENCER_CTRL_3 is not affected by the
hardware
wm5102 applies a custom hardware boot sequence, for this the SYSCLK
needs to be enabled. This patch factors out the code that enables
SYSCLK for this sequence such that it can be used for other boot time
operations that require SYSCLK.
Signed-off-by: Charles Keepax
Acked-by: Lee Jones
---
Ok so I have completed the rework to the second of the two patch
chains on this and pulled them back together into one series.
Note the main difference is I have pulled a couple patches from
the second series to the start of the chain. This is because of
patch 3 which is a bug fix for 5102 I have
This also handily fixes a leak of the GPIO in arizona_dev_exit.
Signed-off-by: Charles Keepax
Acked-by: Lee Jones
---
drivers/mfd/arizona-core.c | 10 --
1 files changed, 4 insertions(+), 6 deletions(-)
diff --git a/drivers/mfd/arizona-core.c b/drivers/mfd/arizona-core.c
index
In preparation for some refactoring fixup some minor style, formating
and code clarity issues.
Signed-off-by: Charles Keepax
Acked-by: Lee Jones
---
drivers/mfd/arizona-core.c | 37 +
1 files changed, 17 insertions(+), 20 deletions(-)
diff --git
This patch adds support for the 1.175V mode on the LDO1 regulator on the
wm5110. This is need as part of the low power sleep mode operation.
Signed-off-by: Charles Keepax
Acked-by: Mark Brown
---
drivers/regulator/arizona-ldo1.c | 15 +++
1 files changed, 15 insertions(+), 0
The low power sleep mode on wm5110 requires that the LDO1 regulator be
set to 1.175V prior to entering sleep, then returned to 1.2V after
exiting sleep mode. This patch apply these regulator settings.
Signed-off-by: Charles Keepax
Acked-by: Mark Brown
Acked-by: Lee Jones
---
On Wed, 29 Apr 2015, Maxime Ripard wrote:
> On Wed, Apr 29, 2015 at 03:17:51PM +0100, Lee Jones wrote:
> > On Wed, 22 Apr 2015, Maxime Ripard wrote:
> >
> > > On Wed, Apr 08, 2015 at 06:23:44PM +0100, Lee Jones wrote:
> > > > On Wed, 08 Apr 2015, Maxime Ripard wrote:
> > > >
> > > > > On Wed,
Cleanup commit 73679e508201 ("compiler-intel.h: Remove duplicate
definition") removed the double definition of __memory_barrier()
intrinsics.
However, in doing so, it also removed the preceding #undef barrier
by accident, meaning, the actual barrier() macro from compiler-gcc.h
with inline asm is
On 04/30/2015 02:37 PM, David Gibson wrote:
On Wed, Apr 29, 2015 at 07:44:20PM +1000, Alexey Kardashevskiy wrote:
On 04/29/2015 03:30 PM, David Gibson wrote:
On Sat, Apr 25, 2015 at 10:14:47PM +1000, Alexey Kardashevskiy wrote:
This extends iommu_table_group_ops by a set of callbacks to
On the wm5110 it is important the reset line is held for slightly longer
to ensure the device starts up well. This patch adds a 5mS delay for
this.
Signed-off-by: Charles Keepax
---
drivers/mfd/arizona-core.c | 10 ++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git
Allow the chip to completely power off if we enter runtime suspend and
there is no jack detection active. This is helpful for systems where
system suspend might remove the supplies to the CODEC, without informing
us. Note the powering off is done in runtime suspend rather than system
suspend,
Some register settings must be applied before the first time low power
sleep mode is entered on the wm5110 to ensure optimium performance.
These settings require SYSCLK to be enabled whilst they are being
applied. This patch applies the settings using the recently factored out
boot time SYSCLK
Hi Paul,
On Thu, Apr 23, 2015 at 01:07:33PM -0700, Paul E. McKenney wrote:
> diff --git a/arch/arm64/kernel/smp.c b/arch/arm64/kernel/smp.c
> index 328b8ce4b007..6dc727a6e73e 100644
> --- a/arch/arm64/kernel/smp.c
> +++ b/arch/arm64/kernel/smp.c
> @@ -252,15 +252,13 @@ static int
On 04/28/2015 12:12 AM, Andrea Arcangeli wrote:
> Hello,
>
> On Thu, Apr 23, 2015 at 09:29:07AM +0300, Pavel Emelyanov wrote:
>> So your proposal is to always report 16 bytes per PF from read() and
>> let userspace decide itself how to handle the result?
>
> Reading 16bytes for each userfault
Michal Hocko wrote:
> I mean we should eventually fail all the allocation types but GFP_NOFS
> is coming from _carefully_ handled code paths which is an easier starting
> point than a random code path in the kernel/drivers. So can we finally
> move at least in this direction?
I agree that all the
On 04/30/2015 05:22 PM, David Gibson wrote:
On Sat, Apr 25, 2015 at 10:14:55PM +1000, Alexey Kardashevskiy wrote:
At the moment only one group per container is supported.
POWER8 CPUs have more flexible design and allows naving 2 TCE tables per
IOMMU group so we can relax this limitation and
On Thu, Apr 30, 2015 at 10:37:58AM +0900, Inha Song wrote:
> This patch add device tree bindings for the pdata needed to configure
> the Accessory Detect Mode select when Headphone detection.
>
> Signed-off-by: Inha Song
> ---
Acked-by: Charles Keepax
Thanks,
Charles
--
To unsubscribe from
On Thu, Apr 30, 2015 at 10:37:57AM +0900, Inha Song wrote:
> This patch add support for select accessory detect mode to HPDETL or HPDETR.
> Arizona provides a headphone detection circuit on the HPDETL and HPDETR pins
> to measure the impedance of an external load connected to the headphone.
>
>
> -Original Message-
> From: James Bottomley [mailto:james.bottom...@hansenpartnership.com]
> Sent: Thursday, April 30, 2015 7:08 AM
> To: linux-...@vger.kernel.org
> Cc: Kweh, Hock Leong; LKML; Andy Lutomirski; Greg Kroah-Hartman; Peter
> Jones
> Subject: [RFC 0/3] Add capsule update
On Mon, Apr 27, 2015 at 09:13:38PM +0900, Chanwoo Choi wrote:
> This patch removes the setting of device name. Instead, extcon_dev_register()
> set the device name such as 'extcon[number]' naming method.
> - /sys/class/extcon/Headset Jack -> /sys/class/extcon/extcon[number]
>
> Cc: Charles Keepax
On Thu, 30 Apr 2015, Chanwoo Choi wrote:
> Hi Ram,
>
> This patch has still one minor issue on below comment.
> But I fix it and will apply it on extcon-next branch
> after discussing how to apply this patch with Lee Jones (MFD maintainer).
>
> Dear Lee,
> Do you want to send pull request after
On Thu, Apr 30, 2015 at 12:31:06AM +0900, Chanwoo Choi wrote:
> Hi Charles,
>
> On Tue, Apr 28, 2015 at 11:17 PM, Charles Keepax
> wrote:
> > On Mon, Apr 27, 2015 at 09:13:35PM +0900, Chanwoo Choi wrote:
> >> This patch modify the device name as extcon[X] for sysfs by using the
> >> 'extcon'
>
Hi,
On 29/04/15 19:54, Fabian Frederick wrote:
-Remove obsolete simple_str functions.
-Return error code when kstr failed.
-This patch also calls functions corresponding to destination type.
Basically it's an RFC because of the type mismatch all over the place.
ie code was doing simple_strtol
On Wed, 2015-04-29 at 10:49 -0600, Mathieu Poirier wrote:
> On 29 April 2015 at 06:20, Ivan T. Ivanov iva...@linaro.org> wrote:
> > +
> > + funnel@821000 {
> > + compatible = "arm,coresight-funnel", "arm,primecell";
> > + reg = <0x821000 0x1000>;
> > +
> > +
On Thu, 30 Apr 2015, Sascha Hauer wrote:
> Some clocks are so critical to the system that they must never be turned
> off unless explicitly requested. Normally unused clocks get disabled in
> the clk_disable_unused initcall. Currently there are two ways for
> keeping clocks enabled even if they
On 04/28/2015 06:16 PM, Lai Jiangshan wrote:
> On 04/28/2015 11:49 AM, Tejun Heo wrote:
>> Hello,
>>
>> On Tue, Apr 28, 2015 at 10:24:31AM +0800, Lai Jiangshan wrote:
> Wouldn't this make a lot more sense above when copying @attrs into
> @new_attrs? The comment there even says "make a
> -Original Message-
> From: Andy Lutomirski [mailto:l...@amacapital.net]
> Sent: Thursday, April 30, 2015 2:41 AM
>
> On Wed, Apr 29, 2015 at 4:23 AM, Kweh, Hock Leong
> wrote:
> >
> > Dear communities,
> >
> > I agree with James. Due to different people may have different needs.
> >
More comments inline.
laurentiu
On Wed, Apr 29, 2015 at 11:13:26PM +0300, Anda-Maria Nicolae wrote:
> Based on the datasheet found here:
> http://www.richtek.com/download_ds.jsp?p=RT9455
>
> Updates from the previous version:
> - replaced license GPLv2 with GPL
> - replaced vendor prefix rt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm announcing the release of the 3.12.41 kernel.
All users of the 3.12 kernel series must upgrade.
The updated 3.12.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.12.y
and can be
On 04/30/2015 02:01 AM, Pai wrote:
> This fixes a few coding style issues in my previous patch:
> commit e913fb279c56
> ("net: Fix Kernel Panic in bonding driver debugfs file: rlb_hash_table")
>
> Signed-off-by: Vishwanath Pai
>
> diff --git a/drivers/net/bonding/bond_main.c
Allow to modify the low-level unbound workqueues cpumask through
sysfs. This is performed by traversing the entire workqueue list
and calling apply_wqattrs_prepare() on the unbound workqueues
with the new low level mask. Only after all the preparation are done,
we commit them all together.
701 - 800 of 1832 matches
Mail list logo
