From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751865AbcF0Qvc (ORCPT ); Mon, 27 Jun 2016 12:51:32 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:51886 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751673AbcF0Qvb (ORCPT ); Mon, 27 Jun 2016 12:51:31 -0400 X-IBM-Helo: d24dlp01.br.ibm.com X-IBM-MailFrom: bauerman@linux.vnet.ibm.com X-IBM-RcptTo: linux-kernel@vger.kernel.org From: Thiago Jung Bauermann To: Dave Young Cc: kexec@lists.infradead.org, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, Eric Biederman Subject: Re: [PATCH v3 3/9] kexec_file: Factor out kexec_locate_mem_hole from kexec_add_buffer. Date: Mon, 27 Jun 2016 13:51:16 -0300 User-Agent: KMail/4.14.3 (Linux/3.13.0-88-generic; KDE/4.14.13; x86_64; ; ) In-Reply-To: <5428891.iJNV8CI1We@hactar> References: <1466538521-31216-1-git-send-email-bauerman@linux.vnet.ibm.com> <20160627161948.GA5876@dhcp-128-65.nay.redhat.com> <5428891.iJNV8CI1We@hactar> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16062716-0020-0000-0000-00000218FB81 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 16062716-0021-0000-0000-00002FF0EA8D Message-Id: <1915759.R1Bukpmjaj@hactar> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-06-27_11:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1606270174 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Montag, 27 Juni 2016, 13:37:58 schrieb Thiago Jung Bauermann: > Should I add a separate top_down argument to kexec_locate_mem_hole to > control if the memory walk should be from top to bottom, and then the > bottom_up member of struct kexec_buf controls where inside each memory > region the memory hole will be allocated? Er, "...the bottom_up member of struct kexec_buf..." should read "...the top_down member of struct kexec buf...". -- []'s Thiago Jung Bauermann IBM Linux Technology Center