From: Andreas Schwab <schwab@suse.de>
To: Anup Patel <anup@brainfault.org>
Cc: Palmer Dabbelt <palmer@sifive.com>,
Anup Patel <Anup.Patel@wdc.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Atish Patra <Atish.Patra@wdc.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Paul Walmsley <paul.walmsley@sifive.com>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v2 6/6] RISC-V: Implement keepinitrd kernel parameter
Date: Tue, 12 Feb 2019 11:37:34 +0100 [thread overview]
Message-ID: <mvmva1ps369.fsf@suse.de> (raw)
In-Reply-To: <CAAhSdy1NED22YyYrAJDqPkDqT1c2ms2QC9OjHP0qLwHT+o2zvg@mail.gmail.com> (Anup Patel's message of "Tue, 12 Feb 2019 15:53:21 +0530")
On Feb 12 2019, Anup Patel <anup@brainfault.org> 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, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@suse.de>
To: Anup Patel <anup@brainfault.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Anup Patel <Anup.Patel@wdc.com>,
Palmer Dabbelt <palmer@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Atish Patra <Atish.Patra@wdc.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
"linux-riscv\@lists.infradead.org"
<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v2 6/6] RISC-V: Implement keepinitrd kernel parameter
Date: Tue, 12 Feb 2019 11:37:34 +0100 [thread overview]
Message-ID: <mvmva1ps369.fsf@suse.de> (raw)
In-Reply-To: <CAAhSdy1NED22YyYrAJDqPkDqT1c2ms2QC9OjHP0qLwHT+o2zvg@mail.gmail.com> (Anup Patel's message of "Tue, 12 Feb 2019 15:53:21 +0530")
On Feb 12 2019, Anup Patel <anup@brainfault.org> 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, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2019-02-12 10:37 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 13:27 [PATCH v2 0/6] Fixmap support and MM cleanups Anup Patel
2019-01-19 13:27 ` Anup Patel
2019-01-19 13:27 ` [PATCH v2 1/6] RISC-V: Move free_initrd_mem() to kernel/setup.c Anup Patel
2019-01-19 13:27 ` Anup Patel
2019-01-19 13:28 ` [PATCH v2 2/6] RISC-V: Setup init_mm before parse_early_param() Anup Patel
2019-01-19 13:28 ` Anup Patel
2019-02-12 7:05 ` Christoph Hellwig
2019-02-12 7:05 ` Christoph Hellwig
2019-01-19 13:28 ` [PATCH v2 3/6] RISC-V: Move setup_bootmem() to mm/init.c Anup Patel
2019-01-19 13:28 ` Anup Patel
2019-01-19 13:28 ` [PATCH v2 4/6] RISC-V: Move setup_vm() " Anup Patel
2019-01-19 13:28 ` Anup Patel
2019-01-19 13:28 ` [PATCH v2 5/6] RISC-V: Implement compile-time fixed mappings Anup Patel
2019-01-19 13:28 ` Anup Patel
2019-02-12 7:06 ` Christoph Hellwig
2019-02-12 7:06 ` Christoph Hellwig
2019-01-19 13:28 ` [PATCH v2 6/6] RISC-V: Implement keepinitrd kernel parameter Anup Patel
2019-01-19 13:28 ` Anup Patel
2019-02-12 7:08 ` Christoph Hellwig
2019-02-12 7:08 ` Christoph Hellwig
2019-02-12 10:23 ` Anup Patel
2019-02-12 10:23 ` Anup Patel
2019-02-12 10:37 ` Andreas Schwab [this message]
2019-02-12 10:37 ` Andreas Schwab
2019-02-12 13:53 ` Anup Patel
2019-02-12 13:53 ` Anup Patel
2019-02-12 18:45 ` Christoph Hellwig
2019-02-12 18:45 ` Christoph Hellwig
2019-02-13 3:43 ` Anup Patel
2019-02-13 3:43 ` Anup Patel
2019-02-13 5:55 ` Christoph Hellwig
2019-02-13 5:55 ` Christoph Hellwig
2019-02-13 6:05 ` Anup Patel
2019-02-13 6:05 ` Anup Patel
2019-02-12 21:59 ` Palmer Dabbelt
2019-02-12 21:59 ` Palmer Dabbelt
2019-02-11 6:27 ` [PATCH v2 0/6] Fixmap support and MM cleanups Anup Patel
2019-02-11 6:27 ` Anup Patel
2019-02-12 23:15 ` Palmer Dabbelt
2019-02-12 23:15 ` Palmer Dabbelt
2019-02-13 8:21 ` Anup Patel
2019-02-13 8:21 ` Anup Patel
2019-02-13 9:20 ` Johan Hovold
2019-02-13 9:20 ` Johan Hovold
2019-02-14 0:37 ` Palmer Dabbelt
2019-02-14 0:37 ` Palmer Dabbelt
2019-02-14 8:28 ` Anup Patel
2019-02-14 8:28 ` Anup Patel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mvmva1ps369.fsf@suse.de \
--to=schwab@suse.de \
--cc=Anup.Patel@wdc.com \
--cc=Atish.Patra@wdc.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.