This patch proposes to remove the use of the IRQF_DISABLED flag
It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
drivers/media/platform/s5p-mfc/s5p_mfc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This patch proposes to remove the use of the IRQF_DISABLED flag
It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
drivers/media/pci/ivtv/ivtv-driver.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This patch proposes to remove the use of the IRQF_DISABLED flag
It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
drivers/media/pci/zoran/zoran_card.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This patch proposes to remove the use of the IRQF_DISABLED flag
It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
drivers/media/pci/bt8xx/bt878.c | 3 +--
drivers/media/pci/bt8xx/bttv-driver.c| 2 +-
This patch proposes to remove the use of the IRQF_DISABLED flag
It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
drivers/media/pci/cx18/cx18-driver.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
This patch proposes to remove the use of the IRQF_DISABLED flag
It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
drivers/media/common/saa7146/saa7146_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This patch proposes to remove the use of the IRQF_DISABLED flag
It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
drivers/isdn/hardware/eicon/divasmain.c | 2 +-
drivers/isdn/sc/init.c | 2 +-
2 files changed, 2 insertions(+), 2
* David Ahern wrote:
> On 10/12/13 10:53 AM, Ingo Molnar wrote:
> >
> >* David Ahern wrote:
> >
> >>On 10/11/13 9:11 AM, David Ahern wrote:
> >>>It would be nice to fix the callchain arg handler to not attempt to
> >>>process the next argument if it is not fp or dwarf.
> >>
> >>Specifically,
This patch proposes to remove the use of the IRQF_DISABLED flag
It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
drivers/edac/mpc85xx_edac.c | 7 +++
drivers/edac/mv64x60_edac.c | 8
drivers/edac/ppc4xx_edac.c | 4 ++--
3 files
This patch proposes to remove the use of the IRQF_DISABLED flag
It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
drivers/dma/amba-pl08x.c | 3 +--
drivers/dma/k3dma.c | 2 +-
drivers/dma/mmp_pdma.c | 4 ++--
drivers/dma/mmp_tdma.c | 4 ++--
This patch proposes to remove the use of the IRQF_DISABLED flag
It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
drivers/dma/coh901318.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/coh901318.c
This patch proposes to remove the use of the IRQF_DISABLED flag
It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
drivers/crypto/mv_cesa.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/mv_cesa.c
This patch proposes to remove the use of the IRQF_DISABLED flag
It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
drivers/clocksource/tcb_clksrc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clocksource/tcb_clksrc.c
This patch proposes to remove the use of the IRQF_DISABLED flag
It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
drivers/clocksource/tegra20_timer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This patch proposes to remove the use of the IRQF_DISABLED flag
It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
drivers/clocksource/vt8500_timer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This patch proposes to remove the use of the IRQF_DISABLED flag
It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
drivers/clocksource/cadence_ttc_timer.c | 3 +--
drivers/clocksource/cs5535-clockevt.c | 2 +-
drivers/clocksource/dw_apb_timer.c
This patch proposes to remove the use of the IRQF_DISABLED flag
It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
drivers/char/tlclk.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/char/tlclk.c b/drivers/char/tlclk.c
This patch proposes to remove the use of the IRQF_DISABLED flag
It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
drivers/char/nwbutton.c | 2 +-
drivers/char/rtc.c| 5 ++---
drivers/char/snsc.c | 3 +--
drivers/char/snsc_event.c | 3
This patch proposes to remove the use of the IRQF_DISABLED flag
It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
drivers/char/ipmi/ipmi_si_intf.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Sun, 2013-10-13 at 08:13 +0800, baker.ker...@gmail.com wrote:
> From: "baker.zhang"
>
> fib_table_lookup has included the rcu lock protection.
>
> Signed-off-by: baker.zhang
> ---
> net/ipv4/fib_frontend.c | 4
> 1 file changed, 4 deletions(-)
>
> diff --git a/net/ipv4/fib_frontend.c
This patch proposes to remove the use of the IRQF_DISABLED flag
It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
drivers/char/hpet.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/char/hpet.c b/drivers/char/hpet.c
On Sat, Oct 12, 2013 at 3:54 PM, Guenter Roeck wrote:
> Hi all,
>
> for_each_child_of_node() and similar functions increase the refcount
> on each returned node and expect the caller to release the node by
> calling of_node_put() when done.
>
> Looking through the kernel code, it appears this is
On Sat, Oct 12, 2013 at 12:30:55PM +0200, Borislav Petkov wrote:
> On Sat, Oct 12, 2013 at 11:13:08AM +0100, Matt Fleming wrote:
> > On Sat, 12 Oct, at 03:54:44PM, Dave Young wrote:
> > > Boris:
> > >
> > > For the boot service region overlapping problem I have another idea,
> > > how about
On Sat, Oct 12, 2013 at 11:13:08AM +0100, Matt Fleming wrote:
> On Sat, 12 Oct, at 03:54:44PM, Dave Young wrote:
> > Boris:
> >
> > For the boot service region overlapping problem I have another idea,
> > how about modify your mapping code to always mapping the RUNTIME region
> > (non boot
On Sun, Oct 13, 2013 at 1:50 AM, Greg KH wrote:
> On Sat, Oct 12, 2013 at 02:52:51PM +0800, Ethan Zhao wrote:
>> >> --- a/drivers/base/core.c
>> >> +++ b/drivers/base/core.c
>> >> @@ -1904,8 +1904,7 @@ int device_rename(struct device *dev, const char
>> >> *new_name)
>> >> if (!dev)
>> >>
On Sunday, October 13, 2013 10:35:09 AM Chris Jones wrote:
> As a temporary work around, can you revert to the older version of RPM?
>
Hi Chris,
I was missing rpm-build, I have a patch submitted to force use of rpm-build.
AFAIK, nobody uses legacy rpm anymore since falling back to just rpm
As a temporary work around, can you revert to the older version of RPM?
Regards
On 10/13/2013 05:03 AM, Shawn Starr wrote:
Hello folks,
My usual approach to testing git snapshots of Linus's tree (with custom
patches applied on top) is to make rpm and install this into my system for a
On 13/10/2013, Rafael J. Wysocki wrote:
> -> What about this:
>
> /*
>* The core will not set policy->cur, because cpufreq_driver->get is
> NULL,
>* so we need to set it here. However, we have to guess it, because the
>* current speed is unknown and not detectable
From: "baker.zhang"
fib_table_lookup has included the rcu lock protection.
Signed-off-by: baker.zhang
---
net/ipv4/fib_frontend.c | 4
1 file changed, 4 deletions(-)
diff --git a/net/ipv4/fib_frontend.c b/net/ipv4/fib_frontend.c
index b3f627a..0e9127d 100644
---
Greetings!I am new to kvm and are writing a python script to get the number of
pre-copy cycles during a remote vm migration given memory size M of a VM in
MB, the page dirty rate R of a vm in MB/s. My question is on
how to get the page dirty rate. Does kvm provide a dirty page
log facility
Hi,
On Sun, Oct 13, 2013 at 12:46:18AM +0300, Aaro Koskinen wrote:
> With v3.12-rc4 I can no longer connect to N800 (OMAP2) with USB
> (peripheral, g_ether).
To clarify, I was running v3.12-rc4 on N800/peripheral side and that's
where the problem is; on host side I'm running some old Debian
On 09/30/13 07:19, Masanari Iida wrote:
> Correct spelling typo within various part of the kernel
>
> Signed-off-by: Masanari Iida
Acked-by: Randy Dunlap
Thanks.
> ---
> drivers/acpi/acpica/utobject.c | 2 +-
> drivers/media/i2c/adv7183.c | 2 +-
When audmux_clk is used and clk_prepare_enable function succeed,
the memory alloc'd to buf variable is leaked
Signed-off-by: Felipe Pena
---
sound/soc/fsl/imx-audmux.c |9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/sound/soc/fsl/imx-audmux.c
On 10/11/2013 09:51 AM, Neil Horman wrote:
> Sébastien Dugué reported to me that devices implementing ipoib (which don't
> have
> checksum offload hardware were spending a significant amount of time computing
> checksums. We found that by splitting the checksum computation into two
> separate
On 11 Oct 2013, at 17:55, Will Deacon wrote:
> On Fri, Oct 11, 2013 at 12:47:05PM +0100, Chen Gang wrote:
>> In current kernel wide source code, except other architectures, only
>> s390 scsi drivers use atomic_clear_mask(), and arm/arm64 need not
>> support s390 drivers.
>>
>> So remove
When audmux_clk is used and clk_prepare_enable function succeed,
the memory alloc'd to buf variable is leaked
Signed-off-by: Felipe Pena
---
sound/soc/fsl/imx-audmux.c |9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/sound/soc/fsl/imx-audmux.c
From: "Victor N. Ramos Mello"
Fix a possible memory leak in sun4i_osc_clk_setup().
Moved clock-frequency check to save superfluous allocation.
Signed-off-by: Victor N. Ramos Mello
---
drivers/clk/sunxi/clk-sunxi.c | 16 +---
1 files changed, 9 insertions(+), 7 deletions(-)
diff
The commit 1696d9dc57e062ce5200f6a42a6aaada15b434bb
("ACPI: Remove the old /proc/acpi/event interface")
removed the old /proc/acpi/event interface but did not remove
/proc/acpi/event from ACPI_BUTTON help.
Signed-off-by: Krzysztof Mazur
---
drivers/acpi/Kconfig | 6 +++---
1 file changed, 3
From: Grygorii Strashko
Clean-up to remove depedency with bootmem headers.
Cc: Yinghai Lu
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Grygorii Strashko
Signed-off-by: Santosh Shilimkar
---
drivers/char/mem.c |1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/char/mem.c
From: Grygorii Strashko
Clean-up to remove depedency with bootmem headers.
Cc: Yinghai Lu
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Grygorii Strashko
Signed-off-by: Santosh Shilimkar
---
mm/memory_hotplug.c |1 -
1 file changed, 1 deletion(-)
diff --git a/mm/memory_hotplug.c
Switch to memblock interfaces for early memory allocator
Cc: Yinghai Lu
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Santosh Shilimkar
---
lib/swiotlb.c | 30 --
1 file changed, 16 insertions(+), 14 deletions(-)
diff --git a/lib/swiotlb.c b/lib/swiotlb.c
From: Grygorii Strashko
Clean-up to remove depedency with bootmem headers.
Cc: Yinghai Lu
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Grygorii Strashko
Signed-off-by: Santosh Shilimkar
---
block/blk-ioc.c |1 -
1 file changed, 1 deletion(-)
diff --git a/block/blk-ioc.c
From: Grygorii Strashko
Switch to memblock interfaces for early memory allocator
Cc: Yinghai Lu
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Grygorii Strashko
Signed-off-by: Santosh Shilimkar
---
mm/page_cgroup.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git
Switch to memblock interfaces for early memory allocator
Cc: Yinghai Lu
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Santosh Shilimkar
---
kernel/power/snapshot.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/power/snapshot.c b/kernel/power/snapshot.c
index
Switch to memblock interfaces for early memory allocator
Cc: Yinghai Lu
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Santosh Shilimkar
---
mm/sparse-vmemmap.c |5 +++--
mm/sparse.c | 24 +---
2 files changed, 16 insertions(+), 13 deletions(-)
diff --git
Switch to memblock interfaces for early memory allocator
Cc: Yinghai Lu
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Grygorii Strashko
Signed-off-by: Santosh Shilimkar
---
drivers/firmware/memmap.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Switch to memblock interfaces for early memory allocator
Cc: Yinghai Lu
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Santosh Shilimkar
---
init/main.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/init/main.c b/init/main.c
index af310af..e8d382a 100644
---
Correct ensure_zone_is_initialized() function description according
to the introduced memblock APIs for early memory allocations.
Cc: Yinghai Lu
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Grygorii Strashko
Signed-off-by: Santosh Shilimkar
---
mm/memory_hotplug.c |2 +-
1 file
From: Grygorii Strashko
Switch to memblock interfaces for early memory allocator
Cc: Yinghai Lu
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Grygorii Strashko
Signed-off-by: Santosh Shilimkar
---
mm/hugetlb.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff
Tejun, Yinghai and others,
Here is an attempt to convert the core kernel code to memblock allocator
APIs when used with NO_BOOTMEM. Based on discussion thread [1] and my
limited understanding of the topic, I tried to cook up this RFC with
help from Grygorii. I am counting on reviews, guidance
Switch to memblock interfaces for early memory allocator
Cc: Yinghai Lu
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Santosh Shilimkar
---
mm/percpu.c | 39 +++
1 file changed, 23 insertions(+), 16 deletions(-)
diff --git a/mm/percpu.c b/mm/percpu.c
From: Grygorii Strashko
When debugging is enabled (cmdline has "memblock=debug") the memblock
will display upper memory boundary per each allocated/freed memory range
wrongly. For example:
memblock_reserve: [0x009e7e8000-0x009e7ed000]
_memblock_early_alloc_try_nid_nopanic+0xfc/0x12c
Switch to memblock interfaces for early memory allocator
Cc: Yinghai Lu
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Santosh Shilimkar
---
arch/arm/mach-omap2/omap_hwmod.c |8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/arch/arm/mach-omap2/omap_hwmod.c
Switch to memblock interfaces for early memory allocator
Cc: Yinghai Lu
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Santosh Shilimkar
---
arch/arm/kernel/devtree.c |2 +-
arch/arm/kernel/setup.c |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
From: Grygorii Strashko
Now the Nobootmem allocator will always try to free memory allocated for
reserved memory regions (free_low_memory_core_early()) without taking
into to account current memblock debugging configuration
(CONFIG_ARCH_DISCARD_MEMBLOCK and CONFIG_DEBUG_FS state).
As result if:
Switch to memblock interfaces for early memory allocator
Cc: Yinghai Lu
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Santosh Shilimkar
---
arch/arm/mm/init.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mm/init.c b/arch/arm/mm/init.c
index
From: Grygorii Strashko
The __free_pages_bootmem is used internally by MM core and
already defined in internal.h. So, remove duplicated declaration.
Cc: Yinghai Lu
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Grygorii Strashko
Signed-off-by: Santosh Shilimkar
---
Switch to memblock interfaces for early memory allocator
Cc: Yinghai Lu
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Grygorii Strashko
Signed-off-by: Santosh Shilimkar
---
kernel/printk/printk.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git
Introduce memblock early memory allocation APIs which allow to support
LPAE extension on 32 bits archs. More over, this is the next step
to get rid of NO_BOOTMEM memblock wrapper(nobootmem.c) and directly use
memblock APIs.
The proposed interface will became active if both CONFIG_HAVE_MEMBLOCK
From: Grygorii Strashko
Clean-up to remove depedency with bootmem headers.
Cc: Yinghai Lu
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Grygorii Strashko
Signed-off-by: Santosh Shilimkar
---
drivers/staging/speakup/main.c |2 --
1 file changed, 2 deletions(-)
diff --git
Switch to memblock interfaces for early memory allocator
Cc: Yinghai Lu
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Santosh Shilimkar
---
lib/cpumask.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/cpumask.c b/lib/cpumask.c
index d327b87..e85ff94 100644
Switch to memblock interfaces for early memory allocator
Cc: Yinghai Lu
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Grygorii Strashko
Signed-off-by: Santosh Shilimkar
---
mm/page_alloc.c | 26 ++
1 file changed, 14 insertions(+), 12 deletions(-)
diff --git
Hi,
With v3.12-rc4 I can no longer connect to N800 (OMAP2) with USB
(peripheral, g_ether).
According to git bisect this is caused by:
9b0a1de3c85d99d881c86a29b3d52da7b9c7bd61 is the first bad commit
commit 9b0a1de3c85d99d881c86a29b3d52da7b9c7bd61
Author: Bin Liu
Date: Tue Sep 17 15:33:35
On Sat, 2013-10-12 at 22:13 +0200, Jiri Slaby wrote:
[]
> To fix that, we use %pS only for stack addresses printouts (via newly
> added printk_stack_address) and %pB for regs->ip (via printk_address).
> I.e. we revert to the old behaviour for all except call stacks. And
> since from all those
This patch adds basic board support for APQ8074 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 ++-
Hi Linus,
Please pull from the git repository at
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
pm+acpi-3.12-rc5
to receive ACPI and power management fixes for v3.12-rc5 with
top-most commit 2c5bfce855ead529e2ea6f33757aa26a651d4460
Merge branch 'acpi-pci-hotplug'
on
On Fri, Oct 11, 2013 at 8:42 PM, Jeff Layton wrote:
> On Fri, 11 Oct 2013 20:18:58 -0400
> Scott Lovenberg wrote:
>
>>
>> On Oct 11, 2013, at 19:49, Jeremy Allison wrote:
>>
>> > On Fri, 11 Oct 2013 15:36:43 -0600 Andreas Dilger
>> > wrote:
>> >>>
>> >>> At this point, my main questions are:
Hi all,
for_each_child_of_node() and similar functions increase the refcount
on each returned node and expect the caller to release the node by
calling of_node_put() when done.
Looking through the kernel code, it appears this is hardly ever done,
if at all. Some code even calls of_node_get() on
Signed-off-by: Varun Sethi
---
MAINTAINERS |7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 8a0cbf3..5b6ea5c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3511,6 +3511,13 @@ S: Maintained
F: drivers/net/ethernet/freescale/fs_enet/
F:
from domain.
Once the PCIe device assigned to a guest VM (via VFIO) gets detached from the
iommu domain
(when guest terminates), its PAMU table entry is disabled. So, this would
prevent the device
from being used once it's assigned back to the host.
This patch allows for creation of a default
Factor out PCI specific code in the PAMU driver.
Signed-off-by: Varun Sethi
---
drivers/iommu/fsl_pamu_domain.c | 81 +++
1 file changed, 40 insertions(+), 41 deletions(-)
diff --git a/drivers/iommu/fsl_pamu_domain.c b/drivers/iommu/fsl_pamu_domain.c
index
Consider modules like this:
static int my_init(void)
{
char *map = (void *)0x5;
*map = 3;
return 0;
}
module_init(my_init);
When we turn off FRAME_POINTERs, the very first instruction in that
function causes a BUG. The problem is that we print IP in the BUG
report using %pB (from
The first patch fixes a build failure, when we try to build for a Freescale
platform without PCI support.
The second patch enables a default DMA window for the device, once it's
detached from a domain. In case of vfio, once device is detached from a
guest it can be again used by the host.
The
Loan offer at 3% interest rate,contact: beverlyloanservi...@outlook.com
Note: Reply to this Email Only: beverlyloanservi...@outlook.com
==
Darlehen Angebot bei 3% Zins, Kontakt: beverlyloanservi...@outlook.com
Hinweis:
On 10/12/2013 12:41 PM, Linus Torvalds wrote:
> On Sat, Oct 12, 2013 at 12:28 PM, Matthew Garrett
> wrote:
>>
>> The most likely cause of the problem that we're seeing here is that we're
>> leaving the hardware in a state that isn't compatible with assumptions made
>> by Dell's SMM code. We've
On Wed, Oct 09, 2013 at 07:14:55PM +0900, HATAYAMA Daisuke wrote:
> Hello,
>
> (2013/10/08 21:49), Alexey Dobriyan wrote:
> > On Mon, Oct 7, 2013 at 5:42 AM, HATAYAMA Daisuke
> > wrote:
> >
> >> +static unsigned long
> >> +get_unmapped_area_vmcore(struct file *filp, unsigned long addr,
> >> +
Hi Thierry, Mark,
On Mon, 30 Sep 2013 12:20:34 +0200 Thierry Reding
wrote:
>
> As I'm sure is the case for many of us, I've become very dependent upon
> the linux-next tree. So everytime Stephen goes on vacation I break out
> in a cold sweat.
>
> Here's my attempt at providing temporary
On Saturday, October 12, 2013 08:58:10 PM Viresh Kumar wrote:
> On 12/10/2013, Rafael J. Wysocki wrote:
> > Well, please merge it with the existing comment and use the usual format
> > for comments that are longer than two lines.
>
> I thought these are separate comments and so keeping them
Am Freitag, 11. Oktober 2013, 21:45:57 schrieb Sandy Harris:
Hi Sandy,
>On Fri, Oct 11, 2013 at 2:38 PM, Stephan Mueller
>wrote:
>
>I like the basic idea. Here I'm alternately reading the email and the
>page you link to & commenting on both.
Thank you very much for reviewing both and sharing
On Sat, 2013-10-12 at 18:02 +0200, Dr. H. Nikolaus Schaller wrote:
> While upgrading the GTA04 kernel to 3.12-rc4 we came across
> an issue with libertas/sdio referencing stale memory on ifconfig up
> when trying to load the firmware (for a second time).
>
> I am not at all sure if the patch is
- Original Message -
> From: "Hannes Frederic Sowa"
> To: "Paul E. McKenney" , "Eric Dumazet"
> , "Josh Triplett"
> , linux-kernel@vger.kernel.org, mi...@kernel.org,
> la...@cn.fujitsu.com, dipan...@in.ibm.com,
> a...@linux-foundation.org, "mathieu desnoyers"
> , n...@us.ibm.com,
On Saturday, October 12, 2013 03:39:05 PM Shawn Starr wrote:
> On Saturday, October 12, 2013 03:03:32 PM Shawn Starr wrote:
> > Hello folks,
> >
> > My usual approach to testing git snapshots of Linus's tree (with custom
> > patches applied on top) is to make rpm and install this into my system
On 10/12/13 10:53 AM, Ingo Molnar wrote:
* David Ahern wrote:
On 10/11/13 9:11 AM, David Ahern wrote:
It would be nice to fix the callchain arg handler to not attempt to
process the next argument if it is not fp or dwarf.
Specifically, something like this which maintains syntax and
On Sat, Oct 12, 2013 at 12:28 PM, Matthew Garrett
wrote:
>
> The most likely cause of the problem that we're seeing here is that we're
> leaving the hardware in a state that isn't compatible with assumptions made
> by Dell's SMM code. We've certainly seen that some previous Dell machines
>
On Saturday, October 12, 2013 03:03:32 PM Shawn Starr wrote:
> Hello folks,
>
> My usual approach to testing git snapshots of Linus's tree (with custom
> patches applied on top) is to make rpm and install this into my system for a
> clean add/remove of test kernels.
>
> However, the developers
Windows definitely uses the ACPI reboot vector. The problem with this is that,
depending on what the ACPI reboot vector points to, it may also trigger some
SMM code. Hitting the PCI reboot vector is likely to skip that in most cases,
which results in us breaking a different set of systems that
Hi,
I am fighting with uprobe bug, and perf_event_mmap() complicates
the problem, it is the only reason (afaics) why the forking task
can not do install_special_mapping(new_child_mm). This means that
the child should do this itself, say, from task_work_run() but
this way it can't handle the error
Hello folks,
My usual approach to testing git snapshots of Linus's tree (with custom
patches applied on top) is to make rpm and install this into my system for a
clean add/remove of test kernels.
However, the developers of rpm removed the --target and -ta options, so I
can't take tarball and
So this is a first take to cleanup the posix cpu timers code. It removes
some optimizations that don't seem very worth the code complications to me,
and also bring some locking cleanup (remove use of tasklist_lock), etc..
It has been only lightly tested for now (just ran though the posix timers
When a task is exiting or has exited, its posix cpu timers
don't tick anymore and won't elapse further. It's too late
for them to expire.
So any further call to timer_gettime() on these timers will
return the same remaining expiry time.
The current code optimize this by caching the remaining
When a timer's target is seen to be buried, for example on calls
to timer_gettime(), the posix cpu timers code behaves a bit
like a garbage collector and releases early the reference to the
task.
Then again, this optimization complicates the code for no much
value: it's up to the user to release
Consolidate the clock sampling common code used for both local
and remote targets.
Note that this introduces a tiny user ABI change: if a
PID is passed to clock_gettime() along the clockid,
we used to forbid a process wide clock sample when that
PID doesn't belong to a group leader. Now after
Now that we removed dead thread posix cpu timers caching,
lets remove the dead process wide version. This caching
is similar to the per thread version but it should be even
more rare:
* If the process id dead, we are not reading its timers
status from a thread belonging to its group. So this only
There is no need for the tasklist_lock just to take a process
wide clock sample.
All we need is to get a coherent sample that doesn't race with
exit() and exec():
* exit() may be concurrently reaping a task and flushing its time
* sighand is unstable under exit() and exec(), and the latter also
Timer deletion doesn't need the tasklist lock.
We need to protect against:
* concurrent access to the lists p->cputime_expires and
p->sighand->cputime_expires
* task reaping that may also delete the timer list entry
* timer firing
We already hold the timer lock which protects us against
The posix cpu timers code makes a heavy use of BUG_ON()
but none of these concern fatal issues that require
to stop the machine. So let's just warn the user when
some internal state slips out of our hands.
Signed-off-by: Frederic Weisbecker
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Peter
a0b2062b0904ef07944c4a6e4d0f88ee44f1e9f2
("posix_timers: fix racy timer delta caching on task exit") forgot
to remove the arguments used for timer caching.
Fix this leftover.
Signed-off-by: Frederic Weisbecker
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Peter Zijlstra
Cc: Oleg Nesterov
Cc:
The remaining uses of tasklist_lock were mostly about synchronizing
against sighand modifications, getting coherent and safe group samples
and also thread/process wide timers list handling.
All of this is already safely synchronizable with the target's
sighand lock. Let's use it on these places
Now that we've removed all the optimizations that could
result in NULL timer's targets, we can remove all the
associated special case handling.
Also add some warnings on NULL targets to spot any possible
leftover.
Signed-off-by: Frederic Weisbecker
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc:
Am Freitag, 11. Oktober 2013, 23:28:35 schrieb Theodore Ts'o:
Hi Theodore,
>Hi Stephan,
>
>I haven't had a chance to look at your paper in detail, yet, but a
>quick scan has found a huge red flag for me that puts the rest of your
>analysis in severe doubt for me.
>
>You say that you got really
1 - 100 of 374 matches
Mail list logo
