From: Keir Fraser <keir@xensource.com>
To: Jan Beulich <jbeulich@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: portability issues
Date: Thu, 21 Jun 2007 11:37:58 +0100 [thread overview]
Message-ID: <C2A01396.11054%keir@xensource.com> (raw)
In-Reply-To: <467A6C05.76E4.0078.0@novell.com>
On 21/6/07 11:16, "Jan Beulich" <jbeulich@novell.com> wrote:
>> I don't see the problem. The guest will not be able to initialise secondary
>> VCPU's sysenter/syscall state via this interface. So what?
>
> For (1), the guest will supply a too short guest_context structure, and
> currently Xen has no way of detecting this. I was proposing two possible
> solutions, neither of which seemed ideal to me.
>
> For (2), I am just not certain whether there isn't an alternative not breaking
> the interface for pure 32-bits.
I'm proposing we do not change the guest_context structure at all. Instead
the tools will get at this extra state via a generalised form of the current
hvm save/restore interface. The guest itself will always have to set the
callback via the callback_op hypercall.
-- Keir
prev parent reply other threads:[~2007-06-21 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 8:10 portability issues Jan Beulich
2007-06-21 8:37 ` Keir Fraser
2007-06-21 9:53 ` Jan Beulich
2007-06-21 9:58 ` Keir Fraser
2007-06-21 10:16 ` Jan Beulich
2007-06-21 10:37 ` Keir Fraser [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=C2A01396.11054%keir@xensource.com \
--to=keir@xensource.com \
--cc=jbeulich@novell.com \
--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.