From: pbonzini@redhat.com (Paolo Bonzini)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v2 3/6] irq: bypass: Extend skeleton for ARM forwarding control
Date: Tue, 7 Jul 2015 15:22:34 +0200 [thread overview]
Message-ID: <559BD29A.9000208@redhat.com> (raw)
In-Reply-To: <E959C4978C3B6342920538CF579893F0025F3645@SHSMSX104.ccr.corp.intel.com>
On 07/07/2015 13:33, Wu, Feng wrote:
>>> > > The need to store the consumer->producer link seems to be unique to
>>> > > posted interrupts. It is difficult to say without seeing the PI code,
>>> > > but I prefer to keep the bypass manager as small as possible.
>> >
>> > Fine. I will follow your suggestion!
> If using the following changes, how can we assign 'prod', we need to use
> container_of to get struct kvm_kernel_irqfd and then refer to 'prod', but
> we cannot do this in irq_bypass_register_consumer(), right? It is a
> common API. But we can only get the associated producer info inside
> bypass manager, right?
KVM's add_producer and del_producer callbacks do have a pointer to the
producer.
Paolo
next prev parent reply other threads:[~2015-07-07 13:22 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 12:11 [RFC v2 0/6] IRQ bypass manager and irqfd consumer Eric Auger
2015-07-06 12:11 ` [RFC v2 1/6] KVM: arm/arm64: select IRQ_BYPASS_MANAGER Eric Auger
2015-07-06 12:24 ` Paolo Bonzini
2015-07-06 12:11 ` [RFC v2 2/6] VFIO: platform: " Eric Auger
2015-07-06 12:11 ` [RFC v2 3/6] irq: bypass: Extend skeleton for ARM forwarding control Eric Auger
2015-07-06 12:27 ` Paolo Bonzini
2015-07-06 15:35 ` Eric Auger
2015-07-06 15:57 ` Paolo Bonzini
2015-07-06 17:09 ` Eric Auger
2015-07-06 17:41 ` Paolo Bonzini
2015-07-07 7:10 ` Eric Auger
2015-07-07 8:58 ` Paolo Bonzini
2015-07-07 10:58 ` Wu, Feng
2015-07-07 11:00 ` Paolo Bonzini
2015-07-07 11:13 ` Wu, Feng
2015-07-07 11:13 ` Paolo Bonzini
2015-07-07 11:18 ` Wu, Feng
2015-07-07 11:21 ` Paolo Bonzini
2015-07-07 11:24 ` Wu, Feng
2015-07-07 11:33 ` Wu, Feng
2015-07-07 13:22 ` Paolo Bonzini [this message]
2015-07-06 12:11 ` [RFC v2 4/6] KVM: create kvm_irqfd.h Eric Auger
2015-07-06 12:11 ` [RFC v2 5/6] KVM: introduce kvm_arch functions for IRQ bypass Eric Auger
2015-07-06 12:11 ` [RFC v2 6/6] KVM: eventfd: add irq bypass consumer management Eric Auger
2015-07-07 8:47 ` Wu, Feng
2015-07-07 9:05 ` Eric Auger
2015-07-07 9:13 ` Wu, Feng
2015-07-07 17:17 ` [RFC v2 0/6] IRQ bypass manager and irqfd consumer Alex Williamson
2015-07-09 12:28 ` Joerg Roedel
2015-07-09 14:13 ` Alex Williamson
2015-07-09 14:38 ` Paolo Bonzini
2015-07-09 15:34 ` Joerg Roedel
2015-07-09 16:06 ` Alex Williamson
2015-07-24 1:27 ` Wu, Feng
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=559BD29A.9000208@redhat.com \
--to=pbonzini@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).