From: Borislav Petkov <bp@suse.de>
To: Alexander Kuleshov <kuleshovmail@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Joerg Roedel <jroedel@suse.de>,
Dave Young <dyoung@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <bhe@redhat.com>, Mark Salter <msalter@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8] x86/setup: get ramdisk parameters only once
Date: Fri, 26 Feb 2016 10:33:49 +0100 [thread overview]
Message-ID: <20160226093349.GB12729@pd.tnic> (raw)
In-Reply-To: <1456477476-16415-1-git-send-email-kuleshovmail@gmail.com>
On Fri, Feb 26, 2016 at 03:04:36PM +0600, Alexander Kuleshov wrote:
> The check and definitions related to ramdisk are similar in the
> early_reserve_initrd() and reserve_initrd() functions.
>
> This patch introduces struct ramdisk which contains information
> about initrd. This structure will be filled in the setup_arch()
> and passed to the reserve_initrd() and relocate_initrd() functions.
>
> This allows us to not get/check ramdisk parameters from the bootparams
> every time in the early_reserve_initrd(), reserve_initrd() and
> relocate_initrd() function.
>
> Signed-off-by: Alexander Kuleshov <kuleshovmail@gmail.com>
...
> arch/x86/kernel/setup.c | 107 ++++++++++++++++++++++++++----------------------
> 1 file changed, 59 insertions(+), 48 deletions(-)
Reviewed-by: Borislav Petkov <bp@suse.de>
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
next prev parent reply other threads:[~2016-02-26 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 9:04 Alexander Kuleshov
2016-02-26 9:33 ` Borislav Petkov [this message]
2016-02-29 10:57 ` [tip:x86/boot] x86/setup: Calculate " tip-bot for Alexander Kuleshov
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=20160226093349.GB12729@pd.tnic \
--to=bp@suse.de \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=jroedel@suse.de \
--cc=kuleshovmail@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=msalter@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®