On Wed, 04 Dec 2013 14:38:11 +0530 Raghavendra K T
wrote:
> On 12/04/2013 02:11 PM, Andrew Morton wrote:
> > On Wed, 04 Dec 2013 14:00:09 +0530 Raghavendra K T
> > wrote:
> >
> >> Unfaortunately, from my search, I saw that the code belonged to pre git
> >> time, so could not get much
On Wed, Dec 04, 2013 at 12:46:42PM -0800, Colin Cross wrote:
> On Wed, Dec 4, 2013 at 10:35 AM, Greg KH wrote:
>
>
> > And finally, is this all really needed? Why not just fix the structures
> > to be "correct", and then fix userspace to use the correct structures as
> > well, thereby not
Hi,
On Tue, Dec 03, 2013 at 11:46:51AM -0800, David Daney wrote:
> From: David Daney
>
> This will be needed by the next patch to use said nodes for probing
> via the device tree.
>
> Signed-off-by: David Daney
Tested-by: Aaro Koskinen
A.
> ---
>
Hi,
On Tue, Dec 03, 2013 at 11:46:52AM -0800, David Daney wrote:
> From: David Daney
>
> Extract clocking parameters from the device tree, and remove now dead
> code and types.
>
> Signed-off-by: David Daney
Tested-by: Aaro Koskinen
Thanks,
A.
> ---
>
On Wed, 04 Dec 2013 16:59:38 +0800 Axel Lin wrote:
> >
> > Please add a lot more printk's so we can narrow it down further? I'd
> > use something like
> >
> > printk(%d: %d\n", __LINE__, preempt_count());
> >
> > (note: preempt_count(), not in_atomic())
> >
> > Paste that all over the
On Wed, Dec 04, 2013 at 03:58:22PM +, Qais Yousef wrote:
> In file included from kernel/crash_dump.c:2:0:
> include/linux/crash_dump.h:22:27: error: unknown type name ‘pgprot_t’
>
> when CONFIG_CRASH_DUMP=y
>
> The error was traced back to this commit:
>
> 9cb218131de1 vmcore:
On Tue, Dec 03, 2013 at 01:54:34PM -0800, Ben Zhang wrote:
> This provides usermode a way to disable only the soft
> lockup detector while keeping the hard lockup detector
> running.
>
> kernel.softlockup_detector_enable=1:
> This is the default. The soft lockup detector is enabled.
> When a soft
On Wed, Dec 04, 2013 at 03:53:02PM -0300, Arnaldo Carvalho de Melo wrote:
SNIP
> Auto-detecting system features:
> ... backtrace: [ on ]
> ... dwarf: [ on ]
> ...fortify-source: [ on ]
> ... glibc: [ on ]
>
On Wed, 4 Dec 2013, Vinayak Kale wrote:
> This patch adds an accessor function for IRQ_PER_CPU flag.
> The accessor function is useful to determine whether an IRQ is percpu or not.
>
> This patch is based on an older patch posted by Chris Smith here [1].
> There is a minor change w.r.t. Chris's
On 12/04/2013 05:09 PM, Konrad Rzeszutek Wilk wrote:
On Wed, Dec 04, 2013 at 10:10:28AM +0100, Daniel Lezcano wrote:
On 12/03/2013 10:33 PM, Rafael J. Wysocki wrote:
On Tuesday, December 03, 2013 10:59:58 AM Konrad Rzeszutek Wilk wrote:
If not, we could end up in the unfortunate situation
On Wednesday, December 04, 2013 02:54:07 AM Matthew Garrett wrote:
> On Tue, Dec 03, 2013 at 06:44:52PM -0800, David E. Box wrote:
> > On Wed, Dec 04, 2013 at 02:21:30AM +, Matthew Garrett wrote:
> > > Well sure, but why do you need to be a platform device at all? This
> > > functionality was
On Fri, Nov 29, 2013 at 02:14:29PM +0100, Michael Grzeschik wrote:
> The ecc_stats.corrected count variable will already be incremented in
> the above framework-layer just after this callback.
>
> Cc: sta...@vger.kernel.org
Added a 2.6.36+ note, just for reference.
> Signed-off-by: Michael
When ACPI SLIT table has an I/O locality (i.e. a locality unique
to an I/O device), numa_set_distance() emits the warning message
below.
NUMA: Warning: node ids are out of bound, from=-1 to=-1 distance=10
acpi_numa_slit_init() calls numa_set_distance() with pxm_to_node(),
which assumes that all
On Wed, Dec 4, 2013 at 1:19 AM, Simon Kirby wrote:
>
> Meanwhile, I still don't understand how moving the unlock _up_ to cover
> less of the code can solve the race, but I will stare at your long
> explanation more tomorrow.
The lock we're moving up isn't the lock that actually protects the
>From 187369f55f9f9bc58c87fc1ac118143db5735033 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Samuel=20Dom=C3=ADnguez?=
Date: Wed, 4 Dec 2013 20:35:41 +
Subject: [PATCH] staging: lustre: lnet: lnet: fixed space coding style issues
Fixed a coding style issue.
Signed-off-by: Samuel Dominguez
---
2013/12/4 Greg Kroah-Hartman :
> Your pid implementation is broken, see my other email about that :(
Thank you for your remarks on pid. I'll try to correct that.
> And again, what's wrong with the existing tracing functionalty that is
> processor agnostic? Why can't we just delete this driver
On Thu, 2013-11-07 at 15:00 +0100, Roberto Sassu wrote:
> With the introduction of the 'ima_template_fmt' kernel cmdline parameter,
> an user can define a new template descriptor with custom format. However,
> in this case, userspace tools will be unable to parse the measurements
> list because
On Wed, Dec 04, 2013 at 05:10:58PM +0900, HATAYAMA Daisuke wrote:
> This patch set is to allow kdump 2nd kernel to wake up multiple CPUs,
> a continueing work from:
>
> [PATCH v3 0/2] x86, apic, kdump: Disable BSP if boot cpu is AP
> https://lkml.org/lkml/2013/10/16/300.
>
> At v4, basic
On Mon, Dec 2, 2013 at 3:07 PM, Leif Lindholm wrote:
> On Mon, Dec 02, 2013 at 01:51:22PM -0600, Matt Sealey wrote:
>> Here's where I think this whole thing falls down as being the weirdest
>> possible implementation of this. It defies logic to put this
>> information in the device tree /chosen
On Thu, 2013-11-07 at 15:00 +0100, Roberto Sassu wrote:
> This patch allows users to provide a custom template format through the
> new kernel command line parameter 'ima_template_fmt'. If the supplied
> format is not valid, IMA uses the default template descriptor.
>
> Signed-off-by: Roberto
Around Wed 04 Dec 2013 17:52:55 +0100 or thereabout, Matthias Brugger wrote:
> The power management has a section mismatch which leads to the following
> warning during compilation:
>
> WARNING: arch/avr32/mach-at32ap/built-in.o(.text+0x16d4): Section
> mismatch in reference from the function
On Wed, Dec 04, 2013 at 09:39:26PM +0200, Ivan Khoronzhuk wrote:
> To reduce code duplicate and increase code readability use WDT core
> code to handle WDT interface.
>
> Remove io_lock as the WDT core uses mutex to lock each wdt device.
> Remove wdt_state as the WDT core tracks state with its
On Wed, Dec 4, 2013 at 10:35 AM, Greg KH wrote:
> And finally, is this all really needed? Why not just fix the structures
> to be "correct", and then fix userspace to use the correct structures as
> well, thereby not needing a compat layer at all?
Some of the binder ioctls take userspace
On Mon, Dec 02, 2013 at 01:05:16PM +0800, rui wang wrote:
> > + TP_printk("%s PCIe Bus Error: severity=%s, %s\n",
> > + __get_str(dev_name),
> > + __entry->severity == HW_EVENT_ERR_CORRECTED ? "Corrected" :
> > + __entry->severity == HW_EVENT_ERR_FATAL ?
> >
From: Magnus Damm
Now when drivers/clocksource/Kconfig has been
updated with entires for CMT, TMU and MTU2
it is safe to remove these from SH.
Signed-off-by: Magnus Damm
---
arch/sh/Kconfig | 21 -
1 file changed, 21 deletions(-)
--- 0001/arch/sh/Kconfig
+++
From: Magnus Damm
Now when drivers/clocksource/Kconfig has been
updated with entires for CMT, TMU and STI
it is safe to remove these from mach-shmobile.
Also select timers per SoC via SYS_SUPPORTS_xxx.
Signed-off-by: Magnus Damm
---
arch/arm/mach-shmobile/Kconfig | 35
From: Magnus Damm
Add Kconfig entries for CMT, MTU2, TMU and STI to
drivers/clocksource/Kconfig. This will allow us to
get rid of duplicated entires in architecture code
such as arch/sh and arch/arm/mach-shmobile.
Signed-off-by: Magnus Damm
---
drivers/clocksource/Kconfig | 36
clocksource: Consolidate SH and ARM mach-shmobile Kconfig bits (v3)
[PATCH v3 01/03] clocksource: Add Kconfig entries for CMT, MTU2, TMU and STI
[PATCH v3 02/03] ARM: shmobile: Remove CMT, TMU and STI Kconfig entries
[PATCH v2 03/03] sh: Remove Kconfig entries for TMU, CMT and MTU2
This is V3 of
On 2013-12-04 18:16, Dmitry Torokhov wrote:
On Mon, Dec 02, 2013 at 09:40:20PM +0100, Manuel Krause wrote:
On 2013-12-02 20:07, Dmitry Torokhov wrote:
Thank you Manuel, but IO think the patch is not complete as we need to
re-enable PNP devices after we make a snapshot to make sure they are
On Tue, Dec 03, 2013 at 10:25:36AM -0500, Vivek Goyal wrote:
>
> Hi Hatayama,
>
> We are almost there. A minor nit. Why have we specified KEXEC here. This
> parameter disabled_cpu_apicid does not seem to dependon CONFIG_KEXEC?
>
> Jerry, this patch looks good to me. Does it work on your
From: Dongsheng Yang
Check for cpu_map__dummy_new() or cpu_map__new() to be called in
perf_evlist__create_maps() is more complicated.
This patch moves the checking work into target.h, combining two
conditions and making perf_evlist__create_maps() more readable.
Signed-off-by: Dongsheng Yang
From: Adrian Hunter
Currently, lookup of an ip's source file name and line number is done
using the dso file name.
Instead retain the file name used to lookup the dso's symbols and use
that.
Signed-off-by: Adrian Hunter
Cc: Andi Kleen
Cc: David Ahern
Cc: Frederic Weisbecker
Cc: Ingo Molnar
From: Dongsheng Yang
As the buildid is read from /sys/kernel/notes, then if we use perf kvm
buildid-list with a perf data file captured by perf kvm record with
--guestkallsyms and --guestmodules, there is no result in output.
This patch add a explanation about it and add a limit of using perf
From: Adrian Hunter
Closng and re-opening for every lookup when using libbfd to lookup
source file name and line number is very very slow. Instead keep the
reference on struct dso.
Signed-off-by: Adrian Hunter
Cc: Andi Kleen
Cc: David Ahern
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Jiri
From: Dongsheng Yang
In machine__get_kernel_start_addr, the code, which is using
machine->root_dir to build filename, works for both host and guests
initialized from guestmount, as root_dir is set to "" for the host
machine in the machine__init() function.
So this patch remove the branch for
From: Adrian Hunter
The asprintf library function is equivalent to malloc plus snprintf so
use it because it is simpler.
Signed-off-by: Adrian Hunter
Cc: Andi Kleen
Cc: David Ahern
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Jiri Olsa
Cc: Mike Galbraith
Cc: Namhyung Kim
Cc: Paul
From: Jiri Olsa
Adding cfg80211 plugin.
This plugin adds handler for __le16_to_cpup function
t properly parse following tracepoint events:
cfg80211:cfg80211_tx_mlme_mgmt
cfg80211:cfg80211_rx_mlme_mgmt
cfg80211:cfg80211_rx_unprot_mlme_mgmt
The diff of 'perf script' output generated by old
From: Jiri Olsa
There's no need for following functions to be global:
process_jbd2_dev_to_name
process_jiffies_to_msecs
Make them static.
Signed-off-by: Jiri Olsa
Cc: Corey Ashford
Cc: David Ahern
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Namhyung Kim
Cc: Paul Mackerras
Cc: Peter
From: Jiri Olsa
Adding scsi plugin.
This plugin adds fields resolving functions for following tracepoint
events:
scsi:scsi_dispatch_cmd_start
scsi:scsi_dispatch_cmd_error
scsi:scsi_dispatch_cmd_done
scsi:scsi_dispatch_cmd_timeout
The diff of 'perf script' output generated by old and
From: Jiri Olsa
Backporting mac80211 plugin.
Backported from Steven Rostedt's trace-cmd repo (HEAD 0f2c2fb):
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
This plugin adds changed field resolving for
mac80211:drv_bss_info_changed tracepoint event.
The diff of 'perf
From: Jiri Olsa
Backporting sched_switch plugin.
Backported from Steven Rostedt's trace-cmd repo (HEAD 0f2c2fb):
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
This plugin adds fields resolving for sched:sched_switch tracepoint
event.
The diff of 'perf script' output
From: Jiri Olsa
Backporting function plugin.
Backported from Steven Rostedt's trace-cmd repo (HEAD 0f2c2fb):
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
This plugin adds function and parent function fields resolving for
ftrace:function tracepoint event.
The diff of
From: Jiri Olsa
Removing malloc_or_die calls from event-plugin.c,
replacing them with standard malloc and error path.
Suggested-by: Namhyung Kim
Signed-off-by: Jiri Olsa
Acked-by: Steven Rostedt
Cc: Corey Ashford
Cc: David Ahern
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Namhyung Kim
From: Jiri Olsa
Adding xen plugin.
This plugin adds fields resolving for following tracepoint events:
xen:xen_mc_entry
xen:xen_mc_extend_args
The diff of 'perf script' output generated by old and new code: (data
was generated by 'perf record -e 'xen:*' ls')
--- script.xen.old
+++
From: Dongsheng Yang
As we have changed the default behavior of 'perf kvm' to --guest
enabled, the parts of the man page that covers the 'record' subcommand
are outdated.
This patch updates it to show the correct output with
--host/--guest/neither/both of them.
Signed-off-by: Dongsheng Yang
From: Dongsheng Yang
As option --host and --guest request no input for it, there should not
be a '=' after them in the man page sources.
And --output expects a filename as the input, so there should be a '='
after it.
This patch removes the needless '=' after --guest and --host, and adds a
'='
From: Jiri Olsa
Add trace-event object to keep together 'struct pevent' object with its
loaded plugins with following interface:
int trace_event__init(struct trace_event *t);
- Initalizes 'struct pevent' object and loads plugins for it
void trace_event__cleanup(struct trace_event *t);
-
From: Jiri Olsa
Removing the 'to ...' part out of the install message, because it does
not fit to the rest of the build messages we use.
Before:
INSTALL plugin_hrtimer.soto
/home/jolsa/libexec/perf-core/traceevent/plugins
INSTALL plugin_jbd2.so to
From: Jiri Olsa
We use -fstack-protector-all option to enable stack protecting for all
available functions. There's no reason for enabling -Wstack-protector to
get warning for unprotected functions.
Removing stackprotector feature check which was used to enable the
-Wstack-protector option.
From: Adrian Hunter
Looking up an ip's source file name and line number does not succeed
always. Current logic disables the lookup for a dso entirely on any
failure. Change it so that disabling never happens if there has ever
been a successful lookup for that dso but disable if the first 123
From: Jiri Olsa
Adding traceevent_host_bigendian function to get host endianity. It's
used in following patches.
Signed-off-by: Jiri Olsa
Cc: Corey Ashford
Cc: David Ahern
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Namhyung Kim
Cc: Paul Mackerras
Cc: Peter Zijlstra
Cc: Steven Rostedt
From: Jiri Olsa
Backporting jbd2 plugin.
Backported from Steven Rostedt's trace-cmd repo (HEAD 0f2c2fb):
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
This plugin adds field resolving functions for following tracepoint
events:
jbd2:jbd2_checkpoint_stats
From: Jiri Olsa
Adding 'plugins' target along with the libtraceevent.a, so plugins are
built together with traceevent library.
Adding 'install-traceevent-plugins' Makefile install target, instructing
perf to install plugins into:
$(HOME)/.traceevent/plugins
- If installed localy under
From: Jiri Olsa
The traceevent lib uses pr_stat to display all standard info. It's
defined as __weak. Overloading it with perf version plugged into perf
output system logic.
Displaying the pr_stat stuff under '-v' option.
Signed-off-by: Jiri Olsa
Cc: Corey Ashford
Cc: David Ahern
Cc:
From: Jiri Olsa
Backporting plugin support for traceevent lib.
Backported from Steven Rostedt's trace-cmd repo (HEAD 0f2c2fb):
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
It's now possible to use following interface to load plugins
(shared objects) to enhance pevent
From: Jiri Olsa
In order to get the proper plugins processing we need to use full
trace-event interface when creating tracepoint events. So far we were
using shortcut to get the parsed format.
Moving current 'event_format__new' function into trace-event object as
'trace_event__tp_format'.
This
From: Arnaldo Carvalho de Melo
Hi Ingo,
Please consider pulling,
- Arnaldo
The following changes since commit 89e3bbd58a6186b832fe2b9419ac2f9ab90e9089:
Merge tag 'perf-core-for-mingo' of
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core
(2013-12-04 10:17:17
From: Jiri Olsa
Backporting kmem plugin.
Backported from Steven Rostedt's trace-cmd repo (HEAD 0f2c2fb):
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
This plugin adds call_site field resolving for following tracepoint
events:
kmem:kfree
kmem:kmalloc
From: Jiri Olsa
Adding is_writable_pte print helper function, so the
kvmmmu:fast_page_fault print format gets resolved properly.
The diff of 'perf script' output generated by old and new code:
(data was generated by 'perf record -e 'kvm:*,kvmmmu:*' -a')
--- script.kvm.old
+++
From: Jiri Olsa
Backporting missing pieces of plugin building infrastructure:
- Adding Makefile 'plugins' target to build all
defined plugins
- Adding Makefile 'install_plugins' target as 'install_lib'
target dependency
- Link plugin objects with shared object building
Since commit 7106b4e3 ("8250: Oxford Semiconductor Devices") the debug
print of the device id does no longer match the real device if it is
located in the "enum" behind oxsemi_pcie_pport. The reason is that the
code assumes that each id contains one entry in the PCI table.
The fix is to lookup the
From: Adrian Hunter
The perf_event__preprocess_sample() function is called in
process_sample_event(). Instead of calling it again in
perf_evsel__print_ip(), pass through the resultant addr_location.
Signed-off-by: Adrian Hunter
Cc: Andi Kleen
Cc: David Ahern
Cc: Frederic Weisbecker
Cc:
From: Jiri Olsa
Backporting hrtimer plugin.
Backported from Steven Rostedt's trace-cmd repo (HEAD 0f2c2fb):
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
This plugin adds function field resolving for following tracepoint
events:
timer:hrtimer_expire_entry
From: Jiri Olsa
Changing the pevent_parse_format interface to include the pevent handle.
The goal is to always use pevent object when dealing with traceevent
library. The reason is that we might need additional processing (like
plugins), which is not possible otherwise.
Patches follow to make
From: Jiri Olsa
Backporting kvm plugin.
Backported from Steven Rostedt's trace-cmd repo (HEAD 0f2c2fb):
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
This plugin adds field resolving functions for following
tracepoint events:
kvm:kvm_exit
kvm:kvm_emulate_insn
From: Jiri Olsa
Adding filename__read_str util function to read
text file and return it in the char array.
The interface is:
int filename__read_str(const char *filename, char **buf, size_t *sizep)
Returns 0/-1 if the read suceeded/fail respectively.
buf - place to store the data
From: Jiri Olsa
Removing malloc_or_die calls from plugin_function.c, replacing them and
factoring the code with standard realloc and error path.
Suggested-by: Namhyung Kim
Signed-off-by: Jiri Olsa
Cc: Corey Ashford
Cc: David Ahern
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Namhyung Kim
From: Jiri Olsa
Several cleanups suggested by Namhyung:
* Remove index field from struct func_stack as it's not needed.
* Rename get_index into add_and_get_index.
* Use '%*X' format string capability instead of the loop
Suggested-by: Namhyung Kim
Signed-off-by: Jiri Olsa
Cc: Corey
From: Jiri Olsa
The pevent_print_func_field function encompasses all the functionality
used in the hrtimer_start handler. Change the handler to use this
function.
This also unifies the function field output with the
hrtimer_expire_entry handler.
Suggested-by: Steven Rostedt
Signed-off-by:
From: Adrian Hunter
When built without libelf, perf tools was failing to initialize a file
descriptor, but nevertheless closing it. That sometimes resulted in the
output being truncated because the stdout file descriptor got closed.
Signed-off-by: Adrian Hunter
Cc: David Ahern
Cc: Frederic
Hello.
On 12/04/2013 06:44 PM, Sebastian Hesselbarth wrote:
Since phy_attach ensures PHYs are resumed, we can now suspend all
PHYs that have no attached netdev after initcalls.
Signed-off-by: Sebastian Hesselbarth
---
Changelog:
RFCv1->RFCv2:
- only check for phydev->attached_dev and let
On Wed, Dec 04, 2013 at 11:39:09AM -0800, Stephen Boyd wrote:
> The msm_serial_hs driver uses mach specific dma APIs. This is not
> compatible with the multi-platform ARM effort. Let's only compile
> this driver on MSM devices that are prepared to support it;
> allowing the DT based MSM devices to
I'm announcing the release of the 3.12.3 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 browsed at the normal kernel.org git web browser:
I'm announcing the release of the 3.10.22 kernel.
All users of the 3.10 kernel series must upgrade.
The updated 3.10.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.10.y
and can be browsed at the normal kernel.org git web
if the DMA driver isn't loaded "on time" then we crash in the irq handler:
| pch_uart :02:0a.4: pch_request_dma:dma_request_channel FAILS(Tx)
| BUG: unable to handle kernel NULL pointer dereference at (null)
| IP: [] pch_uart_interrupt+0x739/0x940
Signed-off-by: Sebastian Andrzej Siewior
I'm announcing the release of the 3.4.72 kernel.
All users of the 3.4 kernel series must upgrade.
The updated 3.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.4.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Documentation/sysctl/kernel.txt b/Documentation/sysctl/kernel.txt
index 6d78841f..99d8ab9d 100644
--- a/Documentation/sysctl/kernel.txt
+++ b/Documentation/sysctl/kernel.txt
@@ -284,13 +284,24 @@ Default value is "/sbin/hotplug".
kptr_restrict:
This toggle indicates whether
On Tuesday, December 03, 2013 06:19:28 PM Yinghai Lu wrote:
> On Sat, Nov 30, 2013 at 5:05 PM, Rafael J. Wysocki wrote:
> > On Saturday, November 30, 2013 02:40:30 PM Yinghai Lu wrote:
> >
> > And this is not enough as I said, can you please stop ignoring me openly?
> >
> > You've already
On 12/04/2013 08:53 AM, Hanjun Guo wrote:
On 2013年12月04日 13:46, Zheng, Lv wrote:
From: linux-acpi-ow...@vger.kernel.org
[mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Hanjun Guo
Sent: Wednesday, December 04, 2013 12:37 AM
introduce arm_core.c and its related head file, after this
The MSM timer is only used on MSM devices that don't have the
architected timers. Introduce a hidden Kconfig option for this
driver so that we don't build it on the platforms that don't need
it.
Signed-off-by: Stephen Boyd
---
arch/arm/mach-msm/Kconfig | 9 +
arch/arm/mach-msm/Makefile
Since Davinci WDT has been switched to use WDT core, it became able
to support timeout-sec property, so add it to it's binding description.
Acked-by: Santosh Shilimkar
Reviewed-by: Guenter Roeck
Signed-off-by: Ivan Khoronzhuk
---
.../devicetree/bindings/watchdog/davinci-wdt.txt |4
Currently, the davinci watchdog can be read while counting,
so we can add ability to report the remaining time before
the system will reboot.
Acked-by: Santosh Shilimkar
Reviewed-by: Guenter Roeck
Signed-off-by: Ivan Khoronzhuk
---
drivers/watchdog/davinci_wdt.c | 26
These patches are intended to update Davinci watchdog to use WDT core
and reuse driver for keystone arch, because Keystone uses the similar
IP like Davinci.
See Documentation:
Davinci DM646x - http://www.ti.com/lit/ug/spruer5b/spruer5b.pdf
Keystone - http://www.ti.com/lit/ug/sprugv5a/sprugv5a.pdf
Some SoCs, like Keystone 2, can support more than one WDT and each
watchdog device has to use it's own base address, clock source,
watchdog device, so add new davinci_wdt_device structure to hold
device data.
Acked-by: Santosh Shilimkar
Reviewed-by: Guenter roeck
Signed-off-by: Ivan Khoronzhuk
The keystone arch uses the same IP watchdog, so add "ti,keystone-wdt"
compatible and correct identity.
The Keystone arch is using clocks in DT and source clock for watchdog
has to be specified, so add this to binding.
Acked-by: Santosh Shilimkar
Reviewed-by: Guenter Roeck
Signed-off-by: Ivan
To reduce code duplicate and increase code readability use WDT core
code to handle WDT interface.
Remove io_lock as the WDT core uses mutex to lock each wdt device.
Remove wdt_state as the WDT core tracks state with its own variable.
The watchdog_init_timeout() can read timeout value from
The functionality provided by clock.c in mach-msm is only needed
on proc_comm based platforms. Only build the file if proc_comm is
enabled. This prevents compile failures for platforms that are
part of the multi-platform kernel.
Signed-off-by: Stephen Boyd
---
arch/arm/mach-msm/Makefile | 2 +-
These patches allow the MSM code to be built as part of the multi-platform
kernel. To be fully functional you need the first patch from Ivan's series[1]
so that the usb-phy driver doesn't use mach specific APIs. I'm hoping that
we can send these all through arm-soc so driver maintainers please ack
Hello, Frederic,
Just realized that I could further decrease RT latency of one of my "shut
up RCU on NO_HZ_FULL CPUs" patches if I relied on CPU 0 always having
a scheduling-clock tick unless the entire system is idle. The trick
is that I could then rely on CPU 0 to detect RCU CPU stall
On Dec 4, 2013, at 7:23 PM, Vlad Yasevich wrote:
> On 12/04/2013 11:25 AM, Michael Tuexen wrote:
>> On Dec 4, 2013, at 5:12 PM, Vlad Yasevich wrote:
>>
>>> On 12/04/2013 11:01 AM, Michael Tuexen wrote:
On Dec 4, 2013, at 4:41 PM, Vlad Yasevich wrote:
> On 12/04/2013 09:50 AM,
The msm_sdcc driver uses mach specific dma APIs. This is not
compatible with the multi-platform ARM effort. Let's only compile
this driver on MSM devices that are prepared to support it,
allowing the DT based MSM devices to enter the multi-platform ARM
build.
Cc: Chris Ball
Signed-off-by:
The DT based MSM platforms can join the multi-platform builds, so
introduce a DT based ARCH_MSM option. This option allows DT based
MSM platforms to be built into the multi-platform kernel. Also
introduce a hidden ARCH_MSM config that both the DT and non-DT
platform support code select to avoid
The msm_serial_hs driver uses mach specific dma APIs. This is not
compatible with the multi-platform ARM effort. Let's only compile
this driver on MSM devices that are prepared to support it;
allowing the DT based MSM devices to enter the multi-platform ARM
build.
Cc: Greg Kroah-Hartman
On 11/18/2013 06:10 AM, Laxman Dewangan wrote:
> NVIDIA Tegra124 supports has the new gpio port as GPIO_FF.
> Add the macro for this port name.
I've applied this to Tegra's for-3.14/dt branch.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On 11/20/2013 07:40 PM, Alexandre Courbot wrote:
> FUSE clock is enabled by most bootloaders, but we cannot expect it to be
> on in all contexts (e.g. kexec).
>
> Ensure the FUSE clock is enabled before any of its registers is touched.
> Since FUSE is touched very early during system boot (before
On Fri, Nov 22, 2013 at 07:23:39PM -0800, Eric W. Biederman wrote:
>
> > [..]
> >> >> There is also a huge missing piece of this in that your purgatory is not
> >> >> checking a hash of the loaded image before jumping too it. Without that
> >> >> this is a huge regression at least for the kexec
On Thu, Nov 28, 2013 at 1:26 AM, Peter Crosthwaite
wrote:
> Hi All,
>
> These two patches support the case where an interrupt controller is
> marked as disabled. Patch 1 fixed the dts interrupt-map search logic to
> ignore disabled interrupt controllers. Patch 2 stops disabled interrupt
>
To help avoid an architecture failing to correctly check kernel/user
boundaries when handling copy_to_user, copy_from_user, put_user, or
get_user, perform some simple tests and fail to load if any of them
behave unexpectedly.
Specifically, this is to make sure there is a way to notice if things
On Tue, Dec 3, 2013 at 7:52 AM, Sebastian Hesselbarth
wrote:
> Currently, of_match_node compares each given match against all node's
> compatible strings with of_device_is_compatible.
>
> To achieve multiple compatible strings per node with ordering from
> specific to generic, this requires given
This is a pair of test modules I'd like to see in the tree. Instead
of putting these in lkdtm, where I've been adding various tests that
trigger crashes, these don't make sense there since they need to be
either distinctly separate, or their pass/fail state don't need to crash
the machine.
These
201 - 300 of 1540 matches
Mail list logo
