public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Carsten Otte <cotte-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
Cc: "kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
	<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: RFC/patch: a very trivial patch towards portability
Date: Tue, 09 Oct 2007 18:17:14 +0200	[thread overview]
Message-ID: <470BA98A.8090900@qumranet.com> (raw)
In-Reply-To: <1191946167.7292.3.camel-WIxn4w2hgUz3YA32ykw5MLlKpX0K8NHHQQ4Iyu8u01E@public.gmane.org>

Carsten Otte wrote:
> We've seen various big patches regarding portability from Christian and
> Xianto, but none was merged to date. Maintaining a large patch set on
> top of a quickly moving code base is painful.
> I thought it might be cool to try to throw trivial patches at Avi that
> obviously don't break things and push towards portability. In case this
> succeeds I'll keep throwing in trivial patches until we've split
> everything proper.
> This patch splits kvm_dev_ioctl into architecture independent and
> architecture dependent ioctls. Those that are arch independent remain in
> kvm_main.c, others are implemented by kvm_arch_dev_ioctl() in kvm_x86.c.
> A header file named kvm_arch.h is being introduced that contains
> prototypes for funtions in kvm_x86.c.
>
> Comments? Is this a preferable approach? What needs to be done
> different?
>
>   

Small, reviewable, posted patches are definitely the best way forward.

> -	case KVM_CHECK_EXTENSION: {
> -		int ext = (long)argp;
> -
> -		switch (ext) {
> -		case KVM_CAP_IRQCHIP:
> -		case KVM_CAP_HLT:
> -		case KVM_CAP_MMU_SHADOW_CACHE_CONTROL:
> -			r = 1;
> -			break;
> -		default:
> -			r = 0;
> -			break;
> -		}
> -		break;
> -	}
>   

CHECK_EXTENSION is hopefully a generic mechanism (even if the some of 
the actual extensions are not).  So there should be a switch in common 
code for the common extensions, and the default: target should call 
kvm_arch_check_extension() for further processing.

> -	case KVM_GET_VCPU_MMAP_SIZE:
> -		r = -EINVAL;
> -		if (arg)
> -			goto out;
> -		r = 2 * PAGE_SIZE;
> -		break;
>   

I would think this is generic too?  Isn't s390 interested in passing 
information to userspace via a mmap()ed region?

Note that mmio data is passed via that region.


>  
> Index: kvm/drivers/kvm/kvm_x86.c
> ===================================================================
> --- /dev/null	1970-01-01 00:00:00.000000000 +0000
> +++ kvm/drivers/kvm/kvm_x86.c	2007-10-09 16:47:55.000000000 +0200
>   

x86.c


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

  parent reply	other threads:[~2007-10-09 16:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-09 16:09 RFC/patch: a very trivial patch towards portability Carsten Otte
     [not found] ` <1191946167.7292.3.camel-WIxn4w2hgUz3YA32ykw5MLlKpX0K8NHHQQ4Iyu8u01E@public.gmane.org>
2007-10-09 16:17   ` Avi Kivity [this message]
     [not found]     ` <470BA98A.8090900-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-10  8:28       ` Carsten Otte
2007-10-09 16:28   ` Avi Kivity
     [not found]     ` <470BAC2B.40201-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-10  8:30       ` Carsten Otte
2007-10-10 12:37   ` RFC/patch: a very trivial patch towards portability V2 Carsten Otte
     [not found]     ` <1192019827.17745.9.camel-WIxn4w2hgUz3YA32ykw5MLlKpX0K8NHHQQ4Iyu8u01E@public.gmane.org>
2007-10-10 12:45       ` RFC/patch: a very trivial patch towards portability V2.1 Carsten Otte
     [not found]         ` <1192020355.17877.4.camel-WIxn4w2hgUz3YA32ykw5MLlKpX0K8NHHQQ4Iyu8u01E@public.gmane.org>
2007-10-10 13:21           ` Avi Kivity
     [not found]             ` <470CD1F7.1030400-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-10 13:59               ` Carsten Otte
2007-10-10 15:16           ` RFC/patch: a very trivial patch towards portability V3 Carsten Otte
     [not found]             ` <1192029379.18392.7.camel-WIxn4w2hgUz3YA32ykw5MLlKpX0K8NHHQQ4Iyu8u01E@public.gmane.org>
2007-10-11  9:15               ` Christian Ehrhardt
2007-10-11 11:09               ` Avi Kivity
     [not found]                 ` <470E046C.2030404-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-11 11:36                   ` 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=470BA98A.8090900@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=cotte-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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