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 10:58:04 +0100 [thread overview]
Message-ID: <C2A00A3C.11047%keir@xensource.com> (raw)
In-Reply-To: <467A66B3.76E4.0078.0@novell.com>
On 21/6/07 10:53, "Jan Beulich" <jbeulich@novell.com> wrote:
>> (1) and (2): I want to kill off use of vcpu_guest_context in dom0 tools,
>> make hvm save/restore a generic state load/save interface, and define
>> extensible structures at that interface (pass a stream of state chunks back
>> and forth at the interface, each chunk having a size in its header, and so
>> increasing the size of a chunk allows it to be naturally appended to and
>> hence extended).
>
> I wasn't concerned about the tools interface. The real compatibility problem
> is VCPUOP_initialize.
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?
-- Keir
next prev parent reply other threads:[~2007-06-21 9:58 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 [this message]
2007-06-21 10:16 ` Jan Beulich
2007-06-21 10:37 ` 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=C2A00A3C.11047%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.