From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hollis Blanchard Subject: portability layer? Date: Mon, 26 Mar 2007 16:20:48 -0500 Message-ID: <1174944048.29357.11.camel@basalt> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Avi Kivity Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org 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