From: eric.auger@linaro.org (Eric Auger)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 2/5] KVM: introduce kvm_arch_is_virtual_intc_initialized
Date: Mon, 12 Jan 2015 14:39:50 +0100 [thread overview]
Message-ID: <54B3CEA6.2030008@linaro.org> (raw)
In-Reply-To: <20150111211129.GD3868@cbox>
Hi Christoffer,
On 01/11/2015 10:11 PM, Christoffer Dall wrote:
> On Wed, Dec 03, 2014 at 05:07:09PM +0100, Eric Auger wrote:
>> Introduce __KVM_HAVE_ARCH_VIRTUAL_INTC_INITIALIZED define and
>> associated kvm_arch_is_virtual_intc_initialized function. This latter
>> allows to test whether the virtual interrupt controller is initialized
>> and ready to accept virtual IRQ injection. On some architectures,
>> the virtual interrupt controller is dynamically instantiated, justifying
>> that kind of check.
>>
>> Signed-off-by: Eric Auger <eric.auger@linaro.org>
>> ---
>> include/linux/kvm_host.h | 12 ++++++++++++
>> 1 file changed, 12 insertions(+)
>>
>> diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
>> index ea53b04..45fea3c 100644
>> --- a/include/linux/kvm_host.h
>> +++ b/include/linux/kvm_host.h
>> @@ -696,6 +696,18 @@ static inline wait_queue_head_t *kvm_arch_vcpu_wq(struct kvm_vcpu *vcpu)
>> #endif
>> }
>>
>> +#ifndef __KVM_HAVE_ARCH_VIRTUAL_INTC_INITIALIZED
>
> maybe you can drop the _virtual_ from all these names to make it
> slightly shorter.
ok. I chose that name to differentiate from the host irqchip. I will
drop "virtual".
>
> alternatively to this approach you could expose a function from the
> irqfd layer that KVM intc implementations call into to say "I'm
> ready"... Not sure if it would look nicer.
>
>> +/*
>> + * returns trues if the virtual interrupt controller is initialized and
>> + * ready to accept virtual IRQ. On some architectures the virtual interrupt
>> + * controller is dynamically instantiated and this is not always true.
>> + */
>> +static inline bool kvm_arch_is_virtual_intc_initialized(struct kvm *kvm)
>> +{
>> + return true;
>> +}
>
> don't you need to define a prototype if the architecture does define the
> symbol?
yes I will move the declaration here
Thanks
Eric
>
>> +#endif
>> +
>> int kvm_arch_init_vm(struct kvm *kvm, unsigned long type);
>> void kvm_arch_destroy_vm(struct kvm *kvm);
>> void kvm_arch_sync_events(struct kvm *kvm);
>> --
>> 1.9.1
>>
WARNING: multiple messages have this Message-ID (diff)
From: Eric Auger <eric.auger@linaro.org>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: eric.auger@st.com, marc.zyngier@arm.com,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
alex.williamson@redhat.com, agraf@suse.de, joel.schopp@amd.com,
gleb@kernel.org, pbonzini@redhat.com, borntraeger@de.ibm.com,
cornelia.huck@de.ibm.com, linux-kernel@vger.kernel.org,
patches@linaro.org, a.motakis@virtualopensystems.com
Subject: Re: [PATCH v5 2/5] KVM: introduce kvm_arch_is_virtual_intc_initialized
Date: Mon, 12 Jan 2015 14:39:50 +0100 [thread overview]
Message-ID: <54B3CEA6.2030008@linaro.org> (raw)
In-Reply-To: <20150111211129.GD3868@cbox>
Hi Christoffer,
On 01/11/2015 10:11 PM, Christoffer Dall wrote:
> On Wed, Dec 03, 2014 at 05:07:09PM +0100, Eric Auger wrote:
>> Introduce __KVM_HAVE_ARCH_VIRTUAL_INTC_INITIALIZED define and
>> associated kvm_arch_is_virtual_intc_initialized function. This latter
>> allows to test whether the virtual interrupt controller is initialized
>> and ready to accept virtual IRQ injection. On some architectures,
>> the virtual interrupt controller is dynamically instantiated, justifying
>> that kind of check.
>>
>> Signed-off-by: Eric Auger <eric.auger@linaro.org>
>> ---
>> include/linux/kvm_host.h | 12 ++++++++++++
>> 1 file changed, 12 insertions(+)
>>
>> diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
>> index ea53b04..45fea3c 100644
>> --- a/include/linux/kvm_host.h
>> +++ b/include/linux/kvm_host.h
>> @@ -696,6 +696,18 @@ static inline wait_queue_head_t *kvm_arch_vcpu_wq(struct kvm_vcpu *vcpu)
>> #endif
>> }
>>
>> +#ifndef __KVM_HAVE_ARCH_VIRTUAL_INTC_INITIALIZED
>
> maybe you can drop the _virtual_ from all these names to make it
> slightly shorter.
ok. I chose that name to differentiate from the host irqchip. I will
drop "virtual".
>
> alternatively to this approach you could expose a function from the
> irqfd layer that KVM intc implementations call into to say "I'm
> ready"... Not sure if it would look nicer.
>
>> +/*
>> + * returns trues if the virtual interrupt controller is initialized and
>> + * ready to accept virtual IRQ. On some architectures the virtual interrupt
>> + * controller is dynamically instantiated and this is not always true.
>> + */
>> +static inline bool kvm_arch_is_virtual_intc_initialized(struct kvm *kvm)
>> +{
>> + return true;
>> +}
>
> don't you need to define a prototype if the architecture does define the
> symbol?
yes I will move the declaration here
Thanks
Eric
>
>> +#endif
>> +
>> int kvm_arch_init_vm(struct kvm *kvm, unsigned long type);
>> void kvm_arch_destroy_vm(struct kvm *kvm);
>> void kvm_arch_sync_events(struct kvm *kvm);
>> --
>> 1.9.1
>>
next prev parent reply other threads:[~2015-01-12 13:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 16:07 [PATCH v5 0/5] irqfd support for arm/arm64 Eric Auger
2014-12-03 16:07 ` Eric Auger
2014-12-03 16:07 ` Eric Auger
2014-12-03 16:07 ` [PATCH v5 1/5] KVM: arm/arm64: unset CONFIG_HAVE_KVM_IRQCHIP Eric Auger
2014-12-03 16:07 ` Eric Auger
2014-12-03 16:07 ` [PATCH v5 2/5] KVM: introduce kvm_arch_is_virtual_intc_initialized Eric Auger
2014-12-03 16:07 ` Eric Auger
2014-12-03 16:07 ` Eric Auger
2015-01-11 21:11 ` Christoffer Dall
2015-01-11 21:11 ` Christoffer Dall
2015-01-12 13:39 ` Eric Auger [this message]
2015-01-12 13:39 ` Eric Auger
2014-12-03 16:07 ` [PATCH v5 3/5] KVM: arm/arm64: implement kvm_arch_is_virtual_intc_initialized Eric Auger
2014-12-03 16:07 ` Eric Auger
2014-12-03 16:07 ` Eric Auger
2015-01-11 21:12 ` Christoffer Dall
2015-01-11 21:12 ` Christoffer Dall
2015-01-12 13:40 ` Eric Auger
2015-01-12 13:40 ` Eric Auger
2014-12-03 16:07 ` [PATCH v5 4/5] KVM: irqfd: use kvm_arch_is_virtual_intc_initialized Eric Auger
2014-12-03 16:07 ` Eric Auger
2014-12-03 16:07 ` Eric Auger
2015-01-11 21:17 ` Christoffer Dall
2015-01-11 21:17 ` Christoffer Dall
2015-01-12 13:40 ` Eric Auger
2015-01-12 13:40 ` Eric Auger
2015-01-12 16:55 ` Christoffer Dall
2015-01-12 16:55 ` Christoffer Dall
2014-12-03 16:07 ` [PATCH v5 5/5] KVM: arm/arm64: add irqfd support Eric Auger
2014-12-03 16:07 ` Eric Auger
2015-01-11 21:43 ` Christoffer Dall
2015-01-11 21:43 ` Christoffer Dall
2015-01-12 14:30 ` Eric Auger
2015-01-12 14:30 ` Eric Auger
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=54B3CEA6.2030008@linaro.org \
--to=eric.auger@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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.