xen-devel
[Xen-devel] Re: [RFC, PATCH 4/24] i386 Vmi inline implementation
|
To: |
Zachary Amsden <zach@xxxxxxxxxx> |
|
Subject: |
[Xen-devel] Re: [RFC, PATCH 4/24] i386 Vmi inline implementation |
|
From: |
Pavel Machek <pavel@xxxxxx> |
|
Date: |
2006年3月15日 23:52:12 +0100 |
|
Cc: |
Andrew Morton <akpm@xxxxxxxx>, Joshua LeVasseur <jtl@xxxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Pratap Subrahmanyam <pratap@xxxxxxxxxx>, Wim Coekaerts <wim.coekaerts@xxxxxxxxxx>, Chris Wright <chrisw@xxxxxxxx>, Jack Lo <jlo@xxxxxxxxxx>, Dan Hecht <dhecht@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxxxx>, Christopher Li <chrisl@xxxxxxxxxx>, Virtualization Mailing List <virtualization@xxxxxxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxx>, Anne Holler <anne@xxxxxxxxxx>, Jyothy Reddy <jreddy@xxxxxxxxxx>, Kip Macy <kmacy@xxxxxxxxxxx>, Ky Srinivasan <ksrinivasan@xxxxxxxxxx>, Leendert van Doorn <leendert@xxxxxxxxxxxxxx>, Dan Arai <arai@xxxxxxxxxx> |
|
Delivery-date: |
2006年3月17日 10:38:57 +0000 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<200603131802.k2DI22OK005657@xxxxxxxxxxxxxxxxxxx> |
|
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
|
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
|
List-post: |
<mailto:xen-devel@lists.xensource.com> |
|
List-subscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
|
List-unsubscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
|
References: |
<200603131802.k2DI22OK005657@xxxxxxxxxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Mutt/1.5.9i |
On Po 13-03-06 10:02:02, Zachary Amsden wrote:
> Macros to use VMI calls from assembly and C languages are introduced.
> The macros are quite complex, but the end result is rather impressive.
> The result is that when compiling a VMI kernel, the native code is
> emitted inline, with no function call overhead, and some wiggle room
> for register allocation. The hypervisor compatibility code is emitted
> out of line into a separate section, and patched dynamically during the
> process of preparing the kernel for boot. In the end, this task is
> envisioned as being done by a loader agent outside of the kernel proper,
> allowing for a completely transparent kernel start of day.
We already do runtime patching for SMP vs. UP, could you use same
infrastructure? I do not want VMI-specific grub.
Pavel
--
42: i < SampleTable.Length;
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|