From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Zhang, Xiantao" <xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] Split kvm_vcpu to support new archs.
Date: Thu, 18 Oct 2007 16:22:33 +0200 [thread overview]
Message-ID: <47176C29.1000300@qumranet.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC809A6A-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Zhang, Xiantao wrote:
> Hi Avi,
> According to your and community's suggestions, I changed the kvm_vcpu
> structure to two parts. To avoid the much intrusive into current code,
> one is common part which is defined as a macro, and the other one is
> arch-specific part.
> In addition, I have a suggestion to re-organize the head files, such as
> kvm.h and x86.h. IMO, kvm.h is changed to kvm_comm.h, and only includes
> common code for all archs.Then x86.h will be changed to kvm-x86.h, and
> linked as kvm.h at compile time. So, other archs also defines its
> kvm-xx.h to accommodate its arch-specific structures. What's your ideas
> ?(This idea doesn't include in this patch.)
>
Let's not hurry with file layout, but split off x86 first.
> >From 34cebd3a3fc0afba4df511219912bc3277e2a8c7 Mon Sep 17 00:00:00 2001
> From: Zhang Xiantao <xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> Date: Thu, 18 Oct 2007 12:51:02 +0800
> Subject: [PATCH] First step to split kvm_vcpu. Currently, we just use an
> macro to define the common fields in kvm_vcpu for all archs, and all
> archs need to define its own kvm_vcpu struct.
> Signed-off-by: Zhang Xiantao <xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
>
Patch is good, but your mailer wordwrapped it. Use git-send-email, or
another mailer, or attach.
> +#define KVM_VCPU_COMM \
>
KVM_VCPU_COMMON.
> + struct kvm *kvm; \
> + struct preempt_notifier preempt_notifier;\
> + int vcpu_id;\
> + struct mutex mutex;\
> + int cpu;\
> + struct kvm_run *run;\
> + int guest_mode;\
> + unsigned long requests;\
> + struct kvm_guest_debug guest_debug;\
> + int fpu_active; \
> + int guest_fpu_loaded;\
> + wait_queue_head_t wq;\
> + int sigset_active;\
> + sigset_t sigset;\
> + struct kvm_stat stat;\
> + KVM_VCPU_MMIO
>
>
Put some spaces between ';' and '\'.
>
> -static inline int memslot_id(struct kvm *kvm, struct kvm_memory_slot
> *slot)
> -{
> - return slot - kvm->memslots;
> -}
> -
>
This baby is not x86 specific.
--
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/
next prev parent reply other threads:[~2007-10-18 14:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 7:34 [PATCH] Split kvm_vcpu to support new archs Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC809A6A-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-18 14:22 ` Avi Kivity [this message]
2007-10-18 20:01 ` Hollis Blanchard
2007-10-18 21:04 ` Anthony Liguori
[not found] ` <4717CA4B.7040307-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-10-18 21:14 ` Hollis Blanchard
2007-10-18 21:31 ` Anthony Liguori
[not found] ` <4717D095.40708-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-10-18 21:43 ` [kvm-ppc-devel] " Hollis Blanchard
2007-10-18 22:04 ` Anthony Liguori
[not found] ` <4717D87E.5010000-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-10-19 17:16 ` Hollis Blanchard
2007-10-19 13:34 ` Carsten Otte
2007-10-21 6:40 ` Avi Kivity
[not found] ` <471AF450.9040202-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-22 19:18 ` Hollis Blanchard
2007-10-23 12:14 ` Carsten Otte
[not found] ` <471DE5B2.4030709-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-10-24 11:44 ` Zhang, Xiantao
2007-10-25 2:56 ` Jerone Young
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=47176C29.1000300@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@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