From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Zhang, Xiantao" <xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: carsteno-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org,
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
carsteno-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org,
Hollis Blanchard
<hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH][RFC] Struct kvm split
Date: Mon, 19 Nov 2007 17:25:55 +0200 [thread overview]
Message-ID: <4741AB03.6090008@qumranet.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC9A0C6A-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Zhang, Xiantao wrote:
> Carsten Otte wrote:
>
>> Zhang, Xiantao wrote:
>>
>>> Based on privious discussion, I made this patch to split struct kvm.
>>> In this patch, strcut kvm only holds common fields, and struct
>>> kvm_x86 will keep x86-specific fields. In this way, struct kvm will
>>> be a sub-filed in struct kvm_x86, and we can use to_kvm_x86 to get
>>> kvm_x86 from struct kvm. It is very similar with current to_vmx
>>> approach for getting struct vmx from struct kvm_vcpu. This is a
>>> rough split based on this idea. Any comments are welcome!
>>>
>> Patch #2 does'nt apply for me, on top of #1 on today's kvm.git:
>> cotte@kvm:~/kvm$ quilt push
>> Wende Patch 0002-Move-strcut-kvm_x86_ops-defintion-to-x86.h.patch an
>> (Stripping trailing CRs from patch.)
>> patching file drivers/kvm/kvm.h
>> (Stripping trailing CRs from patch.)
>> patching file drivers/kvm/x86.h
>> patch: **** malformed patch at line 169: int
>> kvm_mmu_page_fault(struct kvm_vcpu *vcpu, gva_t gva, u32 error_code);
>>
>> Patch 0002-Move-strcut-kvm_x86_ops-defintion-to-x86.h.patch lässt sich
>> nicht anwenden (erzwingen mit -f)
>>
>
> Hi, Carsten
> The first 5 patches have been checked into upstream tree. Maybe you can have a pull. For the sixth one, it can be applied on the latest commits.
> Xiantao
>
They only applied after much massaging by me (I forgot to complain, sorry).
Please use git-send-email, it's much better at getting the patches out
undamaged.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-11-19 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 10:05 [PATCH][RFC] Struct kvm split Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC9A0C2B-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-11-19 14:19 ` Carsten Otte
[not found] ` <47419B7D.2060200-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-11-19 15:20 ` Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC9A0C6A-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-11-19 15:25 ` Avi Kivity [this message]
[not found] ` <4741AB03.6090008-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-19 15:31 ` Zhang, Xiantao
2007-11-19 19:28 ` Hollis Blanchard
2007-11-20 1:33 ` Zhang, Xiantao
2007-11-20 10:04 ` Avi Kivity
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=4741AB03.6090008@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=carsteno-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=carsteno-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org \
--cc=hollisb-r/Jw6+rmf7HQT0dZR+AlfA@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.