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 V3
Date: Thu, 11 Oct 2007 13:09:32 +0200 [thread overview]
Message-ID: <470E046C.2030404@qumranet.com> (raw)
In-Reply-To: <1192029379.18392.7.camel-WIxn4w2hgUz3YA32ykw5MLlKpX0K8NHHQQ4Iyu8u01E@public.gmane.org>
Carsten Otte wrote:
> Thanks to Avi's continued review, we've got even more common code this
> time: KVM_CHECK_EXTENSION ioctl is now completely handled in kvm_main.c
> instead of having arch callbacks to check extensions. The architectures
> are expected to setup a bit mask named KVM_ARCH_EXTENSIONS with
> information about capabilities they support. Possible valus for the bit
> masks are defined in drivers/kvm/kvm.h (KVM_ARCH_HAS_*), which rely on
> KVM_CAP_* definitions in include/linux/kvm.h.
> Function prototypes in drivers/kvm/kvm.h have been fixed: they have
> argument names now.
>
>
The new capability bitmap moves the patch out of the "very trivial"
realm. I removed those hunks and applied.
Send more, the approach is clearly right. Leave things which require
changes (like the capability bitmap) to the end, there's more than
enough stuff for now.
--
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-11 11:09 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
[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 [this message]
[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=470E046C.2030404@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