From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Date: Wed, 23 Nov 2016 09:08:19 +0100 From: Simon Horman Subject: Re: [PATCH 2/2] arm64: Pass RAM boundary and enable-dcache flag to purgatory Message-ID: <20161123080816.GA30255@verge.net.au> References: <53ee2a62-7822-5457-e59f-e65e64a57019@infradead.org> <54cad725-90f0-8dfe-bee6-fe1d3e02175d@redhat.com> <20161123020300.GA3481@dhcp-128-65.nay.redhat.com> <81975e6e-b97a-0401-0e18-b2d26722c1dd@redhat.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <81975e6e-b97a-0401-0e18-b2d26722c1dd@redhat.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Pratyush Anand Cc: Geoff Levand , james.morse@arm.com, Dave Young , kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org On Wed, Nov 23, 2016 at 07:41:52AM +0530, Pratyush Anand wrote: > > > On Wednesday 23 November 2016 07:33 AM, Dave Young wrote: > >>Although this is very unlikely that a hardware will support only 16K page > >>> sizes, however it is possible. Therefore, its better to keep it disabled by > >>> default. > >If it is *unlikely* it could be better to make it as default and add a > >--disable-dcache instead. > > > > I think, I can do that. Can this be detected at run-time? It sounds like it will be painful if on some setups the default doesn't work. _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec