The granular residue accounting code uses certain variables specifically
for residue accounting. Document these in the structure declaration.
Also move around some elements and group them together.
Cc: Thomas Gleixner
Signed-off-by: Joel Fernandes
---
drivers/dma/edma.c | 26
edma param struct is now within an edma_pset struct introduced in Thomas
Gleixner's edma tx status series. Update memcpy function for the same.
Cc: Thomas Gleixner
Signed-off-by: Joel Fernandes
---
drivers/dma/edma.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Mon, 28 Apr 2014, Austin Schuh wrote:
> On Mon, Apr 7, 2014 at 1:08 PM, Austin Schuh wrote:
> > On Mon, Apr 7, 2014 at 1:07 PM, Thomas Gleixner wrote:
> >> On Mon, 7 Apr 2014, Austin Schuh wrote:
> >>> You originally sent the patch out. I could send your patch out back
> >>> to you, but that
On 4/28/2014 3:40 AM, Zhang Rui wrote:
On Mon, 2014-04-28 at 00:01 +0200, Rafael J. Wysocki wrote:
On Tuesday, April 08, 2014 12:06:49 AM Zhang Rui wrote:
[...]
+
+static int acpi_pnp_scan_handler_attach(struct acpi_device *adev,
+ const struct
On 4/28/2014 4:07 AM, Zhang Rui wrote:
On Mon, 2014-04-28 at 00:26 +0200, Rafael J. Wysocki wrote:
On Tuesday, April 08, 2014 12:06:59 AM Zhang Rui wrote:
For some devices with scan handler attached, their children devices
are enumerated by the scan handler, indirectly.
This isn't the case
On 4/28/2014 3:57 AM, Zhang Rui wrote:
On Mon, 2014-04-28 at 00:21 +0200, Rafael J. Wysocki wrote:
On Tuesday, April 08, 2014 12:06:56 AM Zhang Rui wrote:
For ACPI PIC (PNP) and Timer (PNP0100) device objects, although
they have _HID control method, but they should not be enumerated to
t; This is due to Rik's "#include " getting lost somehow.
> This #include is needed in drivers/tty/sysrq.c.
>
> But maybe I need to be using some other branch of linux-next. Am currently
> on 5bd4e10b96ce20271688aa31d8bd739441249152, which is origin/master. And
> is also
From: Alan
This is needed for some of the Xeon Phi type systems.
Signed-off-by: Alan Cox
---
drivers/pci/setup-bus.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/pci/setup-bus.c b/drivers/pci/setup-bus.c
index 138bdd6..5679ec2 100644
---
On 4/28/2014 5:02 AM, Zheng, Lv wrote:
Hi, Rafael
From: linux-acpi-ow...@vger.kernel.org
[mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Rafael J. Wysocki
Sent: Monday, April 28, 2014 5:37 AM
To: Zheng, Lv
On Wednesday, April 23, 2014 02:54:06 PM Lv Zheng wrote:
There is a mis-order
On 14/04/28, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the net-next tree got a conflict in
> net/netlink/af_netlink.c between commit 5187cd055b6e ("netlink: Rename
> netlink_capable netlink_allowed") from the net tree and commit
> 4f520900522f ("netlink: have netlink
Thanks...
Again, the change in riprel_analyze() needs the review from someone
who understands the instruction decoding/encoding.
On 04/28, Denys Vlasenko wrote:
>
> Otherwise, instructions such as cmpxchg and div will be mishandled.
It seems that you are right. But it would be really great if
On 4/28/2014 6:10 AM, Zheng, Lv wrote:
Hi, Rafael
From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
Sent: Monday, April 28, 2014 5:39 AM
On Wednesday, April 23, 2014 02:54:22 PM Lv Zheng wrote:
There are _LINUX defined so that when Linux kernel is compiled using broken
compilers that
Replace ((x) >> PAGE_SHIFT) by pfn macro.
Cc: Andrew Morton
Signed-off-by: Fabian Frederick
---
mm/memory_hotplug.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index a650db2..b756740 100644
--- a/mm/memory_hotplug.c
+++
Replace ((x) >> PAGE_SHIFT) by pfn macro.
Cc: Andrew Morton
Signed-off-by: Fabian Frederick
---
mm/memblock.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/mm/memblock.c b/mm/memblock.c
index e9d6ca9..b459009 100644
--- a/mm/memblock.c
+++ b/mm/memblock.c
@@ -1329,9
Initialize vmpressure_win in vmstat using
calculate_normal_threshold() based on each zone/cpu * SWAP_CLUSTER_SIZE
Value refreshed through cpu notifier
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Fabian Frederick
---
mm/vmpressure.c | 16 +---
mm/vmstat.c | 24
On Mon, Apr 7, 2014 at 1:08 PM, Austin Schuh wrote:
> On Mon, Apr 7, 2014 at 1:07 PM, Thomas Gleixner wrote:
>> On Mon, 7 Apr 2014, Austin Schuh wrote:
>>> You originally sent the patch out. I could send your patch out back
>>> to you, but that feels a bit weird ;)
>>
>> Wheee. Let me dig in my
On Mon, 2014-04-28 at 20:37 +0100, Will Deacon wrote:
> On Mon, Apr 28, 2014 at 04:52:42PM +0100, Antonios Motakis wrote:
> > The ARM SMMU can take an IOMMU_EXEC protection flag in addition to
> > IOMMU_READ and IOMMU_WRITE. Expose this as an IOMMU capability.
>
> The other way of handling this
And of course, I forgot to add Hugh ;) Fix that.
On 04/28, Oleg Nesterov wrote:
>
> valid_vma() rejects the VM_SHARED vmas, but this still allows to insert
> a probe into the MAP_SHARED but not VM_MAYWRITE vma.
>
> Currently this is fine, such a mapping doesn't really differ from the
> private
Fixing some comment errors.
Cc: Andrew Morton
Signed-off-by: Fabian Frederick
---
fs/befs/btree.c | 4 ++--
fs/befs/datastream.c | 2 +-
fs/befs/linuxvfs.c | 16
3 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/fs/befs/btree.c b/fs/befs/btree.c
index
Before this change, you had to check kernel log messages to see if the
non-blocking pool had been properly initialized. With this change, you
can consult the file /proc/sys/kernel/random/intialized instead.
Signed-off-by: Florian Weimer
---
drivers/char/random.c | 19 +++
1
On Mon 28-04-14 15:36:42, Steven Rostedt wrote:
> On Mon, 28 Apr 2014 21:24:16 +0200
> Jan Kara wrote:
>
>
> > So I had a look and we are missing mutex_release() in
> > console_trylock_for_printk() if we don't have a console to print to.
> > Attached patch should fix the problem.
> >
>
>
On Mon, Apr 28, 2014 at 08:03:35PM +0100, Will Deacon wrote:
> By the time rcutorture is initialised via its module_init callback, the
> .init.text section of torture.ko has already been freed, so the calls to
> torture_init{begin,end} end up branching to junk.
>
> This patch removes the __init
On 28/04/14 18:44, Colin Cross wrote:
>>> Is that case documented somewhere in the code comments?
>>
>> Perhaps not near enough to the _nolock but the primary bit of comment is
>> here (and in same file as kdb_sr).
>> --- cut here ---
>> * kdb_main_loop - After initial setup and assignment of the
On Tue, 2014-02-11 at 12:32 -0500, Christopher Covington wrote:
> Hi Pawel,
>
> On 02/11/2014 11:53 AM, Pawel Moll wrote:
> > This patch tries to solve that issue in a generic way,
> > adding a "populated" flag which is set in the device_node
> > structure when a device is being created in the
On Mon, 2014-04-28 at 20:19 +0100, Will Deacon wrote:
> Hi Alex,
>
> On Mon, Apr 28, 2014 at 05:43:41PM +0100, Alex Williamson wrote:
> > On Mon, 2014-04-28 at 17:52 +0200, Antonios Motakis wrote:
> > > This allows to make use of the VFIO_IOMMU_TYPE1 driver with platform
> > > devices on ARM in
k/public_git/linux-next/drivers/tty/sysrq.c:558: undefined
reference to `rcu_sysrq_end'
This is due to Rik's "#include " getting lost somehow.
This #include is needed in drivers/tty/sysrq.c.
But maybe I need to be using some other branch of linux-next. Am currently
on 5bd4e10b96ce20271688a
On 04/28/2014 09:39 PM, Thomas Gleixner wrote:
> On Sat, 26 Apr 2014, Sebastian Hesselbarth wrote:
>
>> Non-DT irq handlers were working through irq causes from most-significant
>> to least-significant bit, while DT irqchip driver does it the other way
>> round. This revealed some more HW issues
> -Original Message-
> From: David Miller [mailto:da...@davemloft.net]
> Sent: Monday, April 28, 2014 10:24 AM
> To: KY Srinivasan
> Cc: net...@vger.kernel.org; linux-kernel@vger.kernel.org;
> de...@linuxdriverproject.org; o...@aepfle.de; a...@canonical.com;
> jasow...@redhat.com;
gt; >
> > [0.00] BIOS-e820: [mem 0xe000-0x]
> > reserved
> > [0.00]
> > [0.00] =
> > [0.00] [ INFO: possible recursive
> From: linux-usb-ow...@vger.kernel.org
> [mailto:linux-usb-ow...@vger.kernel.org] On Behalf Of Felipe Balbi
> Sent: Monday, April 28, 2014 8:56 AM
>
> On Mon, Apr 28, 2014 at 04:49:23PM -0400, Zhuang Jin Can wrote:
> > Adds a debugfs file "snapshot" to dump dwc3 requests, trbs and events.
<
From: "K. Y. Srinivasan"
Date: Fri, 25 Apr 2014 20:55:23 -0700
> @@ -467,6 +467,9 @@ static int netvsc_start_xmit(struct sk_buff *skb, struct
> net_device *net)
> if (skb_is_gso(skb))
> goto do_lso;
>
> + if (skb->ip_summed != CHECKSUM_PARTIAL)
> + goto
In "Device Tree powered" systems, platform devices are usually
massively populated with of_platform_populate() call, executed
at some level of initcalls, either by generic architecture
or by platform-specific code.
There are situations though where certain devices must be
created (and bound with
Greetings,
What follows is the (hopefully) last take on the vexpress
infrastructure changes. With the exception of the first
patch, everything else has been discussed and acked
(or at least not naked) in the past:
http://thread.gmane.org/gmane.linux.kernel/1645586/
The last reason for static memory mapping is the HBI (board
identification number) check early in the machine code.
Moving the check to the sysreg driver makes it possible to
completely remove the early mapping and init functions.
Signed-off-by: Pawel Moll
---
arch/arm/mach-vexpress/v2m.c |
As all cores must be properly described in the Device Tree,
there is no point in getting their numbers from SCU on
A5/A9 platforms. This significantly simplifies the code,
removing the need for flat-tree scanning and early static
mapping.
Signed-off-by: Pawel Moll
---
Hi Felipe,
On Mon, Apr-14-2014 at 10:12:56 PM +0200, Apelete Seketeli wrote:
> Document the process of writing an musb glue layer by taking the
> Ingenic JZ4740 glue layer as an example, as it seems more simple than
> most glue layers due to the basic feature set of the JZ4740 USB device
>
From: Sudeep KarkadaNagesha
arm_dt_init_cpu_maps parses the device tree, validates and sets the
cpu_possible_mask appropriately. It is unnecessary to do another DT
parse to get the number of cpus, use num_possible_cpus instead.
This patch also removes setting cpu_present_mask as platforms
This patch - finally, after over 6 months! :-( - addresses
Samuel's request to split the vexpress-sysreg driver into
smaller portions and define the device in a form of MFD
cells:
* LEDs code has been completely removed and replaced with
"gpio-leds" nodes in the tree (referencing dedicated
Components of the Versatile Express platform (configuration
microcontrollers on motherboard and daughterboards in particular)
talk to each other over a custom configuration bus. They
provide miscellaneous functions (from clock generator control
to energy sensors) which are represented as platform
Move the Kconfig entry for Versatile (& Express) clock drivers
into a separate file and add individual options for sp810
and vexpress_osc drivers, as they are optional in some
configurations and may have separate dependencies.
Cc: Mike Turquette
Signed-off-by: Pawel Moll
---
> BTW some of the functions have already lost their asmlinkage, see
> commit 8783dd3a37a5853689e1a8fa728827a50905b912 ("irqchip: Remove
> asmlinkage from static functions") in torvalds tree and also recent
> thread https://lkml.org/lkml/2014/4/16/453 ("[PATCH] crypto:
> sha{256,512}_ssse3 - remove
Define syscon platform data structure that can be used
to define a regmap config name. This is particularly useful
in the regmap debugfs when there is more than one syscon
device registered, to distinguish the register blocks.
Signed-off-by: Pawel Moll
Acked-by: Lee Jones
---
Use devm_hwmon_device_register_with_groups instead of
the old-style manual attributes and hwmon device registration.
Also, unwind the attribute group macros for better code
readability.
Cc: Jean Delvare
Cc: Guenter Roeck
Cc: lm-sens...@lm-sensors.org
Signed-off-by: Pawel Moll
---
This patch adds a trival sched clock source using free
running, 24MHz clocked counter present in the ARM Ltd.
reference platforms (Versatile, RealView, Versatile
Express) System Registers block.
This code replaces the call in the VE machine code.
Cc: Daniel Lezcano
Cc: Thomas Gleixner
On Tue, Apr 29, 2014 at 1:27 AM, Boris BREZILLON
wrote:
>
> On 28/04/2014 18:02, Chen-Yu Tsai wrote:
>> Hi,
>>
>> On Mon, Apr 28, 2014 at 10:58 PM, Boris BREZILLON
>> wrote:
>>> Add DT definitions for PRCM (Power/Reset/Clock Management) clock and reset
>>> controller subdevices.
>>>
>>>
spidev device registration has always been a controversial subject since the
move to DT.
Obviously, a spidev node has nothing to do in the DT, and the position so far
has been to add the compatible of the devices to drive through spidev to the
list of the compatibles spidev can handle.
While
This is a bug fix that has been lurking in the Google tree but not pushed
upstream.
From: Octavian Purdila
The memory region is already reserved in goldfish_init() during
platform init.
Signed-off-by: Octavian Purdila
Signed-off-by: Jun Tian
Signed-off-by: Alan Cox
---
No objections?
Then I assume this is OK...
Helge
On 04/17/2014 10:45 PM, Helge Deller wrote:
> Would the following patch be acceptable?
> It adds an additional field to struct address_space which will most likely
> only
> be used by the parisc arch.
>
> If it's acceptable, I would like to push
On Thu, Apr 24, 2014 at 05:00:15PM -0400, Don Zickus wrote:
> On Thu, Apr 24, 2014 at 10:41:39PM +0900, Namhyung Kim wrote:
> > Hi Don,
> >
> > 2014-04-23 (수), 08:58 -0400, Don Zickus:
> > > On Wed, Apr 23, 2014 at 03:15:35PM +0900, Namhyung Kim wrote:
> > > > On Tue, 22 Apr 2014 17:16:47 -0400,
Commit-ID: 3894e9e82dfdc87fa35dc7976e0472d220228826
Gitweb: http://git.kernel.org/tip/3894e9e82dfdc87fa35dc7976e0472d220228826
Author: Dan Carpenter
AuthorDate: Thu, 3 Apr 2014 10:21:34 +0300
Committer: Thomas Gleixner
CommitDate: Mon, 28 Apr 2014 21:43:24 +0200
irqchip: irq-crossbar:
On Mon, 2014-04-28 at 19:50 +0100, Marc Zyngier wrote:
> Commit d57c33c5daa4 (add generic fixmap.h) added (among other
> similar things) set_fixmap_io to deal with early ioremap of devices.
>
> More recently, commit bf4b558eba92 (arm64: add early_ioremap support)
> converted the arm64 earlyprintk
On Mon, 2014-04-28 at 12:54 -0500, Felipe Balbi wrote:
> On Mon, Apr 28, 2014 at 08:52:48PM +0300, Ivan T. Ivanov wrote:
> > On Mon, 2014-04-28 at 12:03 -0500, Felipe Balbi wrote:
> > > On Mon, Apr 28, 2014 at 09:00:43PM +0400, Sergei Shtylyov wrote:
> > > > Hello.
> > > >
> > > > On 04/28/2014
On Mon, 2014-04-28 at 17:52 +0200, Antonios Motakis wrote:
> VFIO returns a file descriptor which we can use to manipulate the memory
> regions of the device. Since some memory regions we cannot mmap due to
> security concerns, we also allow to read and write to this file descriptor
> directly.
Currently, the fl_owner isn't set for flock locks. Some filesystems use
byte-range locks to simulate flock locks and there is a common idiom in
those that does:
fl->fl_owner = (fl_owner_t)filp;
fl->fl_start = 0;
fl->fl_end = OFFSET_MAX;
Since flock locks are generally "owned" by the
On Mon, 2014-04-28 at 17:52 +0200, Antonios Motakis wrote:
> Adds support to mask interrupts, and also for automasked interrupts.
> Level sensitive interrupts are exposed as automasked interrupts and
> are masked and disabled automatically when they fire.
>
> Signed-off-by: Antonios Motakis
>
On Mon, 2014-04-28 at 17:52 +0200, Antonios Motakis wrote:
> Allow to memory map the MMIO regions of the device so userspace can
> directly access them.
>
> Signed-off-by: Antonios Motakis
> ---
> drivers/vfio/platform/vfio_platform.c | 40
> ++-
> 1 file
On Mon, Apr 28, 2014 at 04:52:42PM +0100, Antonios Motakis wrote:
> The ARM SMMU can take an IOMMU_EXEC protection flag in addition to
> IOMMU_READ and IOMMU_WRITE. Expose this as an IOMMU capability.
The other way of handling this would be to negate the capability and
advertise a NOEXEC cap
On Mon, 28 Apr 2014 21:24:16 +0200
Jan Kara wrote:
> So I had a look and we are missing mutex_release() in
> console_trylock_for_printk() if we don't have a console to print to.
> Attached patch should fix the problem.
>
Note, your patch changes the logic a bit. It causes the
On Sat, 26 Apr 2014, Sebastian Hesselbarth wrote:
> Non-DT irq handlers were working through irq causes from most-significant
> to least-significant bit, while DT irqchip driver does it the other way
> round. This revealed some more HW issues on Kirkwood peripheral IP, where
> spurious sdio irqs
On Fri, Apr 25, 2014 at 07:40:04PM +0200, Mathieu Souchaud wrote:
> Check return code of every function called.
>
> Signed-off-by: Mathieu Souchaud
> ---
> arch/x86/kernel/cpu/mcheck/mce.c | 30 +++---
> 1 file changed, 23 insertions(+), 7 deletions(-)
>
> diff --git
OK, this is my current theory as to what's going on. I'd appreciate any
comments.
We have an event, let's call it #16.
Event #16 is a SW event created and running in the parent on CPU0.
CPU0 (parent): calls fork()
CPU6 (child): SW Event #16 is still running on CPU0 but is visible
On Mon, Apr 28, 2014 at 3:24 AM, Daniel Thompson
wrote:
> On 25/04/14 17:45, Steven Rostedt wrote:
>> On Fri, 25 Apr 2014 17:29:22 +0100
>> Daniel Thompson wrote:
>>
>>> If kdb is triggered using SysRq-g then any use of the sr command results
>>> in the SysRq key table lock being recursively
On Mon, 2014-04-28 at 22:27 +0800, Lan Tianyu wrote:
> From: Lv Zheng
>
> The size of the buffer allocated for generic_serial_bus region access
> is not correct. This patch introduces acpi_ex_get_serial_access_length()
> to be invoked to obtain correct data buffer length. Reported by
> Lan
Commit-ID: 8cc3cfc5ccf1680b7c88f874912b6bec2797b76b
Gitweb: http://git.kernel.org/tip/8cc3cfc5ccf1680b7c88f874912b6bec2797b76b
Author: Thomas Gleixner
AuthorDate: Tue, 4 Mar 2014 20:43:41 +
Committer: Thomas Gleixner
CommitDate: Mon, 28 Apr 2014 21:27:15 +0200
irqchip: armanda:
On Thu, 2014-02-13 at 13:15 -0600, Rob Herring wrote:
> On Tue, Feb 11, 2014 at 10:53 AM, Pawel Moll wrote:
> > In "Device Tree powered" systems, platform devices are usually
> > massively populated with of_platform_populate() call, executed
> > at some level of initcalls, either by generic
On Sun, 2014-04-27 at 14:01 +0530, Preeti Murthy wrote:
> Hi Jason, Peter,
>
> The below patch looks good to me except for one point.
>
> In idle_balance() the below code snippet does not look right:
>
> - if (pulled_task || time_after(jiffies, this_rq->next_balance)) {
> - /*
> - * We are
On Mon, Apr 28, 2014 at 01:26:46PM +0100, Lee Jones wrote:
> > This patch moves Exynos PMU driver implementation from
> > "arm/mach-exynos" to "drivers/mfd".
> > This driver is mainly used for setting misc bits of register from PMU IP
> > of Exynos SoC which will be required to configure before
On 28/04/2014 20:03, Chen-Yu Tsai wrote:
> On Tue, Apr 29, 2014 at 1:14 AM, Boris BREZILLON
> wrote:
>> Hi Chen-Yu,
>>
>> On 28/04/2014 17:59, Chen-Yu Tsai wrote:
>>> Hi,
>>>
>>> On Mon, Apr 28, 2014 at 10:58 PM, Boris BREZILLON
>>> wrote:
The PRCM (Power/Reset/Clock Management) unit
On 04/23/2014 10:46 AM, Tomasz Figa wrote:
> This patch introduces generic code to perform power domain look-up using
> device tree and automatically bind devices to their power domains.
> Generic device tree binding is introduced to specify power domains of
> devices in their device tree nodes.
>
On Mon, Apr 28, 2014 at 01:43:31PM -0400, Steven Rostedt wrote:
>
> Peter,
>
> Things have changed with regard to printk() in linux-next. Now it
> appears that lockdep is going haywire over it. I don't understand the
> exact reason for the lockdep_off() and lockdep_on() logic that is in
>
On Fri, 25 Apr 2014, Jason Cooper wrote:
> On Thu, Apr 24, 2014 at 06:04:41PM +0200, Gregory CLEMENT wrote:
> >
> > I have just noticed that this patch was not merged in 3.15.
> > Actually it is not in the core/irq branch of tip.git with
> > the other patches of the same series.
> > Is there any
On Thu, 24 Apr 2014, Vince Weaver wrote:
> I got the bug to trigger again, this time it finally managed to hit a
> debug_objects WARNING if that's any additional help.
>
> The bug followed the same pattern, software event
> (PERF_TYPE_SOFTWARE / PERF_COUNT_SW_TASK_CLOCK) created, fork
On 04/28/2014 07:06 PM, Denys Vlasenko wrote:
> + * Note: we can't use rax or rdx registers as scratch!
> + * There are 3-operand insns which use rax or rdx:rax
> + * as an implicit operand, _and_ they use modrm byte
> + * whose reg field indicates third register or opcode
Performing vma lookups without taking the mm->mmap_sem is asking
for trouble. While doing the search, the vma in question can
be modified or even removed before returning to the caller.
Take the lock in order to avoid races while iterating through
the vmacache and/or rbtree.
Also do some very
On Mon, Apr 28, 2014 at 08:47:27PM +0200, Christian Engelmayer wrote:
> Pointer 'pbpctl_dev_c' in function bypass_init_module() is unused. Thus remove
> it. With the last variable declaration gone, there is no more need for an own
> block. Remove it and adapt the indenting accordingly.
>
>
During frequency transitions, the cpufreq core takes the responsibility of
invoking cpufreq_freq_transition_begin() and cpufreq_freq_transition_end()
for those cpufreq drivers that define the ->target_index callback but don't
set the ASYNC_NOTIFICATION flag.
The powernow-k7 cpufreq driver falls
On Mon, 2014-04-28 at 10:52 -0700, Adam Williamson wrote:
> On Mon, 2014-04-28 at 22:27 +0800, Lan Tianyu wrote:
> > From: Lv Zheng
> >
> > The size of the buffer allocated for generic_serial_bus region access
> > is not correct. This patch introduces acpi_ex_get_serial_access_length()
> > to
During frequency transitions, the cpufreq core takes the responsibility of
invoking cpufreq_freq_transition_begin() and cpufreq_freq_transition_end()
for those cpufreq drivers that define the ->target_index callback but don't
set the ASYNC_NOTIFICATION flag.
The longhaul cpufreq driver falls
During frequency transitions, the cpufreq core takes the responsibility of
invoking cpufreq_freq_transition_begin() and cpufreq_freq_transition_end()
for those cpufreq drivers that define the ->target_index callback but don't
set the ASYNC_NOTIFICATION flag.
The powernow-k6 cpufreq driver falls
Some cpufreq drivers were redundantly invoking the _begin() and _end()
APIs around frequency transitions, and this double invocation (one from
the cpufreq core and the other from the cpufreq driver) used to result
in a self-deadlock, leading to system hangs during boot. (The _begin()
API makes
On 04/28/2014 07:34 PM, Oleg Nesterov wrote:
> Thanks...
>
> Again, the change in riprel_analyze() needs the review from someone
> who understands the instruction decoding/encoding.
>
> On 04/28, Denys Vlasenko wrote:
>>
>> Otherwise, instructions such as cmpxchg and div will be mishandled.
>
>
On Mon 28-04-14 14:14:39, Steven Rostedt wrote:
> On Mon, 28 Apr 2014 19:51:39 +0200
> Jan Kara wrote:
>
> > On Mon 28-04-14 13:43:31, Steven Rostedt wrote:
> > > Things have changed with regard to printk() in linux-next. Now it
> > > appears that lockdep is going haywire over it. I don't
The value of 'max_multiplier' is meant to be used for comparison with
clock_ratio[index].driver_data, not the index itself! Fix the code in
powernow_k6_cpu_exit() that has this bug.
Also, while at it, make the for-loop condition look for CPUFREQ_TABLE_END,
instead of hard-coding the loop count to
Hi,
Meelis Roos reported hangs during boot in the longhaul cpufreq driver, after
commit 12478cf0c55 (cpufreq: Make sure frequency transitions are serialized).
The root-cause of this issue is the extra invocation of the
cpufreq_freq_transition_begin() and cpufreq_freq_transition_end() APIs in the
On 28 Apr 2014, Hannes Frederic Sowa uttered the following:
> On Mon, Apr 28, 2014 at 04:35:38PM +0100, Nix wrote:
>> /proc/$pid/stack of the two communicating ssh daemons was instructive:
>>
>> [] unix_wait_for_peer+0x9f/0xbc
>> [] unix_dgram_sendmsg+0x41b/0x534
>
> This one is a dgram
On Mon, Apr 21, 2014 at 10:58 AM, Randy Dunlap wrote:
> [adding more patch committers]
>
> On 04/13/2014 12:05 PM, Stefani Seibold wrote:
>> Since some kernel version it is impossible to select the Enhanced Real
>> Time Clock Support (legacy PC RTC driver) because RTC_LIB is set by
>> default in
[ adding Ben ]
On Mon, Apr 28, 2014 at 10:22 AM, Ondrej Zary
wrote:
> On Monday 28 April 2014 18:51:44 Jiang, Dave wrote:
>> On Mon, 2014-04-28 at 16:28 +, Ondrej Zary wrote:
>> > On Monday 28 April 2014 17:50:29 Jiang, Dave wrote:
>> > > On Mon, 2014-04-28 at 13:03 +0200, Ondrej Zary wrote:
On 04/28, Denys Vlasenko wrote:
>
> On 04/28/2014 07:34 PM, Oleg Nesterov wrote:
> >
> > It seems that you are right. But it would be really great if you also
> > provide the test-case which proves the fix ;)
>
> Working on a testcase for this. So far covered div (test1)
> and cmpxchg (test2).
>
>
On Mon 28-04-14 23:53:28, Jianyu Zhan wrote:
> Hi, Michal,
>
> On Mon, Apr 28, 2014 at 10:54 PM, Michal Hocko wrote:
> > I really fail to see how that helps. compound_head is inlined and the
> > compiler should be clever enough to optimize the code properly. I
> > haven't tried that to be honest
On 28/04/2014 18:02, Chen-Yu Tsai wrote:
> Hi,
>
> On Mon, Apr 28, 2014 at 10:58 PM, Boris BREZILLON
> wrote:
>> Add DT definitions for PRCM (Power/Reset/Clock Management) clock and reset
>> controller subdevices.
>>
>> Signed-off-by: Boris BREZILLON
>> ---
>> arch/arm/boot/dts/sun6i-a31.dtsi
Hi,
This is a first review, from someone who's clearly not a DRM/KMS expert
but who already thought about this specific driver :-).
I strongly recommend that you wait for DRM/KMS maintainers and/or
experienced developers reviews before modifying anything ;-).
On 18/04/2014 11:45, Jean-Jacques
By the time rcutorture is initialised via its module_init callback, the
.init.text section of torture.ko has already been freed, so the calls to
torture_init{begin,end} end up branching to junk.
This patch removes the __init annotations from torture_init_{begin,end}
to make sure the code is there
On Mon, Apr 28, 2014 at 06:17:12PM +0200, Alexandre Belloni wrote:
> Add the pinctrl descriptions for both PWM channels of the Allwinner A20.
>
> Signed-off-by: Alexandre Belloni
Applied, thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
On Mon, 2014-04-28 at 17:52 +0200, Antonios Motakis wrote:
> A VFIO userspace driver will start by opening the VFIO device
> that corresponds to an IOMMU group, and will use the ioctl interface
> to get the basic device info, such as number of memory regions and
> interrupts, and their properties.
On Mon, 2014-04-28 at 17:52 +0200, Antonios Motakis wrote:
> Return information for the interrupts exposed by the device.
> This patch extends VFIO_DEVICE_GET_INFO with the number of IRQs
> and enables VFIO_DEVICE_GET_IRQ_INFO
>
> Signed-off-by: Antonios Motakis
> ---
>
valid_vma() rejects the VM_SHARED vmas, but this still allows to insert
a probe into the MAP_SHARED but not VM_MAYWRITE vma.
Currently this is fine, such a mapping doesn't really differ from the
private read-only mmap except mprotect(PROT_WRITE) won't work. However,
get_user_pages(FOLL_WRITE |
On 04/28/14 06:55, Paul E. McKenney wrote:
> On Sat, Apr 26, 2014 at 11:26:50PM -0700, Paul E. McKenney wrote:
>> On Fri, Apr 25, 2014 at 01:52:30PM -0700, Randy Dunlap wrote:
>>> On 04/25/14 13:44, Randy Dunlap wrote:
On 04/25/14 07:04, Rik van Riel wrote:
> On Thu, 24 Apr 2014 15:40:29
On 04/25/2014 10:59 PM, Meelis Roos wrote:
>> Meelis Roos reported hangs during boot in the longhaul cpufreq driver, after
>> commit 12478cf0c55 (cpufreq: Make sure frequency transitions are serialized).
>> The root-cause of this issue is the extra invocation of the
>>
Hi Alex,
On Mon, Apr 28, 2014 at 05:43:41PM +0100, Alex Williamson wrote:
> On Mon, 2014-04-28 at 17:52 +0200, Antonios Motakis wrote:
> > This allows to make use of the VFIO_IOMMU_TYPE1 driver with platform
> > devices on ARM in addition to PCI. This is required in order to use the
> > Exynos
On Sat, 26 Apr 2014 12:24:45 +0200
Pali Rohár wrote:
> Hello,
>
> on intel haswell mobile cpu it is not possible to load intel_rapl
> driver. Modprobe will show this error message:
>
> intel_rapl.ko': -1 No such device
> intel_rapl: driver does not support CPU family 6 model 60
>
> Is not
301 - 400 of 1754 matches
Mail list logo
