Le 15/10/2013 22:33, Scott Wood a écrit :
On Tue, 2013-10-15 at 18:27 +0200, leroy christophe wrote:
Le 11/10/2013 17:13, Joakim Tjernlund a écrit :
"Linuxppc-dev"
wrote on 2013/10/11 14:56:40:
Activating CONFIG_PIN_TLB allows access to the 24 first Mbytes of memory
at
bootup instead of
Add rq->nr_running to sgs->sum_nr_running directly instead of
assigning it through an intermediate variable nr_running.
Signed-off-by: Kamalesh Babulal
---
kernel/sched/fair.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index
Adds support for High Speed I2C driver found in Exynos5 and
later SoCs from Samsung.
Driver only supports Device Tree method.
Signed-off-by: Naveen Krishna Chatradhi
Signed-off-by: Taekgyun Ko
Reviewed-by: Simon Glass
Tested-by: Andrew Bresticker
Signed-off-by: Yuvaraj Kumar C D
On 10/15/2013 07:02 AM, Thierry Reding wrote:
Hi all,
I've uploaded today's linux-next tree to the master branch of the
repository below:
git://gitorious.org/thierryreding/linux-next.git
A next-20131015 tag is also provided for convenience.
Gained a new conflict, but nothing too
From: Namhyung Kim
The ftrace command is a simple wrapper of kernel's ftrace
functionality. It only supports single thread tracing currently and
just reads trace_pipe in text and then write it to stdout.
Cc: Steven Rostedt
Cc: Frederic Weisbecker
Signed-off-by: Namhyung Kim
---
From: Namhyung Kim
It's helpful for debugging on tracing features.
Signed-off-by: Namhyung Kim
---
tools/perf/util/header.c | 4 ++-
tools/perf/util/trace-event-read.c | 53 ++
2 files changed, 39 insertions(+), 18 deletions(-)
diff --git
From: Namhyung Kim
For reusability, rename trace_event() to dump_raw_event() and pass
size as an argument. And use it in do_ftrace_report() to show raw
data of ftrace entries.
Signed-off-by: Namhyung Kim
---
tools/perf/builtin-ftrace.c | 6 ++
tools/perf/util/debug.c | 8
From: Namhyung Kim
The -p (--pid) option enables to trace existing process by its pid.
Cc: Steven Rostedt
Cc: Frederic Weisbecker
Signed-off-by: Namhyung Kim
---
tools/perf/builtin-ftrace.c | 89 -
1 file changed, 63 insertions(+), 26 deletions(-)
From: Namhyung Kim
Current trace info data lacks the saved cmdline mapping which is
needed for pevent to find out the comm of a task. Add this and bump
up the version number so that perf can determine its presence when
reading.
This is mostly corresponding to trace.dat file version 6, but
Hello,
This patchset implements a front-end tool for kernel's ftrace. It
uses function_graph tracer by default and normal function tracer is
also supported. (Of course you need to enable those tracers in your
kernel first.)
This version is almost merely a rebase onto current development, and I
From: Namhyung Kim
The ftrace report command is for analyzing ftrace result as usual perf
report style. Internal processing of the ftrace buffer is similar to
the 'show' sub-command but it synthesizes necessary information like
thread, dso, map and symbol from saved trace info.
It currently
From: Namhyung Kim
It's convenient to use pager when seeing many lines of result.
Note that setup_pager() should be called after perf_evlist__
prepare_workload() since they can interfere each other regarding
shared stdio streams.
Cc: Steven Rostedt
Cc: Frederic Weisbecker
Signed-off-by:
From: Namhyung Kim
Separate out the default behavior to "live" subcommand. It's a
preparation to support more subcommands like "record" and "report".
Cc: Steven Rostedt
Cc: Frederic Weisbecker
Signed-off-by: Namhyung Kim
---
tools/perf/builtin-ftrace.c | 133
From: Namhyung Kim
Cc: Steven Rostedt
Cc: Frederic Weisbecker
Signed-off-by: Namhyung Kim
---
tools/perf/Documentation/perf-ftrace.txt | 117 +++
1 file changed, 117 insertions(+)
create mode 100644 tools/perf/Documentation/perf-ftrace.txt
diff --git
From: Namhyung Kim
The --filter (-l) option is for filtering specific functions. If this
option is given, only these (and their children) functions will be
shown in the output.
Cc: Steven Rostedt
Cc: Frederic Weisbecker
Signed-off-by: Namhyung Kim
---
From: Namhyung Kim
The ftrace sub-commands share some common code so that factor it out
to ftrace_setup() and ftrace_teardown() helpers.
Cc: Steven Rostedt
Cc: Frederic Weisbecker
Signed-off-by: Namhyung Kim
---
tools/perf/builtin-ftrace.c | 172 +---
From: Namhyung Kim
The --clock (-c) option is for controlling trace_clock. Default to
'perf' if exists, or 'local'.
Cc: Steven Rostedt
Cc: Frederic Weisbecker
Signed-off-by: Namhyung Kim
---
tools/perf/builtin-ftrace.c | 31 +++
1 file changed, 31 insertions(+)
From: Namhyung Kim
Now it doesn't call pevent_print_event() but prints context info in
itself using print_graph_duration(). Make it compact by only print
cpu number and duration:
# perf ftrace show
...
10) 0.065 us | __fsnotify_parent();
10)| fsnotify() {
10)
From: Namhyung Kim
Detect leaf functions and print them in a same line.
Note that it only converts leaf-functions that doesn't have any other
records between entry and exit even in other cpus. I left other leaf
functions as is.
Cc: Steven Rostedt
Cc: Frederic Weisbecker
Signed-off-by:
From: Namhyung Kim
It's for debugging purpose.
Cc: Steven Rostedt
Cc: Frederic Weisbecker
Signed-off-by: Namhyung Kim
---
tools/perf/builtin-ftrace.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/tools/perf/builtin-ftrace.c b/tools/perf/builtin-ftrace.c
index
From: Namhyung Kim
The -a/--all-cpus and -C/--cpu option is for controlling tracing cpus.
To do that, add and use cpu_map__sprintf() function.
Cc: Steven Rostedt
Cc: Frederic Weisbecker
Signed-off-by: Namhyung Kim
---
tools/perf/builtin-ftrace.c | 69
From: Namhyung Kim
The ftrace show subcommand is for viewing recorded ftrace files. It
enters perf.data.dir directory and open perf.header file to find out
necessary information. And then read out per-cpu trace records using
kbuffer helper and print them to stdout in time order.
It only shows
From: Namhyung Kim
The ftrace record command is for saving raw ftrace buffer contents
which can be get from per_cpu/cpuX/trace_pipe_raw.
Since ftrace events are generated very frequently so single thread for
recording mostly resulted in buffer overruns. Thus it uses per-cpu
recorder thread to
On 10/12/2013 08:14 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Tue, Oct 08, 2013 at 05:46:49PM +0800, Wei Ni wrote:
>
>> In the regulator_dev_lookup(), it will try to read the "xx-supply" to
>> get the regnode, but I didn't set the vcc-supply in dts file for lm90,
>> so the
The USB3503 driver had an incorrect depedency on REGMAP, instead of
REGMAP_I2C. This caused the build to fail since the necessary regmap
i2c pieces were not available.
Signed-off-by: Matthew Dawson
---
drivers/usb/misc/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Kuppuswamy Sathyanarayanan
Fixed checkpatch warnings in mrst related files.
Signed-off-by: Kuppuswamy Sathyanarayanan
Signed-off-by: David Cohen
---
arch/x86/platform/mrst/mrst.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/platform/mrst/mrst.c
From: Kuppuswamy Sathyanarayanan
Fixed indentation issues reported by checkpatch script in
mrst related files.
Signed-off-by: Kuppuswamy Sathyanarayanan
Signed-off-by: David Cohen
---
arch/x86/platform/mrst/early_printk_mrst.c | 3 ++-
arch/x86/platform/mrst/mrst.c | 24
From: Kuppuswamy Sathyanarayanan
SFI device_id[] table parsing code is duplicated in every SFI
device handler. This patch removes this code duplication, by
adding a seperate function get_device_id() to parse through the
device table. Also this patch moves the SPI, I2C, IPC info code from
From: Kuppuswamy Sathyanarayanan
This patch provides a means to add custom handler for
SFI devices. If you set device_handler as NULL in
device_id table standard SFI device handler will be used.
If its not NULL custom handler will be called.
Signed-off-by: Kuppuswamy Sathyanarayanan
From: Kuppuswamy Sathyanarayanan
Fixed printk and pr_* related issues in mrst related files.
Signed-off-by: Kuppuswamy Sathyanarayanan
Signed-off-by: David Cohen
---
arch/x86/platform/mrst/early_printk_mrst.c | 2 +-
arch/x86/platform/mrst/mrst.c | 2 +-
From: Kuppuswamy Sathyanarayanan
mrst is used as common name to represent all intel_mid type
soc's. But moorsetwon is just one of the intel_mid soc. So
renamed them to use intel_mid.
This patch mainly renames the variables and related
functions that uses *mrst* prefix with *intel_mid*.
To
From: Kuppuswamy Sathyanarayanan
Following files contains code that is common to all intel mid
soc's. So renamed them as below.
mrst/mrst.c -> intel-mid/intel-mid.c
mrst/vrtc.c -> intel-mid/intel_mid_vrtc.c
mrst/early_printk_mrst.c -> intel-mid/intel_mid_vrtc.c
From: Kuppuswamy Sathyanarayanan
Added a custom handler for medfield based ipc devices and
moved devs_id structure defintion to header file.
Signed-off-by: Kuppuswamy Sathyanarayanan
Signed-off-by: David Cohen
---
arch/x86/include/asm/intel-mid.h| 15 ++
Intel mid sfi code doesn't need struct devs_id.get_platform_data != NULL.
If the callback is not set, just assume there is no platform_data.
Signed-off-by: David Cohen
Cc: Kuppuswamy Sathyanarayanan
---
arch/x86/platform/intel-mid/sfi.c | 11 +++
1 file changed, 7 insertions(+), 4
When Intel mid uses SFI table to enumerate devices, it requires an extra
device table with further information about how to probe such devices.
This patch creates a section where the device table will stay if
CONFIG_X86_INTEL_MID is selected.
Signed-off-by: David Cohen
---
From: Kuppuswamy Sathyanarayanan
Moved SFI specific parsing/handling code to sfi.c. This will enable us
to reuse our intel-mid code for platforms that supports firmware
interfaces other than SFI (like ACPI).
Signed-off-by: Kuppuswamy Sathyanarayanan
Signed-off-by: David Cohen
---
As Intel rolling out more SoC's after Moorestown, we need to
re-structure the code in a way that is backward compatible and easy to
expand. This patch implements a flexible way to support multiple boards
and devices.
This patch does not add any new functional support. It just refactors
the
This patch set does initial rework from arch/x86/platform/mrst to
arch/x86/platform/intel-mid.
These changes are necessary to update the obsolete Intel Atom Moorestown code
to support the newer Atom processors of this family (called 'intel-mid').
David Cohen (3):
intel-mid: sfi: allow struct
On 10/15/2013 05:45 PM, H. Peter Anvin wrote:
On 10/15/2013 04:53 PM, David Cohen wrote:
On 10/15/2013 04:44 PM, H. Peter Anvin wrote:
On 10/15/2013 04:42 PM, David Cohen wrote:
+#define intel_mid_sfi_dev(i) \
+static const struct devs_id *__intel_mid_sfi_##i##_dev __used \
+
On Mon, 07 Oct 2013 16:25:51 +0200 Lukasz Dorau
wrote:
> Since:
> commit 7ceb17e87bde79d285a8b988cfed9eaeebe60b86
> md: Allow devices to be re-added to a read-only array.
>
> spares are activated on a read-only array. In case of raid1 and raid10
> personalities it causes that
On Mon, Oct 07, 2013 at 04:38:49PM +0200, Stefan Beller wrote:
> Also removes (trailing) tabs from an empty line.
>
> Signed-off-by: Stefan Beller
Thanks for sending the patch, but the comments in this section have
since been reworded in random.git, so this patch is no longer
applicable to the
From: Jiang Liu
Reuse FPSIMD hardware context if it hasn't been touched by other thread
yet, so we can get rid of unnecessary FPSIMD context restores. This is
especially useful when switching between kernel thread and user thread
because kernel thread usaually doesn't touch FPSIMD registers.
From: Jiang Liu
Reduce duplicated code when saving/restoring FPSIMD for signal
handling, it also helps to concentrate all FPSIMD hardware related
code into fpsimd.c.
Signed-off-by: Jiang Liu
Cc: Jiang Liu
---
arch/arm64/include/asm/fpsimd.h | 4
arch/arm64/kernel/fpsimd.c | 20
From: Jiang Liu
Restore FPSIMD control and status registers to default values
when creating new FPSIMD contexts for kernel context and reset
FPSIMD status register when creating FPSIMD context for signal
handling, otherwise the stale value in FPSIMD control and status
registers may affect the
Thanks for you reply.
On 10/16 3:06, Sergei Shtylyov wrote:
> Hello.
>
> On 10/15/2013 03:45 PM, Kefeng Wang wrote:
>
>> net_ratelimited_function() is called to simplify code.
>
>> Signed-off-by: Kefeng Wang
>> ---
>> drivers/net/usb/usbnet.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2
Thanks for your reply.
On 10/16 0:24, Joe Perches wrote:
> On Tue, 2013-10-15 at 19:44 +0800, Kefeng Wang wrote:
>> Wrapper functions net_ratelimited_function() and net_XXX_ratelimited()
>> are called to simplify code.
> []
>> diff --git a/net/bridge/br_fdb.c b/net/bridge/br_fdb.c
> []
>> @@
From: Jiang Liu
Use macro JUMP_LABEL_TRUE_BRANCH instead of hard-coding for better
readability.
Signed-off-by: Jiang Liu
Cc: Jiang Liu
---
include/linux/jump_label.h | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/include/linux/jump_label.h
From: Jiang Liu
Optimize jump label implementation for ARM64 by dynamically patching
kernel text.
Signed-off-by: Jiang Liu
Cc: Jiang Liu
---
arch/arm64/Kconfig | 1 +
arch/arm64/include/asm/jump_label.h | 52
arch/arm64/kernel/Makefile
From: Jiang Liu
As commit a9468f30b5eac6 "ARM: 7333/2: jump label: detect %c
support for ARM", this patch detects the same thing for ARM64
because some ARM64 GCC versions have the same issue.
Some versions of ARM64 GCC which do support asm goto, do not
support the %c specifier. Since we need
From: Jiang Liu
Introduce aarch64_insn_gen_{nop|branch_imm}() helper functions, which
will be used to implement jump label on ARM64.
Signed-off-by: Jiang Liu
Cc: Jiang Liu
---
arch/arm64/include/asm/insn.h | 7 +++
arch/arm64/kernel/insn.c | 27 +++
2 files
From: Jiang Liu
Introduce three interfaces to patch kernel and module code:
aarch64_insn_patch_text_nosync():
patch code without synchronization, it's caller's responsibility
to synchronize all CPUs if needed.
aarch64_insn_patch_text_sync():
patch code and always
From: Jiang Liu
Function encode_insn_immediate() will be used by other instruction
manipulate related functions, so move it into insn.c and rename it
as aarch64_insn_encode_immediate().
Signed-off-by: Jiang Liu
Cc: Jiang Liu
---
arch/arm64/include/asm/insn.h | 14
From: Jiang Liu
Introduce basic aarch64 instruction decoding helper
aarch64_get_insn_class() and aarch64_insn_hotpatch_safe().
Signed-off-by: Jiang Liu
Cc: Jiang Liu
---
arch/arm64/include/asm/insn.h | 53 ++
arch/arm64/kernel/Makefile| 2 +-
From: Jiang Liu
This patchset tries to optimize arch specfic jump label implementation
for ARM64 by dynamic kernel text patching.
To enable this feature, your toolchain must support "asm goto" extension
and "%c" constraint extesion. Current GCC for AARCH64 doesn't support
"%c", so you need a
On Tue, 2013-10-15 at 22:46 -0400, Chen Gong wrote:
> On Tue, Oct 15, 2013 at 06:57:18PM -0700, Joe Perches wrote:
> > Date: Tue, 15 Oct 2013 18:57:18 -0700
> > From: Joe Perches
> > To: Borislav Petkov
> > Cc: "Chen, Gong" , tony.l...@intel.com,
> > linux-kernel@vger.kernel.org,
On Tue, Oct 15, 2013 at 06:57:18PM -0700, Joe Perches wrote:
> Date: Tue, 15 Oct 2013 18:57:18 -0700
> From: Joe Perches
> To: Borislav Petkov
> Cc: "Chen, Gong" , tony.l...@intel.com,
> linux-kernel@vger.kernel.org, linux-a...@vger.kernel.org
> Subject: Re: [PATCH 2/8] ACPI, CPER: Update cper
On 10/16/2013 03:15 AM, Sander Eikelenboom wrote:
Hi Raghavendra,
Since the ticketlock series have landed in this mergewindow (thanks :-) ) the
help accompanying the Kconfig entry doesn't seem to reflect the current state
well.
- Wasn't the whole purpose of the ticketlock series to mitigate
Hi Jiri,
On Tue, 15 Oct 2013 16:27:32 +0200, Jiri Olsa wrote:
> This patch is adding 'struct perf_data_file' object as
> a placeholder for all attributes regarding perf.data
> file handling. Changing perf_session__new to take it
> as an argument.
>
> The rest of the functionality will be added
On Tue, Oct 15, 2013 at 10:05:26PM -0400, Rik van Riel wrote:
> On 10/15/2013 07:41 PM, Dave Chinner wrote:
> > On Tue, Oct 15, 2013 at 01:41:28PM -0400, Johannes Weiner wrote:
>
> >> I'm not forgetting about them, I just track them very coarsely by
> >> linking up address spaces and then lazily
On 10/15/2013 02:13 PM, Chang Xiangzhong wrote:
Signed-off-by: Xiangzhong Chang
Your proposed solution is very nice, but it does 2 things in one
patch.
1) It fixes the bug
2) It refactors the code to improve the flow.
While (2) is very nice, it needs a much more careful review.
Can you
The logic used in branch_opcode() to extract the opcode for an instruction
applies to non branch instructions also. So rename to instr_opcode().
Signed-off-by: Sukadev Bhattiprolu
---
arch/powerpc/lib/code-patching.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
Power7 and Power8 processors save the memory hierarchy level (eg: L2, L3)
from which a load or store instruction was satisfied. Export this hierarchy
information to the user via the perf_mem_data_src object.
Thanks to input from Stephane Eranian, Michael Ellerman, Michael Neuling
and Anshuman
Hello Steven,
> -Original Message-
> From: Steven Rostedt [mailto:rost...@goodmis.org]
> Sent: Wednesday, October 16, 2013 10:08 AM
> To: Liu, Chuansheng
> Cc: Ingo Molnar (mi...@kernel.org); h...@zytor.com; fweis...@gmail.com;
> a...@linux-foundation.org; paul...@linux.vnet.ibm.com;
The uninitialized variables cause warnings which are treated as errors
during build (without WERROR=0).
Signed-off-by: Sukadev Bhattiprolu
---
tools/perf/util/srcline.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/perf/util/srcline.c
Remove the local tools/perf/util/include/asm/byteorder.h and add
a few missing typedefs to tools/perf/util/include/linux/types.h.
The local byteorder.h complicates defining big/little endian versions
of data structures in include/uapi/linux/perf_event.h.
Fix proposed by Michael Ellerman.
We used the PME_ prefix earlier to avoid some macro/variable name
collisions. We have since changed the way we define/use the event
macros so we no longer need the prefix.
By dropping the prefix, we keep the the event macros consistent with
their official names.
Reported-by: Michael Ellerman
On 10/15/2013 10:47 PM, Paul E. McKenney wrote:
> On Tue, Oct 15, 2013 at 08:32:41PM +0800, Chen Gang wrote:
>> Yeah, that is a way for it. It seems you (related maintainer) like
>> additional fix for it.
>>
>> Hmm... I will try within this week (although I don't think it is quite
>> necessary to
Export generic perf events for Power8 in sysfs.
Signed-off-by: Sukadev Bhattiprolu
---
Changelog[v6]:
[Michael Ellerman] Drop PME_ prefix in macros
arch/powerpc/perf/power8-events-list.h | 20 +++
arch/powerpc/perf/power8-pmu.c | 44
perf_mem_data_src is an union that is initialized via the ->val field
and accessed via the bitmap fields. For this to work on big endian
platforms, we also need a big-endian represenation of perf_mem_data_src.
Cc: Stephane Eranian
Cc: Michael Ellerman
Signed-off-by: Sukadev Bhattiprolu
---
On Power7, the DCACHE_SRC field in MMCRA register identifies the memory
hierarchy level (eg: L2, L3 etc) from which a data-cache miss for a
marked instruction was satisfied.
Use the 'perf_mem_data_src' object to export this hierarchy level to user
space. Some memory hierarchy levels in Power7
The perf event PM_MRK_GRP_CMPL is useful in analyzing memory hierarchy
of applications.
Signed-off-by: Sukadev Bhattiprolu
---
Changelog[v6]:
- [Michael Ellerman]: Drop redundant PME_ prefix from event name.
arch/powerpc/perf/power8-events-list.h |1 +
1 file changed, 1
On Wed, 16 Oct 2013 01:54:51 +
"Liu, Chuansheng" wrote:
> > Since the NMI iretq nesting has been fixed, there's no reason that
> I think you patch fix the infinite loop, we will have a test soon.
> BTW, we are using 3.10, could you help to point out which NMI iretq nesting
> patch?
There
On Power8, the LDST field in SIER identifies the memory hierarchy level
(eg: L1, L2 etc), from which a data-cache miss for a marked instruction
was satisfied.
Use the 'perf_mem_data_src' object to export this hierarchy level to user
space. Fortunately, the memory hierarchy levels in Power8 map
Implement instr_is_load_store_2_06() to detect whether a given instruction
is one of the fixed-point or floating-point load/store instructions in the
POWER Instruction Set Architecture v2.06.
This function will be used in a follow-on patch to save memory hierarchy
information of the load/store on
On 10/15/2013 07:41 PM, Dave Chinner wrote:
> On Tue, Oct 15, 2013 at 01:41:28PM -0400, Johannes Weiner wrote:
>> I'm not forgetting about them, I just track them very coarsely by
>> linking up address spaces and then lazily enforce their upper limit
>> when memory is tight by using the shrinker
Hello Jan,
Just wanted to let you know I hit this[1] again on Linus' latest. The
setup/workload is *identical* to the reported one a few months ago.
[1] https://lkml.org/lkml/2013/8/1/532
Here's the complete output, I hope it helps...
[ cut here ]
WARNING: CPU: 42 PID:
On 10/15/2013 09:38 PM, Mark Rutland wrote:
On Tue, Oct 08, 2013 at 04:22:07AM +0100, Hongbo Zhang wrote:
Hi Mark, Stephen and other DT maintainers?
The 1/3 had already been acked by Mark, and please have a further look
at this patch 2/3.
The DMA maintainer Vinod needs ack for the DT related
On 10/15/13 7:52 PM, Namhyung Kim wrote:
Aha, okay. So it mostly matters to syscall tracing, right? For a
normal record session, it seems that the effect is not that large:
Yes, that's in the description "When recording raw_syscalls for the
entire system"
There is a small benefit to all
On Fri, 2013-10-11 at 17:47 +0200, Borislav Petkov wrote:
> On Fri, Oct 11, 2013 at 11:06:30AM +0200, Borislav Petkov wrote:
> > > - printk("%s""APEI generic hardware error status\n", pfx);
> > > + printk("%s""Generic Hardware Error Status\n", pfx);
> >
> > Btw, what's the story with printk not
Hello Steven,
> -Original Message-
> From: Steven Rostedt [mailto:rost...@goodmis.org]
> Sent: Wednesday, October 16, 2013 12:40 AM
> To: Liu, Chuansheng
> Cc: Ingo Molnar (mi...@kernel.org); h...@zytor.com; fweis...@gmail.com;
> a...@linux-foundation.org; paul...@linux.vnet.ibm.com;
On Tue, Oct 15, 2013 at 11:47:23PM +0530, Naveen N. Rao wrote:
> Date: Tue, 15 Oct 2013 23:47:23 +0530
> From: "Naveen N. Rao"
> To: "Chen, Gong"
> Cc: tony.l...@intel.com, b...@alien8.de, linux-kernel@vger.kernel.org,
> linux-a...@vger.kernel.org
> Subject: Re: [PATCH 2/8] ACPI, CPER: Update
On Tue, 15 Oct 2013 07:35:53 -0600, David Ahern wrote:
> On 10/15/13 1:31 AM, Namhyung Kim wrote:
>> Hi David,
>>
>> On Mon, 14 Oct 2013 20:55:31 -0600, David Ahern wrote:
>>> When recording raw_syscalls for the entire system, e.g.,
>>> perf record -e raw_syscalls:*,sched:sched_switch -a --
On Tue, Oct 15, 2013 at 10:56:25PM +0530, Naveen N. Rao wrote:
> Date: Tue, 15 Oct 2013 22:56:25 +0530
> From: "Naveen N. Rao"
> To: "Chen, Gong"
> Cc: tony.l...@intel.com, b...@alien8.de, linux-kernel@vger.kernel.org,
> linux-a...@vger.kernel.org
> Subject: Re: [PATCH 5/8] ACPI, APEI, CPER:
Remove the non-standard EP93xx PWM driver in drivers/misc and add
a new driver for the PWM controllers on the EP93xx platform based
on the PWM framework.
These PWM controllers each support 1 PWM channel with programmable
duty cycle, frequency, and polarity inversion.
Signed-off-by: H Hartley
sg3_utils is a package of command line utilities for sending
SCSI and some ATA commands to devices. This package targets
the Linux 3, 2.6 and 2.4 kernel series. It also has ports to
FreeBSD, Tru64, Solaris, and Windows (cygwin and MinGW).
This version contains many fixes, some code cleanup and
A couple more regressions fixed, please pull.
The following changes since commit 34ec4de42be5006abdd8d0c08b306ffaa64d0d5d:
Merge tag 'devicetree-for-linus' of git://git.secretlab.ca/git/linux
(2013-10-15 17:14:13 -0700)
are available in the git repository at:
(2013/10/16 4:30), Vivek Goyal wrote:
On Tue, Oct 15, 2013 at 02:43:27PM +0900, HATAYAMA Daisuke wrote:
Currently, on x86 architecture, if crash happens on AP in the kdump
1st kernel, the 2nd kernel fails to wake up multiple CPUs. The typical
behaviour we actually see is immediate system reset
Hi David,
On Tue, 15 Oct 2013 07:25:04 -0600, David Ahern wrote:
> On 10/15/13 1:09 AM, Namhyung Kim wrote:
>>> The stat() seems superfluous, here in __cmd_record() we've just checked
>>> the output_name and made sure it exists. Can that stat() call ever fail?
>>
>> AFAICS it's needed to check
On Tuesday, October 15, 2013 3:40 AM, Thierry Reding wrote:
> On Mon, Oct 14, 2013 at 02:57:48PM -0700, H Hartley Sweeten wrote:
>> Remove the non-standard EP93xx pwm driver in drivers/misc and add
>
> pwm -> PWM
OK
>> a new driver for the PWM chips on the EP93xx platforms based on the
>> PWM
Commit 4e7ea81db5(ext4: restructure writeback path) introduces
another performance regression on random write:
- one more page may be added to ext4 extent in mpage_prepare_extent_to_map,
and will be submitted for I/O so nr_to_write will become -1 before 'done'
is set
- the worse thing is
(2013/10/16 4:12), Vivek Goyal wrote:
On Tue, Oct 15, 2013 at 02:43:22PM +0900, HATAYAMA Daisuke wrote:
Kexec can enter the kdump 2nd kernel on AP if crash happens on AP. To
check if boot cpu is BSP, introduce a helper function
boot_cpu_is_bsp().
Signed-off-by: HATAYAMA Daisuke
---
Mikulas,
> I/Os shouldn't be returned with -ENOMEM. If they are, you can treat it as
> a hard error.
It seems to be blkdev_issue_discard returns -ENOMEM
when bio_alloc fails, for example.
Waiting for a second and we can alloc the memory is my idea
for handling -ENOMEM returned.
> Blocking I/O
On 10/15/2013 04:53 PM, David Cohen wrote:
> On 10/15/2013 04:44 PM, H. Peter Anvin wrote:
>> On 10/15/2013 04:42 PM, David Cohen wrote:
>>>
>>> +#define intel_mid_sfi_dev(i) \
>>> +static const struct devs_id *__intel_mid_sfi_##i##_dev __used \
>>> +
This patch adds the Port Reset Change flag to the set of bits that are
preemptively cleared on init/resume of a hub. In theory this bit should
never be set unexpectedly... in practice it can still happen if BIOS,
SMM or ACPI code plays around with USB devices without cleaning up
correctly. This is
I see a few problems on this patchset:
Em Tue, 15 Oct 2013 23:00:53 +0530
"Naveen N. Rao" escreveu:
> On 10/15/2013 10:30 PM, Borislav Petkov wrote:
> > On Tue, Oct 15, 2013 at 10:24:35PM +0530, Naveen N. Rao wrote:
> >> On 2013/10/11 02:32AM, Chen Gong wrote:
> >>> Use trace interface to
>> + if ((portchange & USB_PORT_STAT_C_RESET)) {
>
>
>Hm, why these double parens?
Oh... good question. I copied the entry below it, remove the && and
must have overlooked those. Sorry, v2 incoming...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On Oct 16, 2013, at 6:21 AM, Marcelo Tosatti wrote:
> On Tue, Oct 15, 2013 at 06:57:05AM +0300, Gleb Natapov wrote:
>>>
>>> Why is it safe to allow access, by the lockless page write protect
>>> side, to spt pointer for shadow page A that can change to a shadow page
>>> pointer of shadow page
On Wed, Oct 16, 2013 at 4:22 AM, Alan Stern wrote:
> On Tue, 15 Oct 2013, Vishal Annapurve wrote:
>
>> Hi Alan,
>>
>> USB storage maybe just has to say that the abort occurred. By setting the
>> US_FLIDX_TIMED_OUT bit USB storage is getting signaled that the reason was
>> time out and the command
On Tue, 2013-10-15 at 09:21 -0700, Joe Perches wrote:
> Ingo, Eric _showed_ that the prefetch is good here.
> How about looking at a little optimization to the minimal
> prefetch that gives that level of performance.
Wait a minute, my point was to remind that main cost is the
memory fetching.
In the lpfc_ct_free_iocb function after freeing associated memory to the
ctiocb->context3, the ctiocb->context1 is set to NULL instead of context3.
Signed-off-by: Felipe Pena
---
drivers/scsi/lpfc/lpfc_ct.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
1 - 100 of 1514 matches
Mail list logo
