From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754477AbbCLNz7 (ORCPT ); Thu, 12 Mar 2015 09:55:59 -0400 Received: from down.free-electrons.com ([37.187.137.238]:42014 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754019AbbCLNz6 (ORCPT ); Thu, 12 Mar 2015 09:55:58 -0400 Date: Thu, 12 Mar 2015 14:55:54 +0100 From: Thomas Petazzoni To: Stas Sergeev Cc: Russell King - ARM Linux , Linux kernel , linux-arm-kernel@lists.infradead.org, Gregory =?UTF-8?B?Q2zDqW1lbnQ=?= , Catalin Marinas Subject: Re: [PATCH] n_tty: use kmalloc() instead of vmalloc() to avoid crash on armada-xp Message-ID: <20150312145554.72a6b09d@free-electrons.com> In-Reply-To: <55018E8B.8060704@list.ru> References: <54FF21BE.2040506@list.ru> <20150311175227.499612af@free-electrons.com> <55007ADD.6080505@list.ru> <20150311174618.GE8656@n2100.arm.linux.org.uk> <55008483.8050603@list.ru> <20150311193343.0317e3e1@free-electrons.com> <55018A3C.7020409@list.ru> <20150312134756.5335cb32@free-electrons.com> <55018E8B.8060704@list.ru> Organization: Free Electrons X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear Stas Sergeev, On Thu, 12 Mar 2015 16:03:07 +0300, Stas Sergeev wrote: > > No, this is expected. Your physical address space is shared between RAM > > and I/O devices. So the space 0xf0000000 -> 0xffffffff in the physical > > address space is where all the registers for your SoC and PCIe devices > Yeah, I realize that, but I was hoping that some work-around > exists. For example, move entire dimm above 4G? Is this really > impossible? Or maybe move overlapping region above 8G... I am not aware of any trick that would allow to do that, but I have also never looked in the deep details of the Marvell memory controller and what's possible to do with it. Moving entire DIMM above 4G is clearly not possible: devices can only do DMA on the first 32 bits of the physical address space. So if you move all the physical memory above 4G, you don't have any memory left for DMA. Best regards, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com