Watchdog use performance monitor of cpu clock cycle to generate NMI to detect
hard lockup.
But when cpu's frequency changes, the event period will also change.
It's not as expected as the configration.
For example, set the NMI event handler period is 10 seconds when the cpu is
2.0GHz.
If the cpu
Hi Ben,
could you pull the firmware files for Creative CA0132 HD-audio codec
driver from below? It's the revised version.
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/linux-firmware.git
tags/ca0132-fw-v2
Firmware files f
Signed-off-by: Chao Xie
---
drivers/pwm/pwm-pxa.c | 12 +---
1 files changed, 1 insertions(+), 11 deletions(-)
diff --git a/drivers/pwm/pwm-pxa.c b/drivers/pwm/pwm-pxa.c
index f32fc4e..eafca4a 100644
--- a/drivers/pwm/pwm-pxa.c
+++ b/drivers/pwm/pwm-pxa.c
@@ -200,16 +200,6 @@ static st
Hi Grant.likely,
I really preciate if you can spend some times to review this patch.
Thanks,
Yuantian
> -Original Message-
> From: Tang Yuantian-B29983
> Sent: 2013年4月10日 11:37
> To: grant.lik...@secretlab.ca
> Cc: rob.herr...@calxeda.com; devicetree-disc...@lists.ozlabs.org; linux-
> ke
Add the deice tree support for pwm-pxa.
Signed-off-by: Chao Xie
---
drivers/pwm/pwm-pxa.c | 31 ++-
1 files changed, 30 insertions(+), 1 deletions(-)
diff --git a/drivers/pwm/pwm-pxa.c b/drivers/pwm/pwm-pxa.c
index eafca4a..345aa83 100644
--- a/drivers/pwm/pwm-pxa.
The patches fix some bugs
1. pwm-pxa driver is shared by ARCH_PXA and ARCH_MMP
2. use module_platform_driver for driver register
The patches also add device tree support for pwm.
Chao Xie (3):
pwm: pxa: ARCH_MMP share same pwm driver with ARCH_PXA
pwm: pxa: use module_platform_driver for dri
the pwm driver is not only used by ARCH_PXA but also ARCH_MMP
Signed-off-by: Chao Xie
---
drivers/pwm/Kconfig |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/pwm/Kconfig b/drivers/pwm/Kconfig
index e513cd9..ff79632 100644
--- a/drivers/pwm/Kconfig
+++ b/drivers/
Hi Nishanth,
Thanks for reviewing this patch.
On Mon, Apr 15, 2013 at 7:40 PM, Nishanth Menon wrote:
> Daniel,
> On Mon, Apr 15, 2013 at 1:24 AM, Amit Daniel Kachhap
> wrote:
>> As per the OPP library documentation(Documentation/power/opp.txt) all
>> opp find/get calls should be protected by rc
On 15/04/13 11:59, l...@tigusoft.pl wrote:
> There are 2 hard drives (normal, magnetic) in software raid 1
> on 3.2.41 kernel.
>
> When I write into them e.g. using dd from /dev/zero to a local file
> (ext4 on default settings), running 2 dd at once (writing two files) it
> starves all other progr
UBI: fix memory leak when use fastmap
When use ubi fastmap, there is a memory leak which will make destroy_ai()
called in ubi_attach fail.
The following patch base on linux-3.9-rc6 fix this problem.
diff -uprN old_ubi/attach.c new_ubi/attach.c
--- old_ubi/attach.c2013-04-08 03:49:54.000
On Mon, 18 Mar 2013 19:49:04 -0400, Ben Collins wrote:
> of_phy_connect() only required a flags argument in order to pass it down to
> to phy_connect(). Since that argument was removed, it is of no use in this
> function either (confirmed by checking all callers in kernel tree as well).
>
> Signe
> On Mon, Apr 15, 2013 at 6:49 PM, Yijing Wang wrote:
>> Hi Yinghai,
>>Any comments about this patch? I searched the code history and found
>> you introduced pci_hp_add_bridge() function at commit a8e4b9c10. In your
>> patchset use pci_hp_add_bridge() for all pci hotplug drivers except acpiphp
Let kvm do not reuse the rmap of the memslot which is being moved
then the rmap of moved or deleted memslot can only be unmapped, no
new spte can be added on it.
This is good for us to unmap rmap out of mmu-lock in the later patches
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/x86.c |2 +-
Invalid rmaps is the rmap of the invalid memslot which is being
deleted, especially, we can treat all rmaps are invalid when
kvm is being destroyed since all memslot will be deleted soon.
MMU should remove all sptes on these rmaps before the invalid
memslot fully deleted
The reason why we separate
It frees pte-list-descs used by memslot rmap after update
memslot is completed
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/mmu.c | 26 ++
arch/x86/kvm/mmu.h |1 +
2 files changed, 27 insertions(+), 0 deletions(-)
diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mm
This patch introduce PTE_LIST_SPTE_SKIP which is the placeholder and
it will be set on pte-list after removing a spte so that other sptes
on this pte_list are not moved and the pte-list-descs on the pte-list
are not freed.
If vcpu can not add spte to the pte-list (e.g. the rmap on invalid
memslot)
This function is used to reset the large page info of all guest page
which will be used in later patch
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/x86.c | 25 +
arch/x86/kvm/x86.h |2 ++
2 files changed, 27 insertions(+), 0 deletions(-)
diff --git a/arch/x86/kvm
pte_list_clear_concurrently allows us to reset pte-desc entry
out of mmu-lock. We can reset spte out of mmu-lock if we can protect the
lifecycle of sp, we use this way to achieve the goal:
unmap_memslot_rmap_nolock():
for-each-rmap-in-slot:
preempt_disable
kvm->arch.being_unmapped_rmap
Replace kvm_mmu_zap_all by kvm_mmu_invalid_all_pages except on
the path of mmu_notifier->release() which will be replaced in
the later patch
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/x86.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kvm/x86.c b/arch/
Move srcu_read_lock/srcu_read_unlock in kvm_mmu_notifier_release
to kvm_arch_flush_shadow_all since we will hold slot-lock instead
of srcu
Only ARM, POWERPC and x86 are using mmu-notify and
kvm_arch_flush_shadow_all on ARM and POWERPC does nothing, so we
only need to modify the code on x86
Signed
The current kvm_mmu_zap_all is really slow - it is holding mmu-lock to
walk and zap all shadow pages one by one, also it need to zap all guest
page's rmap and all shadow page's parent spte list. Particularly, things
become worse if guest uses more memory or vcpus. It is not good for
scalability.
I
Use kvm_mmu_invalid_all_pages in kvm_arch_flush_shadow_all and
rename kvm_zap_all to kvm_free_all which is used to free all
memmory used by kvm mmu when vm is being destroyed, at this time,
no vcpu exists and mmu-notify has been unregistered, so we can
free the shadow pages out of mmu-lock
Signed-
It is used to set disallowed lage page on the specified level, can be
used in later patch
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/x86.c | 53 ++-
1 files changed, 35 insertions(+), 18 deletions(-)
diff --git a/arch/x86/kvm/x86.c b/arch/x8
Introduce slot_rmap_* functions to abstract memslot rmap related
operations which makes the later patch more clearer
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/mmu.c | 108 +-
arch/x86/kvm/mmu_audit.c | 10 +++--
2 files changed, 84 insert
memslot rmap and lpage-info are never partly reused and nothing need
be freed when new memslot is created
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/x86.c | 21 -
1 files changed, 12 insertions(+), 9 deletions(-)
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
ind
This patchset is based on my previous two patchset:
[PATCH 0/2] KVM: x86: avoid potential soft lockup and unneeded mmu reload
(https://lkml.org/lkml/2013/4/1/2)
[PATCH v2 0/6] KVM: MMU: fast invalid all mmio sptes
(https://lkml.org/lkml/2013/4/1/134)
Changlog:
V3:
completely redesign the algori
It removes a arch-specified interface and also removes unnecessary
empty functions on some architectures
Signed-off-by: Xiao Guangrong
---
arch/arm/kvm/arm.c |5 -
arch/ia64/kvm/kvm-ia64.c |5 -
arch/powerpc/kvm/powerpc.c |8 ++--
arch/s390/kvm/kvm-s390.c |
Introduce rmap_operations to allow rmap having different operations,
then, we are able to handle invalid rmap specially
Signed-off-by: Xiao Guangrong
---
arch/x86/include/asm/kvm_host.h |1 +
arch/x86/kvm/mmu.c | 31 ---
arch/x86/kvm/mmu.h
On Tue, Apr 16, 2013 at 03:11:13PM +0900, Simon Horman wrote:
> On Thu, Apr 11, 2013 at 02:30:09PM +0100, David Howells wrote:
> > Don't use create_proc_read_entry() as that is deprecated, but rather use
> > proc_create_data() and seq_file instead.
>
> Paul, do you want me to handle this?
FWIW, I
On Monday 15 April 2013 01:31 PM, Michael Ellerman wrote:
On Wed, Apr 10, 2013 at 12:53:27PM +0530, Aruna Balakrishnaiah wrote:
This patch exploits pstore infrastructure to read the details
from NVRAM's rtas partition.
Does that mean it's exposed in the pstore filesystem?
Yeah thats right.
Hi Michael,
Thanks for reviewing my patches.
On Monday 15 April 2013 01:25 PM, Michael Ellerman wrote:
On Wed, Apr 10, 2013 at 12:53:03PM +0530, Aruna Balakrishnaiah wrote:
This patch exploits pstore infrastructure in power systems.
IBM's system p machines provide persistent storage for LPARs
On Tuesday 16 of April 2013, Neil Horman wrote:
> A few years back intel published a spec update:
> http://www.intel.com/content/dam/doc/specification-update/5520-and-5500-chi
> pset-ioh-specification-update.pdf
>
> For the 5520 and 5500 chipsets which contained an errata (specificially
> errata 5
On Mon, Apr 15, 2013 at 04:11:18PM -0700, David Rientjes wrote:
> On Mon, 15 Apr 2013, Greg Kroah-Hartman wrote:
>
> > > The positive numbers are used to return information on the remaining
> > > cache size (again, see the comment I pasted above). We could use
> > > -EBUSY, but we'd have to change
In bitmap_find_free_region, If we skip the all-ones words and find bits
in a not-all-ones word, we can improve performance of it.
For example, If bitmap_find_free_region() is called with order=0, First,
It scans bitmap array by the increment of long type, then find 1 free bit
within 1 long type va
On Thu, Apr 11, 2013 at 02:30:09PM +0100, David Howells wrote:
> Don't use create_proc_read_entry() as that is deprecated, but rather use
> proc_create_data() and seq_file instead.
Paul, do you want me to handle this?
>
> Signed-off-by: David Howells
> cc: Paul Mundt
> cc: linux...@vger.kernel
On 04/15/2013 10:57 PM, Kirill A. Shutemov wrote:
>>> > > ** Initial writers **
>>> > > threads:1248 16 32
>>> > > 64 128 256
>>> > > baseline: 1103360 912585 500065 260503 12891862039
>>> > > 347991871
On Mon, 2013-04-15 at 13:16 +0200, richard -rw- weinberger wrote:
> No. If I'm not mistaken we need this to make sure that the compiler
> inlines some functions.
>
> In your case the compiler failed to compute the BUILD_BUG() macro correctly.
> It depends also on optimization.
>
Thank you.
So, t
Al,
I see that you did some consolidating work for clone() in Linux 3.8,
and for that reason I suspect you know the answer to the questions
below. Could you take a short moment to look at the questions?
The relevant pieces of the clone(2) man page are quoted below. There
is some ancient text ther
Dave Hansen wrote:
> On 04/15/2013 11:17 AM, Kirill A. Shutemov wrote:
> > I run iozone using mmap files (-B) with different number of threads.
> > The test machine is 4s Westmere - 4x10 cores + HT.
>
> How did you run this, exactly? Which iozone arguments?
iozone -B -s 2186/$threads -t $thr
This patch replace dma_length in "lib/swiotlb.c" to sg_dma_len() macro, because
the build error can occur
if CONFIG_NEED_SG_DMA_LENGTH is not set, and CONFIG_SWIOTLB is set.
I confirmed compile only.
Singed-off-by: EunBong Song
---
lib/swiotlb.c |8
1 files changed, 4 insertions
We can extend kexec-tools to support multiple "Crash kernel" in /proc/iomem
instead.
So we can use "Crash kernel" instead of "Crash kernel low" in /proc/iomem.
Suggested-by: Vivek Goyal
Signed-off-by: Yinghai Lu
Acked-by: Vivek Goyal
---
kernel/kexec.c |2 +-
1 file changed, 1 insertion(
Per hpa, use crashkernel=X,high crashkernel=Y,low instead of
crashkernel_hign=X crashkernel_low=Y. As that could be extensible.
-v2: according to Vivek, change delimiter to ;
-v3: let hign and low only handle simple form and it conforms to
description in kernel-parameters.txt
still ke
Vivek found some problems with old kexec-tools.
We keep the old crashkernel=X to old behavoir, so it will not break
old kexec-tools.
Add crashkernel=X,high to support new kexec-tools that supports loading high.
when high is used, memblock will search from top to low.
if the allocated one is above
Vivek found old kexec-tools does not work new kernel anymore.
So change back crashkernel= back to old behavoir, and add crashkernel_high=
to let user decide if buffer could be above 4G, and also new kexec-tools will
be needed.
-v2: let crashkernel=X override crashkernel_high=
update descripti
Chao said that kdump does does work well on his system on 3.8
without extra parameter, even iommu does not work with kdump.
And now have to append crashkernel_low=Y in first kernel to make
kdump work.
We have now modified crashkernel=X to allocate memory beyong 4G (if
available) and do not allocat
From 4d629cfb265beece1aae2e3fdf603e36a321f785 Mon Sep 17 00:00:00 2001
From: Runzhen Wang
Date: Mon, 15 Apr 2013 23:17:15 -0400
Subject: [PATCH] perf tool: fix the perf --version bug
The perf --version can't print the right version
information when reset it to an earlier commit.
For example, at
From 4d629cfb265beece1aae2e3fdf603e36a321f785 Mon Sep 17 00:00:00 2001
From: Runzhen Wang
Date: Mon, 15 Apr 2013 23:17:15 -0400
Subject: [PATCH] perf tool: fix the perf --version bug
The perf --version can't print the right version
information when reset it to an earlier commit.
For example, at
Quoting Stephen Rothwell (2013-04-15 17:55:13)
> Hi Sebastian,
>
> On Mon, 15 Apr 2013 09:00:14 +0200 Sebastian Hesselbarth
> wrote:
> >
> > Calling clk-si5351 driver non-OF ready was too early. This patch
> > makes clk-si5351 depend on CONFIG_OF again, until things get sorted out.
> >
> > Sign
On Tue, 16 Apr 2013 03:45:15 + "Pan, Zhenjie" wrote:
> > Overall the patch looks desirable, but it increases the kernel size by
> > several
> > hundred bytes when CONFIG_CPU_FREQ=n. It should produce no code in
> > this case! Take a look at the magic in register_hotcpu_notifier(), the way
On 4/15/13 7:14 PM, Namhyung Kim wrote:
Makefile:755: The path '/usr/bin/python-config' is not executable.
Makefile:755: *** Please set 'PYTHON_CONFIG' appropriately. Stop.
The problem is that I didn't have python-devel package installed and
get-executable-or-default decides to error out instea
On Mon, 2013-04-15 at 10:37 -0400, Waiman Long wrote:
[...]
> +typedef struct mspin_node {
> + struct mspin_node *next;
> + intlocked; /* 1 if lock acquired */
> +} mspin_node_t;
> +
> +typedef mspin_node_t *mspin_lock_t;
I think we could do without the typedefs, speci
From: Thomas Abraham
With device core now able to setup the default pin configuration,
the pin configuration code based on the deprecated Samsung specific
gpio bindings is removed.
Signed-off-by: Thomas Abraham
Signed-off-by: Doug Anderson
Acked-by: Linus Walleij
Reviewed-by: Doug Anderson
T
>
> On 2013/4/1 17:22, Yijing Wang wrote:
>> Use pci_hp_add_bridge() like most other hotplug drivers
>> rather than call pci_scan_bridge() directly.
>>
>> Signed-off-by: Yijing Wang
>> ---
>> drivers/pci/hotplug/acpiphp_glue.c | 24 ++--
>> 1 files changed, 10 insertions(+),
Hello,
The futex-keys of processes share futex determined by page-offset,
mapping-host, and
mapping-index of the user space address.
User appications using hugepage for futex may lead to futex-key conflict.
Assume there
are two or more futexes in diffrent normal pages of the hugepage, and eac
Thanks for your detail comments, Andrew.
Please see my comments below.
> -Original Message-
> From: Andrew Morton [mailto:a...@linux-foundation.org]
> Sent: Tuesday, April 16, 2013 7:31 AM
> To: Pan, Zhenjie
> Cc: a.p.zijls...@chello.nl; pau...@samba.org; mi...@redhat.com;
> a...@ghostprot
On 04/14/2013 12:42 AM, Minchan Kim wrote:
Hi KOSAKI,
On Thu, Apr 11, 2013 at 11:01:11AM -0400, KOSAKI Motohiro wrote:
and adding new syscall invokation is unwelcome.
Sure. But one more system call could be cheaper than page-granuarity
operation on purged range.
I don't think vrange(VOLATILE)
Thanks, Don.
First, I think the frequency of CPU frequency change is depend on the special
platform.
I tested it on Atom Android platform.
When the system is idle(800MHz) or very busy(2000MHz), it's the easiest case.
If do some user operations like move the screen by finger, the cpu will change
On Tue, 9 Apr 2013, Antti Palosaari wrote:
> On 04/08/2013 08:47 PM, Randy Dunlap wrote:
> > From: Randy Dunlap
> >
> > Fix randconfig error when USB is not enabled:
> >
> > ERROR: "usb_control_msg" [drivers/media/common/cypress_firmware.ko]
> > undefined!
> >
> > Signed-off-by: Randy Dunlap
Hi Marcelo,
On 04/16/2013 08:54 AM, Marcelo Tosatti wrote:
> On Mon, Apr 01, 2013 at 05:56:43PM +0800, Xiao Guangrong wrote:
>> Changelog in v2:
>> - rename kvm_mmu_invalid_mmio_spte to kvm_mmu_invalid_mmio_sptes
>> - use kvm->memslots->generation as kvm global generation-number
>> - fix co
Commit 3de4ad210387 ("perf/x86: Fix offcore_rsp valid mask for SNB/IVB")
in perf/urgent breaks the build:
arch/x86/kernel/cpu/perf_event_intel.c:158:2: error: implicit declaration of
function 'INTEL_UEVENT_PEBS_LDLAT_EXTRA_REG'
[-Werror=implicit-function-declaration]
arch/x86/kernel/cpu/perf_ev
From: Eric Dumazet
On Mon, 2013-04-15 at 17:37 -0700, Eric Dumazet wrote:
> On Mon, 2013-04-15 at 16:57 +0300, Vitaly V. Bursov wrote:
> > Hello,
> >
> > I have a bonding device (mode=802.3ad xmit_hash_policy=layer2+3 miimon=300)
> > and
> > for kernels <3.7 forwarded IPv4 traffic distributed f
From: Zhang Yi
Hello,
The function handle_futex_death just wakes one thread, which may be not
enough when the owner process is dead. Think about this scene：
1. A robust futex is shared for two processes, each process has multi
threads try to get the lock.
2. One of the threads gets the lock,
On Mon, Apr 15, 2013 at 12:14:29PM -0500, Robin Holt wrote:
> We recently noticed that reboot of a 1024 cpu machine takes approx 16
> minutes of just stopping the cpus. The slowdown was tracked to commit
> f96972f.
>
> The current implementation does all the work of hot removing the cpus
> before
On Mon, Apr 15, 2013 at 7:36 PM, H. Peter Anvin wrote:
> On 04/15/2013 03:00 PM, Yinghai Lu wrote:
>>
>> looks you are trying redo the work for bootloader to pick loaded phys addr.
>>
>
> Well, that is exactly what they are doing. On top of that they also
> need to randomize the 64-bit virtual ma
On Mon, Apr 15, 2013 at 6:44 PM, Wang YanQing wrote:
>
> The parameter of memblock_reserve is start address,
> and size, not address range.
>
> Signed-off-by: Wang YanQing
> ---
> drivers/acpi/osl.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/acpi/osl.c b/dri
Hi Rafael,
Today's linux-next merge of the pm tree got a conflict in
drivers/acpi/scan.c between commit 5c0b04e3d913 ("PCI/ACPI: Handle PCI
slot devices when creating/destroying PCI buses") from the pci tree and
commit 0a34764411aa ("ACPI / scan: Make memory hotplug driver use struct
acpi_scan_han
On 04/15/2013 07:31 PM, H. Peter Anvin wrote:
>
> I also am starting to think that this really would be done better being
> integrated with the decompressor code, since that code already ends up
> moving the code around... no reason to do this again.
>
Another good reason to do this in the decom
On 04/15/2013 03:00 PM, Yinghai Lu wrote:
>
> looks you are trying redo the work for bootloader to pick loaded phys addr.
>
Well, that is exactly what they are doing. On top of that they also
need to randomize the 64-bit virtual mapping.
I wonder if we need a bootloader bit to inhibit kaslr in
On 04/15/2013 03:38 PM, Yinghai Lu wrote:
> On Mon, Apr 15, 2013 at 3:07 PM, Kees Cook wrote:
>> On Mon, Apr 15, 2013 at 3:00 PM, Yinghai Lu wrote:
>>> also do not overlap with boot_param, command_line, and initrd.
>>>
>>> and need to double check setup_header.init_size to make sure bss and
>>> e
On 04/15/2013 02:59 PM, Kees Cook wrote:
>>
>> The *physical* mapping, where it lands in RAM, is completely
>> independent, and if you're going to randomize the latter, there is no
>> reason it has to match the former. Instead, randomize it freely.
>
> Ah, gotcha. I don't see much benefit in doin
On Mon, Apr 01, 2013 at 05:56:43PM +0800, Xiao Guangrong wrote:
> Changelog in v2:
> - rename kvm_mmu_invalid_mmio_spte to kvm_mmu_invalid_mmio_sptes
> - use kvm->memslots->generation as kvm global generation-number
> - fix comment and codestyle
> - init kvm generation close to mmio wrap-ar
Hi Pekka,
On Mon, 15 Apr 2013 13:58:50 +0300, Pekka Enberg wrote:
> Hello,
>
> I'm seeing this when I try to build perf in v3.9-rc7:
>
> [penberg@golgotha perf]$ make
> CHK -fstack-protector-all
> CHK -Wstack-protector
> CHK -Wvolatile-register-var
> CHK -D_FORTIFY_SOURCE=2
> C
Haojian,
> -Original Message-
> From: Neil Zhang
> Sent: 2013年4月15日 19:10
> To: 'Haojian Zhuang'
> Cc: Grant Likely; linux-arm-ker...@lists.infradead.org;
> linux-kernel@vger.kernel.org; Chao Xie
> Subject: RE: [PATCH 1/4] ARM: mmp: add wakeup function for ICU
>
>
>
>
>
> > -Origi
On 2013/4/15 22:15, Jonghwan Choi wrote:
> From: libin
>
> This patch looks like it should be in the 3.8-stable tree, should we apply
> it?
>
yes, I think this patch should be applied to the 3.8-stable tree. Thanks.
Libin
> --
>
> From: "libin "
>
> commit fd9b86d37a600488dbd
Hi Yinghai,
Any comments about this patch? I searched the code history and found
you introduced pci_hp_add_bridge() function at commit a8e4b9c10. In your
patchset use pci_hp_add_bridge() for all pci hotplug drivers except acpiphp.
So I use pci_hp_add_bridge() in acpiphp instead of using pci_scan
Sarah,
Thanks so much for improving the REPORTING-BUGS file. With your
changes it looks way better!
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
The parameter of memblock_reserve is start address,
and size, not address range.
Signed-off-by: Wang YanQing
---
drivers/acpi/osl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/acpi/osl.c b/drivers/acpi/osl.c
index 586e7e9..bcb7a3b 100644
--- a/drivers/acpi/osl.c
On Fri, Apr 12, 2013 at 12:36:00PM -0700, Kent Overstreet wrote:
> It would be nice if we had unsigned atomic types... but given that we
> don't and I'm pretty sure overflow in atomic types happens all over the
> place that part honestly seems fine to me...
>
> That said, I suppose a comment indic
The memblock_find_in_range return value, addr, will
make sure "addr + aper_size" not beyond GART_MAX_ADDR.
Signed-off-by: Wang YanQing
---
arch/x86/kernel/aperture_64.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/aperture_64.c b/arch/x86/kernel/aperture_6
On Mon, 2013-04-15 at 09:30 -0400, Eduardo Valentin wrote:
> On 13-04-2013 19:46, Ville Syrjälä wrote:
> > On Sun, Apr 14, 2013 at 12:44:00AM +0300, Ville Syrjälä wrote:
> >> On Sat, Apr 13, 2013 at 10:02:21AM -0600, Jake Edge wrote:
> >>> Hi Zhang Rui,
> >>>
> >>> The problem reported in https://l
Andrew Morton writes:
> On Fri, 12 Apr 2013 15:28:56 -0700 Kent Overstreet
> wrote:
>> Those are the main changes (besides adding attributes, of course) that
>> I've made so far.
>>
>> * Get rid of the parallel syscall interface
>>
>>AIO really shouldn't be implementing its own slightly
On Mon, 15 Apr 2013, Michel Lespinasse wrote:
> On Mon, Apr 15, 2013 at 2:47 PM, Hugh Dickins wrote:
> > --- 3.9-rc7/mm/mlock.c 2013-04-01 09:08:05.736012852 -0700
> > +++ linux/mm/mlock.c2013-04-15 14:20:24.454773245 -0700
> > @@ -397,8 +397,7 @@ int __mm_populate(unsigned long start, u
> >
I think the linux.git "system hang" isn't really a hang. For some reason the
panic text wasn't displayed on the console. I've seen this behaviour a few
times now ... maybe there's a bug in the panic output path?
I also haven't determined why I'm seeing a thermal interrupt during a CPU
hotplug te
On 2013年04月15日 13:48, Rusty Russell wrote:
> Chen Gang writes:
>
>> > We don't export any symbols > 128 characters, but if we did then
>> > kallsyms_expand_symbol() would overflow the buffer handed to it.
>> > So we need check destination buffer length when copying.
>> >
>> > the related
Update debugging messages to a more current style.
Emit these debugging messages at KERN_DEBUG instead
of KERN_DEFAULT.
Add and use neigh_dbg(level, fmt, ...) macro
Add dynamic_debug capability via pr_debug
Convert embedded function names to "%s: ", __func__
Signed-off-by: Joe Perches
---
net/
When hot removing memory presented at boot time, following messages are shown:
[ 296.867031] [ cut here ]
[ 296.922273] kernel BUG at mm/slub.c:3409!
[ 296.970229] invalid opcode: [#1] SMP
[ 297.019453] Modules linked in: ebtable_nat ebtables xt_CHECKSUM
iptable_m
On Sun, Mar 10, 2013 at 07:41:06PM +0100, Jiri Olsa wrote:
> Adding RF EFLAGS bit to be restored on return from signal from
> the original register context before the signal was entered.
>
> This will prevent the RF flag to disappear when returning
> from exception due to the signal handler being
Hi Sebastian,
On Mon, 15 Apr 2013 09:00:14 +0200 Sebastian Hesselbarth
wrote:
>
> Calling clk-si5351 driver non-OF ready was too early. This patch
> makes clk-si5351 depend on CONFIG_OF again, until things get sorted out.
>
> Signed-off-by: Sebastian Hesselbarth
> Reported-by: Stephen Rottweil
On Tuesday, April 16, 2013 8:07 AM, Andrew Morton wrote:
>
> On Thu, 11 Apr 2013 13:24:50 -0700 Andrew Bresticker
> wrote:
>
> > Platform LCD devices may need to do some device-specific
> > initialization before they can be used (regulator or GPIO setup,
> > for example), but currently the driv
On 2013/4/15 20:48, Libin wrote:
> (*->vm_end - *->vm_start) >> PAGE_SHIFT operation is implemented
> as a inline funcion vma_pages() in linux/mm.h, so using it.
>
> Signed-off-by: Libin
> ---
> drivers/char/mspec.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/driver
On Sun, Apr 14, 2013 at 09:12:32PM +0200, Oleg Nesterov wrote:
> ptrace_write_dr7() skips ptrace_modify_breakpoint(disabled => true)
> unless second_pass, this buys nothing but complicates the code and
> means that we always do the main loop twice even if "disabled" was
> never true.
>
> The comme
On Mon, Apr 15, 2013 at 04:02:56PM -0700, Yinghai Lu wrote:
> On Mon, Apr 15, 2013 at 3:41 PM, Neil Horman wrote:
> > A few years back intel published a spec update:
> > http://www.intel.com/content/dam/doc/specification-update/5520-and-5500-chipset-ioh-specification-update.pdf
> >
>
> > diff --gi
On Mon, Apr 15, 2013 at 4:59 PM, Rob Herring wrote:
> On 04/15/2013 05:21 PM, Colin Cross wrote:
>> On Wed, Apr 10, 2013 at 6:30 AM, Rob Herring wrote:
>>> On 04/09/2013 10:53 PM, Colin Cross wrote:
On Tue, Apr 9, 2013 at 8:08 PM, Rob Herring wrote:
> From: Rob Herring
>
> Atom
Quoting Sebastian Hesselbarth (2013-04-15 00:03:23)
> On 04/15/2013 07:04 AM, Stephen Rothwell wrote:
> > After merging the clk tree, today's linux-next build (x86_64 allmodconfig)
> > failed like this:
> >
> > ERROR: "of_clk_add_provider" [drivers/clk/clk-si5351.ko] undefined!
> > ERROR: "of_clk_s
On Mon, 2013-04-15 at 16:57 +0300, Vitaly V. Bursov wrote:
> Hello,
>
> I have a bonding device (mode=802.3ad xmit_hash_policy=layer2+3 miimon=300)
> and
> for kernels <3.7 forwarded IPv4 traffic distributed fine across multiple
> physical
> links. Ethernet cards are Intel 82576 with igb driver
Hi Toshi,
2013/04/16 5:01, Toshi Kani wrote:
On Mon, 2013-04-15 at 11:15 +0900, Yasuaki Ishimatsu wrote:
When hot removing memory presented at boot time, following messages are shown:
:
The reason why the messages are shown is to release a resource structure,
allocated by bootmem, by kfree(
On 04/16/2013 07:12 AM, Borislav Petkov wrote:
> On Mon, Apr 15, 2013 at 09:50:22PM +0800, Alex Shi wrote:
>> For fairness and total threads consideration, powersaving cost quit
>> similar energy on kbuild benchmark, and even better.
>>
>> 17348.850 27400.458 159
On Mon, Apr 15, 2013 at 2:47 PM, Hugh Dickins wrote:
> --- 3.9-rc7/mm/mlock.c 2013-04-01 09:08:05.736012852 -0700
> +++ linux/mm/mlock.c2013-04-15 14:20:24.454773245 -0700
> @@ -397,8 +397,7 @@ int __mm_populate(unsigned long start, u
> long ret = 0;
>
> VM_BUG_ON(start & ~PAG
Greg KH twisted the bytes to say:
>> http://o.cs.uvic.ca:20810/perl/next.pl
Greg> Yes, that's a great thing. Maybe the ability to see the subject: line
Greg> of the commit somewhere easier than having to click through to the patch
Greg> would be nice, so we can just glance at the report a
Hi Ohad,
On Mon, 15 Apr 2013 09:28:17 +0300 Ohad Ben-Cohen wrote:
>
> Could you please add:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/ohad/rpmsg.git#for-next
>
> to linux-next to include new stuff coming from Rob?
Well, you could tell me something about it. Like what is in it and how
1 - 100 of 601 matches
Mail list logo
