From: Carsten Otte <cotte-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@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 V2.1
Date: Wed, 10 Oct 2007 15:59:45 +0200 [thread overview]
Message-ID: <470CDAD1.3020102@de.ibm.com> (raw)
In-Reply-To: <470CD1F7.1030400-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Avi Kivity wrote:
> Argument names in prototypes please.
Will do that.
>> 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:
>> - case KVM_CAP_USER_MEMORY:
>> - r = 1;
>> - break;
>> - default:
>> - r = 0;
>> - break;
>> - }
>> + r = kvm_arch_check_extension(ext);
>> break;
>>
>>
>
>
> Reflecting some more, do we want different API availablility for
> different archs? We can make this generic, and ignore arch-specific
> extensions.
>
> But on the other hand, things like KVM_CAP_IRQCHIP _are_ applicable to
> powerpc, but may not be implemented from day 1... should we do
>
> case KVM_CAP_IRQCHIP:
> return KVM_ARCH_HAS_IRQCHIP;
>
> ?
Will do that too.
-------------------------------------------------------------------------
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-10 13:59 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 [this message]
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=470CDAD1.3020102@de.ibm.com \
--to=cotte-ta70fqpds9bqt0dzr+alfa@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=carsteno-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