Hi,
On Fri, Sep 27, 2013 at 12:31:09PM +0200, Robert Baldyga wrote:
> This patch changes ep maxpacket value from 512 to 1024, becouse it's needed
shouldn't you use 3072 instead to cope with high bandwidth ISO
endpoints ?
> to handle interupt and isochronous endpoints in high-speed mode. This cha
This patch adds a very simple driver that enables GPIO lines as wakeup
sources. It only operates on information passed in via DT, and depends
on CONFIG_OF && CONFIG_PM_SLEEP. It can for example be used to connect
wake-on-LAN (WOL) signals or other electric wakeup networks.
The driver accepts a lis
On Tue, Oct 01, 2013 at 01:07:20PM +0200, Thierry Reding wrote:
> Today's linux-next merge of the driver-core tree got conflicts in
>
> include/linux/netdevice.h
>
> I fixed it up (see below). Please check if the resolution looks correct.
Looks correct to me, thanks.
greg k-h
--
To unsubs
On Tue, Oct 01, 2013 at 01:07:23PM +0200, Thierry Reding wrote:
> Today's linux-next merge of the sh tree got conflicts in
>
> arch/sh/kernel/cpu/sh2a/Makefile
> drivers/tty/serial/sh-sci.c
> include/linux/serial_sci.h
>
> I fixed them up (see below). Please check if the resolut
On Tue, Oct 01, 2013 at 05:16:54AM -0700, Paul E. McKenney wrote:
> On Tue, Oct 01, 2013 at 02:52:28PM +1000, Michael Neuling wrote:
> > >> Well we don't have to, I think Mikey wasn't totally clear about that
> > >> "making all registers volatile" business :-) This is just something we
> > >> need
On 30 Sep 2013, at 16:31, Konrad Rzeszutek Wilk wrote:
> On Fri, Sep 27, 2013 at 05:09:58PM +0100, Stefano Stabellini wrote:
>> xen_swiotlb_alloc_coherent needs to allocate a coherent buffer for cpu
>> and devices. On native x86 and ARMv8 is sufficient to call
>> __get_free_pages in order to get a
Hi Jiri,
Mika Westerberg mika.westerb...@linux.intel.com reported a bug introduced in
hid driver after
commit 212a871a393 (HID: hidraw: correctly deallocate memory on device
disconnect)
that hidraw doesn't close the underlying hid device when the device node is
closed last time.
I am proposi
On 10/1/13 1:16 AM, Ingo Molnar wrote:
Just a detail: it would be nice to make all the user facing messages in
tools/perf/util/header.c more specific and more structured. For example
prefixing it with 'perf header:' would be fine:
WARNING: perf/header: Data size is 0. Was the 'perf recor
David Rientjes wrote:
> On Sat, 28 Sep 2013, Tetsuo Handa wrote:
>
> > Some of enterprise users might prefer "kernel panic followed by kdump and
> > automatic reboot" to "a system is not responding for unpredictable period",
> > for
> > the panic helps getting information for analyzing what proce
Hi Roger,
It has been a while, but I would like to pickup this thread. We have a couple
of pandaboards used as test setup. These have an SDIO adapter hooked up to
expansion connector A using MMC2. I have attached the patch file (just ignore
platform_data stuff). Now on one board it works, but
This patch creates a thermal map sysfs node under
/sys/class/thermal/zoneX/. The thermal map
shows the binding relationship between a sensor
and a cooling device within a particular zone.
This contains entries named mapY_trip_type,
mapY_sensor_name, mapY_cdev_name, mapY_trip_mask,
mapY_weightX.
Si
This patch adds a trip point related sysfs nodes
for each sensor under a zone in /sys/class/thermal/zoneX/.
The nodes will be named, sensorX_trip_activeY,
sensorX_trip_passiveY, sensorX_trip_hot, sensorX_trip_critical
for active, passive, hot and critical trip points
respectively for sensorX.
Sign
This patch adds Documentation for the new APIs
introduced in this patch set. The documentation
also has a model sysfs structure for reference.
Signed-off-by: Durgadoss R
---
Documentation/thermal/sysfs-api2.txt | 248 ++
1 file changed, 248 insertions(+)
create
This patch creates sensor level APIs, in the
generic thermal framework.
A Thermal sensor is a piece of hardware that can report
temperature of the spot in which it is placed. A thermal
sensor driver reads the temperature from this sensor
and reports it out. This kind of driver can be in
any subsys
This patch adds Documentation for ABI's introduced
for thermal subsystem (under /sys/class/thermal/).
Signed-off-by: Durgadoss R
---
Documentation/ABI/testing/sysfs-class-thermal | 137 +
1 file changed, 137 insertions(+)
create mode 100644 Documentation/ABI/testing/sys
This patch creates new APIs to add/remove a
cdev to/from a zone. This patch does not change
the old cooling device implementation.
Signed-off-by: Durgadoss R
---
drivers/thermal/thermal_core.c | 136
include/linux/thermal.h|9 +++
2 files cha
This patch set is a v4 of the previous versions submitted here:
[v3]: https://lkml.org/lkml/2013/2/5/228
[v2]: http://lwn.net/Articles/531720/
[v1]: https://lkml.org/lkml/2012/12/18/108
[RFC]:https://patchwork.kernel.org/patch/1758921/
This patch set is based on Rui's -next tree, on top
of commi
This patch adds a new thermal_zone structure to
thermal.h. Also, adds zone level APIs to the thermal
framework.
A thermal zone is a hot spot on the platform, which
can have one or more sensors and cooling devices attached
to it. These sensors can be mapped to a set of cooling
devices, which when t
The thermal_release function is called whenever
any device belonging to 'thermal' class unregisters.
This function performs kfree(cdev) without any check.
In cases where there are more device registrations
other than just 'thermal_zone' and 'cooling_device'
this might accidently free memory allocat
This patch has a dummy driver that can be used for
testing purposes. This patch is not for merge.
Signed-off-by: Durgadoss R
---
drivers/thermal/Kconfig|5 +
drivers/thermal/Makefile |3 +
drivers/thermal/thermal_test.c | 322
3 fil
The ACPI specification requires the parent device to be powered on before
any of its children. It can be only powered off when all the children are
already off.
Currently whenever there is no I2C traffic going on, the I2C controller
driver can put the device into low power state transparently to i
On Fri, Sep 27, 2013 at 09:01:58PM +0200, Zdenek Kabelac wrote:
Dne 27.9.2013 18:01, Veaceslav Falico napsal(a):
On Fri, Sep 27, 2013 at 09:58:28AM -0600, Bjorn Helgaas wrote:
[+cc Veaceslav, linux-pci]
On Fri, Sep 27, 2013 at 7:34 AM, Zdenek Kabelac wrote:
Hi
With recent build of 3.12-rc2
Commit-ID: a6d30e0fffb32ab9e48fa7fc8f463805d5b0bddb
Gitweb: http://git.kernel.org/tip/a6d30e0fffb32ab9e48fa7fc8f463805d5b0bddb
Author: Bartlomiej Zolnierkiewicz
AuthorDate: Mon, 30 Sep 2013 15:21:15 +0200
Committer: Ingo Molnar
CommitDate: Tue, 1 Oct 2013 13:21:27 +0200
x86/geode: Fix
* Ingo Molnar wrote:
> And the actual feature check is roughly 0.330 msecs of that:
>
> comet:~/tip/tools/perf/config/feature-checks> time ( make -j >/dev/null; \
> for N in stackprotector-all volatile-register-var fortify-source libelf \
> libelf-mmap glibc dwarf libelf-getphdrnum libunwind
Em Tue, Oct 01, 2013 at 02:04:55PM +0200, Ingo Molnar escreveu:
> So there's more speedups possible I think, for example we could construct
> an 'optimistic' testcase that is generated live and includes a
> concatenation of all the testcases.
>
> If the build of that file succeeds then we have a
>From 6ff5102b3cd8047bb4bfb4d0165f289249e23bbe Mon Sep 17 00:00:00 2001
From: rchinthekindi
Date: Tue, 1 Oct 2013 17:49:58 +0530
Subject: [PATCH 2/2] skd: Restricted pr_debug() lines to 80 characters
Restricted pr_debug() lines to 80 characters
Signed-off-by: Ramprasad C
---
drivers/block/sk
On Mon, Sep 30, 2013 at 01:29:09PM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> The first loop in ext4_mb_init_cache can bail out when the end of
> all groups is reached. Unfortunately the later loops did not
> have that check and could access uninitialized buffer pointers
> in bh[]. Add the e
On Mon, Sep 30, 2013 at 08:51:43PM +, Luck, Tony wrote:
> > In this case fast_mix would use two uninitialized ints from the stack
> > and mix it into the pool.
>
> Is the concern here is that an attacker might know (or be able to control)
> what is on
> the stack - and so get knowledge of wha
On Tue, 2013-10-01 at 00:20 -0400, Dave Jones wrote:
> It seems like trace-cmd needs to be run as root. all hell will break loose if
> trinity gets root privs.
Then run this:
trace-cmd record -e syscalls -B trinity su davej -c 'trinity '
-- Steve
--
To unsubscribe from this list: send the li
Hi Yoshii-san,
Thank you for the patch.
(CC'ing LAMK as a generic CCF question follows)
On Tuesday 01 October 2013 18:15:26 Magnus Damm wrote:
> On Tue, Sep 24, 2013 at 1:15 PM, wrote:
> > Common clock framework version of emev2 clock support.
> > smu_clkdiv and smu_gclk are handled.
> > So fa
Andi Kleen writes:
> From: Andi Kleen
>
> The error code was ignored, which I assume is a mistake.
Yeah, introduced in d50235b7bc3ee0a0427984d763ea7534149531b4, so I cc'd
Jianpeng Ma, though it looks pretty obvious.
Reviewed-by: Jeff Moyer
> Cc: ax...@kernel.dk
> Signed-off-by: Andi Kleen
>
On Tue, Oct 01, 2013 at 02:52:28PM +1000, Michael Neuling wrote:
> >> Well we don't have to, I think Mikey wasn't totally clear about that
> >> "making all registers volatile" business :-) This is just something we
> >> need to handle in assembly if we are going to reclaim the suspended
> >> transa
On 10/01/2013 01:53 PM, Arend van Spriel wrote:
> On 10/01/2013 11:53 AM, Roger Quadros wrote:
>> On 10/01/2013 12:49 PM, Roger Quadros wrote:
>>> Hi Arend,
>>>
>>> On 10/01/2013 11:05 AM, Arend van Spriel wrote:
On 07/19/2013 12:57 PM, Arend van Spriel wrote:
> On 07/19/2013 12:49 PM, Rog
Hi,
On Mon, 2013-09-23 at 14:32 -0500, Felipe Balbi wrote:
> Hi,
>
> On Wed, Aug 21, 2013 at 04:29:44PM +0300, Ivan T. Ivanov wrote:
> > From: "Ivan T. Ivanov"
> >
> > MSM USB3.0 core wrapper consist of USB3.0 IP from Synopsys
> > (SNPS) and HS, SS PHY's control and configuration registers.
>
Hi,
On Mon, 2013-09-23 at 16:03 -0600, Stephen Warren wrote:
> On 09/23/2013 01:32 PM, Felipe Balbi wrote:
> > Hi,
> >
> > On Wed, Aug 21, 2013 at 04:29:44PM +0300, Ivan T. Ivanov wrote:
> >> From: "Ivan T. Ivanov"
> >>
> >> MSM USB3.0 core wrapper consist of USB3.0 IP from Synopsys (SNPS)
>
On Mon, Sep 30, 2013 at 03:25:47PM +0200, Bartlomiej Zolnierkiewicz wrote:
> This is not a SCSI host driver so remove SCSI subsystem specific
> includes.
The sad thing is that it is a driver for a device speaking SCSI, but for
some reason that was never discussed it is written to the block layer.
* Ingo Molnar wrote:
> Overhead is down from 0.600 secs to 0.540 secs. The only remaining thing
> is the libperl bug, I'll have a look at that next.
So, libperl detection works fine here, once I've installed the prereq
package on Fedora, "perl-ExtUtils-Embed":
comet:~/tip/tools/perf> make
Hello,
On Tue, Oct 01, 2013 at 05:35:48PM +1000, Michael Ellerman wrote:
> > > Roughly third of the drivers just do not care and bail out once
> > > pci_enable_msix() has not succeeded. Not sure how many of these are
> > > mandated by the hardware.
> >
> > Yeah, I mean, this type of interface is
Hi,
On Mon, 2013-09-23 at 14:31 -0500, Felipe Balbi wrote:
> Hi,
>
> On Tue, Aug 20, 2013 at 12:56:03PM +0300, Ivan T. Ivanov wrote:
> > From: "Ivan T. Ivanov"
> >
> > MSM USB3.0 core wrapper consist of USB3.0 IP from Synopsys
> > (SNPS) and HS, SS PHY's control and configuration registers.
Hi, I am sorry for delay answer.
On Thu, 2013-09-26 at 10:46 +0100, Mark Rutland wrote:
> On Mon, Sep 23, 2013 at 08:31:48PM +0100, Felipe Balbi wrote:
> > Hi,
> >
> > On Tue, Aug 20, 2013 at 12:56:03PM +0300, Ivan T. Ivanov wrote:
> > > From: "Ivan T. Ivanov"
> > >
> > > MSM USB3.0 core wrap
This leak was added by v3.11-8748-g1d3d443 "vmscan: per-node deferred work"
unreferenced object 0x88006ada3bd0 (size 8):
comm "criu", pid 14781, jiffies 4295238251 (age 105.641s)
hex dump (first 8 bytes):
00 00 00 00 00 00 00 00
backtrace:
[] kme
On Tue, 24 Sep 2013, Laxman Dewangan wrote:
> The AMS AS3722 is a compact system PMU suitable for mobile phones,
s/AMS/ams
> tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
> controller, 11 LDOs, RTC, automatic battery, temperature and
> over-current monitoring, 8 GPIOs, ADC
Hi Yoshii-san and Simon,
On Tuesday 24 September 2013 13:52:15 Simon Horman wrote:
> [ Cc Laurent ]
>
> On Tue, Sep 24, 2013 at 01:13:31PM +0900, takas...@ops.dti.ne.jp wrote:
> > Device tree clock binding document for EMMA Mobile EV2 SMU.
> > Following nodes are defined to describe clock tree.
>
* Ingo Molnar wrote:
> > > > Checking why that strlcpy failed...
> > >
> > > I don't think glibc does strlcpy. It's not a standard C function,
> > > and
> >
> > My concern was more about the thinking: ``Is this red "OFF" thing a
> > problem? I feel so much more confortable when all entries
Generated by: coccinelle/misc/memcpy-assign.cocci
CC: Alexander Shiyan
Signed-off-by: Fengguang Wu
---
drivers/tty/serial/sccnxp.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next.orig/drivers/tty/serial/sccnxp.c 2013-10-01 19:27:55.057537955
+0800
+++ linux-next/drive
Hi,
On Tue, 2013-10-01 at 12:53 +0200, Arend van Spriel wrote:
> On 10/01/2013 11:53 AM, Roger Quadros wrote:
> > On 10/01/2013 12:49 PM, Roger Quadros wrote:
> >> Hi Arend,
> >>
> >> On 10/01/2013 11:05 AM, Arend van Spriel wrote:
> >>> On 07/19/2013 12:57 PM, Arend van Spriel wrote:
> On 07
On Tue, Oct 01, 2013 at 01:07:22PM +0200, Thierry Reding wrote:
> Today's linux-next merge of the random tree got a conflict in:
>
> init/main.c
>
> I fixed it up (see below). Please check if the resolution looks correct.
Looks good, thanks.
On Mon, Sep 30, 2013 at 6:54 PM, Peter Zijlstra wrote:
>
> On Mon, Sep 30, 2013 at 06:48:55PM +0200, Stephane Eranian wrote:
> > On Mon, Sep 30, 2013 at 6:15 PM, Peter Zijlstra
> > wrote:
> > > On Mon, Sep 30, 2013 at 05:44:41PM +0200, Stephane Eranian wrote:
> > >> Hi,
> > >>
> > >> I was alert
Il 01/10/2013 11:38, Benjamin Herrenschmidt ha scritto:
> So for the sake of that dogma you are going to make us do something that
> is about 100 times slower ? (and possibly involves more lines of code)
If it's 100 times slower there is something else that's wrong. It's
most likely not 100 times
On Mon, Sep 30, 2013 at 09:09:47AM -0500, Suravee Suthikulpanit wrote:
> On 4/29/2013 7:30 AM, Oleg Nesterov wrote:
> >On 04/29, Ingo Molnar wrote:
> >>* Oleg Nesterov wrote:
> >>>Obviously I can't ack the changes in this area, but to me the whole
> >>>series looks fine.
> >>Thanks Oleg - can I ad
On Tue, Oct 1, 2013 at 9:34 AM, Javier Martinez Canillas
wrote:
> Linus,
>
> Since this patch-set doesn't cause any regression and fix a long standing
> issue
> on OMAP, do you think that it would be possible to include on the -rc series
> as
> a bugfix or do you prefer to wait until 3.13?
I'v
Hi,
On Monday 30 September 2013 08:39 PM, Rob Herring wrote:
> On 09/30/2013 08:59 AM, Sricharan R wrote:
>> Some socs have a large number of interrupts requests to service
>> the needs of its many peripherals and subsystems. All of the interrupt
>> requests lines from the subsystems are not neede
Today's linux-next merge of the driver-core tree got conflicts in
include/linux/netdevice.h
I fixed it up (see below). Please check if the resolution looks correct.
Thanks,
Thierry
---
diff --cc drivers/mtd/nand/atmel_nand.c
index ef9c9f5,bd1ce7d..2dbd913
--- a/drivers/mtd/nand/atmel_nan
Today's linux-next merge of the random tree got a conflict in:
init/main.c
I fixed it up (see below). Please check if the resolution looks correct.
Thanks,
Thierry
---
diff --cc init/main.c
index 7cc4b78,586cd33..379090f
--- a/init/main.c
+++ b/init/main.c
@@@ -75,7 -75,7 +75,8 @@@
#in
Today's linux-next merge of the vfs tree got conflicts in:
fs/nfs/direct.c
fs/nfs/file.c
I fixed them up (see below). Please check if the resolution looks correct.
Thanks,
Thierry
---
diff --cc fs/nfs/direct.c
index 239c2fe,d71d66c..e83817c
--- a/fs/nfs/direct.c
+++ b/fs/nfs/dire
Today's linux-next merge of the block tree got conflicts in:
drivers/md/bcache/bcache.h
drivers/md/bcache/bset.c
drivers/md/bcache/journal.c
drivers/md/bcache/request.c
drivers/md/bcache/writeback.c
I fixed it up (see below). Please check if the resolution
Today's linux-next merge of the cgroup tree got a conflict in:
mm/memcontrol.c
I fixed it up (see below). Please check if the resolution looks correct.
Thanks,
Thierry
---
diff --cc mm/memcontrol.c
index 1c52ddb,65a46ef..84dcc5c
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@@ -6203,9 -59
Today's linux-next merge of the sh tree got conflicts in
arch/sh/kernel/cpu/sh2a/Makefile
drivers/tty/serial/sh-sci.c
include/linux/serial_sci.h
I fixed them up (see below). Please check if the resolution looks correct.
Thanks,
Thierry
---
diff --cc arch/sh/kernel/cpu/sh2
Today's linux-next merge of the net-next tree got conflicts in
arch/h8300/include/uapi/asm/socket.h
drivers/net/usb/qmi_wwan.c
drivers/net/wireless/brcm80211/brcmfmac/dhd_bus.h
include/net/secure_seq.h
I removed the h8300 file and fixed up the other three (see belo
On Mon, Sep 30, 2013 at 05:02:47PM +0200, Frederic Weisbecker wrote:
> Ingo, Thomas,
>
> Please pull the irq/core-v5 branch that can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> irq/core-v5
>
> HEAD: f6f626fa877c96974fadc595ddd72543d8c6106b
Hi all,
I've uploaded today's linux-next tree to the master branch of the
repository below:
git://gitorious.org/thierryreding/linux-next.git
A next-20131001 tag is also provided for convenience.
The situation is pretty much the same as yesterday. Some conflicts went
away
On Tue, Oct 01, 2013 at 08:55:16AM +0200, Ingo Molnar wrote:
>
> * Frederic Weisbecker wrote:
>
> > On Mon, Sep 30, 2013 at 09:07:19AM -0700, Linus Torvalds wrote:
> > > On Mon, Sep 30, 2013 at 7:55 AM, Frederic Weisbecker
> > > wrote:
> > > > ...
> > > > the chances for a stack overrun as
> >Warning message triggered with 3.12.0-0.rc3.git0.1.fc21.x86_64.
> >
> >[ 10.886016] applesmc: key count changed from 261 to 1174405121
> >
>
> Explains the crash, but the new key count is very wrong. 1174405121 =
> 0x4601.
> Which I guess explains the subsequent memory allocation error i
On 10/01/2013 11:53 AM, Roger Quadros wrote:
On 10/01/2013 12:49 PM, Roger Quadros wrote:
Hi Arend,
On 10/01/2013 11:05 AM, Arend van Spriel wrote:
On 07/19/2013 12:57 PM, Arend van Spriel wrote:
On 07/19/2013 12:49 PM, Roger Quadros wrote:
On 07/19/2013 01:36 PM, Arend van Spriel wrote:
On
This patch supplies I2C configuration to STiH415 SoC.
Cc: Srinivas Kandagatla
Signed-off-by: Maxime Coquelin
---
arch/arm/boot/dts/stih415-pinctrl.dtsi | 36 ++
arch/arm/boot/dts/stih415.dtsi | 53
2 files changed, 89 insertions(+
This patch supplies I2C configuration to B2000 and B2020
based on either STiH415 or STiH416 SoCs.
Cc: Srinivas Kandagatla
Signed-off-by: Maxime Coquelin
---
arch/arm/boot/dts/stih41x-b2000.dtsi |9 +
arch/arm/boot/dts/stih41x-b2020.dtsi | 22 ++
2 files changed
This patch adds support to SSC (Synchronous Serial Controller)
I2C driver. This IP also supports SPI protocol, but this is not
the aim of this driver.
This IP is embedded in all ST SoCs for Set-top box platorms, and
supports I2C Standard and Fast modes.
Signed-off-by: Maxime Coquelin
Cc: Sriniva
This patch supplies I2C configuration to STiH416 SoC.
Cc: Srinivas Kandagatla
Signed-off-by: Maxime Coquelin
---
arch/arm/boot/dts/stih416-pinctrl.dtsi | 35 +
arch/arm/boot/dts/stih416.dtsi | 53
2 files changed, 88 insertions(+)
The goal of this series is to add I2C support to ST SoCs.
The DT definition is added for STiH415 and STiH416 SoCs on
B2000 and B2020 boards.
The series has been tested working on STiH416-B2020 board.
It applies on top of v3.12-rc3.
Changes since v2:
- Create generic DT property for Anti-glitch
Hi,
On Tuesday, October 01, 2013 08:59:50 AM Ingo Molnar wrote:
>
> * Bartlomiej Zolnierkiewicz wrote:
>
> > __initdata tag should be placed between the variable name and equal
> > sign for the variable to be placed in the intended .init.data section.
> >
> > Signed-off-by: Bartlomiej Zolnier
On Tue, Oct 01, 2013 at 05:51:33PM +1000, Michael Ellerman wrote:
> The disadvantage is that any restriction imposed on us above the quota
> can only be reported as an error from pci_enable_msix().
>
> The quota code, called from pci_get_msix_limit(), can only do so much to
> interogate firmware a
Hi Paul/SH folks.
Would appreciate your ACK/NAK on this.
Thx,
-Vineet
On 09/17/2013 11:47 AM, Vineet Gupta wrote:
> Only a couple of arches (sh/x86) use fpu_counter in task_struct so it
> can be moved out into ARCH specific thread_struct, reducing the size of
> task_struct for other arches.
>
>
The goal of this series is to add I2C support to ST SoCs.
The DT definition is added for STiH415 and STiH416 SoCs on
B2000 and B2020 boards.
The series has been tested working on STiH416-B2020 board.
It applies on top of v3.12-rc3.
Changes since v2:
- Create generic DT property for Anti-glitch
On Wed, 2013-09-18 at 11:45 +0800, Xishi Qiu wrote:
>
> to ensure the driver cannot be built-in when rfkill is modular. The !RFKILL
> -case allows the driver to be built when rfkill is not configured, which which
> +case allows the driver to be built when rfkill is not configured, which
> case
Hello guys, this is the part2 of our memory hotplug work. This part
is based on the part1:
"x86, memblock: Allocate memory near kernel image before SRAT parsed"
You could refer part1 from: https://lkml.org/lkml/2013/9/24/421
Any comments are welcome! Thanks!
[Problem]
The current Linux cann
On 10/01/2013 11:23 AM, Paul Mackerras wrote:
On Tue, Oct 01, 2013 at 11:39:08AM +0300, Gleb Natapov wrote:
On Tue, Oct 01, 2013 at 06:34:26PM +1000, Michael Ellerman wrote:
On Thu, Sep 26, 2013 at 11:06:59AM +0200, Paolo Bonzini wrote:
Il 26/09/2013 08:31, Michael Ellerman ha scritto:
Some p
On Tue, Oct 01, 2013 at 07:23:20PM +1000, Paul Mackerras wrote:
> On Tue, Oct 01, 2013 at 11:39:08AM +0300, Gleb Natapov wrote:
> > On Tue, Oct 01, 2013 at 06:34:26PM +1000, Michael Ellerman wrote:
> > > On Thu, Sep 26, 2013 at 11:06:59AM +0200, Paolo Bonzini wrote:
> > > > Il 26/09/2013 08:31, Mic
Il 01/10/2013 10:34, Michael Ellerman ha scritto:
>> If you really want to have the hypercall, implementing it in QEMU means
>> that you can support it on all systems, in fact even when running
>> without KVM.
>
> Sure, I can add a fallback to /dev/hwrng for full emulation.
>
>> The QEMU comman
From: Tang Chen
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 movabl
From: Tang Chen
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
From: Tang Chen
At very early time, the kernel have to use some memory such as
loading the kernel image. We cannot prevent this anyway. So any
node the kernel resides in should be un-hotpluggable.
Signed-off-by: Zhang Yanfei
Reviewed-by: Zhang Yanfei
---
arch/x86/mm/numa.c | 44
From: Tang Chen
When parsing SRAT, we know that which memory area is hotpluggable.
So we invoke function memblock_mark_hotplug() introduced by previous
patch to mark hotpluggable memory in memblock.
Besides, move setting back to top-down allocation just right after
we mark hotpluggable memory in
From: Tang Chen
Signed-off-by: Tang Chen
Reviewed-by: Zhang Yanfei
---
arch/metag/mm/init.c |3 ++-
arch/metag/mm/numa.c |3 ++-
arch/microblaze/mm/init.c |3 ++-
arch/powerpc/mm/mem.c |2 +-
arch/powerpc/mm/numa.c|8 +---
arch/sh/kernel/setup.c|
On 10/01/2013 12:49 PM, Roger Quadros wrote:
> Hi Arend,
>
> On 10/01/2013 11:05 AM, Arend van Spriel wrote:
>> On 07/19/2013 12:57 PM, Arend van Spriel wrote:
>>> On 07/19/2013 12:49 PM, Roger Quadros wrote:
On 07/19/2013 01:36 PM, Arend van Spriel wrote:
> On 07/18/2013 10:59 AM, Tony L
From: Tang Chen
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 f
Hi Arend,
On 10/01/2013 11:05 AM, Arend van Spriel wrote:
> On 07/19/2013 12:57 PM, Arend van Spriel wrote:
>> On 07/19/2013 12:49 PM, Roger Quadros wrote:
>>> On 07/19/2013 01:36 PM, Arend van Spriel wrote:
On 07/18/2013 10:59 AM, Tony Lindgren wrote:
> Then for the SDIO with device tree
From: Tang Chen
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
On Mon, Sep 30, 2013 at 05:43:48PM +0300, Mika Westerberg wrote:
> +static void acpi_i2c_device_pm_get(struct i2c_client *client)
> +{
> + struct i2c_adapter *adap = client->adapter;
> +
> + /* Make sure the adapter is active */
> + if (ACPI_HANDLE(adap->dev.parent))
> + pm_
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, invoke memblock_alloc_nid(...MAX_NUMNODES) again to retry when
the first allocation fails. Otherwise, the sys
On Tue, 2013-10-01 at 11:39 +0300, Gleb Natapov wrote:
> On Tue, Oct 01, 2013 at 06:34:26PM +1000, Michael Ellerman wrote:
> > On Thu, Sep 26, 2013 at 11:06:59AM +0200, Paolo Bonzini wrote:
> > > Il 26/09/2013 08:31, Michael Ellerman ha scritto:
> > > > Some powernv systems include a hwrng. Guests
Fixed a brace coding style issue. (Brace not on the good line)
Signed-off-by: Mathieu Rhéaume
---
drivers/acpi/processor_driver.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/acpi/processor_driver.c b/drivers/acpi/processor_driver.c
index e534ba6..40fc773 100644
On Tue, Sep 24, 2013 at 1:12 PM, wrote:
> Make sh clock framework core depend on HAVE_MACH_CLKDEV, and
> set it
> - y on sh for backward compatibility
> - !CONFIG_COMMON_CLK on sh-mobile
> This is a preparation for migration to common clock framework
> from sh clock framework on sh-mobile.
>
> Si
On Tue, Sep 24, 2013 at 1:17 PM, wrote:
> Use common clock framework version of clock
> drivers/clk/shmobile/clk-emev2.c
> instead of sh-clkfwk version
> arch/arm/mach-shmobile/clock-emev2.c
>
> kzm9d(without -reference) still uses sh-clkfwk version.
>
> Because two of that framework can not li
On Tue, Oct 01, 2013 at 09:41:04AM +0530, Manish Badarkhe wrote:
> This patch changes the driver to avoid the usage of IS_ERR_OR_NULL()
> macro.
Why?
signature.asc
Description: Digital signature
On Tue, Oct 01, 2013 at 11:39:08AM +0300, Gleb Natapov wrote:
> On Tue, Oct 01, 2013 at 06:34:26PM +1000, Michael Ellerman wrote:
> > On Thu, Sep 26, 2013 at 11:06:59AM +0200, Paolo Bonzini wrote:
> > > Il 26/09/2013 08:31, Michael Ellerman ha scritto:
> > > > Some powernv systems include a hwrng.
On Tue, Sep 24, 2013 at 1:15 PM, wrote:
> Common clock framework version of emev2 clock support.
> smu_clkdiv and smu_gclk are handled.
> So far, reparent is not implemented, and is fixed to index #0.
> SMU and small numbers of clocks are described in emev2.dtsi.
>
> That function and numbers of
Commit-ID: a17bce4d1dce8f3cf714bc2e5d8e4bac009dc077
Gitweb: http://git.kernel.org/tip/a17bce4d1dce8f3cf714bc2e5d8e4bac009dc077
Author: Borislav Petkov
AuthorDate: Mon, 30 Sep 2013 11:56:24 +0200
Committer: Ingo Molnar
CommitDate: Tue, 1 Oct 2013 10:52:30 +0200
x86/boot: Further compres
On Tue, Sep 24, 2013 at 1:10 PM, wrote:
> From: Shinya Kuribayashi
>
> Add calls to clk_prepare and unprepare so that EMMA Mobile EV2 can
> migrate to the common clock framework.
>
> Signed-off-by: Shinya Kuribayashi
> [takashi.yoshii...@renesas.com: edited for conflicts]
> Signed-off-by: Takas
On Tue, Sep 24, 2013 at 1:09 PM, wrote:
> From: Shinya Kuribayashi
>
> Add calls to clk_prepare and unprepare so that EMMA Mobile EV2 can
> migrate to the common clock framework.
>
> Signed-off-by: Shinya Kuribayashi
> ---
> drivers/clocksource/em_sti.c | 4 ++--
> 1 file changed, 2 insertions
* Borislav Petkov wrote:
> On Mon, Sep 30, 2013 at 08:28:48AM +0200, Ingo Molnar wrote:
> > * H. Peter Anvin wrote:
> >
> > > If the goal is to feed this to the field width in printf, which I would
> > > think would be the dominant use, then you do have to account for the
> > > minus sign.
>
401 - 500 of 538 matches
Mail list logo
