From: David Woodhouse <dwmw2@infradead.org>
To: Jan Beulich <jbeulich@suse.com>
Cc: xen-devel@lists.xenproject.org, jiewen.yao@intel.com, jeff.fan@intel.com
Subject: Re: [PATCH] x86/efi: Do not write relocations in efi_arch_relocate_image() first pass
Date: Wed, 02 Aug 2017 16:56:18 +0100 [thread overview]
Message-ID: <1501689378.4771.427.camel@infradead.org> (raw)
In-Reply-To: <5981ECB402000078001033D6@prv-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 1466 bytes --]
On Wed, 2017-08-02 at 09:16 -0600, Jan Beulich wrote:
>
> Well, I've seen breakage in all sorts of places I wouldn't have expected
> anyone to fine a need to fiddle with.
This is the nature of 'value subtract', I suppose.
How about something like this? Somewhat complicated by the fact that
COFF section names get truncated, so maybe there's a nicer place to put
it (or maybe we explicitly include .init.da into the .init.data output
section, in the efi.lds linker script, or something?)....
--- a/xen/arch/x86/efi/mkreloc.c
+++ b/xen/arch/x86/efi/mkreloc.c
@@ -346,6 +346,15 @@ int main(int argc, char *argv[])
memcmp(sec1[i].name, ".lockpro", sizeof(sec1[i].name)) == 0 )
continue;
+ /* For sections with relocations, force them to be writeable */
+ if (memcmp(sec1[i].name, ".init.da", sizeof(sec1[i].name)) == 0)
+ printf(".pushsection .init.data, \"awx\"\n");
+ else if (memcmp(sec1[i].name, ".init.te", sizeof(sec1[i].name) ) == 0)
+ printf(".pushsection .init.text, \"awx\"\n");
+ else
+ printf(".pushsection %.*s, \"awx\"\n", (int)sizeof(sec1[i].name), sec1[i].name);
+ printf(".popsection\n");
+
if ( !sec1[i].rva )
{
fprintf(stderr, "Can't handle section %u with zero RVA\n", i);
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 4938 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-08-02 15:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 15:20 xen/link: Move .data.rel.ro sections into .rodata for final link David Woodhouse
2017-07-20 16:46 ` Wei Liu
2017-07-20 16:54 ` Wei Liu
2017-07-21 10:43 ` Julien Grall
2017-07-21 16:41 ` Andrew Cooper
2017-07-25 9:21 ` [PATCH v2] " David Woodhouse
2017-07-30 6:16 ` Jan Beulich
2017-07-30 12:50 ` Andrew Cooper
2017-07-30 23:18 ` David Woodhouse
2017-07-31 9:57 ` Jan Beulich
2017-07-31 10:15 ` David Woodhouse
2017-07-31 9:55 ` Jan Beulich
2017-07-31 11:02 ` David Woodhouse
2017-07-31 13:15 ` Jan Beulich
2017-07-31 15:56 ` David Woodhouse
2017-08-02 9:17 ` Jan Beulich
2017-08-02 11:30 ` [PATCH] x86/efi: Do not write relocations in efi_arch_relocate_image() first pass David Woodhouse
2017-08-02 11:56 ` Jan Beulich
2017-08-02 12:11 ` David Woodhouse
2017-08-02 13:58 ` Jan Beulich
2017-08-02 14:45 ` David Woodhouse
2017-08-02 15:16 ` Jan Beulich
2017-08-02 15:56 ` David Woodhouse [this message]
2017-08-02 11:43 ` xen/link: Move .data.rel.ro sections into .rodata for final link David Woodhouse
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=1501689378.4771.427.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=jbeulich@suse.com \
--cc=jeff.fan@intel.com \
--cc=jiewen.yao@intel.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).