From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752353AbbICInF (ORCPT ); Thu, 3 Sep 2015 04:43:05 -0400 Received: from mailout4.samsung.com ([203.254.224.34]:33910 "EHLO mailout4.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751408AbbICInA (ORCPT ); Thu, 3 Sep 2015 04:43:00 -0400 X-AuditID: cbfee68e-f79c56d000006efb-67-55e80812749a From: Yongtaek Lee To: Russell King Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Nicolas Pitre Subject: Re: Re: Re: [PATCH] ARM: fix bug which VMALLOC_START is lowwer than 0xf0000000 Date: Thu, 03 Sep 2015 17:43:29 +0900 Message-id: <1441269809-11688-1-git-send-email-ytk.lee@samsung.com> X-Mailer: git-send-email 1.7.9 In-reply-to: <1441269272.3102.3.camel@pengutronix.de> References: <1441269272.3102.3.camel@pengutronix.de> X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrCLMWRmVeSWpSXmKPExsVy+t8zXV0hjhehBg8valpsenyN1eLyrjls Frcv81p8evaP3YHFo6W5h83jzrU9bB6bl9R7fN4kF8ASxWWTkpqTWZZapG+XwJVxfpd1wQKW ii2LJzE1MK5j7mLk5JAQMJH48foelC0mceHeerYuRi4OIYGVjBK37nxjgin61PESKjGLUeLN 4fssEM4PRolzWz+wg1SxCWhI7OxcygJiiwhoSpxafBFoLAcHs0CRxJyOcJCwsECkxL+T5xhB bBYBVYmFx16D2bwCzhJXDm5jhFgmJ9HZ+w3M5hQwlZjybD3YdUIgR8ztZALZKyHwnU3i+YGN zBCDBCS+TT7EArJLQkBWYtMBqG8kJQ6uuMEygVF4ASPDKkbR1ILkguKk9CIjveLE3OLSvHS9 5PzcTYyQwO3bwXjzgPUhRgEORiUe3gmzn4cKsSaWFVfmHmI0BdowkVlKNDkfGB95JfGGxmZG FqYmpsZG5pZmSuK8CVI/g4UE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUwZvxdZJPxL6R293YO 7YRwy7OTvKpizvMf+T4jODCSJUZj8su/mjfqEs/uy5a7MvVC8/mfJr4z3bQmrbp4Ntg8cN6q y2lSqzZsEuGSre2fkbclauLLeO77kgcnra3a5Vd/us31tsq6602rVc/33Duhf/WFRsZqw7KM uEXui+fbBQv0vSp77FfMqcRSnJFoqMVcVJwIABqKxKpXAgAA X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprIIsWRmVeSWpSXmKPExsVy+t9jQV0hjhehBl2n1Sw2Pb7GanF51xw2 i9uXeS0+PfvH7sDi0dLcw+Zx59oeNo/NS+o9Pm+SC2CJamC0yUhNTEktUkjNS85PycxLt1Xy Do53jjc1MzDUNbS0MFdSyEvMTbVVcvEJ0HXLzAHaqKRQlphTChQKSCwuVtK3wzQhNMRN1wKm MULXNyQIrsfIAA0krGPMOL/LumABS8WWxZOYGhjXMXcxcnJICJhIfOp4yQZhi0lcuLceyObi EBKYxSjx5vB9FgjnB6PEua0f2EGq2AQ0JHZ2LmUBsUUENCVOLb4INImDg1mgSGJORzhIWFgg UuLfyXOMIDaLgKrEwmOvwWxeAWeJKwe3MUIsk5Po7P0GZnMKmEpMebYe7CAhkIPmdjJNYORd wMiwilEitSC5oDgpPdcoL7Vcrzgxt7g0L10vOT93EyM4Op5J72A8vMv9EKMAB6MSD++E2c9D hVgTy4orcw8xSnAwK4nwprwBCvGmJFZWpRblxxeV5qQWH2I0BTpsIrOUaHI+MHLzSuINjU3M jCyNzIxNzI2NlcR5ZVc+CxUSSE8sSc1OTS1ILYLpY+LglGpgzJTResAw/8eF9xlTtha4n9zb tq1+QoDKebFU4zkrdnOvWda/RkRKKkdmO9v+6+7BdY7brBe7bQt5JTA/7nfPtyyTI1HfpJwU FPZzH9gRdvCxsf/P6V1zwp42n56+YdeeVbW6VvO8Ej5uKbmx5RHzbmbuJH82a6sdAWJZl0XX Pv6yNt0u4o3ADyWW4oxEQy3mouJEAHmhwkSkAgAA DLP-Filter: Pass X-MTR: 20000000000000000@CPGS X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > So, if we go and apply your logic to a 1GB system we should resize the > vmalloc area to 0 bytes in order to avoid RAM truncation without > CONFIG_HIGHMEM? As you already know, CONFIG_HIGHMEM option is necessary if RAM is more than 1GB. So no need to resize vmalloc area to 0. > Sorry, but the only sane options here are to either live with the > truncation, enable CONFIG_HIGHMEM, or set vmalloc size manually. > Changing a default value that affects everyone for the benefit of your > specific use-case isn't a sane option.