From: Ingo Molnar <mingo@kernel.org>
To: Maarten Lankhorst <m.b.lankhorst@gmail.com>
Cc: lee.g.rosenbaum@intel.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, jordan.l.justen@intel.com,
tglx@linutronix.de, rydberg@euromail.se, matt.fleming@intel.com,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86, efi stub: Add .reloc section back into image
Date: Fri, 8 Jun 2012 11:06:21 +0200 [thread overview]
Message-ID: <20120608090621.GB10841@gmail.com> (raw)
In-Reply-To: <4FD10CFC.8030000@gmail.com>
* Maarten Lankhorst <m.b.lankhorst@gmail.com> wrote:
> Hey,
>
> Op 07-06-12 20:37, tip-bot for Jordan Justen schreef:
> > Commit-ID: 743628e868c5992354fc80b4d1e9a6143da1c0e6
> > Gitweb: http://git.kernel.org/tip/743628e868c5992354fc80b4d1e9a6143da1c0e6
> > Author: Jordan Justen <jordan.l.justen@intel.com>
> > AuthorDate: Thu, 7 Jun 2012 09:05:21 -0700
> > Committer: H. Peter Anvin <hpa@zytor.com>
> > CommitDate: Thu, 7 Jun 2012 09:52:33 -0700
> >
> > x86, efi stub: Add .reloc section back into image
> >
> > Some UEFI firmware will not load a .efi with a .reloc section
> > with a size of 0.
> >
> > Therefore, we create a .efi image with 4 main areas and 3 sections.
> > 1. PE/COFF file header
> > 2. .setup section (covers all setup code following the first sector)
> > 3. .reloc section (contains 1 dummy reloc entry, created in build.c)
> > 4. .text section (covers the remaining kernel image)
> >
> Scary how some patches arrive a few minutes before you need them.
We are all working hard on perfecting our precog skills!
Thanks,
Ingo
prev parent reply other threads:[~2012-06-08 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1339085121-12760-1-git-send-email-jordan.l.justen@intel.com>
2012-06-07 18:37 ` [tip:x86/urgent] x86, efi stub: Add .reloc section back into image tip-bot for Jordan Justen
2012-06-07 20:20 ` Maarten Lankhorst
2012-06-08 9:06 ` Ingo Molnar [this message]
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=20120608090621.GB10841@gmail.com \
--to=mingo@kernel.org \
--cc=hpa@zytor.com \
--cc=jordan.l.justen@intel.com \
--cc=lee.g.rosenbaum@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=m.b.lankhorst@gmail.com \
--cc=matt.fleming@intel.com \
--cc=rydberg@euromail.se \
--cc=tglx@linutronix.de \
/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