On Tue, Aug 6, 2013 at 8:14 AM, Namhyung Kim wrote:
> Run GTK hist and annotation browser using libdl.
>
> Cc: Andi Kleen
> Cc: Pekka Enberg
> Signed-off-by: Namhyung Kim
Reviewed-by: Pekka Enberg
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Tue, Aug 6, 2013 at 8:14 AM, Namhyung Kim wrote:
> Call setup/exit GTK browser function using libdl.
>
> Cc: Andi Kleen
> Cc: Pekka Enberg
> Signed-off-by: Namhyung Kim
Reviewed-by: Pekka Enberg
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Tue, Aug 6, 2013 at 8:14 AM, Namhyung Kim wrote:
> Separate out GTK codes to a shared object called libperf-gtk.so. This
> time only GTK codes are built with -fPIC and libperf remains as is.
>
> Cc: Andi Kleen
> Cc: Pekka Enberg
> Signed-off-by: Namhyung Kim
Reviewed-by: Pekka Enberg
--
On Tue, Aug 6, 2013 at 8:14 AM, Namhyung Kim wrote:
> From: Namhyung Kim
>
> The commit 2b8bfa6bb8a7 ("perf tools: Centralize default columns init
> in perf_hpp__init") moves initialization of common overhead column to
> perf_hpp__init() but forgot about the gtk code.
>
> So the gtk code added
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in
drivers/gpu/drm/i915/i915_gem.c between commit a70a3148b0c6 ("drm/i915:
Make proper functions for VMs") from the drm-intel tree and commit
e6950216e0af ("drivers: convert shrinkers to new count/scan API") from
the akpm tree.
On 08/06/2013 09:41 AM, David Ahern wrote:
> Hi Arnaldo:
>
> This round addresses all of Xiao's comments. It also includes a small
> change in the live mode introduction to improve ordered samples
> processing. For that a change in perf-session functions is needed.
Reviewed-by: Xiao Guangrong
I love emacs, but these settings for coding style are
annoying when trying to open the efi.h file. More important,
we already have checkpatch for that.
Signed-off-by: Davidlohr Bueso
---
block/partitions/efi.h | 19 ---
1 file changed, 19 deletions(-)
diff --git
Hi, Miles
On 08/06/2013 12:30 PM, Miles Lane wrote:
I am not seeing any problems in the behavior of the computer, but
wonder if this indicates something that needs fixing.
[1.969109] WARNING: CPU: 1 PID: 1 at kernel/time/tick-sched.c:185
can_stop_full_tick+0x7e/0x89()
According to the
Trivial coding style cleanups - still plenty left.
Signed-off-by: Davidlohr Bueso
---
block/partitions/efi.c | 19 ---
1 file changed, 8 insertions(+), 11 deletions(-)
diff --git a/block/partitions/efi.c b/block/partitions/efi.c
index 9a81c3b..8e6d77e 100644
---
One of the biggest problems with GPT is compatibility with older,
non-GPT systems. The problem is addressed by creating hybrid mbrs,
an extension, or variant, of the traditional protective mbr. This
contains, apart from the 0xEE partition, up three additional
primary partitions that point to the
The kernel's GPT implementation currently uses the generic
'struct partition' type for dealing with legacy MBR partition
records. While this is is useful for disklabels that we designed
for CHS addressing, such as msdos, it doesn't adapt well to newer
standards that use LBA instead, such as GUID
When detecting a valid protective MBR, the Linux kernel isn't picky about
the partition (1-4) the 0xEE is at, but, unlike other operating systems,
it does require it to begin at the second sector (sector 1). This check, apart
from it not being enforced by UEFI, and causing Linux to potentially
This patchset teaches the kernel about hybrid master boot records (MBRs), one of
the most common issues with GUID partition tables, as a workaround to layout
disk partitions to be compatible with both EFI and legacy MBR based systems.
Except for adding more pmbr checks, to better comply with the
Per the UEFI Specs 2.4, June 2013, the starting lba of the partition
that has the EFI GPT (0xEE) must be set to 0x0001 - this is obviously
the LBA of the GPT Partition Header.
Signed-off-by: Davidlohr Bueso
---
block/partitions/efi.c | 15 ---
1 file changed, 12 insertions(+), 3
The partition that has the 0xEE (GPT protective), must
have the size in lba field set to the lesser of the size
of the disk minus one or 0x for larger disks.
Signed-off-by: Davidlohr Bueso
---
block/partitions/efi.c | 21 ++---
1 file changed, 18 insertions(+), 3
When verifying GPT header integrity, make sure that
first usable LBA is smaller than last usable LBA.
Signed-off-by: Davidlohr Bueso
---
block/partitions/efi.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/block/partitions/efi.c b/block/partitions/efi.c
index
> -Original Message-
> From: Vinod Koul [mailto:vinod.k...@intel.com]
> Sent: Tuesday, August 06, 2013 12:25 PM
> To: Lu Jingchang-B35083
> Cc: d...@fb.com; shawn@linaro.org; linux-kernel@vger.kernel.org;
> linux-arm-ker...@lists.infradead.org; Wang Huan-B18965; Li Xiaochun-
> B41219
Separate out GTK codes to a shared object called libperf-gtk.so. This
time only GTK codes are built with -fPIC and libperf remains as is.
Cc: Andi Kleen
Cc: Pekka Enberg
Signed-off-by: Namhyung Kim
---
tools/perf/Makefile| 39 ---
Run GTK hist and annotation browser using libdl.
Cc: Andi Kleen
Cc: Pekka Enberg
Signed-off-by: Namhyung Kim
---
tools/perf/builtin-annotate.c | 26 +++---
tools/perf/builtin-report.c | 16 ++--
tools/perf/config/Makefile| 2 +-
Hi,
This is v2 of gtk code separation patchset to reduce library
dependencies of the perf executable.
I only built libperf-gtk.so with -fPIC, and it's not linked to libperf
at build time. All unresolved symbols used for perf should be
resolved at runtime via perf executable (so libperf.a) - I
Call setup/exit GTK browser function using libdl.
Cc: Andi Kleen
Cc: Pekka Enberg
Signed-off-by: Namhyung Kim
---
tools/perf/ui/gtk/gtk.h | 3 +++
tools/perf/ui/setup.c | 51 +++--
tools/perf/ui/ui.h | 12 +---
3 files changed, 53
From: Namhyung Kim
The commit 2b8bfa6bb8a7 ("perf tools: Centralize default columns init
in perf_hpp__init") moves initialization of common overhead column to
perf_hpp__init() but forgot about the gtk code.
So the gtk code added the same column to the list twice causing
infinite loop when
On Tue, Aug 6, 2013 at 12:37 PM, Rusty Russell wrote:
> Xiaotian Feng writes:
>> On Sat, Jul 27, 2013 at 3:26 PM, Xiaotian Feng wrote:
>>> If doms_new is NULL, partition_sched_domains() will reset ndoms_cur
>>> to 0, and free old sched domains with free_sched_domains(doms_cur,
>>> ndoms_cur).
On Tue, Aug 06, 2013 at 01:24:31AM +, Lu Jingchang-B35083 wrote:
> > -Original Message-
> > From: Vinod Koul [mailto:vinod.k...@intel.com]
> > Sent: Tuesday, August 06, 2013 12:35 AM
> > To: Lu Jingchang-B35083
> > Cc: d...@fb.com; shawn@linaro.org; linux-kernel@vger.kernel.org;
>
While I'm porting a new mach for ARM. I hit a case to produce
"Inconsistent kallsyms data".
I try to find out the solution and then get an interesting case is
about "array name length"
Kernel is 3.4.56 and gcc version 4.3.5 (Buildroot 2010.11)
While register serial8250 platform device, the code
From: Sahara
The advantage of using __print_symbolic() is that it allows both perf
and trace-cmd to read this event properly. Their parsers are not full C
parsers, and when you open code the the processing, they both will fail
to parse how to read the output, and will just default to printing
From: Sahara
This patch is to prevent the same __print_symbolic functions from
being used repeatedly.
Signed-off-by: Sahara
---
include/trace/events/power.h | 43 +
1 files changed, 22 insertions(+), 21 deletions(-)
diff --git
On Tue, Aug 06, 2013 at 07:26:10AM +0530, Aneesh Kumar K.V wrote:
> Naoya Horiguchi writes:
>
> > This patch is motivated by the discussion with Aneesh about "extend
> > hugepage migration" patchset.
> > http://thread.gmane.org/gmane.linux.kernel.mm/103933/focus=104391
> > I'll append this to
On 5 August 2013 18:17, Rafael J. Wysocki wrote:
> On Monday, August 05, 2013 07:29:09 AM Nishanth Menon wrote:
>> minor nitpick.
>> $subject: PM / OPP:
Stupid mistake.
> Those are things I can easily fix up when I'm applying the patch.
Thanks :)
--
To unsubscribe from this list: send the line
Xiaotian Feng writes:
> On Sat, Jul 27, 2013 at 3:26 PM, Xiaotian Feng wrote:
>> If doms_new is NULL, partition_sched_domains() will reset ndoms_cur
>> to 0, and free old sched domains with free_sched_domains(doms_cur,
>> ndoms_cur).
>> As ndoms_cur is 0, the cpumask will not be freed.
>>
>>
I am not seeing any problems in the behavior of the computer, but
wonder if this indicates something that needs fixing.
[1.969109] WARNING: CPU: 1 PID: 1 at kernel/time/tick-sched.c:185
can_stop_full_tick+0x7e/0x89()
[1.969121] NO_HZ FULL will not work with unstable sched clock
[
On Tue, Aug 06, 2013 at 07:22:02AM +0530, Aneesh Kumar K.V wrote:
> Naoya Horiguchi writes:
> >>
> >> Considering that we have architectures that won't support migrating
> >> explicit hugepages with this patch series, is it ok to use
> >> GFP_HIGHUSER_MOVABLE for hugepage allocation ?
> >
> >
On 08/05/2013 09:14 PM, Mathieu Desnoyers wrote:
>>
>> For unconditional jmp that should be pretty safe barring any fundamental
>> changes to the instruction set, in which case we can enable it as
>> needed, but for extra robustness it probably should skip prefix bytes.
>
> On x86-32, some
Hi Mike,
On Tue, Aug 6, 2013 at 4:53 AM, Mike Turquette wrote:
> Quoting Yadwinder Singh Brar (2013-07-07 04:44:20)
>> This patch adds support to register three(AP/CP/BT) buffered 32.768 KHz
>> outputs of mfd-s2mps11 with common clock framework.
>>
>> Signed-off-by: Yadwinder Singh Brar
>
>
* H. Peter Anvin (h...@linux.intel.com) wrote:
> On 08/05/2013 02:28 PM, Mathieu Desnoyers wrote:
> > * Linus Torvalds (torva...@linux-foundation.org) wrote:
> >> On Mon, Aug 5, 2013 at 12:54 PM, Mathieu Desnoyers
> >> wrote:
> >>>
> >>> I remember that choosing between 2 and 5 bytes nop in the
If node == NUMA_NO_NODE, pol is NULL, we should return NULL instead of
do "if (!pol->mode)" check.
Signed-off-by: Jianguo Wu
---
mm/mempolicy.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/mm/mempolicy.c b/mm/mempolicy.c
index 4baf12e..e0e3398 100644
--- a/mm/mempolicy.c
+++
Sudeep Dutt writes:
> On Mon, 2013-07-29 at 10:05 +0300, Michael S. Tsirkin wrote:
>> On Wed, Jul 24, 2013 at 08:31:34PM -0700, Sudeep Dutt wrote:
>> > From: Ashutosh Dixit
>> >
>> > This patch introduces the host "Virtio over PCIe" interface for
>> > Intel MIC. It allows creating user space
2013/8/5 Roland Dreier :
> From: Roland Dreier
>
> There is a nasty bug in the SCSI SG_IO ioctl that in some circumstances
> leads to one process writing data into the address space of some other
> random unrelated process if the ioctl is interrupted by a signal.
> What happens is the following:
From: Andy Green
warning-elimination: android: binder
This commit in mainline (now) causes a couple of warnings
commit 975a1ac9a9fe65d66ee1726c0db6dc58e53d232a
Author: Arve Hjønnevåg
Date: Tue Oct 16 15:29:53 2012 -0700
Staging: android: binder: Add some tracepoints
This patch fixes
>> diff --git a/arch/arm/boot/compressed/head.S
>> b/arch/arm/boot/compressed/head.S
>> index 75189f1..4c70b9e 100644
>> --- a/arch/arm/boot/compressed/head.S
>> +++ b/arch/arm/boot/compressed/head.S
>> @@ -122,19 +122,106 @@
>> .arm@ Always enter in ARM
On Mon, 2013-08-05 at 22:55 -0400, Steven Rostedt wrote:
> Some of my configs I test with have CONFIG_A11Y_BRAILLE_CONSOLE set.
> When I started testing against v3.11-rc4 my console went bonkers. Using
> ktest to bisect the issue, it came down to:
>
> commit bbeddf52a "printk: move braille
On Thu, Aug 1, 2013 at 10:51 PM, Casey Schaufler wrote:
> On 7/31/2013 7:48 PM, Balbir Singh wrote:
>> On Thu, Jul 25, 2013 at 11:52 PM, Casey Schaufler
>> wrote:
>>> Subject: [PATCH v14 0/6] LSM: Multiple concurrent LSMs
>>>
>>> Version 14 of this patchset is based on v3.10.
>>> It required
On Sun, Aug 4, 2013 at 9:37 PM, Tejun Heo wrote:
> cgroup_event is way over-designed and tries to build a generic
> flexible event mechanism into cgroup - fully customizable event
> specification for each user of the interface. This is utterly
> unnecessary and overboard especially in the light
On Thu, Aug 1, 2013 at 5:25 PM, Santosh Shilimkar
wrote:
> Most of the kernel code assumes that max*pfn is maximum pfns because
> the physical start of memory is expected to be PFN0. Since this
> assumption is not true on ARM architectures, the meaning of max*pfn
> is number of memory pages. This
This patch enables the x86 architecture to do lockless reference
count update using the generic lockref implementation with default
parameters. Only the x86/Kconfig file needs to be changed.
Signed-off-by: Waiman Long
---
arch/x86/Kconfig |3 +++
1 files changed, 3 insertions(+), 0
The current code takes the dentry's d_lock lock whenever the refcnt
is being updated. In reality, nothing big really happens until refcnt
goes to 0 in dput(). So it is not necessary to take the lock if the
reference count won't go to 0. On the other hand, there are cases
where refcnt should not be
This patch replaces the d_lock and d_count fields of the dentry
data structure by the combined d_lockcnt structure. A d_lock macro
is defined to remap the old d_lock name to the new d_lockcnt.lock
name. This is needed as a lot of files use the d_lock spinlock.
Read accesses to d_count are
v6->v7:
- Substantially reduce the number of patches from 14 to 4 because a
lot of the minor filesystem related changes had been merged to
v3.11-rc1.
- Remove architecture specific customization (LOCKREF_WAIT_SHIFT &
LOCKREF_RETRY_COUNT).
- Tune single-thread performance of
This patch introduces a new set of spinlock_refcount.h header files to
be included by kernel codes that want to do a faster lockless update
of reference count protected by a spinlock.
The new lockref structure consists of just the spinlock and the
reference count data. Helper functions are
I acked the following commit but I hit a problem by the commit.
So I report it.
commit cecdb193c8d91a42d9489d00618cc3dfff92e55a
Author: Rafael J. Wysocki
Date: Tue Jan 15 13:24:02 2013 +0100
ACPI / scan: Change the implementation of acpi_bus_trim()
Before applying the commit,
On Mon, 2013-08-05 at 22:26 -0400, Jason Baron wrote:
> I think if the 'cold' attribute on the default disabled static_key
> branch moved the text completely out-of-line, it would satisfy your
> requirement here?
>
> If you like this approach, perhaps we can make something like this work
>
Some of my configs I test with have CONFIG_A11Y_BRAILLE_CONSOLE set.
When I started testing against v3.11-rc4 my console went bonkers. Using
ktest to bisect the issue, it came down to:
commit bbeddf52a "printk: move braille console support into separate
braille.[ch] files"
Looking into the patch
At early time, memblock will reserve some memory for the kernel,
such as the kernel code and data segments, initrd file, and so on，
which means the kernel resides in these memory regions.
Even if these memory regions are hotpluggable, we should not
mark them as hotpluggable. Otherwise the kernel
On 08/06/2013 04:20 AM, H. Peter Anvin wrote:
So, having read through the entire thread I *think* this is what the
status of this patchset is:
1. Patches 1-17 are noncontroversial, Raghavendra is going to send an
update split into two patchsets;
Yes. Only one patch would be common to
On Sat, Jul 27, 2013 at 3:26 PM, Xiaotian Feng wrote:
> If doms_new is NULL, partition_sched_domains() will reset ndoms_cur
> to 0, and free old sched domains with free_sched_domains(doms_cur, ndoms_cur).
> As ndoms_cur is 0, the cpumask will not be freed.
>
> Signed-off-by: Xiaotian Feng
> Cc:
On 08/05/2013 10:52 PM, Tejun Heo wrote:
On Mon, Aug 05, 2013 at 02:22:47PM +0800, Tang Chen wrote:
I have resent the v2 patch-set. Would you please give some more
comments about the memblock and x86 booting code modification ?
Patch 13 still seems corrupt. Is it a problem on my side maybe?
On 08/05/2013 04:35 PM, Richard Henderson wrote:
On 08/05/2013 09:57 AM, Jason Baron wrote:
On 08/05/2013 03:40 PM, Marek Polacek wrote:
On Mon, Aug 05, 2013 at 11:34:55AM -0700, Linus Torvalds wrote:
On Mon, Aug 5, 2013 at 11:24 AM, Linus Torvalds
wrote:
Ugh. I can see the attraction of
On 2013/8/6 10:02, Li Zefan wrote:
>> static struct cftype mem_cgroup_files[] = {
>> {
>> .name = "usage_in_bytes",
>> @@ -5973,6 +6192,12 @@ static struct cftype mem_cgroup_files[] = {
>> .read_u64 = mem_cgroup_hierarchy_read,
>> },
>> {
>> +
On Mon, 2013-08-05 at 14:33 -0400, Jeff Layton wrote:
> On Mon, 5 Aug 2013 18:18:03 +
> "Myklebust, Trond" wrote:
>
> > On Mon, 2013-08-05 at 13:37 -0400, Jeff Layton wrote:
> > > On Mon, 5 Aug 2013 16:15:01 +
> > > "Myklebust, Trond" wrote:
> > >
> > > > From
(2013/08/06 9:15), Rafael J. Wysocki wrote:
On Monday, August 05, 2013 05:19:56 PM Toshi Kani wrote:
On Mon, 2013-08-05 at 15:14 +0200, Rafael J. Wysocki wrote:
:
Can you please test the appended patch? I tested it somewhat, but since the
greatest number of physical nodes per ACPI device
> static struct cftype mem_cgroup_files[] = {
> {
> .name = "usage_in_bytes",
> @@ -5973,6 +6192,12 @@ static struct cftype mem_cgroup_files[] = {
> .read_u64 = mem_cgroup_hierarchy_read,
> },
> {
> + .name = "cgroup.event_control",
> +
Naoya Horiguchi writes:
> This patch is motivated by the discussion with Aneesh about "extend
> hugepage migration" patchset.
> http://thread.gmane.org/gmane.linux.kernel.mm/103933/focus=104391
> I'll append this to the patchset in the next post, but before that
> I want this patch to be
Naoya Horiguchi writes:
>>
>> Considering that we have architectures that won't support migrating
>> explicit hugepages with this patch series, is it ok to use
>> GFP_HIGHUSER_MOVABLE for hugepage allocation ?
>
> Originally this parameter was introduced to make hugepage pool on
>
On Mon, Aug 05, 2013 at 09:29:37AM -0700, Kevin Hilman wrote:
> The SmartReflex AVS driver evolved out of the OMAP kernel and now
> lives under drivers/power/avs.
>
> I've historically been maintainer of this but Nishanth Menon is doing
> most of the heavy lifting now. Add us both as
"include/uapi/" is the whole Linux kernel API, it is important enough
to get more global explanations by comments.
In "include/uapi/Kbuild", "Makefile..." and "non-arch..." comments are
meaningless for current 'Kbuild', so delete them.
And add more explanations for "include/uapi/" in
Taking a lesson from perf-trace and bringing in control of event
processing to perf-kvm-stat-live: parse the sample to get access the
time leaving just the need to queue it to the ordered samples list.
For that the queue_event function needs to be exported.
Unexport perf_session__process_event.
Add an option to analyze a specific VM within a data file. This
allows the collection of kvm events for all VMs and then analyze
data for each VM (or set of VMs) individually.
Signed-off-by: David Ahern
Cc: Arnaldo Carvalho de Melo
Cc: Ingo Molnar
Cc: Frederic Weisbecker
Cc: Peter Zijlstra
Add max and min times for exit events.
v2: address Xia's comment to use get_event function for pulling max and
min from stats struct similar to mean and count
Signed-off-by: David Ahern
Cc: Arnaldo Carvalho de Melo
Cc: Ingo Molnar
Cc: Frederic Weisbecker
Cc: Peter Zijlstra
Cc: Jiri Olsa
This is useful to spot high latency blips. It is normal for HLT
reasons to have long exit times, so strip those from the threshold
check.
Signed-off-by: David Ahern
Cc: Arnaldo Carvalho de Melo
Cc: Ingo Molnar
Cc: Frederic Weisbecker
Cc: Peter Zijlstra
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc:
perf kvm stat currently requires back to back record and report commands
to see stats. e.g,.
perf kvm stat record -p $pid -- sleep 1
perf kvm stat report
This is inconvenvient for on box monitoring of a VM. This patch introduces
a 'live' mode that in effect combines the record plus report
Hi Arnaldo:
This round addresses all of Xiao's comments. It also includes a small
change in the live mode introduction to improve ordered samples
processing. For that a change in perf-session functions is needed.
David Ahern (5):
perf session: Export queue_event function
perf kvm: add live
Hi Daniel,
On Thu, Aug 01, 2013 at 07:48:04PM +0200, Daniel Lezcano wrote:
> On 08/01/2013 07:43 PM, Sören Brinkmann wrote:
> > On Thu, Aug 01, 2013 at 07:29:12PM +0200, Daniel Lezcano wrote:
> >> On 08/01/2013 01:38 AM, Sören Brinkmann wrote:
> >>> On Thu, Aug 01, 2013 at 01:01:27AM +0200,
> -Original Message-
> From: Vinod Koul [mailto:vinod.k...@intel.com]
> Sent: Tuesday, August 06, 2013 12:35 AM
> To: Lu Jingchang-B35083
> Cc: d...@fb.com; shawn@linaro.org; linux-kernel@vger.kernel.org;
> linux-arm-ker...@lists.infradead.org; Wang Huan-B18965; Li Xiaochun-
> B41219
>
On Tuesday, August 06, 2013 3:09 AM, Dongjin Kim wrote:
>
> This patch adds EHCI and OHCI host device nodes for Exynos4.
>
> CC: Jingoo Han
Acked-by: Jingoo Han
> Signed-off-by: Dongjin Kim
> ---
> arch/arm/boot/dts/exynos4.dtsi | 18 ++
> 1 file changed, 18
On Mon, 2013-08-05 at 14:08 +0300, Phil Carmody wrote:
> Lines with incorrect spacing around an operator, such as:
> bystander, correct,incorrect
> would get "fixed" to
> bystander,correct, incorrect
> as the correct argument as well as the incorrectly-spaced operator
> were both being
From: Roland Dreier
There is a nasty bug in the SCSI SG_IO ioctl that in some circumstances
leads to one process writing data into the address space of some other
random unrelated process if the ioctl is interrupted by a signal.
What happens is the following:
- A process issues an SG_IO ioctl
On Mon, 2013-08-05 at 19:30 +0300, Dan Carpenter wrote:
> On Mon, Aug 05, 2013 at 09:17:07AM -0700, Joe Perches wrote:
> > ov7670_read via i2c_transfer can return a positive # too.
> > Perhaps all of these should be individually tested for "< 0".
> You're misreading something. ov7670_read_i2c()
On Mon, Aug 05, 2013 at 03:42:22PM -0700, Stephen Hemminger wrote:
> On Tue, 6 Aug 2013 00:32:05 +0200
> Linus Lüssing wrote:
>
> > Currently we are reading an uninitialized value for the max_delay
> > variable when snooping an MLD query message of invalid length and would
> > update our timers
From: Rafael J. Wysocki
The error code path in acpi_unbind_one() is unnecessarily complicated
(in particular, the err label is not really necessary) and the error
message printed by it is inaccurate (there's nothing called
'acpi_handle' in that function), so clean up those things.
From: Rafael J. Wysocki
Clean up some inconsistent use of whitespace in acpi_bind_one() and
acpi_unbind_one().
Signed-off-by: Rafael J. Wysocki
---
drivers/acpi/glue.c |7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
Index: linux-pm/drivers/acpi/glue.c
From: Rafael J. Wysocki
Put the creation of symlinks in acpi_bind_one() under the
physical_node_lock mutex of the given ACPI device objects, because
that is part of the binding operation logically (those links are
already removed under that mutex too).
Signed-off-by: Rafael J. Wysocki
---
Hi All,
The following 5 patches clean up a little mess in acpi_bind_one() and
acpi_unbind_one(). They are on top of current linux-next plus the patch
at https://patchwork.kernel.org/patch/2839101/ .
[1/5] Move duplicated code from acpi_bind_one()/acpi_unbind_one() to a separate
function.
From: Rafael J. Wysocki
Since acpi_unbind_one() walks physical_node_list under the ACPI
device object's physical_node_lock mutex and the walk may be
terminated as soon as the matching entry has been found, it is
not necessary to use list_for_each_safe() for that walk, so use
From: Rafael J. Wysocki
Move some duplicated code from acpi_bind_one() and acpi_unbind_one()
into a separate function and make that function use snprintf()
instead of sprintf() for extra safety.
Signed-off-by: Rafael J. Wysocki
---
drivers/acpi/glue.c | 22 +++---
1 file
Roland,
When this sg code was originally designed, there wasn't a bio
in sight :-)
Now I'm trying to get my head around this. We have launched
a "data-in" SCSI command like READ(10) and the DMA is underway
so we are waiting for a "done" indication. Instead we receive
a signal interruption. It is
On 08/06/2013 04:41 AM, Jay Fenlason wrote:
> On Mon, Aug 05, 2013 at 12:59:04PM +1000, Alexey Kardashevskiy wrote:
>> Hi!
>>
>> Recently I started getting multiple errors like this:
>>
>> cxgb3 0006:01:00.0: iommu_alloc failed, tbl c3067980 vaddr
>> c01fbdaaa882 npages 1
>> cxgb3
On Mon, Aug 5, 2013 at 8:33 AM, Leif Lindholm wrote:
> On Mon, Aug 05, 2013 at 03:11:49PM +0100, Dave Martin wrote:
>> > diff --git a/arch/arm/boot/compressed/head.S
>> > b/arch/arm/boot/compressed/head.S
>> > index 75189f1..4c70b9e 100644
>> > --- a/arch/arm/boot/compressed/head.S
>> > +++
On Monday, August 05, 2013 05:19:56 PM Toshi Kani wrote:
> On Mon, 2013-08-05 at 15:14 +0200, Rafael J. Wysocki wrote:
> :
> > Can you please test the appended patch? I tested it somewhat, but since the
> > greatest number of physical nodes per ACPI device object I can get on my
> > test
> >
On Mon, Aug 5, 2013 at 7:12 AM, Dave Martin wrote:
> On Fri, Aug 02, 2013 at 02:29:02PM -0700, Roy Franz wrote:
>> The ARM kernel also has an EFI stub which works largely the same way
>> as the x86 stub, so move the documentation out of x86 directory and
>> update to reflect that it is generic,
Greg
Thanks for discussing the module with me. I think I'm now
closer to distilling it down to its essence.
GOAL:
The goal of this module is to give user space programs an
interface similar to that enjoyed by the kernel using procfs
and sysfs. All of the following should be possible
On Mon, Aug 05, 2013 at 05:43:47PM -0500, Rob Herring wrote:
> On Thu, Aug 1, 2013 at 5:20 PM, Russell King
> wrote:
> > We need to start treating DMA masks as something which is specific to
> > the bus that the device resides on, otherwise we're going to hit all
> > sorts of nasty issues with
On Mon, 2013-08-05 at 16:38 -0700, Roland Dreier wrote:
> On Mon, Aug 5, 2013 at 4:31 PM, James Bottomley
> wrote:
> > I agree with the analysis. The fix is a bit draconian, though. A
> > workqueue actually runs in a kernel thread and there's a simple test for
> > that (!current->mm), so how
On Mon, Aug 5, 2013 at 4:31 PM, James Bottomley
wrote:
> I agree with the analysis. The fix is a bit draconian, though. A
> workqueue actually runs in a kernel thread and there's a simple test for
> that (!current->mm), so how about this instead (which is much less
> intrusive)
> ---
> diff
On Mon, 2013-08-05 at 15:02 -0700, Roland Dreier wrote:
> From: Roland Dreier
>
> There is a nasty bug in the SCSI SG_IO ioctl that in some circumstances
> leads to one process writing data into the address space of some other
> random unrelated process if the ioctl is interrupted by a signal.
>
On Mon, 2013-08-05 at 15:10 -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> Check for const __devinitdata and non const __devinitconst
>
> People get this regularly wrong and it breaks the LTO builds,
> as it causes a section attribute conflict.
>
> This doesn't catch all mistakes -- spreading
Quoting Yadwinder Singh Brar (2013-07-07 04:44:20)
> This patch adds support to register three(AP/CP/BT) buffered 32.768 KHz
> outputs of mfd-s2mps11 with common clock framework.
>
> Signed-off-by: Yadwinder Singh Brar
Yadwinder,
Looks good to me with the exception of a binding description
On Mon, 2013-08-05 at 15:14 +0200, Rafael J. Wysocki wrote:
:
> Can you please test the appended patch? I tested it somewhat, but since the
> greatest number of physical nodes per ACPI device object I can get on my test
> machines is 2 (and even that after hacking the kernel somewhat), that was
On Mon, Aug 05, 2013 at 04:03:27PM -0700, H. Peter Anvin wrote:
> On 08/05/2013 03:02 PM, Andi Kleen wrote:
> > From: Andi Kleen
> >
> > A function pointer cannot be asmlinkage. Just drop it.
> >
> > Signed-off-by: Andi Kleen
>
> Eh? It certainly matters for the function pointer if it is
This patch adds basic board support for MSM8974 Dragonboard
which belongs to the Snapdragon 800 family.
For now, just support a basic machine with device tree.
Signed-off-by: Rohit Vaswani
---
arch/arm/boot/dts/Makefile| 3 ++-
arch/arm/boot/dts/msm8974-db.dts | 26
On 08/05/2013 03:02 PM, Andi Kleen wrote:
> From: Andi Kleen
>
> A function pointer cannot be asmlinkage. Just drop it.
>
> Signed-off-by: Andi Kleen
Eh? It certainly matters for the function pointer if it is regparm(0)
or regparm(3), and the pointed-to function definitely assumes
1 - 100 of 1482 matches
Mail list logo
