On Tue, 2013-04-30 at 13:59 +0100, Daniel Kiper wrote:
> On Mon, Apr 29, 2013 at 03:44:09PM +0100, Ian Campbell wrote:
> > On Mon, 2013-04-29 at 12:37 +0100, Daniel Kiper wrote:
> >
> > > This patch enforces on target limit statically defined in Linux Kernel
> > > source and limit defined by
Commit cc014f3 (mmc: sdhci-s3c: remove platform dependencies) changed
the platform dependency in Kconfig to depend on SAMSUNG_SINGLE, meaning
the driver was available only on single zImage Samsung platforms. This
breaks platforms that haven't been converted such as S3C64xx. Revert
that part of
On Tue, 30 Apr 2013, Nicolas Ferre wrote:
> Addition of boolean field to machine_desc structure in commit
> 4dbfa9a25367cfa91aec0e56d75a6905d3242cd3 (ARM: Enable selection of
> SMP operations at boot time) was triggering compilation errors like:
>
> CC
On Sat, Apr 13, 2013 at 11:44:54AM -0700, Linus Torvalds wrote:
> PS. This is the "Make sure 'total' fits in 32 bits first" version. Not
> really tested, but it's just changing the order of operations a bit.
>
> /* We know one of the values has a bit set in the high 32 bits */
> for (;;)
On Tue, 30 Apr 2013 06:59:22 +0200 (CEST)
Jiri Kosina wrote:
> Or have it depend on CONFIG_EXPERT would probably make most sense ... ?
We could also just have it tell you when you screwed up? Something like
the following (compile tested only)?
jon
---
dummy-irq: require the user to specify an
On Tue, 30 Apr 2013, Stephen Rothwell wrote:
> Hi Stefano,
>
> On Mon, 29 Apr 2013 10:50:22 +0100 Stefano Stabellini
> wrote:
> >
> > On Mon, 29 Apr 2013, Catalin Marinas wrote:
> > >
> > > On Mon, Apr 29, 2013 at 08:54:26AM +0100, Stephen Rothwell wrote:
> > > > Today's linux-next merge of
Hi Linus,
The following changes since commit 1166fde6a923c30f4351515b6a9a1efc513e7d00:
SUNRPC: Add barriers to ensure read ordering in rpc_wake_up_task_queue_locked
(2013-03-25 11:23:40 -0400)
are available in the git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git
Hi Linus,
Please pull the following arch/metag changes (see tag message below for
overview).
Thanks
James
The following changes since commit f6161aa153581da4a3867a2d1a7caf4be19b6ec9:
Linux 3.9-rc2 (2013-03-10 16:54:19 -0700)
are available in the git repository at:
Mikael Pettersson writes:
> Write to the fpstate ->mxcsr and ->swd fields in the sigaction handler's
> uc_mcontext.
To me, "sigaction handler's uc_mcontext" sounds like userspace, which really
confuses me:
Even in most recent glibc-2.17, uc_mcontext is of type mcontext_t, which us
defined as:
On Mon, 29 Apr 2013, Tim Chen wrote:
> diff --git a/include/linux/percpu_counter.h b/include/linux/percpu_counter.h
> index d5dd465..5ca7df5 100644
> --- a/include/linux/percpu_counter.h
> +++ b/include/linux/percpu_counter.h
> @@ -22,6 +22,7 @@ struct percpu_counter {
> struct list_head
[ Blast from the past! ]
When merging in 3.4.42 into the 3.4-rt branch I hit a conflict with the
try_to_wake_up_local() call. It seems that the 3.4-rt patch has this
patch applied. Although, this is not applied to any of the other -rt patches.
My question is, what was the final verdict of this
On Mon, 2013-04-29 at 23:17 -0400, kosaki.motoh...@gmail.com wrote:
> From: KOSAKI Motohiro
>
> Currently glibc's rt/tst-cputimer1 testcase is spradically fail because
> a timer created by timer_create() may fire earlier than it's specified.
>
> posix_cpu_timer_set() uses "val" as current time
Hi Robert,
Thanks for the patch. In the first email in this thread I was
proposing the same solution and had asked whether doing this has any
side effects.
That is how this discussion started. I did some experiments and have
got the answers for that. Just for every ones benefit I've re-worded
the
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.10-rc1
to receive ACPI and power management updates for v3.10 with top-most commit
371deb9500831ad1afbf9ea00e373f650deaed2f
Merge branch 'pm-cpufreq'
on top of
On Tue, 30 Apr 2013, Linus Walleij wrote:
> On Wed, Apr 24, 2013 at 12:58 PM, Lee Jones wrote:
>
> > Currently, if DMA information isn't passed from platform data, then DMA
> > will not be used. This patch allows DMA information obtained though Device
> > Tree to be used as well.
> >
> > Cc:
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-edac.git
linux_next
For two edac fixes:
- i7300_edac currently reports a wrong number of DIMMs when
the memory controller is in single channel mode;
- on some Sandy Bridge
On Tue, 2013-04-30 at 12:02 +0200, dl...@gmx.de wrote:
> From: Jan-Simon Möller
>
> The variable name events_group is already in used and led to a compilation
> error
> when using clang to build the Linux Kernel . The fix is just to rename the
> var.
> No functional change. Please apply.
Need
On Wed, Apr 24, 2013 at 12:58 PM, Lee Jones wrote:
> Currently, if DMA information isn't passed from platform data, then DMA
> will not be used. This patch allows DMA information obtained though Device
> Tree to be used as well.
>
> Cc: Russell King
> Cc: Chris Ball
> Cc:
On Mon, Apr 29, 2013 at 03:44:09PM +0100, Ian Campbell wrote:
> On Mon, 2013-04-29 at 12:37 +0100, Daniel Kiper wrote:
>
> > This patch enforces on target limit statically defined in Linux Kernel
> > source and limit defined by hypervisor or host. This way the balloon
> > driver should not attempt
On Fri, Apr 26, 2013 at 12:27:59AM -0400, Olivier Langlois wrote:
> On Fri, 2013-04-19 at 14:47 +0200, Frederic Weisbecker wrote:
>
> >
> > >
> > > I might be mistaken but I believe that firing timers are not rescheduled
> > > in the current interrupt context. They are going to be rescheduled
On Tuesday 30 April 2013 04:00 PM, Vinod Koul wrote:
On Wed, Apr 24, 2013 at 03:24:27PM +0530, Laxman Dewangan wrote:
+
+ /* Enable clock before accessing register */
+ ret = tegra_dma_runtime_resume(dev);
+ if (ret < 0)
+ return ret;
You dont seem to handle
Fix clk_reg_sysctrl() to set main clock registers of new struct
clk_sysctrl even if the registered clock has no parents.
This fixes an issue where "ulpclk" was registered with all clk->reg_*
fields uninitialized, causing a -EINVAL error from clk_prepare().
Cc: Ulf Hansson
Signed-off-by: Fabio
On Mon, Apr 29, 2013 at 03:35:11PM +0100, Ian Campbell wrote:
> On Mon, 2013-04-29 at 12:37 +0100, Daniel Kiper wrote:
> > Notify a host about a guest memory size limit.
> >
> > Idea of this patch was discussed with Ian Campbell and Ian Jackson.
> >
> > Signed-off-by: Daniel Kiper
> > ---
> >
On 04/30/2013 01:58 PM, Stefano Stabellini :
> On Tue, 30 Apr 2013, Geert Uytterhoeven wrote:
>> On Tue, Apr 30, 2013 at 11:33 AM, Nicolas Ferre
>> wrote:
>>> So, I am wondering if the best correction is to add the types.h header file
>>> in the asm/mach/arch.h file, like this:
>>>
>>> ---
Addition of boolean field to machine_desc structure in commit
4dbfa9a25367cfa91aec0e56d75a6905d3242cd3 (ARM: Enable selection of
SMP operations at boot time) was triggering compilation errors like:
CC arch/arm/mach-at91/at91sam9260_devices.o
In file included from
2nd try at this ... going with a more global cc.
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?
It seems that the power interrupt
On Tue, Apr 16, 2013 at 02:05:22PM -0700, Dave Hansen wrote:
> > But since this (most likely) is rtime monotonicity problem it
> > is bug by itself and probably that should be fixed. Can you
> > check second patch attached and see if it trigger the warning.
>
> Yup, it triggers lots of warnings.
Hi all!
The LLVMLinux project is using clang to compile the Linux Kernel. On our way
reaching this endeavour we invite students to submit proposals for work
on LLVM/Clang and the Linux Kernel.
Our GSoC page is:
http://llvm.linuxfoundation.org/index.php/GSoC
as well as
(added Russell to CC, sorry for not including initially)
Hi Vinod
On Tue, 30 Apr 2013, Vinod Koul wrote:
> On Tue, Apr 30, 2013 at 09:11:19AM +0200, Guennadi Liakhovetski wrote:
> > Previously an issue has been discussed, arising on sh-/r-mobile ARM-based
> > systems. There we typically have
On Tue, 30 Apr 2013, Vinod Koul wrote:
> On Fri, Apr 26, 2013 at 08:26:16AM +0200, Guennadi Liakhovetski wrote:
> > SHDMA uses only standard DMA Device Tree bindings. This patch adds
> > documentation, exactly describing the use of the bindings and providing
> > examples.
> >
> > Signed-off-by:
Hi,
>To revert to the old behaviour while still preventing attackers to
>guess the password length, we update the timestamps in one-minute
>intervals by this patch.
Sorry if I miss something, but isn't this an issue that should be very
obviously fixed in user space? Only user space knows
On 04/30/2013 02:40 PM, Sam Ravnborg wrote:
>> SHOW_ALL_DRIVERS" is not very descriptive. I'm not sure if that matters,
>> though. One doesn't need to read the Kconfig files every day =).
>>
>> But presuming most of the drivers would use that, it would add quite a
>> bit of repetition to the
On Tue, 30 Apr 2013, Geert Uytterhoeven wrote:
> On Tue, Apr 30, 2013 at 11:33 AM, Nicolas Ferre
> wrote:
> > So, I am wondering if the best correction is to add the types.h header file
> > in the asm/mach/arch.h file, like this:
> >
> > --- a/arch/arm/include/asm/mach/arch.h
> > +++
On 30/04/13 09:47, Ingo Molnar wrote:
> The other problem is that tip:x86/efi also conflicts with current -git, as
> of v3.9 - due to interaction with an EFI fix tree ...
>
> This is getting ugly pretty fast, so I'd suggest to re-do the merges
> cleanly, not by rebasing the tree, but by redoing
On Monday, April 29, 2013 04:11:06 PM Greg Kroah-Hartman wrote:
> On Mon, Apr 29, 2013 at 02:28:02PM +0200, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Rework the CPU hotplug code in drivers/base/cpu.c to use the
> > generic offline/online support introduced previously instead
On Monday, April 29, 2013 04:10:19 PM Greg Kroah-Hartman wrote:
> On Mon, Apr 29, 2013 at 02:26:56PM +0200, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > In some cases, graceful hot-removal of devices is not possible,
> > although in principle the devices in question support
Hi Sascha,
On Tuesday 30 April 2013 08:16:25 Sascha Hauer wrote:
> On Mon, Apr 29, 2013 at 01:30:01PM +0530, Prabhakar Lad wrote:
> > From: Lad, Prabhakar
> >
> > add OF support for the mt9p031 sensor driver.
> >
> > +static struct mt9p031_platform_data
> > + *mt9p031_get_pdata(struct
On Monday, April 29, 2013 03:16:24 PM Tejun Heo wrote:
> On Mon, Apr 29, 2013 at 03:08:31PM -0700, Tejun Heo wrote:
> > > spent freezing by a factor of 5. It will have a similar effect on a
> > > non-Android system, although those generally don't care about
> > > suspend/resume optimization.
> >
> SHOW_ALL_DRIVERS" is not very descriptive. I'm not sure if that matters,
> though. One doesn't need to read the Kconfig files every day =).
>
> But presuming most of the drivers would use that, it would add quite a
> bit of repetition to the Kconfig files. Well, ok, I have no idea how
> many
Warlich, Christof writes:
> Andi Kleen writes:
> > The FP registers are restored lazily, but the state for this is kept in
> > the kernel.
>
> I'm not sure if I understand "lazily" in this context: Do you mean that FP
> registers _are_ restored within the kernel, but _not_ from a (possibly
On Tue, Apr 30, 2013 at 01:33:18PM +0300, Felipe Balbi wrote:
>
> I think something like 'available on ARCH_OMAP' might be useful,
> however.
In general I try to avoid extending the Kconfig language.
Let's try to keep it simple.
So as long as we can do it within the current language let's not
This patch is used to fix the panic issue of parallel device removal on
different pci hierarchy,
refer to https://bugzilla.kernel.org/show_bug.cgi?id=54411.
[ 418.775140] ioatdma i7core_edac edac_core sg e1000e igb dca ptp pps_core
sd_mod crc_t10dif megaraid_sas mptsas mptscsih mptbase
>From a870da3615988f53a8949e5f8c907b079162067b Mon Sep 17 00:00:00 2001
From: Gu Zheng
Date: Tue, 30 Apr 2013 18:45:12 +0800
Subject: [PATCH v2 4/4] PCI: Check if the pci device get removed from pci tree
already in remove_callback
We found nested removing through:
echo -n 1 >
>From 055d93b0e9a29f3786996f90b7893bd6eb4d244b Mon Sep 17 00:00:00 2001
From: Gu Zheng
Date: Tue, 30 Apr 2013 17:23:31 +0900
Subject: [PATCH v2 3/4] PCI: Convert alloc_pci_dev(void) to pci_alloc_dev(bus)
instead
Use the new pci_alloc_dev(bus) to replace the existing using of
>From 888e824c01f9c039622a2ab74c3df3b884fd7b12 Mon Sep 17 00:00:00 2001
From: Gu Zheng
Date: Mon, 22 Apr 2013 19:04:07 +0900
Subject: [PATCH v2 1/4] PCI: Introduce pci_alloc_dev(struct pci_bus*) to replace
alloc_pci_dev()
Now here we introduce a new struct pci_dev *pci_alloc_dev(struct pci_bus
>From ff785e84afd2558dd52de8e73c4f75b7563a595b Mon Sep 17 00:00:00 2001
From: Gu Zheng
Date: Tue, 30 Apr 2013 17:22:02 +0900
Subject: [PATCH v2 2/4] PCI: introduce pci_bus_get()/pci_bus_put() to hide
pci_bus' reference management
Signed-off-by: Gu Zheng
---
drivers/pci/bus.c | 15
Hi Maxime,
El 30/04/13 06:56, Maxime Ripard escribió:
> The Allwinner A13 has a smaller clock set than the one found in the A10.
> Fix the A13 device tree and documentation to reflect this.
>
> Signed-off-by: Maxime Ripard
The patch looks fine to me.
Acked-by: Emilio López
> ---
>
On 26/04/13 16:43, Seiji Aguchi wrote:
> I tested pstore_read() as well.
> And /dev/pstore/dmesg-efi-X was empty
>
> This must be __efivar_entry_get() instead of __efivar_entry_size().
> (We may have to introduce _efivar_entry_get_locked() to avoid deadlock.)
>
> I think it is a final bug
my kernel version: linux 2.6.34.14
in block/blk-core.c file, blk_alloc_queue_node() function:
struct request_queue *blk_alloc_queue_node(gfp_t gfp_mask, int node_id)
{
...
setup_timer(>timeout, blk_rq_timed_out_timer, (unsigned long) q);
...
}
when bio request timeout, execute
Hi Maxime,
El 30/04/13 06:56, Maxime Ripard escribió:
> The A13 has a lot less clocks than the one found in the Allwinner A10.
> Add these stripped down clocks to the clock driver and in the
> documentation.
>
> Signed-off-by: Maxime Ripard
This patch looks good to me.
Acked-by: Emilio López
Add platform data and dt bindings to allow user override disabled state.
Signed-off-by: Marek Belisko
---
.../devicetree/bindings/clock/silabs,si5351.txt|5 +++
drivers/clk/clk-si5351.c | 36 +---
include/linux/platform_data/si5351.h
On Tue, Apr 30, 2013 at 09:11:19AM +0200, Guennadi Liakhovetski wrote:
> Previously an issue has been discussed, arising on sh-/r-mobile ARM-based
> systems. There we typically have multiple DMA controller instances with
> exactly equal or very similar capabilities. Each of them can serve the
On Fri, Apr 26, 2013 at 08:26:16AM +0200, Guennadi Liakhovetski wrote:
> SHDMA uses only standard DMA Device Tree bindings. This patch adds
> documentation, exactly describing the use of the bindings and providing
> examples.
>
> Signed-off-by: Guennadi Liakhovetski
> ---
>
> This patch adds
* Stanislaw Gruszka wrote:
> Here is patch, which add Linus cputime scaling algorithm to the kernel.
>
> This is follow up of commit d9a3c9823a2e6a543eb7807fb3d15d8233817ec5
> "sched: Lower chances of cputime scaling overflow" which try to avoid
> multiplication overflow, but not guarantee
On 04/30/2013 01:33 PM, Felipe Balbi wrote:
> Hi,
>
> On Tue, Apr 30, 2013 at 12:24:40PM +0200, Sam Ravnborg wrote:
>>> So, my idea is to have a new kind of Kconfig dependency. I'll call it
>>> "softdepends" in lack of better name. A driver maintainer could use
>>> "softdepends on ARCH_OMAP",
Signed-off-by: Alexander Gordeev
---
drivers/iommu/irq_remapping.c | 12 +++-
1 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/drivers/iommu/irq_remapping.c b/drivers/iommu/irq_remapping.c
index d56f8c1..9eeb6cf 100644
--- a/drivers/iommu/irq_remapping.c
+++
On Wed, Apr 24, 2013 at 03:24:27PM +0530, Laxman Dewangan wrote:
> Implement suspend/resume callbacks to store APB DMA channel's
> register on suspend and restore APB DMA channel's register on
> resume.
>
> Signed-off-by: Laxman Dewangan
> ---
> drivers/dma/tegra20-apb-dma.c | 65
>
On Tue, Apr 30 2013, Dmitry Monakhov wrote:
> On Mon, 22 Apr 2013 11:57:52 +0400, Dmitry Monakhov
> wrote:
> Non-text part: multipart/mixed
> >
> Seriously. Am I an only one who use blktrace?
I do :-)
> Jens can you please take it?
Thanks, will do.
--
Jens Axboe
--
To unsubscribe from
On Fri, Apr 26, 2013 at 10:41:23AM +0100, Russell King - ARM Linux wrote:
> On Fri, Apr 26, 2013 at 01:46:46PM +0530, Vinod Koul wrote:
> > On Fri, Apr 26, 2013 at 10:28:39AM +0200, Linus Walleij wrote:
> > > On Thu, Apr 25, 2013 at 4:11 PM, Arnd Bergmann wrote:
> > >
> > > > The dma engine
* Clark Williams | 2013-04-29 16:19:25 [-0500]:
>On Mon, 29 Apr 2013 22:12:02 +0200
>Sebastian Andrzej Siewior wrote:
>> - suspend / resume seems to program program the timer wrong and wait
>> ages until it continues.
>>
>
>It has to be something we're doing when we apply RT to
Hi,
On Tue, Apr 30, 2013 at 12:24:40PM +0200, Sam Ravnborg wrote:
> > So, my idea is to have a new kind of Kconfig dependency. I'll call it
> > "softdepends" in lack of better name. A driver maintainer could use
> > "softdepends on ARCH_OMAP", instead of "depends on ARCH_OMAP", to say
> > that
Hi,
On Tue, Apr 30, 2013 at 03:17:16PM +0530, Srivatsa S. Bhat wrote:
> I get the following warning on boot:
>
> [ cut here ]
> WARNING: at drivers/base/core.c:575 device_create_file+0x9a/0xa0()
> Hardware name: -[8737R2A]-
> Write permission without 'store'
> Modules
On Tuesday 30 April 2013, Samuel Ortiz wrote:
> I suppose we don't expect any non MFD drivers to use this interface ?
Yes, that is correct.
> If that's so, I'll take it through mfd-next.
Ok, thanks!
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
>
> So, my idea is to have a new kind of Kconfig dependency. I'll call it
> "softdepends" in lack of better name. A driver maintainer could use
> "softdepends on ARCH_OMAP", instead of "depends on ARCH_OMAP", to say
> that this driver does not actually build depend on ARCH_OMAP, but for
> all
Hi Arnd,
On Tue, Apr 30, 2013 at 12:00:19AM +0200, Arnd Bergmann wrote:
> There is no reason for ssbi to have its own top-level driver directory
> when the only users of this interface are all MFD drivers. The only
> mainline driver using it at the moment (PM8921) is marked broken and in
> fact
On 30/04/13 11:04, Kirill A. Shutemov wrote:
On Tue, Apr 30, 2013 at 09:52:34AM +0100, Serban Constantinescu wrote:
Hi Kirill,
On 30/04/13 08:31, Kirill A. Shutemov wrote:
On Fri, Apr 12, 2013 at 01:25:49PM +0100, Serban Constantinescu wrote:
The patch set has been successfully tested with a
Add new property tx-rx-clk-separate which we can distinquish between common
and separate clock for tx and rx blocks.
Signed-off-by: Marek Belisko
---
.../bindings/sound/davinci-mcasp-audio.txt |2 ++
include/linux/platform_data/davinci_asp.h |1 +
> - *busw = 0;
> - if (le16_to_cpu(p->features) & 1)
> - *busw = NAND_BUSWIDTH_16;
> +
> + *busw = (onfi_feature(chip) & ONFI_FEATURE_16_BIT_BUS) ?
> + NAND_BUSWIDTH_16 : 0;
Is this really needed ? you have already checked the 'onfi_version' above in
From: Jan-Simon Möller
The variable name events_group is already in used and led to a compilation error
when using clang to build the Linux Kernel . The fix is just to rename the var.
No functional change. Please apply.
Fix suggested in discussion by PaX Team
Signed-off-by: Jan-Simon Möller
On Tue, 2013-04-30 at 11:49 +0200, Mike Galbraith wrote:
> On Tue, 2013-04-30 at 11:35 +0200, Mike Galbraith wrote:
> > On Tue, 2013-04-30 at 10:41 +0200, Ingo Molnar wrote:
>
> > > Which are the workloads where 'powersaving' mode hurts workload
> > > performance measurably?
> >
> > Well,
The Allwinner A13 has a smaller clock set than the one found in the A10.
Fix the A13 device tree and documentation to reflect this.
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/sun5i-a13.dtsi | 35 ---
1 file changed, 12 insertions(+), 23 deletions(-)
diff
The A13 has a lot less clocks than the one found in the Allwinner A10.
Add these stripped down clocks to the clock driver and in the
documentation.
Signed-off-by: Maxime Ripard
---
Documentation/devicetree/bindings/clock/sunxi.txt | 117 +++--
Hi,
I have an idea to improve the Kconfig dependencies, especially for
subsystem maintainers. First a bit of history:
I recently changed the Kconfig rules for omapdss driver to not depend on
OMAP platform, as the driver itself uses no OMAP specific APIs, and can
be compiled fine on, say, x86.
On Tue, 2013-04-30 at 11:35 +0200, Mike Galbraith wrote:
> On Tue, 2013-04-30 at 10:41 +0200, Ingo Molnar wrote:
> > Which are the workloads where 'powersaving' mode hurts workload
> > performance measurably?
>
> Well, it'll lose throughput any time there's parallel execution
> potential but
I get the following warning on boot:
[ cut here ]
WARNING: at drivers/base/core.c:575 device_create_file+0x9a/0xa0()
Hardware name: -[8737R2A]-
Write permission without 'store'
Modules linked in: sb_edac(+) edac_core i2c_i801 i2c_core lpc_ich mfd_core
shpchp wmi ioatdma
Commit b00adbe0 ("ARM: sunxi: Rename uart nodes to serial") changed the
node names in the DTSI, changes that were not accordingly made to the
Mini X-Plus device tree. This breakage slipped through because it was
not properly declared in the Makefile.
Fix both issues.
Signed-off-by: Maxime Ripard
From: Jan-Simon Möller
Signed-off-by: Jan-Simon Möller
---
include/acpi/acpiosxf.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/acpi/acpiosxf.h b/include/acpi/acpiosxf.h
index 5b3d2bd..64b8c76 100644
--- a/include/acpi/acpiosxf.h
+++ b/include/acpi/acpiosxf.h
@@
On Tue, Apr 30, 2013 at 11:33 AM, Nicolas Ferre wrote:
> So, I am wondering if the best correction is to add the types.h header file
> in the asm/mach/arch.h file, like this:
>
> --- a/arch/arm/include/asm/mach/arch.h
> +++ b/arch/arm/include/asm/mach/arch.h
> @@ -8,6 +8,8 @@
> * published by
On Tue, 2013-04-30 at 10:41 +0200, Ingo Molnar wrote:
> * Mike Galbraith wrote:
>
> > On Tue, 2013-04-30 at 07:16 +0200, Mike Galbraith wrote:
> >
> > > Well now, that's not exactly what I expected to see for AIM7 compute.
> > > Filesystem is munching cycles otherwise used for compute when
Here is patch, which add Linus cputime scaling algorithm to the kernel.
This is follow up of commit d9a3c9823a2e6a543eb7807fb3d15d8233817ec5
"sched: Lower chances of cputime scaling overflow" which try to avoid
multiplication overflow, but not guarantee that the overflow will not
happen.
Linus
Due to rounding in scale_stime(), for big numbers, scaled stime values
will grow in chunks. Since rtime grow in jiffies and we calculate utime
like below:
prev->stime = max(prev->stime, stime);
prev->utime = max(prev->utime, rtime - prev->stime);
we could erroneously account
This reverts commit f792685006274a850e6cc0ea9ade275ccdfc90bc.
Scaling cputime code was changed and does not need div64_u64_rem
primitives. They seems to have no other users, so let's remove them.
Signed-off-by: Stanislaw Gruszka
---
include/linux/math64.h | 19 +--
lib/div64.c
Dave Hansen reported strange utime/stime values on his system:
https://lkml.org/lkml/2013/4/4/435
This happens because prev->stime value is bigger than rtime value.
Root of the problem are non-monotonic rtime values (i.e. current rtime
is smaller than previous rtime) and that should be debugged
Hi,
Today I discovered an issue while building linux-next for at91:
CC arch/arm/mach-at91/at91sam9260_devices.o
In file included from
/home/nferre/dev/lnx_buid_test/arch/arm/mach-at91/at91sam9260_devices.c:12:0:
/home/nferre/dev/lnx_buid_test/arch/arm/include/asm/mach/arch.h:46:2: error:
Hi Steve and all RT Folks
> I'm pleased to announce the 3.4.41-rt55-feat3 feature release.
>
> Note, I first uploaded -feat2 then realized I didn't add a compile fix by
> Mike Galbraith, and then created the -feat3 with that fix.
I just wanted to say thanks that this patch enables compilation
From: Yasuaki Ishimatsu
If system can create movable node which all memory of the
node is allocated as ZONE_MOVABLE, setup_node_data() cannot
allocate memory for the node's pg_data_t.
So, use memblock_alloc_try_nid() instead of memblock_alloc_nid()
to retry when the first allocation fails.
The Hot-Pluggable field in SRAT suggests if the memory could be
hotplugged while the system is running. Print it as well when
parsing SRAT will help users to know which memory is hotpluggable.
Signed-off-by: Tang Chen
---
arch/x86/mm/srat.c |9 ++---
1 files changed, 6 insertions(+), 3
The Hot-Pluggable Fired in SRAT specified which memory ranges are hotpluggable.
We will arrange hotpluggable memory as ZONE_MOVABLE for users who want to use
memory hotplug functionality. But this will cause NUMA performance decreased
because kernel cannot use ZONE_MOVABLE.
So we improve
Since Yinghai has implement "Allocate pagetable pages in local node", for a
node with hotpluggable memory, we have to allocate pagetable pages first, and
then reserve the rest as hotpluggable memory in memblock.
But the kernel parse SRAT first, and then initialize memory mapping. So we have
to
On Mon, Apr 22, 2013 at 12:22:32PM +0200, Nicolas Ferre wrote:
> On 04/19/2013 11:11 AM, ludovic.desroc...@atmel.com :
> > From: Ludovic Desroches
> >
> > Update at_hdmac driver to support generic DMA device tree binding. Devices
> > can still request channel with dma_request_channel() then it
There is no flag in memblock to discribe what type the memory is.
Sometimes, we may use memblock to reserve some memory for special usage.
For example, as Yinghai did in his patch, allocate pagetables on local
node before all the memory on the node is mapped.
Please refer to Yinghai's patch:
v1:
Since we modify movablecore boot option to support
"movablecore=acpi", this patch adds doc for it.
Signed-off-by: Tang Chen
---
Documentation/kernel-parameters.txt |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/Documentation/kernel-parameters.txt
If all the memory ranges in SRAT are hotpluggable, we should not
arrange them all in ZONE_MOVABLE. Otherwise the kernel won't have
enough memory to boot.
This patch introduce a global variable kernel_nodemask to mark
all the nodes the kernel resides in. And no matter if they are
hotpluggable, we
In memory hotplug situation, the hotpluggable memory should be
arranged in ZONE_MOVABLE because memory in ZONE_NORMAL may be
used by kernel, and Linux cannot migrate pages used by kernel.
So we need a way to specify hotpluggable memory as movable. It
should be as easy as possible.
According to
We reserved hotpluggable memory in memblock. And when memory initialization
is done, we have to free it to buddy system.
This patch free memory reserved by memblock with flag MEMBLK_HOTPLUGGABLE.
Signed-off-by: Tang Chen
---
include/linux/memblock.h |1 +
mm/memblock.c| 20
On 04/30/2013 02:15 AM, Bjorn Helgaas wrote:
> On Mon, Apr 29, 2013 at 08:19:10AM -0700, Yinghai Lu wrote:
>> On Mon, Apr 29, 2013 at 3:04 AM, Gu Zheng wrote:
>>> On 04/27/2013 05:01 AM, Yinghai Lu wrote:
On Fri, Apr 26, 2013 at 1:53 PM, Bjorn Helgaas wrote:
>
> You can't be
node-life-cycle data (whose life cycle is the same as a node)
allocated by memblock should be marked so that when we free usable
memory to buddy system, we can skip them.
This patch introduces a flag MEMBLK_LOCAL_NODE for memblock to reserve
node-life-cycle data. For now, it is only kernel direct
Since we have introduced hotplug info into struct numa_meminfo, we need
to consider it when cleanup numa_meminfo.
The original logic in numa_cleanup_meminfo() is:
Merge blocks on the same node, holes between which don't overlap with
memory on other nodes.
This patch modifies
Arrange hotpluggable memory as ZONE_MOVABLE will cause NUMA performance
decreased
because the kernel cannot use movable memory.
For users who don't use memory hotplug and who don't want to lose their NUMA
performance, they need a way to disable this functionality.
So, if users specify
We mark out movable memory ranges and reserve them with MEMBLK_HOTPLUGGABLE
flag in
memblock.reserved. This should be done after the memory mapping is initialized
because the kernel now supports allocate pagetable pages on local node, which
are kernel pages.
The reserved hotpluggable will be
301 - 400 of 926 matches
Mail list logo
