All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Paul A. Karger" <karger-aZOuKsOsJu3MbYB6QlFGEg@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ports of KVM to non x86 processors
Date: Thu, 26 Jul 2007 19:26:31 +0300	[thread overview]
Message-ID: <46A8CB37.8010905@qumranet.com> (raw)
In-Reply-To: <46A8C2F7.4000301-aZOuKsOsJu3MbYB6QlFGEg@public.gmane.org>

Paul A. Karger wrote:
> The wikipedia page on KVM says that ports are underway to other 
> non-x86 processors.  However, I can't find any mention of this on the 
> KVM wiki.
> Do such ports exist, and if so, where can I find out about them? 
> Please respond directly, as I do not subscribe to the mailing list.

The ports are currently being developed in top secret underground 
bunkers of certain large companies. 66.7% are being developed by a 
certain 3-letter company you may be familiar with.  The other 33.3% were 
undertaken by a large microprocessor vendor.

The ports will be outed on the kvm forum, you can glean some information 
from the agenda here: http://www.qumranet.com/agenda.php

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

  parent reply	other threads:[~2007-07-26 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26 15:51 ports of KVM to non x86 processors Paul A. Karger
     [not found] ` <46A8C2F7.4000301-aZOuKsOsJu3MbYB6QlFGEg@public.gmane.org>
2007-07-26 16:26   ` Avi Kivity [this message]
2007-07-26 19:18 ` Hollis Blanchard

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=46A8CB37.8010905@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=karger-aZOuKsOsJu3MbYB6QlFGEg@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.