ul Walmsley ;
> linux-ri...@lists.infradead.org
> Subject: Re: [PATCH v2 6/6] RISC-V: Implement keepinitrd kernel parameter
>
> On Wed, Feb 13, 2019 at 03:43:06AM +, Anup Patel wrote:
> > Sure, the keepinitrd=0 by default so it will always free-up initrd by
> > default.
&
On Wed, Feb 13, 2019 at 03:43:06AM +, Anup Patel wrote:
> Sure, the keepinitrd=0 by default so it will always free-up initrd by default.
> Please look at v3 patchset.
>
> Of course, we need separate patch to update documentation of keepinitrd.
No, we need to not just blindly copy what arm
Patel ; linux-
> ker...@vger.kernel.org; Atish Patra ; Albert Ou
> ; Paul Walmsley ;
> linux-ri...@lists.infradead.org
> Subject: Re: [PATCH v2 6/6] RISC-V: Implement keepinitrd kernel parameter
>
> On Tue, Feb 12, 2019 at 03:53:21PM +0530, Anup Patel wrote:
> > If it is initramfs (i
On Sat, 19 Jan 2019 05:28:59 PST (-0800), anup.pa...@wdc.com wrote:
This patch implements keepinitrd kernel parameter. By default,
keepinitrd=1 but users can pass "keepinitrd=0" to free-up
initrd memory at boot-time in free_initrd_mem() function.
The keepinitrd kernel parameter is already
On Tue, Feb 12, 2019 at 03:53:21PM +0530, Anup Patel wrote:
> If it is initramfs (i.e. CPIO image) then contents of CPIO archive
> are extracted to create a ramfs instance.
>
> If it is initrd (i.e. some filesystem image) then RAM block device
> is created in-place at initrd location. (Please
On Tue, Feb 12, 2019 at 4:07 PM Andreas Schwab wrote:
>
> On Feb 12 2019, Anup Patel wrote:
>
> > So in case of initrd we might not want to free-up the RAM but
> > we can certainly free-up in case of initramfs.
>
> But the default should be keepinitrd=0, shoudn't it?
Actually, it is
On Feb 12 2019, Anup Patel wrote:
> So in case of initrd we might not want to free-up the RAM but
> we can certainly free-up in case of initramfs.
But the default should be keepinitrd=0, shoudn't it?
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9
On Tue, Feb 12, 2019 at 12:38 PM Christoph Hellwig wrote:
>
> On Sat, Jan 19, 2019 at 01:28:59PM +, Anup Patel wrote:
> > This patch implements keepinitrd kernel parameter. By default,
> > keepinitrd=1 but users can pass "keepinitrd=0" to free-up
> > initrd memory at boot-time in
On Sat, Jan 19, 2019 at 01:28:59PM +, Anup Patel wrote:
> This patch implements keepinitrd kernel parameter. By default,
> keepinitrd=1 but users can pass "keepinitrd=0" to free-up
> initrd memory at boot-time in free_initrd_mem() function.
>
> The keepinitrd kernel parameter is already
This patch implements keepinitrd kernel parameter. By default,
keepinitrd=1 but users can pass "keepinitrd=0" to free-up
initrd memory at boot-time in free_initrd_mem() function.
The keepinitrd kernel parameter is already implemented by
unicore32, arm, and arm64 architectures and it is documented
10 matches
Mail list logo
