From: "Jan Beulich" <jbeulich@novell.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: [PATCH 6/7, RFC] x86_64: basic changes for supporting compatibility mode guest
Date: Wed, 23 Aug 2006 12:17:02 +0200 [thread overview]
Message-ID: <44EC473E.76E4.0078.0@novell.com> (raw)
In-Reply-To: <C111E116.143E%Keir.Fraser@cl.cam.ac.uk>
>>> Keir Fraser <Keir.Fraser@cl.cam.ac.uk> 23.08.06 11:40 >>>
>On 23/8/06 10:16 am, "Jan Beulich" <jbeulich@novell.com> wrote:
>
>> This changes the ABI in adding to vcpu_guest_context - does a change like
>> this require bumping the ABI version?
>
>We can't do this as the struct is part of the domU ABI (used for
>initialising secondary VCPUs). You'll have to add the extra CS values to
>64-bit arch_vcpu, I think.
Then libxc/xc_linux_build.c (after appropriate adjustment) wouldn't have
a way to communicate these for a new domain. If extending the structure
isn't possible at all, then we'll either have to make event_callback_eip and
failsafe_callback_eip unions (permitting a selector:offset pair) or make
syscall_callback_eip a union (permitting storing the selectors). I'd favor
the second option as that field is entirely useless as long as x86_32
doesn't support syscall (which doesn't make sense as it would make
things slower rather than speeding them up) - that way one doesn't have
to be careful to not access the other two full 64bit *_callback_eip
fields.
Jan
next prev parent reply other threads:[~2006-08-23 10:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 9:16 [PATCH 6/7, RFC] x86_64: basic changes for supporting compatibility mode guest Jan Beulich
2006-08-23 9:40 ` Keir Fraser
2006-08-23 10:17 ` Jan Beulich [this message]
2006-08-23 10:36 ` Keir Fraser
2006-08-23 11:10 ` Jan Beulich
2006-08-23 11:44 ` Gerd Hoffmann
2006-08-23 10:32 ` Jan Beulich
2006-08-23 10:33 ` Keir Fraser
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=44EC473E.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/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.