From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ross Lagerwall <ross.lagerwall@citrix.com>
Cc: wei.liu2@citrix.com, ian.campbell@citrix.com,
andrew.cooper3@citrix.com, ian.jackson@eu.citrix.com,
mpohlack@amazon.com, stefano.stabellini@citrix.com,
jbeulich@suse.com, sasha.levin@oracle.com,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 08/13] xsplice: Implement payload loading (v2)
Date: Tue, 19 Jan 2016 11:59:11 -0500 [thread overview]
Message-ID: <20160119165911.GE17737@char.us.oracle.com> (raw)
In-Reply-To: <569E4990.1010603@citrix.com>
> >+static void find_hole(ssize_t pages, unsigned long *hole_start,
> >+ unsigned long *hole_end)
> >+{
> >+ struct payload *data, *data2;
> >+
> >+ spin_lock(&payload_list_lock);
> >+ list_for_each_entry ( data, &payload_list, list )
> >+ {
> >+ list_for_each_entry ( data2, &payload_list, list )
> >+ {
> >+ unsigned long start, end;
> >+
> >+ start = (unsigned long)data2->payload_address;
> >+ end = start + data2->payload_pages * PAGE_SIZE;
> >+ if ( *hole_end > start && *hole_start < end )
> >+ {
> >+ *hole_start = end;
> >+ *hole_end = *hole_start + pages * PAGE_SIZE;
> >+ break;
> >+ }
> >+ }
> >+ if ( &data2->list == &payload_list )
> >+ break;
> >+ }
> >+ spin_unlock(&payload_list_lock);
> >+}
>
> This function above should go down into the CONFIG_X86 section below.
Odd. I have it in my tree. Ah right I - I had the patch not committed in. <sigh>
.. snip..
> >+int xsplice_elf_resolve_symbols(struct xsplice_elf *elf)
.. snip..
> >+int xsplice_elf_perform_relocs(struct xsplice_elf *elf)
.. snip..
>
> Is there a reason the above two functions weren't put in the previous patch?
Historical. I will move them there. Thanks!
>
> >diff --git a/xen/include/asm-arm/config.h b/xen/include/asm-arm/config.h
> >index bd832df..4ea66bf 100644
> >--- a/xen/include/asm-arm/config.h
> >+++ b/xen/include/asm-arm/config.h
> >@@ -15,8 +15,10 @@
> >
> > #if defined(CONFIG_ARM_64)
> > # define LONG_BYTEORDER 3
> >+# define ELFSIZE 64
> > #else
> > # define LONG_BYTEORDER 2
> >+# define ELFSIZE 32
> > #endif
>
> What does this do?
Make Elf_Note and all the ELf_* macros actually work.
>
> (And perhaps it should also be in the previous patch since it's mentioned in
> the previous patch's changelog?)
I kind of lost where it was added.
I could spin it out as a seperate patch - or make it part of the previous
patch? Thoughts?
>
> --
> Ross Lagerwall
next prev parent reply other threads:[~2016-01-19 16:59 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 21:46 [PATCH v2] xSplice v1 implementation Konrad Rzeszutek Wilk
2016-01-14 21:46 ` [PATCH v2 01/13] xsplice: Design document (v5) Konrad Rzeszutek Wilk
2016-01-19 11:14 ` Wei Liu
2016-01-19 14:31 ` Ross Lagerwall
2016-02-05 18:27 ` Konrad Rzeszutek Wilk
2016-02-05 18:34 ` Konrad Rzeszutek Wilk
2016-02-05 15:25 ` Jan Beulich
2016-02-05 21:47 ` Konrad Rzeszutek Wilk
2016-02-09 8:25 ` Jan Beulich
2016-01-14 21:47 ` [PATCH v2 02/13] hypervisor/arm/keyhandler: Declare struct cpu_user_regs; Konrad Rzeszutek Wilk
2016-01-14 21:47 ` [PATCH v2 03/13] xen/xsplice: Hypervisor implementation of XEN_XSPLICE_op (v7) Konrad Rzeszutek Wilk
2016-01-19 14:30 ` Ross Lagerwall
2016-02-06 22:35 ` Doug Goldstein
2016-02-09 8:28 ` Jan Beulich
2016-02-09 14:39 ` Konrad Rzeszutek Wilk
2016-01-14 21:47 ` [PATCH v2 04/13] libxc: Implementation of XEN_XSPLICE_op in libxc (v4) Konrad Rzeszutek Wilk
2016-01-19 11:14 ` Wei Liu
2016-01-14 21:47 ` [PATCH v2 05/13] xen-xsplice: Tool to manipulate xsplice payloads (v3) Konrad Rzeszutek Wilk
2016-01-19 11:14 ` Wei Liu
2016-01-19 14:30 ` Ross Lagerwall
2016-01-14 21:47 ` [PATCH v2 06/13] elf: Add relocation types to elfstructs.h Konrad Rzeszutek Wilk
2016-01-14 21:47 ` [PATCH v2 07/13] xsplice: Add helper elf routines (v2) Konrad Rzeszutek Wilk
2016-01-19 14:33 ` Ross Lagerwall
2016-02-05 18:38 ` Konrad Rzeszutek Wilk
2016-02-05 20:34 ` Konrad Rzeszutek Wilk
2016-01-14 21:47 ` [PATCH v2 08/13] xsplice: Implement payload loading (v2) Konrad Rzeszutek Wilk
2016-01-19 14:34 ` Ross Lagerwall
2016-01-19 16:59 ` Konrad Rzeszutek Wilk [this message]
2016-01-25 11:21 ` Ross Lagerwall
2016-01-19 16:45 ` Ross Lagerwall
2016-01-14 21:47 ` [PATCH v2 09/13] xsplice: Implement support for applying/reverting/replacing patches. (v2) Konrad Rzeszutek Wilk
2016-01-19 14:39 ` Ross Lagerwall
2016-01-19 16:55 ` Konrad Rzeszutek Wilk
2016-01-25 11:43 ` Ross Lagerwall
2016-02-05 19:30 ` Konrad Rzeszutek Wilk
2016-01-14 21:47 ` [PATCH v2 10/13] xen_hello_world.xsplice: Test payload for patching 'xen_extra_version' Konrad Rzeszutek Wilk
2016-01-19 11:14 ` Wei Liu
2016-01-19 14:57 ` Ross Lagerwall
2016-01-19 16:47 ` Ross Lagerwall
2016-01-14 21:47 ` [PATCH v2 11/13] xsplice: Add support for bug frames. (v2) Konrad Rzeszutek Wilk
2016-01-19 14:42 ` Ross Lagerwall
2016-01-14 21:47 ` [PATCH v2 12/13] xsplice: Add support for exception tables. (v2) Konrad Rzeszutek Wilk
2016-01-14 21:47 ` [PATCH v2 13/13] xsplice: Add support for alternatives Konrad Rzeszutek Wilk
2016-01-15 16:58 ` [PATCH v2] xSplice v1 implementation Konrad Rzeszutek Wilk
2016-01-25 11:57 ` Ross Lagerwall
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=20160119165911.GE17737@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=mpohlack@amazon.com \
--cc=ross.lagerwall@citrix.com \
--cc=sasha.levin@oracle.com \
--cc=stefano.stabellini@citrix.com \
--cc=wei.liu2@citrix.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).