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][RFC]Split kvm_vcpu to support new archs.
Date: Mon, 15 Oct 2007 11:14:44 +0200 [thread overview]
Message-ID: <47132F84.9070002@qumranet.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC808F90-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Zhang, Xiantao wrote:
>
>>> - u64 ia32_misc_enable_msr;
>>>
>>> struct kvm_mmu mmu;
>>>
>>>
>> mmu
>>
>
> About mmu, i am not sure about this. IA64 only need kvm module to
> allocate and free memory for guests. Most functions related to mmu are
> useless for IA64. If we put them as common, Maybe we have to define some
> blank functions.
>
>
I meant the mmu is x86 specific.
>>>
>> pio is x86 specific
>>
>
> Why see pio as x86 specific? as I know, most archs have port IO access .
>
>
Which ones? ppc and s390 don't, and I think ia64 doesn't either?
--
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-15 9:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 6:07 [Patch][RFC]Split kvm_vcpu to support new archs Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC808C85-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-12 8:37 ` Christian Ehrhardt
[not found] ` <470F3240.7060008-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2007-10-12 8:51 ` Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC808D59-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-12 9:04 ` Carsten Otte
[not found] ` <470F38A6.1030106-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-10-12 10:36 ` Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC808D7D-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-12 10:40 ` Carsten Otte
[not found] ` <470F4F26.3050709-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-10-12 10:42 ` Zhang, Xiantao
2007-10-12 9:00 ` Carsten Otte
[not found] ` <470F37A5.8090104-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-10-12 9:11 ` Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC808D68-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-12 9:17 ` Carsten Otte
[not found] ` <470F3B9A.8040108-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-10-12 9:20 ` Zhang, Xiantao
2007-10-13 7:37 ` Avi Kivity
[not found] ` <471075A4.5030809-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-15 4:22 ` Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC808F90-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-15 9:14 ` Avi Kivity [this message]
[not found] ` <47132F84.9070002-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-16 9:55 ` Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC809429-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-16 10:09 ` Dong, Eddie
2007-10-16 10:21 ` Avi Kivity
[not found] ` <471490A8.5050502-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-16 10:27 ` Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC809434-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-16 10:32 ` Avi Kivity
[not found] ` <4714933E.2050201-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-16 11:31 ` Zhang, Xiantao
2007-10-15 8:32 ` Carsten Otte
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=47132F84.9070002@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.