This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Xen + VT

To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Xen + VT
From: Deepak Manohar <mjdeepak@xxxxxxxxx>
Date: Wed, 9 Mar 2005 18:30:20 -0500
Delivery-date: Wed, 09 Mar 2005 23:31:40 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=rTrB0Zgnvi0f+rS0M2d2BA48n+A2CHV52Ca1+bZxZF5xLGcynmTiaOksK7r9X175rb9goNgXFpeWglrMzOcHTnovNwyAsCpaChCwGrWRm6eoxAwwJstlqGcVAyZw+5dSWlIn5ebUS6n0AvLNFz/R0w6zrL1yCLwQZZyiCeBLJQI=
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Reply-to: Deepak Manohar <mjdeepak@xxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Hi all,

I did see some previous threads regd Xen & VT. But cudnt find detailed answers.

So here is alist of questions:

1. Wht is the device access model with XenVT and unmod Linux .
Obviously it cannot be using the front end back end, becos there is no
front end in unmod Linux. So how exactly is Xen still controlling
access to devices by unmod Linux?

2. System calls: How are system calls within unmod Linux being
serviced now? Since unmod Linux runs in ring 0 - the sys call int can
go directly to unmod Linux itself instead of via Xen. How is it being

3. External interrupts: With multiple domains and with VT how exactly
are external interrupts being demultiplexed to the different domains?

4.  Task switches. How was task switching happening in XenoLinux? Now
VT specifically mentions that Task switches are not allowed in VMX
Non-root mode is there any change in the way Task switches are done.

5. Shadow page tables: How exactly has this changed from the existing
handling of the page tables & directories. I didnt quite understand
the explanation in /docs/misc/VMX_changes.txt


SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>