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][0/5] kvm:libkvm : KVM/IA64 libkvmfor ia64
Date: Tue, 04 Dec 2007 12:09:21 +0200 [thread overview]
Message-ID: <47552751.2080601@qumranet.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDCA39CE2-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Zhang, Xiantao wrote:
> Hi, Avi
> These patches enable libkvm built successfully for ia64. This
> is the preparation support for kvm/ia64. It will help us to reduce the
> maintain effor once check-in. I will send the subsequent patches to
> enable ia64 userspace support.
>
> [1/5] Update configure file to make it work for ia64.
> [2/5] Add libkvm-ia64.c for libkvm support on ia64
> [3/5] Add the kvm-ia64.h for ia64 support.
> [4/5] Moving kvm_set/kvm_get_shadow_pages to libkvm-x86.c
> [5/5] Moving the delarations of kvm_set_cr8 and kvm_get_cr8 to
> x86-specific area.
>
Applied all, thanks.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
prev parent reply other threads:[~2007-12-04 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 14:50 [PATCH][0/5] kvm:libkvm : KVM/IA64 libkvmfor ia64 Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDCA39CE2-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-12-04 10:09 ` 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=47552751.2080601@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.