From: Deepak Manohar <mjdeepak@gmail.com>
To: xen-devel@lists.sourceforge.net
Subject: Xen + VT
Date: Wed, 9 Mar 2005 18:30:20 -0500 [thread overview]
Message-ID: <fdef3c240503091530408c2f80@mail.gmail.com> (raw)
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
done?
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
thanks.
Deepak
-------------------------------------------------------
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.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-03-09 23:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 23:30 Deepak Manohar [this message]
2005-03-12 3:38 ` Xen + VT Mark Williamson
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 22:02 Xen & VT Deepak Manohar
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=fdef3c240503091530408c2f80@mail.gmail.com \
--to=mjdeepak@gmail.com \
--cc=xen-devel@lists.sourceforge.net \
/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.