On Fri, Aug 2, 2013 at 12:12 PM, Cho KyongHo wrote:
>> -Original Message-
>> From: Rahul Sharma [mailto:r.sh.o...@gmail.com]
>> Sent: Friday, August 02, 2013 2:18 PM
>>
>> Hi Cho,
>>
>> On Fri, Jul 26, 2013 at 5:00 PM, Cho KyongHo wrote:
>> > When a device driver is registered, all constr
On 08/02/2013 12:29 PM, Viresh Kumar wrote:
> On 2 August 2013 12:19, Srivatsa S. Bhat
> wrote:
>> But lsmod shows 0 for the cpufreq driver right? (Note, your related_cpus
>> should have only 1 CPU each, for you to see 0. Else, you'll see a non-zero
>> value due to the very bug/inconsistency that
From: Cong Wang
selinux has some similar definition like union inet_addr,
it can re-use the generic union inet_addr too.
Cc: James Morris
Cc: Stephen Smalley
Cc: Eric Paris
Cc: Paul Moore
Cc: linux-kernel@vger.kernel.org
Cc: linux-security-mod...@vger.kernel.org
Signed-off-by: Cong Wang
---
From: Cong Wang
nfs and cifs define some helper functions for sockaddr,
they can use the generic functions for union inet_addr too.
Since some dlm code needs to compare ->sin_port, introduce a
generic function inet_addr_equal_strict() for it.
Cc: Steve French
Cc: Christine Caulfield
Cc: David
On 2 August 2013 12:39, Srivatsa S. Bhat
wrote:
> I guess you are printing it at an odd time, when the module
> is still running its init function. Perhaps the core kernel
> module infrastructure increments the refcount around that
> region temporarily?
If I think logically, that sounds correct.
From: Cong Wang
Introduce a generic IP address type, union inet_addr, so that
subsystems don't have to use their own definitions. Because
netpoll already defines union inet_addr, just move it to global.
Some of the helper functions will be used by VXLAN IPv6 code too.
This patch also reuses the
Hi,
On Fri, Aug 02, 2013 at 04:38:18PM +1000, Stephen Rothwell wrote:
> Today's linux-next merge of the usb-gadget tree got a conflict in
> drivers/usb/host/ehci-tegra.c between commit d4f09e28d7bc ("USB: host:
> use dev_get_platdata()") from the usb tree and commit d50642794508 ("usb:
> tegra: ho
Hello,
Yes, it works! I get now 11 levels from all black to the brightest.
acpi_listen shows messages
Josep
On 2 August 2013 08:36, Aaron Lu wrote:
> On 08/02/2013 02:25 PM, Josep Lladonosa wrote:
>> Hello,
>>
>> I am using a Lenovo Edge E530 and, with kernel 3.11.0-rc3, I had to
>> change to
Hi Nishant,
On 08/01/2013 06:06 PM, Nishanth Menon wrote:
> On 08/01/2013 09:58 AM, Roger Quadros wrote:
>> USB_DPLL must be initialized and locked at boot so that
>> USB modules can work.
>>
>> Also program USB_DLL_M2 output to half rate.
>>
>> Signed-off-by: Roger Quadros
>> ---
>> drivers/cl
On Fri, Aug 02, 2013 at 02:22:08AM -0400, Johannes Weiner wrote:
> On Thu, Aug 01, 2013 at 11:56:36AM +0900, Minchan Kim wrote:
> > Hi Hannes,
> >
> > On Fri, Jul 19, 2013 at 04:55:25PM -0400, Johannes Weiner wrote:
> > > Each zone that holds userspace pages of one workload must be aged at a
> > >
On Thu 01-08-13 21:39:48, KOSAKI Motohiro wrote:
> On Wed, Jul 31, 2013 at 11:17 PM, Andrew Morton
> wrote:
> > On Wed, 31 Jul 2013 23:11:50 -0400 KOSAKI Motohiro
> > wrote:
> >
> >> >> --- a/fs/drop_caches.c
> >> >> +++ b/fs/drop_caches.c
> >> >> @@ -59,6 +59,8 @@ int drop_caches_sysctl_handler
Le 01/08/2013 19:15, Jiang, Dave a écrit :
> On Thu, 2013-08-01 at 10:11 -0700, Jon Mason wrote:
>> On Wed, Jul 31, 2013 at 03:14:07PM -0700, Jiang, Dave wrote:
>>> I'm ok with enabling this for people that just want to use DMA and not
>>> RAID.
>> I might be crazy, but I'd be in favor of disablin
On Thu, Aug 01, 2013 at 09:03:32PM -0700, Joe Perches wrote:
> There are several drivers in drivers/net/usb/ that
> do not have specific MAINTAINERS that should have
> emails forwarded to the linux-usb mailing list.
>
> Add a section for those drivers.
Thanks, I'll queue this up next week for the
Hello everyone,
I let the system running for almost 12 hours
but the failure didn't show up.
I'll provide you the dropwatch output once the
failure happens again.
- Sebastiano
On Thu, Aug 1, 2013 at 4:40 PM, Sebastiano Spicuglia
wrote:
> Hi Hannes,
>
> here the info about the commit:
>
> comm
Hi,
On Thu, Aug 01, 2013 at 07:07:50PM +0200, Boris BREZILLON wrote:
> @@ -1851,6 +1860,12 @@ fail3:
> fail2:
> free_irq(udc->udp_irq, udc);
> fail1:
> + if (IS_ENABLED(CONFIG_COMMON_CLK) && !IS_ERR(udc->uclk))
> + clk_put(udc->uclk);
> + if (!IS_ERR(udc->fclk))
> +
On 08/02/2013 07:54 AM, Toshi Kani wrote:
..
/*
+ * acpi_root_table_init - Initialize acpi_gbl_root_table_list.
+ *
+ * This function will parse RSDT or XSDT, find all tables' phys addr,
+ * initialize acpi_gbl_root_table_list, and record all tables' phys addr
+ * in acpi_gbl_root_table_lis
Hi,
On Thu, Aug 01, 2013 at 05:52:04PM -0700, Julius Werner wrote:
> This patch simplifies the way the phy-samsung-usb code finds the correct
> power management register to enable PHY clock gating. Previously, the
> code would calculate the register address from a device tree supplied
> base addre
On 2 August 2013 03:50, Joonsoo Kim wrote:
> Now checking whether this cpu is appropriate to balance or not
> is embedded into update_sg_lb_stats() and this checking has no direct
> relationship to this function. There is not enough reason to place
> this checking at update_sg_lb_stats(), except s
On Thu, Aug 01, 2013 at 10:22:19AM -0600, Stephen Warren wrote:
> On 08/01/2013 07:02 AM, Tuomas Tynkkynen wrote:
> > On 08/01/2013 02:22 AM, Stephen Warren wrote:
> >> On 07/31/2013 11:41 AM, Tuomas Tynkkynen wrote:
> >>> Hi all,
> >>>
> >>> Here are the patches for the USB tree to enable USB Host
* Greg KH [130731 05:39]:
> On Wed, Jul 31, 2013 at 12:38:03AM -0700, Tony Lindgren wrote:
> > Hi all,
> >
> > Probably the biggest kernel data bloat issue is in the ARM land, but
> > it also seems that it's becoming a Linux generic issue too, so I
> > guess it could be discussed in either contex
* Jason Cooper [130731 07:00]:
> On Wed, Jul 31, 2013 at 05:33:51AM -0700, Greg KH wrote:
> > On Wed, Jul 31, 2013 at 12:38:03AM -0700, Tony Lindgren wrote:
> > > Hi all,
> > >
> > > Probably the biggest kernel data bloat issue is in the ARM land, but
> > > it also seems that it's becoming a Linu
On Fri, Aug 2, 2013 at 1:56 AM, Aaron Lu wrote:
> On 08/02/2013 02:44 PM, Felipe Contreras wrote:
>> The initial _BCM commands don't work, so the level remains at 100%.
>> Since the level is max_level, acpi_video_bqc_quirk() tries with the
>> first level, which is 0, and 0 happens to be the index
From: "Felipe F. Tonello"
The new ALSA jack API ensures that " Jack" is appended by default.
It's also good practice that all codecs name jacks based on its type.
Signed-off-by: Felipe F. Tonello
---
sound/soc/mid-x86/mfld_machine.c | 2 +-
sound/soc/omap/omap-abe-twl6040.c | 2 +-
sound/s
From: "Felipe F. Tonello"
This patch adds jack support for ALSA KControl.
This support is necessary since the new kcontrol is used by user-space
daemons, such as PulseAudio(>=2.0), to do jack detection.)
Also, HDA's CONFIG_SND_HDA_INPUT_JACK is disabled because it causes to use
standard
snd_ja
From: "Felipe F. Tonello"
On this second version I made sure that the patch series can be bisected.
Also, since HDA codec has it's own jack infrastructure, I just disabled the
support of the core ALSA jack in it. Why? Because it's causing duplication of
controls, although the input events works f
Hi,
On Fri, Aug 02, 2013 at 12:53:53AM -0700, Tony Lindgren wrote:
> > > Basically the data bloat issue is there for the arch code and drivers
> > > and may not show up initially until things have headed the wrong way for
> > > too long.
> >
> > What do you mean by this? You seem to be very vagu
Hi all,
Changes since 20130801:
The ext4 tree still has its build failure so I used the version from
next-20130726.
The usb-gadget tree gained a conflict against the usb tree.
I have created today's linux-next tree at
On 08/02/2013 03:59 PM, Felipe Contreras wrote:
> On Fri, Aug 2, 2013 at 1:56 AM, Aaron Lu wrote:
>> On 08/02/2013 02:44 PM, Felipe Contreras wrote:
>
>>> The initial _BCM commands don't work, so the level remains at 100%.
>>> Since the level is max_level, acpi_video_bqc_quirk() tries with the
>>
On Wed, Jul 31, 2013 at 04:29:01PM +0200, Lothar Waßmann wrote:
> It's always a bad idea to poll on HW bits without a timeout.
>
> The i.MX28 RTC can be easily brought into a state in which the RTC is
> not running (until after a power-on-reset) and thus the status bits
> which are polled in the d
On Fri, Aug 02, 2013 at 12:53:53AM -0700, Tony Lindgren wrote:
> * Greg KH [130731 05:39]:
> > On Wed, Jul 31, 2013 at 12:38:03AM -0700, Tony Lindgren wrote:
> > > Hi all,
> > >
> > > Probably the biggest kernel data bloat issue is in the ARM land, but
> > > it also seems that it's becoming a Lin
In the case of lazy umount, "umount -l", some processes are able to use the
file system even if its mountpoint was disconnected.
At this moment, we should not allow mkfs.f2fs.
This patch adds this condition check.
Signed-off-by: Jaegeuk Kim
---
fsck/main.c| 2 +-
include/f2fs_fs.h | 2
* Mel Gorman [130731 08:28]:
> On Wed, Jul 31, 2013 at 12:38:03AM -0700, Tony Lindgren wrote:
> > Hi all,
> >
> > Probably the biggest kernel data bloat issue is in the ARM land, but
> > it also seems that it's becoming a Linux generic issue too, so I
> > guess it could be discussed in either con
On Fri, Aug 2, 2013 at 3:06 AM, Aaron Lu wrote:
> On 08/02/2013 03:59 PM, Felipe Contreras wrote:
>> On Fri, Aug 2, 2013 at 1:56 AM, Aaron Lu wrote:
>>> On 08/02/2013 02:44 PM, Felipe Contreras wrote:
>>
The initial _BCM commands don't work, so the level remains at 100%.
Since the level
Cc: Ben Greear
Cc: Tejun
Hi Willy,
This patch introduced a bug, which was then fixed by commit 34376a50fb1f
("Fix lockup related to stop_machine being stuck in __do_softirq."),
do we need this fix for 2.6.32 ?
On 2013/6/5 1:23, Willy Tarreau wrote:
> 2.6.32-longterm review patch. If anyone has
On Fri, Aug 02, 2013 at 02:00:42PM +0800, Aaron Lu wrote:
> Assume you have specified to use intel_backlight in xorg.conf
Right, I have:
Section "Device"
Option "Backlight" "intel_backlight"
Identifier "Card0"
Driver "intel"
BusID "PCI:0:2:0"
EndSe
No functional change, just makes the code shorter.
Signed-off-by: Daniel Mack
---
drivers/regulator/max8660.c | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/drivers/regulator/max8660.c b/drivers/regulator/max8660.c
index ba3b8af..a5caaa0 100644
--- a/drivers/re
Introduce an enum and denote the device type via struct i2c_id's
driver_data field rather than comparing strings.
Signed-off-by: Daniel Mack
---
drivers/regulator/max8660.c | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/drivers/regulator/max8660.c b/drivers/re
On Wed, 2013-07-31 at 11:53 +0200, Peter Zijlstra wrote:
> No they're quite unrelated. I think you can measure the max time we've
> ever spend in newidle balance and use that to clip the values.
So I tried using the rq's max newidle balance cost to compare with the
average and used sysctl_migrati
This patch adds devicetree bindings for max8660, along with some
documentation.
Signed-off-by: Daniel Mack
---
.../devicetree/bindings/regulator/max8660.txt | 47 +
drivers/regulator/max8660.c| 79 +-
include/linux/regulator/max8660.h
On 08/02/2013 04:14 PM, Felipe Contreras wrote:
> On Fri, Aug 2, 2013 at 3:06 AM, Aaron Lu wrote:
>> On 08/02/2013 03:59 PM, Felipe Contreras wrote:
>>> On Fri, Aug 2, 2013 at 1:56 AM, Aaron Lu wrote:
On 08/02/2013 02:44 PM, Felipe Contreras wrote:
>>>
> The initial _BCM commands don't w
* Felipe Balbi [130802 01:11]:
> Hi,
>
> On Fri, Aug 02, 2013 at 12:53:53AM -0700, Tony Lindgren wrote:
> > > > Basically the data bloat issue is there for the arch code and drivers
> > > > and may not show up initially until things have headed the wrong way for
> > > > too long.
> > >
> > > Wha
Hi Tomi,
On Thu, Aug 01, 2013 at 03:39:27PM +0300, Tomi Valkeinen wrote:
> Hi,
>
> On 01/08/13 11:40, Maxime Ripard wrote:
> > From: Alexandre Belloni
> >
> > Add support for the Himax HX8369 controller as it is quite similar to the
> > hx8357.
> >
> > Signed-off-by: Alexandre Belloni
> > Sig
Hello,
This patch series prepare the at91 SoCs transition to common clk framework.
This is done by adding a new clock (called usb clock or uclk) to at91_udc
driver. This clock will be used to configure the usb port clock rate.
Best Regards,
Boris
Changes since v2:
- split the patch in 2 parts:
* Jason Cooper [130731 07:25]:
> All,
>
> I'd like to take the opportunity to discuss the layout/config of the arm
> SoCs. By the time the KS rolls around, we should have at least two or more
> use-cases to present and discuss (mvebu, bcm).
>
> Between devicetree and multiplatform the concept o
On Fri, Aug 02, 2013 at 09:16:03AM +0800, Aaron Lu wrote:
> Since the sysfs interface works on your system, I think your problem
> should be different. Can you please file a bug for this? I can provide
> you with a debug patch and then see what happened. Please attach
> acpidump when filing the bug
On 01/08/13 11:40, Maxime Ripard wrote:
> From: Hector Palacios
>
> For a combination of 18bit LCD data bus width and a color
> mode of 32bpp, the driver was setting the color mapping to
> rgb666, which is wrong, as the color in memory realy has an
> rgb888 layout.
>
> This patch also removes th
The AT91 PMC (Power Management Controller) provides an USB clock used by
USB Full Speed host (ohci) and USB Full Speed device (udc).
The usb drivers (ohci and udc) must configure this clock to 48Mhz.
This configuration was formely done in mach-at91/clock.c, but this
implementation will be removed w
This patch adds missing clk_put on fclk and iclk in case the probe function
fails after these clocks have been retrieved.
Signed-off-by: Boris BREZILLON
---
drivers/usb/gadget/at91_udc.c |4
1 file changed, 4 insertions(+)
diff --git a/drivers/usb/gadget/at91_udc.c b/drivers/usb/gadget
* Greg KH [130802 01:16]:
> On Fri, Aug 02, 2013 at 12:53:53AM -0700, Tony Lindgren wrote:
> > * Greg KH [130731 05:39]:
> > > On Wed, Jul 31, 2013 at 12:38:03AM -0700, Tony Lindgren wrote:
> > > > Hi all,
> > > >
> > > > Probably the biggest kernel data bloat issue is in the ARM land, but
> > >
The following changes since commit 07862c1cd6675cde2dd4bd64e64d704ea2185b79:
ARM: clocksource: Add support for MOXA ART SoCs (2013-07-18 15:27:47
+0200)
are available in the git repository at:
git://git.linaro.org/people/dlezcano/clockevents.git
timers/clockevents-next
for you to fetch chan
Add Freescale enhanced direct memory(eDMA) controller support.
The eDMA controller deploys DMAMUXs routing DMA request sources(slot)
to eDMA channels.
This module can be found on Vybrid and LS-1 SoCs.
Signed-off-by: Alison Wang
Signed-off-by: Xiaochun Li
Signed-off-by: Jingchang Lu
---
.../dev
* Russell King - ARM Linux [130731 13:22]:
> On Wed, Jul 31, 2013 at 10:00:17PM +0200, Richard Cochran wrote:
> > On Wed, Jul 31, 2013 at 09:29:35PM +0200, Tomasz Figa wrote:
> > >
> > > I showed you two example solutions that could handle this use case
> > > without
> > > stable binding ABI, j
Signed-off-by: Jingchang Lu
---
arch/arm/mach-imx/clk-vf610.c | 5 +
include/dt-bindings/clock/vf610-clock.h | 6 +-
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mach-imx/clk-vf610.c b/arch/arm/mach-imx/clk-vf610.c
index b169a39..29f88a2 100644
--- a/a
Signed-off-by: Jingchang Lu
---
arch/arm/boot/dts/vf610.dtsi | 49 +
include/dt-bindings/dma/vf610-edma.h | 103 +++
2 files changed, 152 insertions(+)
create mode 100644 include/dt-bindings/dma/vf610-edma.h
diff --git a/arch/arm/boot/dts
On 08/02/2013 01:58 AM, Casey Schaufler wrote:
> On 6/27/2013 2:11 PM, Casey Schaufler wrote:
>> On 6/11/2013 5:55 AM, Tomasz Stanislawski wrote:
>>> This patch adds a hash table to quicken searching of a smack label by its
>>> name.
>>>
>>> Basically, the patch improves performance of SMACK initi
> -Original Message-
> From: Preeti U Murthy [mailto:pre...@linux.vnet.ibm.com]
> Sent: Friday, August 02, 2013 1:23 PM
> To: Joonsoo Kim
> Cc: Ingo Molnar; Peter Zijlstra; linux-kernel@vger.kernel.org; Mike
> Galbraith; Paul Turner; Alex Shi; Vincent Guittot; Morten Rasmussen;
> Namhyung
Hello Richard,
On 01/08/2013 09:37, Richard Genoud wrote:
2013/8/1 Boris BREZILLON :
Hello,
This patch series move at91 SoCs peripheral id definitions from machine
specific include dir to dt-bindings include dir.
These macros are used to reference interrupts instead of peripheral numbers.
Thi
Commit-ID: 8f898fbbe5ee5e20a77c4074472a1fd088dc47d1
Gitweb: http://git.kernel.org/tip/8f898fbbe5ee5e20a77c4074472a1fd088dc47d1
Author: Rik van Riel
AuthorDate: Wed, 31 Jul 2013 22:14:21 -0400
Committer: Ingo Molnar
CommitDate: Thu, 1 Aug 2013 09:10:26 +0200
sched/x86: Optimize switch_m
Commit-ID: 41e85ce8220c6e5fdef706fda6696cd291115b63
Gitweb: http://git.kernel.org/tip/41e85ce8220c6e5fdef706fda6696cd291115b63
Author: Oleg Nesterov
AuthorDate: Thu, 1 Aug 2013 18:59:41 +0200
Committer: Ingo Molnar
CommitDate: Fri, 2 Aug 2013 11:02:42 +0200
hung_task debugging: Print m
On Fri, Aug 02, 2013 at 09:51:45AM +0200, Vincent Guittot wrote:
> On 2 August 2013 03:50, Joonsoo Kim wrote:
> > Now checking whether this cpu is appropriate to balance or not
> > is embedded into update_sg_lb_stats() and this checking has no direct
> > relationship to this function. There is not
* tip-bot for Rik van Riel wrote:
> Commit-ID: 8f898fbbe5ee5e20a77c4074472a1fd088dc47d1
> Gitweb: http://git.kernel.org/tip/8f898fbbe5ee5e20a77c4074472a1fd088dc47d1
> Author: Rik van Riel
> AuthorDate: Wed, 31 Jul 2013 22:14:21 -0400
> Committer: Ingo Molnar
> CommitDate: Thu, 1 Aug 2
On Thu, 2013-08-01 at 21:13 -0400, Ed Cashin wrote:
> Thanks.
>
> I agree that we could do that. I'm not sure it increases readability to put
> this much stuff on one line, though. What is the motivation?
Motivation is to explicitly show that that operation is to calculate a
minimum of two th
There is no flag in memblock to describe what type the memory is.
Sometimes, we may use memblock to reserve some memory for special usage.
And we want to know what kind of memory it is. So we need a way to
differentiate memory for different usage.
In hotplug environment, we want to reserve hotplug
Linux cannot migrate pages used by the kernel due to the direct mapping
(va = pa + PAGE_OFFSET), any memory used by the kernel cannot be hot-removed.
So when using memory hotplug, we have to prevent the kernel from using
hotpluggable memory.
The ACPI table SRAT (System Resource Affinity Table) con
In the following patches, we need to call get_ramdisk_{image|size}()
to get initrd file's address and size. So make these two functions
global.
v1 -> v2:
As tj suggested, make these two function static inline in
arch/x86/include/asm/setup.h.
Signed-off-by: Tang Chen
Reviewed-by: Zhang Yanfei
--
Besides the phys addr of the acpi tables, it will be very convenient if
we also have the signature of each table in acpi_gbl_root_table_list at
early time. We can find SRAT easily by comparing the signature.
This patch alse record signature and some other info in
acpi_gbl_root_table_list at early
* Jiri Olsa wrote:
> On Tue, Jul 30, 2013 at 06:18:57PM +0900, Namhyung Kim wrote:
> > This patchset implements a front-end tool for kernel's ftrace. It
> > uses function_graph tracer by default and normal function tracer is
> > also supported. (Of course you need to enable those tracers in yo
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
Reviewed-by: Wanpeng Li
Reviewed-by: Zhang Yanfei
Acked-by: Tejun Heo
---
a
Arrange hotpluggable memory as ZONE_MOVABLE will cause NUMA performance down
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 we improved movablecore boot option.
The Hot-Pluggable fired in SRAT specifies which memory is hotpluggable.
As we mentioned before, if hotpluggable memory is used by the kernel,
it cannot be hot-removed. So memory hotplug users may want to set all
hotpluggable memory in ZONE_MOVABLE so that the kernel won't use it.
Memory hotplug us
Linux kernel cannot migrate pages used by the kernel. As a result, hotpluggable
memory used by the kernel won't be able to be hot-removed. To solve this
problem, the basic idea is to prevent memblock from allocating hotpluggable
memory for the kernel at early time, and arrange all hotpluggable memo
This patch introduce early_acpi_firmware_srat() to find the
phys addr of SRAT provided by firmware. And call it in
find_hotpluggable_memory().
Since we have initialized acpi_gbl_root_table_list earlier,
and store all the tables' phys addrs and signatures in it,
it is easy to find the SRAT.
Signed
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. Otherw
In find_hotpluggable_memory, once we find out a memory region which is
hotpluggable, we want to mark them in memblock.memory. So that we could
control memblock allocator not to allocte hotpluggable memory for the kernel
later.
To achieve this goal, we introduce MEMBLOCK_HOTPLUG flag to indicate th
At early time, memblock will reserve some memory for the kernel,
such as the kernel code and data segments, initrd file, and so on，
which means the kernel resides in these memory regions.
Even if these memory regions are hotpluggable, we should not
mark them as hotpluggable. Otherwise the kernel w
Rebased to Linux 3.11-rc3, and followed some advice from Toshi Kani.
Please refer to the change log in the end of the comment.
This patch-set aims to solve some problems at system boot time
to enhance memory hotplug functionality.
[Background]
The Linux kernel cannot migrate pages used by the ke
On Fri, Aug 02, 2013 at 11:35:29AM +0300, Tomi Valkeinen wrote:
> On 01/08/13 11:40, Maxime Ripard wrote:
> > From: Hector Palacios
> >
> > For a combination of 18bit LCD data bus width and a color
> > mode of 32bpp, the driver was setting the color mapping to
> > rgb666, which is wrong, as the c
The comments of find_cpio_data() says:
* @offset: When a matching file is found, this is the offset to the
* beginning of the cpio. ..
But according to the code,
dptr = PTR_ALIGN(p + ch[C_NAMESIZE], 4);
nptr = PTR_ALIGN(dptr + ch[C_FILESIZE], 4);
*offset = (long)npt
On 2013-08-01 23:16, Konrad Rzeszutek Wilk wrote:
On Wed, Jul 31, 2013 at 04:41:32PM -0600, Bjorn Helgaas wrote:
On Tue, Jul 23, 2013 at 9:08 PM, Zhenzhong Duan
wrote:
xen_initdom_restore_msi_irqs trigger a hypercall to restore addr/data/mask
in dom0. It's better to do the same for default_re
In ACPI, SRAT(System Resource Affinity Table) contains NUMA info.
The memory affinities in SRAT record every memory range in the
system, and also, flags specifying if the memory range is
hotpluggable.
(Please refer to ACPI spec 5.0 5.2.16)
memblock starts to work at very early time, and SRAT has n
In acpi_initrd_override(), it checks several things to ensure the
table it found is valid. In later patches, we need to do these check
somewhere else. So this patch introduces a common function
acpi_verify_initrd() to do all these checks, and reuse it in different
places. The function will be used
We have split acpi_table_init() into two steps:
1. Pares RSDT or XSDT, and initialize acpi_gbl_root_table_list.
This step will record all tables' physical address in memory.
2. Check acpi initrd table override and install all tables into
acpi_gbl_root_table_list.
This patch does step 1 earli
The macro INVALID_TABLE() is defined like this:
#define INVALID_TABLE(x, path, name)\
{ pr_err("ACPI OVERRIDE: " x " [%s%s]\n", path, name); continue; }
And it is used like this:
for (...) {
...
if (...)
* Raghavendra K T wrote:
> On 08/01/2013 02:34 PM, Raghavendra K T wrote:
> >On 08/01/2013 01:15 PM, Gleb Natapov wrote:
> >>>Shall I consider this as an ack for kvm part?
> >>>
> >>For everything except 18/18. For that I still want to see numbers. But
> >>18/18 is pretty independent from the re
Fix some trivial typos in comments.
Signed-off-by: Jianguo Wu
---
mm/zbud.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/mm/zbud.c b/mm/zbud.c
index ad1e781..9451361 100644
--- a/mm/zbud.c
+++ b/mm/zbud.c
@@ -16,7 +16,7 @@
*
* zbud works by storing compressed
* Raghavendra K T wrote:
> On 07/31/2013 11:54 AM, Gleb Natapov wrote:
> >On Tue, Jul 30, 2013 at 10:13:12PM +0530, Raghavendra K T wrote:
> >>On 07/25/2013 03:08 PM, Raghavendra K T wrote:
> >>>On 07/25/2013 02:45 PM, Gleb Natapov wrote:
> On Thu, Jul 25, 2013 at 02:47:37PM +0530, Raghavend
On 02/08/2013 11:04, boris brezillon wrote:
> Hello Richard,
>
> On 01/08/2013 09:37, Richard Genoud wrote:
>> 2013/8/1 Boris BREZILLON :
>>> Hello,
>>>
>>> This patch series move at91 SoCs peripheral id definitions from machine
>>> specific include dir to dt-bindings include dir.
>>> These macros
In ACPI SRAT(System Resource Affinity Table), there is a memory affinity for
each
memory range in the system. In each memory affinity, there is a field indicating
that if the memory range is hotpluggable.
This patch parses all the memory affinities in SRAT only, and find out all the
hotpluggable
On 08/02/2013 02:35 PM, 김준수 wrote:
>
>
>> -Original Message-
>> From: Preeti U Murthy [mailto:pre...@linux.vnet.ibm.com]
>> Sent: Friday, August 02, 2013 1:23 PM
>> To: Joonsoo Kim
>> Cc: Ingo Molnar; Peter Zijlstra; linux-kernel@vger.kernel.org; Mike
>> Galbraith; Paul Turner; Alex Shi;
Hi Daniel,
On 22/07/13 12:21, Sudeep KarkadaNagesha wrote:
> From: Sudeep KarkadaNagesha
>
> This patch series adds support to configure the rate and enable the event
> stream for architected timer. Since the timer control register is reset to
> zero on warm boot, CPU PM notifier is added to re-
On Thu, Jul 18, 2013 at 09:50:26AM +0100, Jonas Jensen wrote:
> Add binding document for MOXA ART SoCs interrupt controller.
>
> Signed-off-by: Jonas Jensen
> ---
>
> Notes:
> The MOXA ART irqchip driver was added without accompanying devicetree
> document.
> ( in next-20130716 driver
On 2 August 2013 12:19, Srivatsa S. Bhat
wrote:
> On 08/02/2013 10:07 AM, Viresh Kumar wrote:
>> So, we can't rmmod the module as soon as it is inserted and so the
>> problem stays as is. :(
>>
>
> No, we get one step closer to the solution, since we fix the inconsistency
> between refcounts. Next
On 08/02/2013 02:53 PM, Ingo Molnar wrote:
* Raghavendra K T wrote:
On 08/01/2013 02:34 PM, Raghavendra K T wrote:
On 08/01/2013 01:15 PM, Gleb Natapov wrote:
Shall I consider this as an ack for kvm part?
For everything except 18/18. For that I still want to see numbers. But
18/18 is pret
commit a59f4e079d19464eebb9b06513a1d4f55fdae5ba
Author: Zhu Yanhai
Date: Tue Jan 8 12:56:52 2013 +0800
sched: Fix the broken sched_rr_get_interval()
Without this patch, syscall sched_rr_get_interval() can return wrong
value, and the bug was introduced in 2.6.24, so this looks like a
candid
On 31 July 2013 22:09, Viresh Kumar wrote:
> On 31 July 2013 22:06, Sachin Kamat wrote:
>> Hi Viresh,
>>
>> On 31 July 2013 19:49, Viresh Kumar wrote:
>>> CPUFreq core does following at multiple places:
>>> module_{get|put}(cpufreq_driver->owner)).
>>>
>>> This is done to make sure module doesn'
On 08/02/2013 11:32 AM, Sudeep KarkadaNagesha wrote:
> Hi Daniel,
>
> On 22/07/13 12:21, Sudeep KarkadaNagesha wrote:
>> From: Sudeep KarkadaNagesha
>>
>> This patch series adds support to configure the rate and enable the event
>> stream for architected timer. Since the timer control register is
I am announcing the release of the Linux 3.5.7.18 kernel.
The updated 3.5.y tree can be found at:
git://kernel.ubuntu.com/ubuntu/linux.git linux-3.5.y
and can be browsed at:
http://kernel.ubuntu.com/git?p=ubuntu/linux.git;h=refs/heads/linux-3.5.y;a=shortlog
The diff from v3.5.7.17 is posted
On 02/08/13 10:48, Daniel Lezcano wrote:
> On 08/02/2013 11:32 AM, Sudeep KarkadaNagesha wrote:
>> Hi Daniel,
>>
>> On 22/07/13 12:21, Sudeep KarkadaNagesha wrote:
>>> From: Sudeep KarkadaNagesha
>>>
>>> This patch series adds support to configure the rate and enable the event
>>> stream for archi
On Fri, Aug 02, 2013 at 11:25:39AM +0200, Ingo Molnar wrote:
> > Ingo,
> >
> > Do you have any concerns reg this series? please let me know if this
> > looks good now to you.
>
> I'm inclined to NAK it for excessive quotation - who knows how many people
> left the discussion in disgust? Was it
Am 31.07.2013 10:35, schrieb Javier Martinez Canillas:
The problem is that board files and drivers that has not not been completed
migrated to DT assumes (at least for OMAP) that *every* GPIO line is mapped as
an IRQ and they just do:
gpio_request(gpio,...);
gpio_direction_input()
request[_thr
1 - 100 of 802 matches
Mail list logo
