From: Alex Williamson <alex.williamson@hp.com>
To: Tristan Gingold <Tristan.Gingold@bull.net>,
Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, xen-ia64-devel@lists.xensource.com
Subject: Re: PATCH (and RFC): new dom0 hypercall: DOM0_DOMAIN_SETUP
Date: Mon, 19 Jun 2006 08:22:36 -0600 [thread overview]
Message-ID: <1150726956.5331.3.camel@lappy> (raw)
In-Reply-To: <200606151019.24560.Tristan.Gingold@bull.net>
Hi Keir,
Do you have an comments on this new hypercall Tristan is proposing?
We have a patch pending in xen/ia64 that makes use of this new hypercall
as a first step towards domain save/restore. Thanks,
Alex
On Thu, 2006-06-15 at 10:19 +0200, Tristan Gingold wrote:
> Hi,
>
> for IA64, I'd like to create a new dom0 hypercall: DOM0_DOMAIN_SETUP.
>
> The purpose of this hypercall is to do some setup in a new domain: it builds
> the firmware (~ BIOS), and creates the mm structures.
>
> This can't be done a domain creation because memory (and max_mem) is required.
> This can't be completly done in user space and since the code has to be executed
> for dom0 it is already present in the hypervisor.
>
> Previously this was done during vcpusetcontext. But this was almost a kuldge
> and became difficult to manage when I worked on save & restore feature.
>
> I don't know wether or not other architectures might be interested in this hypercall.
> In the later case, we may define an arch-dependant content.
>
> Tristan.
>
>
> # HG changeset patch
> # User gingold@virtu10
> # Node ID 6838c14692df784c96f8fc28416e1c33b0dca74a
> # Parent 67b9f433900069efbbc9b198158ef0639b41e4b6
> Add DOM0_DOMAIN_SETUP hypercall.
>
> Signed-off-by: Tristan Gingold <tristan.gingold@bull.net>
>
> diff -r 67b9f4339000 -r 6838c14692df xen/include/public/dom0_ops.h
> --- a/xen/include/public/dom0_ops.h Thu Jun 15 08:47:00 2006 +0200
> +++ b/xen/include/public/dom0_ops.h Thu Jun 15 08:54:15 2006 +0200
> @@ -513,6 +513,16 @@ struct dom0_hypercall_init {
> };
> typedef struct dom0_hypercall_init dom0_hypercall_init_t;
> DEFINE_XEN_GUEST_HANDLE(dom0_hypercall_init_t);
> +
> +#define DOM0_DOMAIN_SETUP 49
> +#define DOM0_DOMAIN_SETUP_VMX (1 << 0)
> +typedef struct dom0_domain_setup {
> + domid_t domain; /* domain to be affected */
> + unsigned long flags;
> + unsigned long bp; /* mpaddr of boot param area */
> + unsigned long maxmem; /* Highest memory address for MDT. */
> +} dom0_domain_setup_t;
> +DEFINE_XEN_GUEST_HANDLE(dom0_domain_setup_t);
>
> struct dom0_op {
> uint32_t cmd;
> @@ -555,6 +565,7 @@ struct dom0_op {
> struct dom0_irq_permission irq_permission;
> struct dom0_iomem_permission iomem_permission;
> struct dom0_hypercall_init hypercall_init;
> + struct dom0_domain_setup domain_setup;
> uint8_t pad[128];
> } u;
> };
--
Alex Williamson HP Open Source & Linux Org.
next prev parent reply other threads:[~2006-06-19 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 8:19 PATCH (and RFC): new dom0 hypercall: DOM0_DOMAIN_SETUP Tristan Gingold
2006-06-19 14:22 ` Alex Williamson [this message]
2006-06-19 14:35 ` Keir Fraser
2006-06-19 14:43 ` [Xen-devel] " Tristan Gingold
2006-06-19 14:45 ` Keir Fraser
2006-06-19 15:20 ` PATCH: was Re**2: " Tristan Gingold
2006-06-19 15:32 ` 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=1150726956.5331.3.camel@lappy \
--to=alex.williamson@hp.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=Tristan.Gingold@bull.net \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-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.