From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Cc: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Qemu and (Pacifica | Vanderpool)
Date: Sun, 06 Nov 2005 19:01:59 -0600 [thread overview]
Message-ID: <436EA787.5040503@us.ibm.com> (raw)
In-Reply-To: <200511061616.25284.mark.williamson@cl.cam.ac.uk>
Mark Williamson wrote:
>>qemu is an emulator, not a virtualizer, so these extensions don't really
>>help.
>>
>>
>
>They could be leveraged by kqemu one day...
>
>/me thinks we'll see a rash of Linux kernel "hypervisor modules" when VTX /
>SVM hardware is available.
>
>
Indeed. I've already started my own ;-) My initial guess is that the
kqemu/qvm86 model would work quite well extended for VT/SVM.
That is, a kernel driver that provides a memory area that can be
read-from/written-to in userspace, and then an ioctl interface that
blocks while running code and returns when a sensitive instruction is
hit. It probably makes sense to handle most of the stuff in kernel
space (shadow paging and such) and just return to userspace for IO
operations.
Regards,
Anthony Liguori
>Cheers,
>Mark
>
>
>
>>You may want to look at Xen (www.xensource.com), which already supports
>>these.
>>
>>Paul
>>
>>
>>_______________________________________________
>>Qemu-devel mailing list
>>Qemu-devel@nongnu.org
>>http://lists.nongnu.org/mailman/listinfo/qemu-devel
>>
>>
>
>
>_______________________________________________
>Qemu-devel mailing list
>Qemu-devel@nongnu.org
>http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
>
>
next prev parent reply other threads:[~2005-11-07 1:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-06 15:19 [Qemu-devel] Qemu and (Pacifica | Vanderpool) Dave Feustel
2005-11-06 15:32 ` Hetz Ben Hamo
2005-11-06 15:33 ` Paul Brook
2005-11-06 16:16 ` Mark Williamson
2005-11-07 1:01 ` Anthony Liguori [this message]
2005-11-06 16:36 ` Dave Feustel
2005-11-07 0:57 ` Anthony Liguori
2005-11-07 5:56 ` Jim C. Brown
2005-11-07 6:30 ` Anthony Liguori
2005-11-06 16:24 ` Jim C. Brown
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=436EA787.5040503@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
/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.