From: Avi Kivity <avi@qumranet•com>
To: Hollis Blanchard <hollisb@us•ibm.com>
Cc: kvm-ppc-devel@lists•sourceforge.net, linuxppc-dev@ozlabs•org,
kvm-devel@lists•sourceforge.net
Subject: Re: [PATCH 4 of 4] [KVM POWERPC] PowerPC 440 KVM implementation
Date: Thu, 17 Apr 2008 14:14:37 +0300 [thread overview]
Message-ID: <4807311D.3020402@qumranet.com> (raw)
In-Reply-To: <442f314cd08ea6addd39.1208406489@localhost.localdomain>
Hollis Blanchard wrote:
> +config KVM
> + tristate "Kernel-based Virtual Machine (KVM) support"
> + depends on EXPERIMENTAL
> + select PREEMPT_NOTIFIERS
> + select ANON_INODES
> + ---help---
> + Support hosting virtualized guest machines. You will also
> + need to select one or more of the processor modules below.
> +
> + This module provides access to the hardware capabilities through
> + a character device node named /dev/kvm.
> +
> + To compile this as a module, choose M here: the module
> + will be called kvm.
> +
> + If unsure, say N.
>
In my ignorance, I set KVM=m on a non-44x build, which then failed. This
needs either to depend on 44x, or to be fixed to compile.
> +
> +config KVM_BOOKE_HOST
> + tristate "KVM host support for Book E PowerPC processors"
> + depends on KVM && 44x
> + ---help---
> + Provides host support for KVM on Book E PowerPC processors. Currently
> + this works on 440 processors only.
> +
>
--
error compiling committee.c: too many arguments to function
next parent reply other threads:[~2008-04-17 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <442f314cd08ea6addd39.1208406489@localhost.localdomain>
2008-04-17 11:14 ` Avi Kivity [this message]
2008-04-17 11:19 ` [PATCH 4 of 4] [KVM POWERPC] PowerPC 440 KVM implementation Avi Kivity
2008-04-17 14:00 ` [kvm-devel] " Christian Ehrhardt
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=4807311D.3020402@qumranet.com \
--to=avi@qumranet$(echo .)com \
--cc=hollisb@us$(echo .)ibm.com \
--cc=kvm-devel@lists$(echo .)sourceforge.net \
--cc=kvm-ppc-devel@lists$(echo .)sourceforge.net \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox