From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Christian Ehrhardt
<ehrhardt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: "kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH 2/3] Architecture independence layer - v0 - basic mechanism
Date: Wed, 22 Aug 2007 13:14:38 +0300 [thread overview]
Message-ID: <46CC0C8E.8050803@qumranet.com> (raw)
In-Reply-To: <46CBFE06.7030608-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Christian Ehrhardt wrote:
> [Patch 2/3]
> This introduces the Kconfig & Makefile changes as well as creating the
> still empty body of kvm_x86.*
>
> Related part from the 0/3 mail:
> - Since architecture will not change at runtime I do not use a
> arch_ops structure
> - Instead I used a hidden Kconfig value specifying the kvm
> architecture which then
> influence the make file to link together the generic and the arch
> specific part
> to one kvm module
> - I split the code into kvm_main.c (generic) and kvm_x86.h/kvm_x86.c
> (arch portion)
> @@ -27,18 +27,40 @@ config KVM
>
> If unsure, say N.
>
> +config KVM_X86
> + bool
> +
>
As previously mentioned, X86 (and X86_64, X86_32) already cover this.
--
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/
prev parent reply other threads:[~2007-08-22 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 9:12 [PATCH 2/3] Architecture independence layer - v0 - basic mechanism Christian Ehrhardt
[not found] ` <46CBFE06.7030608-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2007-08-22 10:14 ` Avi Kivity [this message]
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=46CC0C8E.8050803@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=ehrhardt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox