* Re: [Xen-changelog] Indirect hypercalls through a hypercall transfer page.
[not found] <E1F1lA0-0001fQ-Mv@xenbits.xensource.com>
@ 2006-02-08 4:57 ` Hollis Blanchard
2006-02-08 8:46 ` Keir Fraser
0 siblings, 1 reply; 3+ messages in thread
From: Hollis Blanchard @ 2006-02-08 4:57 UTC (permalink / raw)
To: xen-devel
On Wed, 2006-01-25 at 13:58 +0000, Xen patchbot -unstable wrote:
> # HG changeset patch
> # User kaf24@firebug.cl.cam.ac.uk
> # Node ID 71914b64b5770285cf095c1906e346b814f4878b
> # Parent 246b6444c6432193ea98c9f01de58e6740bde09c
> Indirect hypercalls through a hypercall transfer page.
Sorry, I may have missed some conversation about this...
What is this patch about? I mean I can see how it works, but what is the
motivation for it?
--
Hollis Blanchard
IBM Linux Technology Center
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [Xen-changelog] Indirect hypercalls through a hypercall transfer page.
2006-02-08 4:57 ` [Xen-changelog] Indirect hypercalls through a hypercall transfer page Hollis Blanchard
@ 2006-02-08 8:46 ` Keir Fraser
2006-02-08 15:37 ` Anthony Liguori
0 siblings, 1 reply; 3+ messages in thread
From: Keir Fraser @ 2006-02-08 8:46 UTC (permalink / raw)
To: Hollis Blanchard; +Cc: xen-devel
On 8 Feb 2006, at 04:57, Hollis Blanchard wrote:
>> Indirect hypercalls through a hypercall transfer page.
>
> Sorry, I may have missed some conversation about this...
>
> What is this patch about? I mean I can see how it works, but what is
> the
> motivation for it?
Allows a different hypercall implementation on platforms where that
makes sense. For example, we would like to run XenLinux on native by
running it over a small 'Xen shim' that provides the Xen API but no
protection or multiplexing. In that case it would be most efficient to
turn syscall instructions into jumps.
-- Keir
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Re: [Xen-changelog] Indirect hypercalls through a hypercall transfer page.
2006-02-08 8:46 ` Keir Fraser
@ 2006-02-08 15:37 ` Anthony Liguori
0 siblings, 0 replies; 3+ messages in thread
From: Anthony Liguori @ 2006-02-08 15:37 UTC (permalink / raw)
To: Keir Fraser; +Cc: Gerrit Huizenga, xen-devel, Hollis Blanchard
Keir Fraser wrote:
> Allows a different hypercall implementation on platforms where that
> makes sense. For example, we would like to run XenLinux on native by
> running it over a small 'Xen shim' that provides the Xen API but no
> protection or multiplexing. In that case it would be most efficient to
> turn syscall instructions into jumps.
Is someone working on this?
I had been thinking of something like this myself. A pretty
straight-forward kernel module that could allow you to run XenLinux on
native (so we could have our own "player").
Regards,
Anthony Liguori
> -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-02-08 15:37 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <E1F1lA0-0001fQ-Mv@xenbits.xensource.com>
2006-02-08 4:57 ` [Xen-changelog] Indirect hypercalls through a hypercall transfer page Hollis Blanchard
2006-02-08 8:46 ` Keir Fraser
2006-02-08 15:37 ` Anthony Liguori
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.