From: kyak
Date: Tue, 24 Jul 2012 09:39:40 +0400 (MSK)
> This patch was created against linux-3.5, but it applies perfectly
> against net-next tree, i just checked..
>
> I'm sorry for not being able to submit the correct patch from the
> first attempt (and not even from the third attempt). Could
Hi Yaniv,
On Tue, Jul 24 2012, Yaniv Gardi wrote:
> Are there any additional open issues to discuss regarding the sanitize
> capability ?
> If not, we would like to see this patch pushed into mmc-next.
I think you've responded to all of the open issues, thanks -- I'm adding
everyone who made a re
Implement support for pinctrl on lantiq/falcon socs. The FALCON has 5 banks
of up to 32 pins.
Signed-off-by: John Crispin
Signed-off-by: Thomas Langer
Cc: Linus Walleij
Cc: devicetree-disc...@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org
---
.../include/asm/mach-lantiq/falcon/lantiq_soc.h
The driver was using a 16 bit field for storing the shadow value of the shift
register cascade. This resulted in only the first 2 shift registeres receiving
the correct data. The third shift register would always receive 0x00.
Fix this by using a 32bit field for the shadow value.
Signed-off-by: J
Signed-off-by: John Crispin
Signed-off-by: Thomas Langer
Cc: Linus Walleij
Cc: devicetree-disc...@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org
---
.../bindings/pinctrl/lantiq,falcon-pinumx.txt | 83
1 files changed, 83 insertions(+), 0 deletions(-)
create mode
Add driver for GPIO blocks found on Lantiq FALCON SoC. The SoC has 5 banks of
up to 32 pads. The GPIO blocks have a per pin IRQs.
Signed-off-by: John Crispin
Signed-off-by: Thomas Langer
Cc: linux-kernel@vger.kernel.org
---
arch/mips/include/asm/mach-lantiq/gpio.h |4 +
drivers/gpio/Kconfig
Signed-off-by: John Crispin
Cc: Linus Walleij
Cc: devicetree-disc...@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org
---
.../bindings/pinctrl/lantiq,xway-pinumx.txt| 97
1 files changed, 97 insertions(+), 0 deletions(-)
create mode 100644
Documentation/devicetr
Implement support for pinctrl on lantiq/xway socs. The IO core found on these
socs has the registers for pinctrl, pinconf and gpio mixed up in the same
register range. As the gpio_chip handling is only a few lines, the driver also
implements the gpio functionality. This obseletes the old gpio drive
On Mon, Jul 23, 2012 at 10:15:07PM +0200, Lars-Peter Clausen wrote:
> On 07/23/2012 10:30 AM, Thierry Reding wrote:
> > On Wed, Jul 18, 2012 at 06:24:13PM +0530, Philip, Avinash wrote:
> >>[...]
> >> diff --git a/include/linux/pwm.h b/include/linux/pwm.h
> >> index 21d076c..2e4e960 100644
> >> ---
On Tue, Jul 24, 2012 at 09:21:34AM +0800, wwang wrote:
> Hi Borislav:
>
> Realtek card reader supports not only SDMMC card, but also Memory
> stick. This part is the common code, so it is located in
> drivers/misc. There is also SDMMC-relevant code under CONFIG_MMC.
> And in the future, Memstick-r
2012/7/18 Colin Cross :
> Many clocks that are used to provide sched_clock will reset during
> suspend. If read_sched_clock returns 0 after suspend, sched_clock will
> appear to jump forward. This patch resets cd.epoch_cyc to the current
> value of read_sched_clock during resume, which causes sch
Hi Chris,
Are there any additional open issues to discuss regarding the sanitize
capability ?
If not, we would like to see this patch pushed into mmc-next.
Thanks,
Yaniv
= > -Original Message-
= > From: linux-mmc-ow...@vger.kernel.org [mailto:linux-mmc-
= > ow...@vger.kernel.org] On Beha
On Mon, Jul 23, 2012 at 04:06:08PM -0700, Ben Chan wrote:
> This patch fixes commit 8df858ea76b76dde9a39d4edd9aaded983582cfe,
Please put the human readable patch title as well as just the hash.
Hashes sometimes change when they get merged into Linus's tree as
well.
> which
> mishandles the refere
It is not necessary to call max8997_update_reg() twice just for updating
MAX8997_REG_LEN_CNTL register. With proper val and mask arguments to
max8997_update_reg() call, this can be done in one max8997_update_reg() call.
And then we can remove max8997_led_clear_mode() function.
Signed-off-by: Axel
On Tue, Jul 24, 2012 at 8:00 AM, Yan, Zheng wrote:
> [...snip...]
>>> +
>>> +static int __init intel_uncore_init(void)
>>> +{
>>> + int ret;
>>> +
>>> + if (boot_cpu_data.x86_vendor != X86_VENDOR_INTEL)
>>> + return -ENODEV;
>>> +
>>> + ret = uncore_cpu_init();
>>>
On Tue, Jul 24, 2012 at 01:22:49, Thierry Reding wrote:
> On Mon, Jul 23, 2012 at 03:05:26PM +, Philip, Avinash wrote:
> > On Mon, Jul 23, 2012 at 18:38:25, Thierry Reding wrote:
> > > On Mon, Jul 23, 2012 at 12:51:11PM +, Philip, Avinash wrote:
> > > > On Mon, Jul 23, 2012 at 14:00:32, Thi
[...snip...]
>> +
>> +static int __init intel_uncore_init(void)
>> +{
>> + int ret;
>> +
>> + if (boot_cpu_data.x86_vendor != X86_VENDOR_INTEL)
>> + return -ENODEV;
>> +
>> + ret = uncore_cpu_init();
>> + if (ret)
>> + goto fail;
>> +
>> + u
On Mon, 2012-07-23 at 14:38 +0100, Mel Gorman wrote:
> Changelog since V1
> o Expand some of the notes (jrnieder)
> o Correct upstream commit SHA1 (hugh)
>
> This series is related to the new addition to stable_kernel_rules.txt
>
Hi linus,
This is the new pull request about blackfin changes for 3.6-rc1.
I've rebased my tree to 3.5.
The big changes are adding PM and HDMI support for bf60x, other patches are
various
bug fix and code cleanup.
Thanks,
-Bob
The following changes since commit 28a33cbc24e4256c143dce96c7d93bf4
Hi linus,
On Tue, Jul 24, 2012 at 12:54 PM, Linus Torvalds
wrote:
> On Mon, Jul 23, 2012 at 8:54 PM, Bob Liu wrote:
>>
>> Please pull blackfin changes for 3.6-rc1.
>
> No.
>
> These were clearly rebased today. And on top of random state in the
> merge window.
>
Sorry for that, i've rebased my t
This patch was created against linux-3.5, but it applies perfectly
against net-next tree, i just checked..
I'm sorry for not being able to submit the correct patch from the first
attempt (and not even from the third attempt). Could you be more specific
about "doesn't apply cleanly at all"? By
Hi all,
Please do not add anything to linux-next included branches/series that is
destined for v3.7 until after v3.6-rc1 is released.
Reminder: do not rebase your branches before asking Linus to pull them ...
Changes since 20120723:
The nfs tree lost its conflict.
The device-mapper tree lost
The most important feature of this patch set is the new async
infrastructure that makes sure async_synchronize_full() synchronizes all
domains and allows us to remove all the hacks (like having
scsi_complete_async_scans() in the device base code) and means that the
async infrastructure will "just w
Hi Linus,
Here is the slave-dmaengine update for 3.6
This time we have new dmaengine driver from tegra folks. Also we have
Guennadi's cleanup of sh drivers which incudes a library for sh drivers.
And the usual odd fixes in bunch of drivers and some nice cleanup of
dw_dmac from Andy.
The follow
On Mon, 23 Jul 2012 22:32:39 +0200, Sasha Levin wrote:
> As it was discussed recently, there's currently no way for the guest to notify
> the host about panics. Further more, there's no reasonable way to notify the
> host of other critical events such as an OOM kill.
I clearly missed the discussi
On Thu, 28 Jun 2012 01:01:46 +0200, Peter Zijlstra
wrote:
> +#ifdef CONFIG_STRICT_TLB_FILL
> +/*
> + * Some archictures (sparc64, ppc) cannot refill TLBs after the they've
> removed
> + * the PTE entries from their hash-table. Their hardware never looks at the
> + * linux page-table structure
On Tuesday 24 July 2012 10:38 AM, Vinod Koul wrote:
On Fri, 2012-07-20 at 13:31 +0530, Laxman Dewangan wrote:
Enable the DMA clock when allocating channel and
disable clock when freeing channels.
Signed-off-by: Laxman Dewangan
---
+ clk_disable_unprepare(tdma->dma_clk);
What if another c
A release candidate Git v1.7.12-rc0 is now available for testing
at the usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
09016e819a69b49090756e9bc5c97a4df25c2f78 git-1.7.12.rc0.tar.gz
e85ad0780ff81eacdb05a10762
On Fri, 2012-07-20 at 13:31 +0530, Laxman Dewangan wrote:
> Enable the DMA clock when allocating channel and
> disable clock when freeing channels.
>
> Signed-off-by: Laxman Dewangan
> ---
> Changes from V1 to V2:
> - Enable/disable clock when allocating/freeing channels.
> - rewrite the descript
The patch is bugfix. So I want you to review it and merge into linux-3.6.
2012/07/17 11:17, Yasuaki Ishimatsu wrote:
> There are two ways to create /sys/firmware/memmap/X sysfs:
>
>- firmware_map_add_early
> When the system starts, it is calledd from e820_reserve_resources()
>- firmw
On Mon, Jul 23, 2012 at 8:54 PM, Bob Liu wrote:
>
> Please pull blackfin changes for 3.6-rc1.
No.
These were clearly rebased today. And on top of random state in the
merge window.
Why would you do that? It's so horribly wrong that there's no way in
hell I'm pulling this mess.
Lin
On Tuesday 24 July 2012 02:21 AM, Stephen Warren wrote:
On 07/13/2012 07:50 AM, Laxman Dewangan wrote:
sm[0-2], ldo[0-9] and ldo_rtc
+- sm0-supply: The input supply for the SM0.
+- sm1-supply: The input supply for the SM1.
+- sm2-supply: The input supply for the SM2.
+- vinldo01-supply: The
On Mon, Jul 23, 2012 at 9:21 PM, Benjamin Herrenschmidt
wrote:
> On Mon, 2012-07-23 at 16:32 -0600, Grant Likely wrote:
>> > As-is I'm backing off from the linear/legacy/tree merge patch as just
>> > too risky. I've already pulled that stuff out of linux-next.
>>
>> Can I pull you pseries fix into
Hi Thomas
Could you please teach me current status of these patches ?
Kuninori Morimoto (2):
genirq: export irq_set_chip_and_handler_name()
genirq: export dummy_irq_chip
At Mon, 9 Jul 2012 22:34:23 +0200,
Linus Walleij wrote:
>
> On Mon, Jul 9, 2012 at 4:04 AM, Kuninori Morimoto
>
Hi linus,
Please pull blackfin changes for 3.6-rc1.
The big changes are adding PM and HDMI support for bf60x, other patches are
various
bug fix and code cleanup.
Thanks,
-Bob
The following changes since commit 97e7292ab5ccd30a13c3612835535fc3f3e59715:
Merge tag 'clk' of git://git.kernel.org/
From: "Justin P. Mattock"
Signed-off-by: Justin P. Mattock
---
The below patch fixes typos found while reading through staging: tidsbridge:
.../staging/tidspbridge/Documentation/error-codes |2 +-
drivers/staging/tidspbridge/core/_tiomap.h |2 +-
drivers/staging/tidspbridge/
On 07/23/2012 01:44 PM, Ramirez Luna, Omar wrote:
Hi Justin,
On Mon, Jul 23, 2012 at 8:49 AM, Justin P. Mattock
wrote:
diff --git a/drivers/staging/tidspbridge/core/tiomap3430.c
b/drivers/staging/tidspbridge/core/tiomap3430.c
index f9609ce..2c82d5a 100644
--- a/drivers/staging/tidspbridge/cor
On Fri, Jun 15, 2012 at 8:31 AM, Yan, Zheng wrote:
> From: "Yan, Zheng"
>
> This patch adds the generic intel uncore pmu support, including helper
> functions that add/delete uncore events, a hrtimer that periodically
> polls the counters to avoid overflow and code that places all events
> for a
(2012/07/24 11:36), Yoshihiro YUNOMAE wrote:
> Therefore, we propose a new system "virtio-trace", which uses enhanced
> virtio-serial and existing ring-buffer of ftrace, for collecting guest kernel
> tracing data. In this system, there are 5 main components:
> (1) Ring-buffer of ftrace in a guest
On Mon, 2012-07-23 at 16:32 -0600, Grant Likely wrote:
> > As-is I'm backing off from the linear/legacy/tree merge patch as just
> > too risky. I've already pulled that stuff out of linux-next.
>
> Can I pull you pseries fix into my tree (my preference), or do I need
> to rebase on top of yours?
On Mon, Jul 23, 2012 at 03:44:41PM +0200, Miguel Gómez wrote:
> El 23/07/12 15:36, Matthew Garrett escribió:
> >On Mon, Jul 23, 2012 at 03:33:27PM +0200, Miguel Gómez wrote:
> >
> >>Names are upper-cased in acpica, so the device is reported as
> >>FNBT. But in the driver it's named FnBT, an
There is no comment on the patch about a month. But I want to merge the patch
into linux-3.6. So I resend it.
---
Even if container device has _SUN method, the method is ignored. So we cannot
know slot-unique ID number of the container device. The patch creates "sun"
file in sysfs so that we can
On 07/24/2012 10:27 AM, Vlad Yasevich wrote:
xufeng zhang wrote:
On 07/19/2012 01:57 PM, xufengzhang.m...@gmail.com wrote:
When "Invalid Stream Identifier" ERROR happens after process the
received DATA chunks, this ERROR chunk is enqueued into outqueue
before SACK chunk, so when bun
From: "Yan, Zheng"
The event control register of SNB-EP uncore QPI box has a one bit
extension at bit position 21.
Reported-by: Stephane Eranian
Signed-off-by: Yan, Zheng
---
Changes since V1:
- Define the extentsion bit together with event select field
arch/x86/kernel/cpu/perf_event_intel_
This patch adds a user tool, "trace agent" for sending trace data of a guest to
a Host in low overhead. This agent has the following functions:
- splice a page of ring-buffer to read_pipe without memory copying
- splice the page from write_pipe to virtio-console without memory copying
- write tr
From: Masami Hiramatsu
Use generic steal operation on pipe buffer to allow stealing
ring buffer's read page from pipe buffer.
Note that this could reduce the performance of splice on the
splice_write side operation without affinity setting.
Since the ring buffer's read pages are allocated on the
From: Masami Hiramatsu
Wait if the port is not connected or full on splice
like as write is doing.
Signed-off-by: Masami Hiramatsu
Cc: Amit Shah
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
---
drivers/char/virtio_console.c | 39 +++
1 files changed, 27 in
From: Masami Hiramatsu
Allocate scatterlist according to the current pipe size.
This allows splicing bigger buffer if the pipe size has
been changed by fcntl.
Signed-off-by: Masami Hiramatsu
Cc: Amit Shah
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
---
drivers/char/virtio_console.c | 23 +++
From: Masami Hiramatsu
Add a failback memcpy path for unstealable pipe buffer.
If buf->ops->steal() fails, virtio-serial tries to
copy the page contents to an allocated page, instead
of just failing splice().
Signed-off-by: Masami Hiramatsu
Cc: Amit Shah
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartm
From: Masami Hiramatsu
Enable to use splice_write from pipe to virtio-console port.
This steals pages from pipe and directly send it to host.
Note that this may accelerate only the guest to host path.
Signed-off-by: Masami Hiramatsu
Cc: Amit Shah
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
---
Hi All,
The following patch set provides a low-overhead system for collecting kernel
tracing data of guests by a host in a virtualization environment.
A guest OS generally shares some devices with other guests or a host, so
reasons of any problems occurring in a guest may be from other guests or
On Mon, 2012-07-23 at 12:51 -0700, John Stultz wrote:
> On 07/19/2012 01:48 PM, Christoph Biedl wrote:
> > John Stultz wrote...
> >
> >> Attached is the test case I used to reproduce and test the solution
> >> to the hard-hang deadlock.
> > I was wondering whether anybody managed to crash a virtual
On Mon, 2012-07-23 at 22:13 +0100, Mel Gorman wrote:
> The backing database was postgres.
FWIW, that wouldn't have been my choice. I don't know if it still does,
but it used to use userland spinlocks to achieve scalability. Turning
your CPUs into space heaters to combat concurrency issues makes
On Fri, Jul 20, 2012 at 03:09:00PM +0100, Alan Cox wrote:
> On Fri, 20 Jul 2012 20:45:25 +0800
> Zhao Chenhui wrote:
>
> > Add IDE support for MPC85xxCDS.
> >
> > Signed-off-by: Zhao Chenhui
> > ---
> > arch/powerpc/configs/mpc85xx_defconfig |2 ++
> > 1 files changed, 2 insertions(+), 0 d
xufeng zhang wrote:
>On 07/19/2012 01:57 PM, xufengzhang.m...@gmail.com wrote:
>> When "Invalid Stream Identifier" ERROR happens after process the
>> received DATA chunks, this ERROR chunk is enqueued into outqueue
>> before SACK chunk, so when bundling ERROR chunk with SACK chunk,
>> the ERROR c
Hi Greg,
On Mon, Jul 23, 2012 at 03:27:49PM -0700, Greg Kroah-Hartman wrote:
> On Mon, Jul 23, 2012 at 05:10:39PM -0500, Seth Jennings wrote:
> > Greg,
> >
> > I know it's the first Monday after a kernel release and
> > things are crazy for you. I was hoping to get this zsmalloc
> > stuff in bef
On 07/23/2012 10:03 PM, Xiao Guangrong wrote:
> Currently, kvm allocates some pages and use then as error indicators,
> it wastes memory and is not good for scalability.
>
> In this patchset, we introduce some error code instead of the pages to
> indicate the error conditions.
>
Sorry for the no
Hey,
Linus released this Saturday v3.5 and there were quite a few
of interesting components/fixes/features that went in!
Going to go down the list of what shortlog provided:
- Less MSR traps when using AMD machines - so better performance. [andre]
- The APIC IPI interface works - which means th
Thank you all. Maybe both of the two ideas are acceptable.
Seeing your discussion, I prefer to group patches in thread if thread is
not heavy, else I would like to start a new thread.
Thanks again.
Du, Changbin
> -Original Message-
> From: Randy Dunlap [mailto:rdun...@xenotime.net]
> Sent
convert arch/x86/mm/pat_rbtree.c to the proposed augmented rbtree api
and remove the old augmented rbtree implementation.
Signed-off-by: Michel Lespinasse
---
arch/x86/mm/pat_rbtree.c | 63
include/linux/rbtree.h |8 -
lib/rbtree.c
Add an augmented tree rotation callback to __rb_erase_color(), so that
augmented tree information can be maintained while rebalancing.
Also introduce rb_erase_augmented(), which is a version of rb_erase()
with augmented tree callbacks. We need three callbacks here: one to
copy the subtree's augmen
On 7/23/12, Neil Horman wrote:
> On Mon, Jul 23, 2012 at 10:30:34AM +0800, xufeng zhang wrote:
>> On 07/23/2012 08:49 AM, Neil Horman wrote:
>> >
>> >Not sure I understand how you came into this error. If we get an
>> > invalid
>> >stream, we issue an SCTP_REPORT_TSN side effect, followed by an
>
On Fri, Jul 20, 2012 at 05:31:01AM -0700, Michel Lespinasse wrote:
> Patch 5 speeds up the augmented rbtree erase. Here again we use a tree
> rotation callback during rebalancing; however we also have to propagate
> the augmented node information above nodes being erased and/or stitched,
> and I ha
Signed-off-by: Paul Cercueil
---
drivers/video/console/fbcon.c | 102 -
1 file changed, 69 insertions(+), 33 deletions(-)
diff --git a/drivers/video/console/fbcon.c b/drivers/video/console/fbcon.c
index 2e471c2..a0b1818 100644
--- a/drivers/video/console
Signed-off-by: Paul Cercueil
---
drivers/video/console/fbcon.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/video/console/fbcon.c b/drivers/video/console/fbcon.c
index a0b1818..3ffab97 100644
--- a/drivers/video/console/fbcon.c
+++ b/drivers/video/console/fbcon.
Signed-off-by: Paul Cercueil
---
drivers/video/console/fbcon.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/video/console/fbcon.c b/drivers/video/console/fbcon.c
index 3ffab97..9b83b75 100644
--- a/drivers/video/console/fbcon.c
+++ b/drivers/video/console/fb
Signed-off-by: Paul Cercueil
---
drivers/video/console/fbcon.c |8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/drivers/video/console/fbcon.c b/drivers/video/console/fbcon.c
index 9b83b75..1ecaf68 100644
--- a/drivers/video/console/fbcon.c
+++ b/drivers/video/console
On 07/24/2012 02:02 AM, Doug Anderson wrote:
> The documentation for the dw_mmc part says that the low power
> mode should normally only be set for MMC and SD memory and should
> be turned off for SDIO cards that need interrupts detected.
>
> The best place I could find to do this is when the SDIO
commit 01eaf24 "extcon: Convert extcon_gpio to devm_gpio_request_one"
missed the replacement for devm_gpio_request_one. fix it.
Signed-off-by: Axel Lin
---
drivers/extcon/extcon_gpio.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/extcon/extcon_gpio.c b/drivers
Hi Borislav:
Realtek card reader supports not only SDMMC card, but also Memory stick.
This part is the common code, so it is located in drivers/misc. There is
also SDMMC-relevant code under CONFIG_MMC. And in the future,
Memstick-relevant code will be added under CONFIG_MEMSTICK.
BR,
wwang
On 07/24/2012 02:46 AM, Martin Mokrejs wrote:
> Hi,
> I see few more RCU bugs reported in bugzilla:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=43028
> https://bugzilla.kernel.org/show_bug.cgi?id=40092
> https://bugzilla.kernel.org/show_bug.cgi?id=42997
>
> And, I placed my previous long em
On Mon, 2012-07-23 at 22:41 +0200, Andrea Righi wrote:
> On Thu, Jun 21, 2012 at 10:23:02AM +0200, Mike Galbraith wrote:
> > On Thu, 2012-06-21 at 11:54 +0400, Alexey Vlasov wrote:
> > > On Wed, Jun 20, 2012 at 02:28:18PM +0200, Mike Galbraith wrote:
> > > >
> > > > kernel/cgroup.c::cgroup_attac
July 24, 2012, Doug Anderson wrote:
> The documentation for the dw_mmc part says that the low power
> mode should normally only be set for MMC and SD memory and should
> be turned off for SDIO cards that need interrupts detected.
>
> The best place I could find to do this is when the SDIO interru
Texas Instruments Keystone family of multicore devices now includes an
upcoming slew of Cortex A15 based devices. This patch adds basic definitions
for a new Keystone sub-architecture in ARM.
Subsequent patches in this series will extend support to include SMP and take
advantage of the large phys
From: Vitaly Andrianov
This patch fixes the initrd setup code to use phys_addr_t instead of assuming
32-bit addressing. Without this we cannot boot on systems where initrd is
located above the 4G physical address limit.
Signed-off-by: Vitaly Andrianov
Signed-off-by: Cyril Chemparathy
---
arc
Keystone platforms have their physical memory mapped at an address outside the
32-bit physical range. A Keystone machine with 16G of RAM would find its
memory at 0x08 - 0x0b.
For boot purposes, the interconnect supports a limited alias of some of this
memory within the 32-bit addr
On Keystone platforms, physical memory is entirely outside the 32-bit
addressible range. Therefore, the (bank->start > ULONG_MAX) check below marks
the entire system memory as highmem, and this causes unpleasentness all over.
This patch eliminates the extra bank start check (against ULONG_MAX) by
This patch modifies the switch_mm() processor functions to use 64-bit
addresses. We use u64 instead of phys_addr_t, in order to avoid having config
dependent register usage when calling into switch_mm assembly code.
The changes in this patch are primarily adjustments for registers used for
argume
This patch redefines the early boot time use of the R4 register to steal a few
low order bits (ARCH_PGD_SHIFT bits), allowing for up to 38-bit physical
addresses.
This is probably not the best means to the end, and a better alternative may
be to modify the head.S register allocations to fit in ful
From: Vitaly Andrianov
The current phys-to-virt patching mechanism is broken on PAE machines with
64-bit physical addressing. This patch disables the patching mechanism in
such configurations.
Signed-off-by: Vitaly Andrianov
Signed-off-by: Cyril Chemparathy
---
arch/arm/Kconfig |1 +
1 f
This patch changes the membank structure's size field to phys_addr_t to allow
banks larger than 4G.
Signed-off-by: Cyril Chemparathy
Signed-off-by: Vitaly Andrianov
---
arch/arm/include/asm/setup.h |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/include/asm/s
This patch cleans up the highmem sanity check code by simplifying the range
checks with a pre-calculated size_limit. This patch should otherwise have no
functional impact on behavior.
This patch also removes a redundant (bank->start < vmalloc_limit) check, since
this is already covered by the !hi
This patch adds a machine descriptor hook that gives control to machine
specific code prior to memory and paging initialization.
On Keystone platforms, this hook is used to switch the PHYS_OFFSET over
to the "real" non-32-bit-addressable address range.
Signed-off-by: Cyril Chemparathy
Signed-off
This patch applies to PAGE_MASK, PMD_MASK, and PGDIR_MASK, where forcing
unsigned long math truncates the mask at the 32-bits. This clearly does bad
things on PAE systems.
This patch fixes this problem by defining these masks as signed quantities.
We then rely on sign extension to do the right th
From: Vitaly Andrianov
This patch fixes the alloc_init_pud() function to use phys_addr_t instead of
unsigned long when passing in the phys argument.
This is an extension to commit 97092e0c56830457af0639f6bd904537a150ea4a, which
applied similar changes elsewhere in the ARM memory management code.
This patch moves the TTBR1 offset calculation and the T1SZ calculation out
of the TTB setup assembly code. This should not affect functionality in
any way, but improves code readability as well as readability of subsequent
patches in this series.
Signed-off-by: Cyril Chemparathy
Signed-off-by: V
This patch warns if memory-hotplug/boot code doesn't initialize
pg_data_t with zero when it's allocated. As I looked arch code and
memory hotplug, they already seem to initiailize pg_data_t.
So this warning should be never happen. It needs double check and
let's add checking garbage with warn. I se
pg_data_t should be zero out before reaching free_area_init_core
so remove unnecessary initialization.
Signed-off-by: Minchan Kim
---
include/linux/vmstat.h |5 -
mm/page_alloc.c|9 ++---
2 files changed, 2 insertions(+), 12 deletions(-)
diff --git a/include/linux/vmstat
This patch adds an architecture defined override for ARCH_LOW_ADDRESS_LIMIT.
On PAE systems, the absence of this override causes bootmem to incorrectly
limit itself to 32-bit addressable physical memory.
Signed-off-by: Cyril Chemparathy
Signed-off-by: Vitaly Andrianov
---
arch/arm/include/asm/m
From: Vitaly Andrianov
On some PAE systems (e.g. TI Keystone), memory is above the 32-bit addressible
limit, and the interconnect provides an aliased view of parts of physical
memory in the 32-bit addressible space. This alias is strictly for boot time
usage, and is not otherwise usable because
This patch modifies the highmem sanity checking code to use physical addresses
instead. This change eliminates the wrap-around problems associated with the
original virtual address based checks, and this simplifies the code a bit.
The one constraint imposed here is that low physical memory must b
This patch adds TTBR accessor macros, and modifies cpu_get_pgd() and
the LPAE version of cpu_set_reserved_ttbr0() to use these instead.
In the process, we also fix these functions to correctly handle cases
where the physical address lies beyond the 4G limit of 32-bit addressing.
Signed-off-by: Cy
This patch is ready for next patch which try to remove zero-out
of pg_data_t in core MM part. At a glance, all archs except this part
already have done it so this patch makes consistent with other archs.
Cc: Ralf Baechle
Cc: linux-m...@linux-mips.org
Signed-off-by: Minchan Kim
---
arch/mips/sgi
From: Vitaly Andrianov
On a physical address extended (PAE) systems physical memory may be located
outside the first 4GB address range. In particular, on TI Keystone devices,
all memory (including lowmem) is located outside the 4G address space. Many
functions in the bootmem.c use unsigned long
This patch adds basic SMP support for Keystone machines. Nothing very fancy
here, just enough to get 4 CPUs booted up. This does not include support for
hotplug, etc.
Signed-off-by: Vitaly Andrianov
Signed-off-by: Cyril Chemparathy
---
arch/arm/Kconfig|1 +
arch/arm/co
This patch allows ARM processor setup functions (*_setup in proc-*.S) to
indicate that the page table has already been programmed. This is
done by setting r4 (page table pointer) to -1 before returning from the
processor setup handler.
This capability is particularly needed on LPAE systems, where
TI's scalable KeyStone II architecture includes support for both TMS320C66x
floating point DSPs and ARM Cortex-A15 clusters, for a mixture of up to 32
cores per SoC. The solution is optimized around a high performance chip
interconnect and a rich set of on chip peripherals. Please refer [1] for
i
This patch fixes up the types used when converting back and forth between
physical and virtual addresses.
Signed-off-by: Vitaly Andrianov
Signed-off-by: Cyril Chemparathy
---
arch/arm/include/asm/memory.h | 17 +++--
1 file changed, 11 insertions(+), 6 deletions(-)
diff --git a/a
From: Vitaly Andrianov
The free_memmap() was mistakenly using unsigned long type to represent
physical addresses. This breaks on PAE systems where memory could be placed
above the 32-bit addressible limit.
This patch fixes this function to properly use phys_addr_t instead.
Signed-off-by: Vital
This patch fixes a couple of bugs that otherwise impair CMA functionality on
PAE machines:
- alignment must be a 64-bit type when running on systems with 64-bit
physical addresses. If this is not the case, the limit calculation thunks
allocations down to an address range < 4G.
- The
1 - 100 of 509 matches
Mail list logo
