From: Rusty Russell <rusty@rustcorp.com.au>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Chris Wright <chrisw@sous-sol.org>,
virtualization@lists.osdl.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [RFC/PATCH LGUEST X86_64 03/13] lguest64 core
Date: Fri, 09 Mar 2007 15:10:48 +1100 [thread overview]
Message-ID: <1173413448.32234.119.camel@localhost.localdomain> (raw)
In-Reply-To: <1173375527.32170.5.camel@localhost.localdomain>
On Thu, 2007-03-08 at 12:38 -0500, Steven Rostedt wrote:
> +lg-objs := core.o hypervisor.o lguest_user.o hv_vm.o page_tables.o \
> +hypercalls.o io.o interrupts_and_traps.o lguest_debug.o
Right, I missed the trick here: hypervisor.S doesn't require any
relocations, so that fact that it's linked at the wrong address doesn't
matter at all. Excuse me while I prepare a patch 8)
> +extern long end_hyper_text;
> +extern long start_hyper_text;
The standard way of doing this is "extern char end_hyper_text[];"
doesn't matter on x86/x86-64, but on some platforms gcc can make
assumptions about addresses based on the size of the variable (sbss
etc). So nice to use that everywhere for asm constants.
Cheers,
Rusty.
next prev parent reply other threads:[~2007-03-09 4:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070308162348.299676000@redhat.com>
2007-03-08 17:38 ` [RFC/PATCH LGUEST X86_64 01/13] HV VM Fix map area for HV Steven Rostedt
2007-03-09 3:52 ` Rusty Russell
2007-03-08 17:38 ` [RFC/PATCH LGUEST X86_64 02/13] hvvm export page utils Steven Rostedt
2007-03-08 17:38 ` [RFC/PATCH LGUEST X86_64 03/13] lguest64 core Steven Rostedt
2007-03-09 4:10 ` Rusty Russell [this message]
2007-03-08 17:38 ` [RFC/PATCH LGUEST X86_64 04/13] Useful debugging Steven Rostedt
2007-03-08 17:38 ` [RFC/PATCH LGUEST X86_64 05/13] asm-offsets update Steven Rostedt
2007-03-08 17:38 ` [RFC/PATCH LGUEST X86_64 06/13] lguest64 Kconfig Steven Rostedt
2007-03-09 3:55 ` Rusty Russell
2007-03-08 17:39 ` [RFC/PATCH LGUEST X86_64 07/13] lguest64 loader Steven Rostedt
2007-03-08 17:39 ` [RFC/PATCH LGUEST X86_64 08/13] lguest64 user header Steven Rostedt
2007-03-08 17:39 ` [RFC/PATCH LGUEST X86_64 09/13] lguest64 devices Steven Rostedt
2007-03-08 17:39 ` [RFC/PATCH LGUEST X86_64 10/13] dont compile in the lguest_net Steven Rostedt
2007-03-08 17:39 ` [RFC/PATCH LGUEST X86_64 11/13] x86_64 HVC attempt Steven Rostedt
2007-03-08 17:39 ` [RFC/PATCH LGUEST X86_64 12/13] dump stack on crash Steven Rostedt
2007-03-08 17:39 ` [RFC/PATCH LGUEST X86_64 13/13] Hack to get output Steven Rostedt
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=1173413448.32234.119.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=chrisw@sous-sol.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=virtualization@lists.osdl.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