All of lore.kernel.org
 help / color / mirror / Atom feed
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: [2/6][PATCH]  kvm: Moving memslot_id to x86.h
Date: Thu, 13 Dec 2007 16:49:50 +0200	[thread overview]
Message-ID: <4761468E.6070709@qumranet.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDCAD006D-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>

Zhang, Xiantao wrote:
> Avi Kivity wrote:
>   
>> Zhang, Xiantao wrote:
>>     
>>> From: Zhang Xiantao <xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
>>> Date: Tue, 11 Dec 2007 20:45:48 +0800
>>> Subject: [PATCH] kvm: Moving memslot_id to x86.h
>>>
>>> Since it is not called in kvm_main.c, and it also will block
>>> kvm structure split, so moved it out.
>>>
>>>       
>> memslot_id() is not x86 specific.  Why are you moving it?
>>     
>
> Maybe we can move it to kvm_main.c. If it is inline style in kvm.h, it
> will meet compile issue, since it needs to know kvm strucure. :)
>   

I see.  What we want is to #include "x86.h" at the beginning of kvm.h.

That means we need to switch to

    struct kvm {
         struct kvm_arch arch;
         ...
    };

(and similarly for struct kvm_vcpu) sooner rather than later.  Otherwise 
we will spiral into never-ending #include problems.

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


-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

      parent reply	other threads:[~2007-12-13 14:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11 13:30 [2/6][PATCH] kvm: Moving memslot_id to x86.h Zhang, Xiantao
     [not found] ` <42DFA526FC41B1429CE7279EF83C6BDCACF90C-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-12-13 14:27   ` Avi Kivity
     [not found]     ` <47614161.80402-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-13 14:40       ` Zhang, Xiantao
     [not found]         ` <42DFA526FC41B1429CE7279EF83C6BDCAD006D-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-12-13 14:49           ` 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=4761468E.6070709@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 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.