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,
virtualization
<virtualization-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: [RFC] KVM Source layout Proposal to accommodate new CPU architecture
Date: Sun, 30 Sep 2007 12:52:38 +0200 [thread overview]
Message-ID: <46FF7FF6.6090103@qumranet.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC754076-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Zhang, Xiantao wrote:
> Zhang, Xiantao wrote:
>
>>> Hi Avi,
>>> So you mean IA64 can adopt the similar method as well?
>>>
>
>
>> What method do you mean exactly?
>>
> Put all arch-specific files into arch/ia64/kvm as you described in
> future KVM infrastructure.
>
>> The powerpc people had some patches to make kvm_main arch independent.
>> We should work on that base.
>> To avoid a dependency on the x86 merge, we can start by working withing
>> drivers/kvm/, for example creating drivers/kvm/x86.c and
>> drivers/kvm/ia64.c. Later patches can move these to arch/*/.
>>
> It may work on x86 side. But for IA64, we have several source files and
> assembly files to implement a VMM module, which contains the
> virtualization logic of CPU, MMU and other platform devices. (In KVM
> forum, Anthony had presented IA64/KVM architecture which is a bit
> different with x86 side due to different approaches for VT.).If we put
> all such these arch-specific files in one directory, it looks very
> strange!
>
ia64/ subdirectory is also fine.
--
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-09-30 10:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 8:33 [RFC] KVM Source layout Proposal to accommodate new CPU architecture Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC753A4E-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-09-26 8:44 ` Laurent Vivier
[not found] ` <46FA1BDA.2060003-6ktuUTfB/bM@public.gmane.org>
2007-09-26 9:38 ` Zhang, Xiantao
2007-09-27 9:18 ` Avi Kivity
[not found] ` <46FB7566.9030504-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-28 2:16 ` Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC753E73-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-09-28 14:45 ` Avi Kivity
[not found] ` <46FD1392.1080905-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-28 15:28 ` Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC754031-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-09-28 17:03 ` Avi Kivity
[not found] ` <46FD33F2.9090506-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-29 1:47 ` Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC754076-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-09-30 10:52 ` Avi Kivity [this message]
[not found] ` <46FF7FF6.6090103-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-30 13:53 ` Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC75421C-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-09-30 13:56 ` Avi Kivity
2007-10-02 1:19 ` Hollis Blanchard
2007-10-02 4:11 ` Rusty Russell
[not found] ` <1191298279.6979.50.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-10-02 6:01 ` Hollis Blanchard
2007-10-02 6:29 ` Rusty Russell
[not found] ` <1191306576.6979.91.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-10-02 11:43 ` Carsten Otte
[not found] ` <46FFAB00.4050103-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-30 15:01 ` Zhang, Xiantao
2007-10-08 2:36 ` Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC7AE225-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-08 4:04 ` Hollis Blanchard
2007-10-08 4:16 ` [RFC] KVM Source layout Proposal to accommodate newCPU architecture Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC7AE2A8-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-08 9:57 ` Avi Kivity
[not found] ` <4709FEF1.6010006-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-09 1:10 ` Zhang, Xiantao
2007-09-28 8:20 ` [RFC] KVM Source layout Proposal to accommodate new CPU architecture Carsten Otte
[not found] ` <46FCB954.50005-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-09-30 2:26 ` Zhang, Xiantao
2007-09-29 13:06 ` Rusty Russell
[not found] ` <1191071211.26950.28.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-09-29 14:25 ` Sam Ravnborg
2007-09-30 2:26 ` [RFC] KVM Source layout Proposal to accommodatenew " Zhang, Xiantao
[not found] <FD80ED6F62DC5E41910477505FA01BDFA62D00@pdsmsx415.ccr.corp.intel.com>
[not found] ` <FD80ED6F62DC5E41910477505FA01BDFA62D00-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-09-26 8:58 ` [RFC] KVM Source layout Proposal to accommodate new " Zhang, Xiantao
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=46FF7FF6.6090103@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=virtualization-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@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