From: Hollis Blanchard <hollis-yUx37fBWTUITNcAmw9vGhQ@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: portability layer?
Date: Mon, 26 Mar 2007 16:20:48 -0500 [thread overview]
Message-ID: <1174944048.29357.11.camel@basalt> (raw)
Hi Avi, I was wondering what you think is the right abstraction layer to
target for porting KVM to non-x86 architectures? To me it looks like
libkvm is the answer.
The kernel/userland interface is heavily x86-specific, including things
like struct kvm_run. So it looks like the higher-level API of
kvm_init(), kvm_create(), etc would be the right cut? struct
kvm_callbacks is even reasonably portable, especially if cpuid is hidden
behind an "arch" callback.
-Hollis
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next reply other threads:[~2007-03-26 21:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 21:20 Hollis Blanchard [this message]
2007-03-27 6:57 ` portability layer? Avi Kivity
[not found] ` <4608C06C.2000708-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-28 14:26 ` Hollis Blanchard
2007-03-28 15:06 ` Arnd Bergmann
2007-03-28 15:48 ` Avi Kivity
[not found] ` <460A8E44.5080305-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-28 18:50 ` Hollis Blanchard
2007-03-29 7:11 ` Avi Kivity
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=1174944048.29357.11.camel@basalt \
--to=hollis-yux37fbwtuitncamw9vghq@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.