From: Borislav Petkov <bp@suse.de>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: hpa@zytor.com, torvalds@linux-foundation.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org, mingo@kernel.org,
peterz@infradead.org
Subject: Re: [tip:x86/microcode] x86/microcode: Document the three loading methods
Date: Sat, 5 Aug 2017 08:15:44 +0200 [thread overview]
Message-ID: <20170805061544.GA23869@nazgul.tnic> (raw)
In-Reply-To: <7e438573-b35d-eea8-8f8a-c341c4dd91a4@molgen.mpg.de>
On Fri, Aug 04, 2017 at 01:24:02PM +0200, Paul Menzel wrote:
> > Gitweb: http://git.kernel.org/tip/0e3258753f8183c63bf68bd274d2cc7e71e5f402
>
> Could you the script(?) please be updated to use HTTPS URLs?
tip guys?
> Maybe it could be added, that certain bootloaders like GRUB allow to specify
> several `initrd` images. So you wouldn’t need to concatenate the file [1].
So this is the simplest script possible just to show the basic steps
that are required. Any treatise of what some bootloaders do is out of
scope as then I'm going to have to maintain a full-fledged script (there
will be other people saying, but but, on my system... ) which is going to
be pointless - distros are free to create the initrd they way they see
best. This script is an example only and the bare minimum at that.
> The *legacy* confuses me a little. Is it because `/sys` is used?
They're legacy because they're the older methods and people should try
to avoid them and concentrate on the early, initrd loading.
Thanks.
--
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:[~2017-08-05 6:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 10:12 [PATCH 0/3] x86 stuff for 4.14 Borislav Petkov
2017-07-24 10:12 ` [PATCH 1/3] x86/microcode/AMD: Free unneeded patch before exit from update_cache() Borislav Petkov
2017-07-25 13:50 ` [tip:x86/microcode] " tip-bot for Shu Wang
2017-07-24 10:12 ` [PATCH 2/3] x86/microcode: Document the three loading methods Borislav Petkov
2017-07-25 13:51 ` [tip:x86/microcode] " tip-bot for Borislav Petkov
2017-08-04 11:24 ` Paul Menzel
2017-08-05 6:15 ` Borislav Petkov [this message]
2017-07-24 10:12 ` [PATCH 3/3] x86/mce/AMD: Allow any CPU to initialize smca_banks array Borislav Petkov
2017-07-25 13:51 ` [tip:ras/core] x86/mce/AMD: Allow any CPU to initialize the " tip-bot for Yazen Ghannam
2017-07-25 13:51 ` tip-bot for Borislav Petkov
2017-07-25 13:55 ` tip-bot for Yazen Ghannam
2017-07-25 13:55 ` tip-bot for Borislav Petkov
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=20170805061544.GA23869@nazgul.tnic \
--to=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=pmenzel@molgen.mpg.de \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 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.