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 3/3] Architecture independence layer - v0 - split generic/x86
Date: Wed, 22 Aug 2007 13:22:17 +0300 [thread overview]
Message-ID: <46CC0E59.8030208@qumranet.com> (raw)
In-Reply-To: <46CBFE0B.2070102-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Christian Ehrhardt wrote:
> [Patch 3/3]
> This patch moves the arch specific x86 code from kvm_main.c to
> kvm_x86.c and fills the kvm_arch.h
> header defining the current interface.
>
> Related part from the 0/3 mail:
> - A new header kvm_arch.h specifies the interface the architecture has
> to implement
> - The ioctl interfaces are implemented by the generic kvm_main.c in
> three ways
> a) a completely generic function is covered by kvm_main.c completely
> b) a completely arch dependent function is not covered in kvm_main.c -
> at the end
> each ioctl goes to a architecture mapping doing the rest of the
> ioctl not handled
> in the generic part e.g. in kvm_vcpu_ioctl:
> default:
> r = kvm_arch_vcpu_ioctl(filp, ioctl, arg);
> }
> c) functions that have a significant amount of shared code are
> implemented by
> kvm_main.c using kvm_arch_* to implement the arch specific part.
> Either by just
> mapping the old *_ioctl_whatever to *_arch_whatever or by moving
> some more of the
> code out of the arch function up to the generic portion e.g.:
> case KVM_RUN:
> r = -EINVAL;
> if (arg)
> goto out;
> r = kvm_arch_vcpu_run(vcpu, vcpu->run);
> break;
The patch is nearly unreadable due to its hugeness (can't be helped, I
know). Can you experiment with the magic git switches that detect code
movement? Maybe that will give a more readable patch. If not I'll just
have to read it all.
The parts I did read seem fine.
--
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:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 9:12 [PATCH 3/3] Architecture independence layer - v0 - split generic/x86 Christian Ehrhardt
[not found] ` <46CBFE0B.2070102-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2007-08-22 10:22 ` 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=46CC0E59.8030208@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