Hello,
last night I ran into an oops on -next-20140312. Hasn't occurred again since
and I don't have a clue on how to reproduce it either. Anyway, here it goes:
===
Mar 13 21:07:00 darkstar kernel: [10579.371582]
On Thu, 13 Mar 2014, Krzysztof Mazur wrote:
> Hi,
>
> The commit 3f2dc5ac05714711fc14f2bf0ee5e42d5c08c581 (drm/i915: Fix 915GM
> self-refresh enable/disable) causes strange regression on the HP Compaq
> nc6120. During and after boot to framebuffer console with just LVDS
> the screen is black
On 03/13/2014 04:51 AM, Christoffer Dall wrote:
> On Tue, Mar 11, 2014 at 02:05:38AM +0530, Srivatsa S. Bhat wrote:
>> Subsystems that want to register CPU hotplug callbacks, as well as perform
>> initialization for the CPUs that are already online, often do it as shown
>> below:
>>
>>
2014-03-12 6:20 GMT+08:00 Matthew Garrett :
> The existing SBS code explicitly sets the selected battery in the SBS
> manager regardless of whether the battery in question is already selected.
> This causes bus timeouts on Apple hardware. Check for this case and avoid
> it.
>
Hi Matthew:
On 03/13/2014 11:33 PM, Sören Brinkmann wrote:
> On Thu, 2014-03-13 at 03:16PM -0700, Sören Brinkmann wrote:
>> Hi Nicolas,
>>
>> I did some testing on the current linux-next tree and ran iperf on Zynq.
>> It seems that network and even the whole system can collapse when doing
>> that.
>> I don't
Thank you for you clarification, Steven.
-Takahiro AKASHI
On 03/14/2014 03:33 AM, Steven Rostedt wrote:
On Thu, 2014-03-13 at 18:10 +, Will Deacon wrote:
+#else /* CONFIG_DYNAMIC_FTRACE */
+/*
+ * _mcount() is used to build the kernel with -pg option, but all the branch
+ * instructions
On 03/14/2014 03:10 AM, Will Deacon wrote:
On Thu, Mar 13, 2014 at 10:13:48AM +, AKASHI Takahiro wrote:
This patch allows "dynamic ftrace" if CONFIG_DYNAMIC_FTRACE is enabled.
Here we can turn on and off tracing dynamically per-function base.
On arm64, this is done by patching single
From: "Lad, Prabhakar"
this patch fixes following build warning
drivers/media/platform/davinci/vpbe_display.c: In function
'vpbe_start_streaming':
drivers/media/platform/davinci/vpbe_display.c:344: warning: unused variable
'vpbe_dev'
Signed-off-by: Lad, Prabhakar
---
Some redundant error message is removed and some error messages
are changed to error level from debug level.
Signed-off-by: Cho KyongHo
---
drivers/iommu/exynos-iommu.c | 23 +--
1 file changed, 9 insertions(+), 14 deletions(-)
diff --git a/drivers/iommu/exynos-iommu.c
This commit changes the function to get MMU version simpler.
Signed-off-by: Cho KyongHo
---
drivers/iommu/exynos-iommu.c | 30 ++
1 file changed, 6 insertions(+), 24 deletions(-)
diff --git a/drivers/iommu/exynos-iommu.c b/drivers/iommu/exynos-iommu.c
index
For ARM926T, the value in the Makefile are assigned to arm9tdmi.
Actually all ARM9xxx are assigned by value arm9tdmi.
But in some cross compile GCC toolchains, such as from Buildroot, they
have different specified tune value
for example, in buildroot GCC
config BR2_GCC_TARGET_TUNE
...
default
This patch contains 2 workaround for the System MMU v3.x.
System MMU v3.2 and v3.3 has FLPD cache that caches first level page
table entries to reduce page table walking latency. However, the
FLPD cache is filled with a first level page table entry even though
it is not accessed by a master H/W
This commit introduces sysmmu_pte_t for page table entries and
sysmmu_iova_t vor I/O virtual address that is manipulated by
exynos-iommu driver. The purpose of the typedef is to remove
dependencies to the driver code from the change of CPU architecture
from 32 bit to 64 bit.
Signed-off-by: Cho
Use of __pa and __va macro is changed to virt_to_phys and phys_to_virt
which are recommended in driver code. printk formatting of physical
address is also fixed to %pa.
Signed-off-by: Cho KyongHo
---
drivers/iommu/exynos-iommu.c | 45 +++---
1 file changed,
Patch written by Antonios Motakis :
IOMMU groups are expected by certain users of the IOMMU API,
e.g. VFIO. Since each device is behind its own System MMU, we
can allocate a new IOMMU group for each device.
Reviewd-by: Cho KyongHo
Signed-off-by: Antonios Motakis
---
This adds support for Suspend to RAM and Runtime Power Management.
Since System MMU is located in the same local power domain of its
master H/W, System MMU must be initialized before it is working if
its power domain was ever turned off. TLB invalidation according to
unmapping on page tables must
Since acquiring read_lock is not more frequent than write_lock, it is
not beneficial to use rwlock, this commit changes rwlock to spinlock.
Reviewed-by: Grant Grundler
Signed-off-by: Cho KyongHo
---
drivers/iommu/exynos-iommu.c | 39 ---
1 file changed, 20
Some master device descriptor like fimc-is which is an abstraction
of very complex H/W may have multiple System MMUs. For those devices,
the design of the link between System MMU and its master H/W is needed
to be reconsidered.
A link structure, sysmmu_list_data is introduced that provides a link
exynos-iommu driver must care about master H/W's gate clock as well as
System MMU's gate clock. To enhance readability of the source code,
macros to gate/ungate those clocks are defined.
Signed-off-by: Cho KyongHo
---
drivers/iommu/exynos-iommu.c | 34 ++
1
This patch gates clocks of master H/W as well as clocks of System MMU
if master clocks are specified.
Some Exynos SoCs (i.e. GScalers in Exynos5250) have dependencies in
the gating clocks of master H/W and its System MMU. If a H/W is the
case, accessing control registers of System MMU is
This turns on FLPD_CACHE, ACGEN and SYSSEL.
FLPD_CACHE is a cache of 1st level page table entries that contains
the address of a 2nd level page table to reduce latency of page table
walking.
ACGEN is architectural clock gating that gates clocks by System MMU
itself if it is not active. Note that
This commit adds device tree support for System MMU.
Signed-off-by: Cho KyongHo
---
drivers/iommu/Kconfig|5 ++---
drivers/iommu/exynos-iommu.c | 21 +
2 files changed, 19 insertions(+), 7 deletions(-)
diff --git a/drivers/iommu/Kconfig b/drivers/iommu/Kconfig
This commit removes custom fault handler. The device drivers that
need to register fault handler can register
with iommu_set_fault_handler().
CC: Grant Grundler
Signed-off-by: Cho KyongHo
---
drivers/iommu/exynos-iommu.c | 80 +-
1 file changed, 24
Runtime power management by exynos-iommu driver independently from
master H/W's runtime pm is not useful for power saving since attaching
master H/W in probing time turns on its local power endlessly.
Thus this removes runtime pm API calls.
Runtime PM support is added in the following commits to
This patch adds dts entries for the System MMU devices found on
Exynos4 and Exynos5 SoC series and the System MMU binding
documentation.
CC: Rob Herring
CC: Sylwester Nawrocki
Signed-off-by: Cho KyongHo
---
.../bindings/iommu/samsung,exynos4210-sysmmu.txt | 86 +++
This adds gate clocks of all System MMUs and their master IPs
that are not apeared in clk-exynos5250.c and clk-exynos5420.c
Also fixes GATE_IP_ACP to 0x18800 and changed GATE_DA to GATE
for System MMU clocks in clk-exynos4.c
Signed-off-by: Cho KyongHo
---
This patch uses managed device helper functions in the probe().
Signed-off-by: Cho KyongHo
---
drivers/iommu/exynos-iommu.c | 64 +-
1 file changed, 26 insertions(+), 38 deletions(-)
diff --git a/drivers/iommu/exynos-iommu.c
System MMU driver is changed to control only a single instance of
System MMU at a time. Since a single instance of System MMU has only
a single clock descriptor for its clock gating, there is no need to
obtain two or more clock descriptors.
Signed-off-by: Cho KyongHo
---
This patch removes dbgname member from sysmmu_drvdata structure.
Kernel message for debugging already has the name of a single
System MMU node.
Signed-off-by: Cho KyongHo
---
drivers/iommu/exynos-iommu.c | 32 +---
1 file changed, 13 insertions(+), 19 deletions(-)
Checking if the probing device has a parent device was just to discover
if the probing device is involved in a power domain when the power
domain controlled by Samsung's custom implementation.
Since generic IO power domain is applied, it is required to remove
the condition to see if the probing
Since kmalloc() does not guarantee that the allignment of 1KiB when it
allocates 1KiB, it is required to allocate lv2 page table from own
slab that guarantees alignment of 1KiB
Signed-off-by: Cho KyongHo
---
drivers/iommu/exynos-iommu.c | 34 --
1 file changed,
Prefetch buffer is a cache of System MMU 3.x and caches a block of
page table entries to make effect of larger page with small pages.
However, how to control prefetch buffers and the specifications of
prefetch buffers different from minor versions of System MMU v3.
Prefetch buffers must be
L2TLB is 8-way set-associative TLB with 512 entries. The number of
sets is 64.
A single 4KB(small page) translation information is cached
only to a set whose index is the same with the lower 6 bits of the page
frame number.
A single 64KB(large page) translation information can be
cached to any 16
This commit adds cache flush for removed small and large page entries
in exynos_iommu_unmap(). Missing cache flush of removed page table
entries can cause missing page fault interrupt when a master IP
accesses an unmapped area.
Reviewed-by: Tomasz Figa
Tested-by: Grant Grundler
Signed-off-by:
This patch changes not to panic on any error when updating page table.
Instead prints error messages with callstack.
Signed-off-by: Cho KyongHo
---
drivers/iommu/exynos-iommu.c | 58 --
1 file changed, 44 insertions(+), 14 deletions(-)
diff --git
Commit 25e9d28d92 (ARM: EXYNOS: remove system mmu initialization from
exynos tree) removed arch/arm/mach-exynos/mach/sysmmu.h header without
removing remaining use of it from exynos-iommu driver, thus causing a
compilation error.
This patch fixes the error by removing respective include line
from
Sorry for the delayed posting the v11 patchset.
The current exynos-iommu(System MMU) driver does not work autonomously
since it is lack of support for power management of peripheral blocks.
For example, MFC device driver must ensure that its System MMU is disabled
before MFC block is power-down
On Thu, Mar 13, 2014 at 11:06 PM, wrote:
> From: Dirk Brandewie
>
> Some drivers (intel_pstate) need to modify state on a core before it
> is completely offline. The ->exit() callback is executed during the
> CPU_POST_DEAD phase of the cpu offline process which is too late to
> change the
On 03/14/2014 03:07 AM, Steven Rostedt wrote:
On Thu, 2014-03-13 at 15:54 +, Will Deacon wrote:
On Thu, Mar 13, 2014 at 10:13:49AM +, AKASHI Takahiro wrote:
CALLER_ADDRx returns caller's address at specified level in call stacks.
They are used for several tracers like irqsoff and
On Wed, Mar 12, 2014 at 04:54:47PM +, Mel Gorman wrote:
> On Tue, Feb 18, 2014 at 04:01:22PM +0800, Yuanhan Liu wrote:
> > Hi,
> >
> > Commit e82e0561("mm: vmscan: obey proportional scanning requirements for
> > kswapd") caused a big performance regression(73%) for vm-scalability/
> >
On Thu, Mar 13, 2014 at 04:55:41PM +1100, NeilBrown wrote:
> Can we do direct writes from kernel space yet? If so I'll change the code to
> do that so that it will work with any filesystem (which supports direct
> writes).
You can - see __swap_writepage() (mm/page_io.c). However, that area is
On 03/14/2014 02:08 AM, Will Deacon wrote:
On Thu, Mar 13, 2014 at 10:13:47AM +, AKASHI Takahiro wrote:
This patch implements arm64 specific part to support function tracers,
such as function (CONFIG_FUNCTION_TRACER), function_graph
(CONFIG_FUNCTION_GRAPH_TRACER) and function profiler
On Fri, 14 Mar 2014 11:05:51 +0800 Li Zefan wrote:
> Hi Davidlohr,
>
> On 2014/3/4 11:26, Linus Torvalds wrote:
> > On Mon, Mar 3, 2014 at 7:13 PM, Davidlohr Bueso wrote:
> >>
> >> Yes, I shortly realized that was silly... but I can say for sure it can
> >> happen and a quick qemu run confirms
From: hayeswang
Date: Fri, 14 Mar 2014 10:37:21 +0800
> From: David Miller [mailto:da...@davemloft.net]
> Sent: Friday, March 14, 2014 1:22 AM
> [...]
>> And I fundamentally disagree with this being a Kconfig parameter.
>>
>> Make it run-time calculated _or_ settable via ethtool.
>
> Excuse
Hi Linus,
pretty minor set of fixes for radeon, ttm and vmwgfx,
ttm ones are a regression and an oops seen on server chipsets.
Dave.
The following changes since commit fa389e220254c69ffae0d403eac4146171062d08:
Linux 3.14-rc6 (2014-03-09 19:41:57 -0700)
are available in the git repository
On 03/14/2014 01:25 AM, Will Deacon wrote:
On Thu, Mar 13, 2014 at 10:13:50AM +, AKASHI Takahiro wrote:
This patch allows system call entry or exit to be traced as ftrace events,
ie. sys_enter_*/sys_exit_*, if CONFIG_FTRACE_SYSCALLS is enabled.
Those events appear and can be controlled
Hi,
On 03/14/2014 01:43 AM, Bartlomiej Zolnierkiewicz wrote:
>
> Hi,
>
> On Thursday, March 13, 2014 05:17:21 PM Chanwoo Choi wrote:
>> This patchset support devicetree and use common ppmu driver instead of
>> individual code of exynos4_bus.c to remove duplicate code. Also this patchset
>> get
Hi Davidlohr,
On 2014/3/4 11:26, Linus Torvalds wrote:
> On Mon, Mar 3, 2014 at 7:13 PM, Davidlohr Bueso wrote:
>>
>> Yes, I shortly realized that was silly... but I can say for sure it can
>> happen and a quick qemu run confirms it. So I see your point as to
>> asking why we need it, so now I'm
On 03/14/2014 12:54 AM, Will Deacon wrote:
On Thu, Mar 13, 2014 at 10:13:49AM +, AKASHI Takahiro wrote:
CALLER_ADDRx returns caller's address at specified level in call stacks.
They are used for several tracers like irqsoff and preemptoff.
Strange to say, however, they are refered even
smp_read_barrier_depends() can be used if there is data dependency between
the readers - i.e. if the read operation after the barrier uses address
that was obtained from the read operation before the barrier.
In this file, there is only control dependency, no data dependecy, so the
use of
Includes:
- /proc/irq/default_smp_affinity
- /proc/irq/*/affinity_hint
- /proc/irq/*/smp_affinity
- /proc/irq/*/smp_affinity_list
Users can distill the same information by reading /proc/interrupts.
Signed-off-by: Chema Gonzalez
---
kernel/irq/proc.c | 8
1 file changed, 4
Commit-ID: 1f2cbcf648962cdcf511d234cb39745baa9f5d07
Gitweb: http://git.kernel.org/tip/1f2cbcf648962cdcf511d234cb39745baa9f5d07
Author: H. Peter Anvin
AuthorDate: Thu, 13 Mar 2014 19:44:47 -0700
Committer: H. Peter Anvin
CommitDate: Thu, 13 Mar 2014 19:44:47 -0700
x86, vdso, xen:
> [..]
>
> I tested on a prototype system with 231 entries in the map with good results.
> Everything succeeds when using kexec to initiate a fast reboot. For crash, it
> works with and without --pass-memmap-cmdline when using noefi. I hit the
> following panic when initiating a crash leaving EFI
0444 maybe?
-Chema
On Thu, Mar 13, 2014 at 7:37 PM, Eric Dumazet wrote:
> On Thu, 2014-03-13 at 19:05 -0700, Chema Gonzalez wrote:
>> Includes:
>> - /proc/irq/default_smp_affinity
>> - /proc/irq/*/smp_affinity
>> - /proc/irq/*/smp_affinity_list
>>
>> Users can distill the same information by
From: David Miller [mailto:da...@davemloft.net]
Sent: Friday, March 14, 2014 1:22 AM
[...]
> And I fundamentally disagree with this being a Kconfig parameter.
>
> Make it run-time calculated _or_ settable via ethtool.
Excuse me. How should I make it run-time calculated without a
Kconfig
On Thu, 2014-03-13 at 19:05 -0700, Chema Gonzalez wrote:
> Includes:
> - /proc/irq/default_smp_affinity
> - /proc/irq/*/smp_affinity
> - /proc/irq/*/smp_affinity_list
>
> Users can distill the same information by reading /proc/interrupts.
>
> Signed-off-by: Chema Gonzalez
> ---
Seems good to
On 03/12/2014 04:34 PM, Dietmar Eggemann wrote:
> On 12/03/14 07:44, Vincent Guittot wrote:
>> On 12 March 2014 05:42, Preeti U Murthy wrote:
>>> On 03/11/2014 06:48 PM, Vincent Guittot wrote:
On 11 March 2014 11:08, Preeti U Murthy wrote:
> Hi Vincent,
>
> On 03/05/2014 12:48
Add tunable RX interrupt trigger I/F of FIFO buffers.
Serial devices are used as not only message communication devices but control
or sending communication devices. For the latter uses, normally small data
will be exchanged, so user applications want to receive data unit as soon as
possible for
On Friday, March 14, 2014 11:14 AM, Daniel Jeong wrote:
>
> change to use devm_backlight_device_register() for simple cleanup.
>
> Signed-off-by: Daniel Jeong
Acked-by: Jingoo Han
Lee Jones,
Would you merge this patch into your backlight tree?
Best regards,
Jingoo Han
> ---
>
On 03/12/2014 01:14 PM, Vincent Guittot wrote:
> On 12 March 2014 05:42, Preeti U Murthy wrote:
>> On 03/11/2014 06:48 PM, Vincent Guittot wrote:
>>> On 11 March 2014 11:08, Preeti U Murthy wrote:
Hi Vincent,
On 03/05/2014 12:48 PM, Vincent Guittot wrote:
> Create a dedicated
True, we could create new wakeup sources specifically to
track this information, perhaps as needed once an IRQ is first
observed to trigger a wakeup.
We would want to know which wakeup sources were responsible for the
most recent wakeup, since we keep a timeline of suspend/resume events
with
change to use devm_backlight_device_register() for simple cleanup.
Signed-off-by: Daniel Jeong
---
drivers/video/backlight/lm3639_bl.c | 17 +++--
1 file changed, 7 insertions(+), 10 deletions(-)
diff --git a/drivers/video/backlight/lm3639_bl.c
Dear Sir,
Please do you handle Copyright Infringement Cases as our long time
business associate has violated our copyright agreement and we need a
good lawyer to handle this matter urgently.
If your firm is retained, our expectation of your services for now
will be within the scenario
This fifth revision of the QUP I2C driver comes with minor fixes, as per review
comments on the second third revision.
Regards,
Bjorn
Changes from second v3:
- Reformat device tree binding description related to clocks
- Minor cleanup related to dt parsing of clock frequency
- Properly return
This bus driver supports the QUP i2c hardware controller in the Qualcomm SOCs.
The Qualcomm Universal Peripheral Engine (QUP) is a general purpose data path
engine with input/output FIFOs and an embedded i2c mini-core. The driver
supports FIFO mode (for low bandwidth applications) and block mode
From: "Ivan T. Ivanov"
The Qualcomm Universal Peripherial (QUP) wraps I2C mini-core and
provide input and output FIFO's for it. I2C controller can operate
as master with supported bus speeds of 100Kbps and 400Kbps.
Signed-off-by: Ivan T. Ivanov
[bjorn: reformulated part of binding description
On 3/12/2014 4:13 PM, Bjorn Helgaas wrote:
I assume the system is fully functional even without these patches,
>right? The only effect of these changes should be a performance
>improvement.
[Suravee] Yes, the system is fully functional except the numa
information for PCI ethernet adapters is
Includes:
- /proc/irq/default_smp_affinity
- /proc/irq/*/smp_affinity
- /proc/irq/*/smp_affinity_list
Users can distill the same information by reading /proc/interrupts.
Signed-off-by: Chema Gonzalez
---
kernel/irq/proc.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
BCM590XX_NUM_REGS is known in compile time.
Use array to save desc and *info makes the code simpler.
Signed-off-by: Axel Lin
---
drivers/regulator/bcm590xx-regulator.c | 18 ++
1 file changed, 2 insertions(+), 16 deletions(-)
diff --git a/drivers/regulator/bcm590xx-regulator.c
The **rdev of 'struct bcm590xx_reg' isn't used anywhere in the driver so
remove it.
Signed-off-by: Axel Lin
---
drivers/regulator/bcm590xx-regulator.c | 10 --
1 file changed, 10 deletions(-)
diff --git a/drivers/regulator/bcm590xx-regulator.c
b/drivers/regulator/bcm590xx-regulator.c
Signed-off-by: Axel Lin
---
drivers/regulator/bcm590xx-regulator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/bcm590xx-regulator.c
b/drivers/regulator/bcm590xx-regulator.c
index e6b2e8e..d12d6d6 100644
--- a/drivers/regulator/bcm590xx-regulator.c
+++
On Thu, 2014-03-13 at 23:21 +, One Thousand Gnomes wrote:
> On Thu, 13 Mar 2014 21:30:48 +
> Matthew Garrett wrote:
>
> > On Thu, 2014-03-13 at 21:24 +, One Thousand Gnomes wrote:
> >
> > > If I have CAP_SYS_RAWIO I can make arbitary ring 0 calls from userspace,
> > > trivially and
On Fri, Mar 14, 2014 at 12:08 AM, Bjorn Helgaas wrote:
> On Thu, Mar 13, 2014 at 2:51 AM, Ming Lei wrote:
>> Hi Bjorn,
>>
>> I found this patch broke virtio-pci devices.
>
> Thanks a lot for testing this.
>
>> On Thu, Feb 27, 2014 at 3:37 AM, Bjorn Helgaas wrote:
>>> Don't rely on BAR contents
A hardware quirk in P320h/P420m interfere with PCIe transactions on some
AMD chipsets, making P320h/P420m unusable. This workaround is to disable
ERO and NoSnoop bits in the parent and root complex for normal functioning
of these devices
NOTE: This workaround is specific to AMD chipset with a
On 2014/3/14 0:04, Glyn Normington wrote:
> Hi Tejun
>
> Stepping back from the patch for a while, we'd like to explore the issues you
> raise. Please bear with us as we try to capture the ideas precisely.
>
> Continued inline...
>
> Regards,
> Glyn (& Steve Powell, copied)
>
> On 10/03/2014
Hi Sander,
On 03/13/2014 08:49 PM, Sander Eikelenboom wrote:
Is it just me .. or is this going at the speed of about a bluetooth connection
..
and probably missing the boot for 3.14 ? (for no good reason IMHO)
(it was not in John's nor Dave's last pull request, although it seems to be
Hi Sander,
Since:
- 3.14-RC6 has been cut
- this regression is known and reported since the merge window
- the fix (revert of 3 patches) is known for over a month now
- but it's still not in mainline
- my polite ping request from last week seems to have provoked
Add readl() and writel() for 'PM_' macros, just like another areas have
done within unicored32, or will cause compiling issue.
The related error (allmodconfig for unicored32):
CC arch/unicore32/kernel/clock.o
arch/unicore32/kernel/clock.c: In function ‘clk_set_rate’:
On Thursday, March 13, 2014 05:43:20 PM Ruchi Kandoi wrote:
> This should be true most of the times.
>
> But there might be cases otherwise too.
>
> For instance, there was a bug earlier with wi-fi which would cause the
> system to wake up but not get hold of a wakeup source because there
>
On Thu, Mar 13, 2014 at 4:07 PM, Sasha Levin wrote:
>
> I figured that I'll just read it from System.map (and do the math when
> adding the offset). That should work, right?
Yes, although just reading the symbols from the vmlinux file would be
*much* more convenient, since I know that not
Tuesday, March 11, 2014, 4:14:38 PM, you wrote:
> Hi John,
>>> Since:
>>> - 3.14-RC6 has been cut
>>> - this regression is known and reported since the merge window
>>> - the fix (revert of 3 patches) is known for over a month now
>>> - but it's still not in mainline
>>> - my polite ping
__vmalloc_area() has already been removed from upstream kernel, need
use __vmalloc_node_range() instead of.
The related commit: "d0a2126 mm: unify module_alloc code for vmalloc".
The related error (allmodconfig for unicore32):
CC arch/unicore32/kernel/module.o
This should be true most of the times.
But there might be cases otherwise too.
For instance, there was a bug earlier with wi-fi which would cause the
system to wake up but not get hold of a wakeup source because there
wasn't any work for it to do. In that case, the wakeup sources would
not log
On Thu, Mar 13, 2014 at 01:40:35PM -0700, Andrew Morton wrote:
> On Thu, 13 Mar 2014 11:46:17 +0900 Joonsoo Kim wrote:
>
> > Hello, Andrew.
> >
> > I applied all your comments in below patch. :)
>
> OK, thanks. I'll grab this instead of v5 - I wasn't thinking very
> clearly with the lock hold
On Thu, Mar 13, 2014 at 10:23:51PM +0100, Rafael J. Wysocki wrote:
> On Thursday, March 13, 2014 02:48:31 PM Valdis Kletnieks wrote:
> > Seen in the most recent linux-next with a CONFIG_SUSPEND=n .config:
> >
> > CC drivers/acpi/sleep.o
> > drivers/acpi/sleep.c: In function
On 03/13/2014 03:48 PM, Tony Lindgren wrote:
> * Joel Fernandes [140313 13:43]:
>> We introduce functions to initialize clocksource and clockevent, use
>> CLOCKSOURCE_OF_DECLARE to declare the clocksource, and handle the clocksource
>> selection on a per-SoC basis (Currently only AM335x is
On Thu, Mar 13, 2014 at 01:40:35PM -0700, Andrew Morton wrote:
> On Thu, 13 Mar 2014 11:46:17 +0900 Joonsoo Kim wrote:
>
> > Hello, Andrew.
> >
> > I applied all your comments in below patch. :)
>
> OK, thanks. I'll grab this instead of v5 - I wasn't thinking very
> clearly with the lock hold
On 03/13/2014 04:52 PM, Rob Herring wrote:
> On Thu, Mar 13, 2014 at 3:35 PM, Joel Fernandes wrote:
>> Introduce a generic omap timer initialization function that can
>> be used by all SoCs for which support is available in the clocksource
>> driver introduced in the series.
>>
>> The function
Commit-ID: 7dda038756704b3562187b29c81f86de935148c6
Gitweb: http://git.kernel.org/tip/7dda038756704b3562187b29c81f86de935148c6
Author: Andy Lutomirski
AuthorDate: Thu, 13 Mar 2014 16:01:27 -0700
Committer: H. Peter Anvin
CommitDate: Thu, 13 Mar 2014 16:20:17 -0700
x86_32, mm: Remove
Commit-ID: b0b49f2673f011cad7deeabf7a683b388c351278
Gitweb: http://git.kernel.org/tip/b0b49f2673f011cad7deeabf7a683b388c351278
Author: Andy Lutomirski
AuthorDate: Thu, 13 Mar 2014 16:01:26 -0700
Committer: H. Peter Anvin
CommitDate: Thu, 13 Mar 2014 16:20:09 -0700
x86, vdso: Remove
> Creating yet more kernel threads to solve this problem is a bit sad.
> Is there no way in which we can borrow one of the existing threads?
schedule_work()
Surely that's all we need, if we get bunged up for a bit then it ends up
on a work queue item and everyone with a billion disks and a 9600
On Thu, 13 Mar 2014 21:30:48 +
Matthew Garrett wrote:
> On Thu, 2014-03-13 at 21:24 +, One Thousand Gnomes wrote:
>
> > If I have CAP_SYS_RAWIO I can make arbitary ring 0 calls from userspace,
> > trivially and in a fashion well known and documented.
>
> How?
You want a list... there
Commit-ID: c0a639ad0bc6b178b46996bd1f821a04643e2bde
Gitweb: http://git.kernel.org/tip/c0a639ad0bc6b178b46996bd1f821a04643e2bde
Author: Borislav Petkov
AuthorDate: Sun, 9 Mar 2014 18:05:25 +0100
Committer: H. Peter Anvin
CommitDate: Thu, 13 Mar 2014 15:35:09 -0700
x86, Intel: Convert
Commit-ID: 22085a66c2fab6cf9b9393c056a3600a6b4735de
Gitweb: http://git.kernel.org/tip/22085a66c2fab6cf9b9393c056a3600a6b4735de
Author: Borislav Petkov
AuthorDate: Sun, 9 Mar 2014 18:05:23 +0100
Committer: H. Peter Anvin
CommitDate: Thu, 13 Mar 2014 15:34:45 -0700
x86: Add another set
Commit-ID: 8f86a7373a1c8ee52d3cc64adf7f2ace13fd24ed
Gitweb: http://git.kernel.org/tip/8f86a7373a1c8ee52d3cc64adf7f2ace13fd24ed
Author: Borislav Petkov
AuthorDate: Sun, 9 Mar 2014 18:05:24 +0100
Committer: H. Peter Anvin
CommitDate: Thu, 13 Mar 2014 15:35:03 -0700
x86, AMD: Convert to
> Usage is simple: 1) write a file path to be scanned into the interface,
> and 2) read 64-bit entries, each of which is associated with the page on
> each page index.
Do we have other interfaces that work like that? I suppose this is file is
only open
to "root", so it may be safe to assume
On Thu, Mar 13, 2014 at 03:03:41PM -0700, Linus Torvalds wrote:
> You need to look at the *symbol* number. In this output:
>
> [] do_one_initcall+0xc2/0x1e0
>
> that "810020c2" is crap, and is going away. The address that
> is meaningful and valid is the
On Thu, 13 Mar 2014 16:58:38 +0100 Jan Kara wrote:
> When there are lots of messages accumulated in printk buffer, printing
> them (especially over serial console) can take a long time (tens of
> seconds). stop_machine() will effectively make all cpus spin in
> multi_cpu_stop() waiting for the
On 03/13/2014 06:59 PM, Linus Torvalds wrote:
On Thu, Mar 13, 2014 at 3:20 PM, Sasha Levin wrote:
I'll fix it up and re-send this patch.
The problem (as you will find out) is that "addr2line" doesn't take
symbolic names.
So either addr2line needs to be improved (which really would be a
On Thu, 13 Mar 2014 16:58:37 +0100 Jan Kara wrote:
> Currently, console_unlock() prints messages from kernel printk buffer to
> console while the buffer is non-empty. When serial console is attached,
> printing is slow and thus other CPUs in the system have plenty of time
> to append new
1 - 100 of 1456 matches
Mail list logo
