From: Arun Sharma <arun.sharma@intel.com>
To: John Byrne <john.l.byrne@hp.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Status of ioemu code in unstable?
Date: Mon, 18 Jul 2005 15:26:12 -0700 [thread overview]
Message-ID: <42DC2C84.1000403@intel.com> (raw)
In-Reply-To: <mailman.1121724192.5752@unix-os.sc.intel.com>
John Byrne wrote:
>
> Hi,
>
> I've been trying to find out from the xen-devel archives and Google and
> I cannot seem to find the information I'm looking for.
>
> I assume the goal of the ioemu is to provide necessary support for
> non-paravirtualized guess running on VT-x hardware. At a minimum I'd
> guess you'd need BIOS emulation, display card emulation, and timer/
> interrupt emulation.
See foil 10 of:
http://summit.xensource.com/pdfs/Xen_VT_Status_TODO_Intel_ASharma_EtAl.pdf
for a summary of what's working.
Since then, we've added support for BIOS emulation (tools/firmware).
The current device models are based on qemu-0.6.1.
> I'd like to know what's there; what works; and what else might be
> needed. A pointer to the information or a summary would be appreciated.
> Also, there is one item in the todo list in the wiki that suggests that
> the ioemu code will all be re-written. Is this for performance reasons?
Yes, switching to dom0 for every I/O request is very expensive. But that
was the easiest and cleanest initial implementation.
We've also accelerated the PIT by moving it into the hypervisor and have
patches for implementing the local APIC support in xen.
-Arun
next prev parent reply other threads:[~2005-07-18 22:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 22:02 Status of ioemu code in unstable? John Byrne
[not found] ` <mailman.1121724192.5752@unix-os.sc.intel.com>
2005-07-18 22:26 ` Arun Sharma [this message]
2005-07-19 0:13 ` John Byrne
2005-07-19 0:20 ` Arun Sharma
2005-07-19 0:34 ` Anthony Liguori
2005-07-20 19:15 ` John Byrne
2005-07-21 4:36 ` Gerd Knorr
2005-07-21 14:00 ` Anthony Liguori
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=42DC2C84.1000403@intel.com \
--to=arun.sharma@intel.com \
--cc=john.l.byrne@hp.com \
--cc=xen-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.