public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: carsteno-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	carsteno-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org,
	"Zhang,
	 Xiantao" <xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH][Resend] Split kvm_vcpu to support new archs.
Date: Sun, 14 Oct 2007 08:07:25 +0200	[thread overview]
Message-ID: <4711B21D.3080302@qumranet.com> (raw)
In-Reply-To: <47107DF1.4020403-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>

Carsten Otte wrote:
> Avi Kivity wrote:
>   
>> Using previous terminology, mmio is s390 special.  Everyone else does
>> have them.  We can #ifndef them on s390, but we won't duplicate mmio on
>> all other archs.
>>     
> No need to duplicate the code for all other archs: we should think 
> about a functional split here, like having an mmio.c which can be 
> linked in case the architecture has mmio. We have CONFIG_MMIO in the 
> kernel to distinguish that, and CONFIG_PCI and such. This seems way 
> prefereable to me over a bunch of #ifdef CONFIG_ARCH_WHATEVER.
> Any reason why we should do this different on kvm then in the rest of 
> the kernel?
>   

CONFIG_MMIO works too.  I'm not sure mmio.c is warranted, though. 
Modularity can be carried too far.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
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/

      parent reply	other threads:[~2007-10-14  6:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-12 10:39 [PATCH][Resend] Split kvm_vcpu to support new archs Zhang, Xiantao
     [not found] ` <42DFA526FC41B1429CE7279EF83C6BDC808D7E-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-12 14:09   ` Carsten Otte
     [not found]     ` <470F8025.6060001-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-10-13  4:20       ` Zhang, Xiantao
     [not found]         ` <42DFA526FC41B1429CE7279EF83C6BDC808DBC-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-13  7:48           ` Carsten Otte
2007-10-13  7:59       ` Avi Kivity
     [not found]         ` <47107ADA.90204-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-13  8:12           ` Carsten Otte
     [not found]             ` <47107DF1.4020403-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-10-14  6:07               ` 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=4711B21D.3080302@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=carsteno-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    --cc=carsteno-tA70FqPdS9bQT0dZR+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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox