From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Lan Tianyu <tianyu.lan@intel.com>
Cc: kevin.tian@intel.com, sstabellini@kernel.org,
andrew.cooper3@citrix.com, xen-devel@lists.xen.org,
julien.grall@arm.com, jbeulich@suse.com, chao.gao@intel.com
Subject: Re: [RFC PATCH 3/23] VIOMMU: Add irq request callback to deal with irq remapping
Date: Mon, 17 Apr 2017 10:39:00 -0400 [thread overview]
Message-ID: <20170417143900.GE3137@char.us.oracle.com> (raw)
In-Reply-To: <1489750043-17260-4-git-send-email-tianyu.lan@intel.com>
On Fri, Mar 17, 2017 at 07:27:03PM +0800, Lan Tianyu wrote:
> This patch is to add irq request callback for platform implementation
> to deal with irq remapping request.
>
> Signed-off-by: Lan Tianyu <tianyu.lan@intel.com>
> ---
> xen/common/viommu.c | 11 +++++++++++
> xen/include/asm-arm/viommu.h | 4 ++++
> xen/include/asm-x86/viommu.h | 15 +++++++++++++++
> xen/include/xen/viommu.h | 8 ++++++++
> 4 files changed, 38 insertions(+)
>
> diff --git a/xen/common/viommu.c b/xen/common/viommu.c
> index 4c1c788..62c66db 100644
> --- a/xen/common/viommu.c
> +++ b/xen/common/viommu.c
> @@ -87,6 +87,17 @@ u64 viommu_query_caps(struct domain *d)
> return info->ops->query_caps(d);
> }
>
> +int viommu_handle_irq_request(struct domain *d,
> + struct irq_remapping_request *request)
> +{
> + struct viommu_info *info = &d->viommu;
> +
> + if ( !info || !info->ops || !info->ops->handle_irq_request)
You are missing an space at the end.
> + return -EINVAL;
> +
> + return info->ops->handle_irq_request(d, request);
> +}
> +
> /*
> * Local variables:
> * mode: C
> diff --git a/xen/include/asm-arm/viommu.h b/xen/include/asm-arm/viommu.h
> index ef6a60b..6a81ecb 100644
> --- a/xen/include/asm-arm/viommu.h
> +++ b/xen/include/asm-arm/viommu.h
> @@ -22,6 +22,10 @@
>
> #include <xen/viommu.h>
>
> +struct irq_remapping_request
> +{
> +};
> +
> static inline const struct viommu_ops *viommu_get_ops(void)
> {
> return NULL;
> diff --git a/xen/include/asm-x86/viommu.h b/xen/include/asm-x86/viommu.h
> index efb435f..b6e01a5 100644
> --- a/xen/include/asm-x86/viommu.h
> +++ b/xen/include/asm-x86/viommu.h
> @@ -23,6 +23,21 @@
> #include <xen/viommu.h>
> #include <asm/types.h>
>
> +struct irq_remapping_request
> +{
> + u8 type;
> + u16 source_id;
> + union {
> + /* MSI */
> + struct {
> + u64 addr;
> + u32 data;
> + } msi;
> + /* Redirection Entry in IOAPIC */
> + u64 rte;
> + } msg;
> +};
Will this work right? As in with the default padding and such?
> +
> static inline const struct viommu_ops *viommu_get_ops(void)
> {
> return NULL;
> diff --git a/xen/include/xen/viommu.h b/xen/include/xen/viommu.h
> index a0abbdf..246b29d 100644
> --- a/xen/include/xen/viommu.h
> +++ b/xen/include/xen/viommu.h
> @@ -24,6 +24,10 @@
>
> #define NR_VIOMMU_PER_DOMAIN 1
>
> +/* IRQ request type */
> +#define VIOMMU_REQUEST_IRQ_MSI 0
> +#define VIOMMU_REQUEST_IRQ_APIC 1
What is this used for?
> +
> struct viommu {
> u64 base_address;
> u64 length;
> @@ -36,6 +40,8 @@ struct viommu_ops {
> u64 (*query_caps)(struct domain *d);
> int (*create)(struct domain *d, struct viommu *viommu);
> int (*destroy)(struct viommu *viommu);
> + int (*handle_irq_request)(struct domain *d,
> + struct irq_remapping_request *request);
> };
>
> struct viommu_info {
> @@ -48,6 +54,8 @@ int viommu_init_domain(struct domain *d);
> int viommu_create(struct domain *d, u64 base_address, u64 length, u64 caps);
> int viommu_destroy(struct domain *d, u32 viommu_id);
> u64 viommu_query_caps(struct domain *d);
> +int viommu_handle_irq_request(struct domain *d,
> + struct irq_remapping_request *request);
>
> #endif /* __XEN_VIOMMU_H__ */
>
> --
> 1.8.3.1
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-04-17 14:39 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 11:27 [RFC PATCH 00/23] xen/vIOMMU: Add vIOMMU support with irq remapping fucntion on Intel platform Lan Tianyu
2017-03-17 11:27 ` [RFC PATCH 1/23] VIOMMU: Add vIOMMU helper functions to create, destroy and query capabilities Lan Tianyu
2017-03-21 19:56 ` Julien Grall
2017-03-22 8:36 ` Tian, Kevin
2017-03-22 12:41 ` Lan, Tianyu
2017-03-22 8:45 ` Lan Tianyu
2017-03-22 11:40 ` Julien Grall
2017-03-22 13:32 ` Lan, Tianyu
2017-03-17 11:27 ` [RFC PATCH 2/23] DMOP: Introduce new DMOP commands for vIOMMU support Lan Tianyu
2017-04-17 14:36 ` Konrad Rzeszutek Wilk
2017-04-18 7:24 ` Lan Tianyu
2017-04-18 13:32 ` Konrad Rzeszutek Wilk
2017-03-17 11:27 ` [RFC PATCH 3/23] VIOMMU: Add irq request callback to deal with irq remapping Lan Tianyu
2017-04-17 14:39 ` Konrad Rzeszutek Wilk [this message]
2017-04-18 8:18 ` Lan Tianyu
2017-04-18 13:36 ` Konrad Rzeszutek Wilk
2017-03-17 11:27 ` [RFC PATCH 4/23] VIOMMU: Add get irq info callback to convert irq remapping request Lan Tianyu
2017-04-17 14:39 ` Konrad Rzeszutek Wilk
2017-03-17 11:27 ` [RFC PATCH 5/23] Tools/libxc: Add viommu operations in libxc Lan Tianyu
2017-03-28 16:24 ` Wei Liu
2017-03-29 0:40 ` Chao Gao
2017-03-29 9:08 ` Paul Durrant
2017-03-30 19:57 ` Chao Gao
2017-04-14 15:38 ` Lan, Tianyu
2017-04-17 11:08 ` Wei Liu
2017-04-17 12:01 ` Lan Tianyu
2017-05-11 12:35 ` Wei Liu
2017-05-11 12:31 ` Lan Tianyu
2017-04-18 9:08 ` Paul Durrant
2017-04-18 9:59 ` Lan Tianyu
2017-04-18 14:15 ` Paul Durrant
2017-04-19 12:21 ` Lan Tianyu
2017-03-17 11:27 ` [RFC PATCH 6/23] Tools/libacpi: Add DMA remapping reporting (DMAR) ACPI table structures Lan Tianyu
2017-03-17 11:27 ` [RFC PATCH 7/23] Tools/libacpi: Add new fields in acpi_config to build DMAR table Lan Tianyu
2017-03-17 11:27 ` [RFC PATCH 8/23] Tools/libacpi: Add a user configurable parameter to control vIOMMU attributes Lan Tianyu
2017-03-17 11:27 ` [RFC PATCH 9/23] Tools/libxl: Inform device model to create a guest with a vIOMMU device Lan Tianyu
2017-03-28 16:24 ` Wei Liu
2017-03-17 11:27 ` [RFC PATCH 10/23] x86/hvm: Introduce a emulated VTD for HVM Lan Tianyu
2017-03-17 11:27 ` [RFC PATCH 11/23] X86/vvtd: Add MMIO handler for VVTD Lan Tianyu
2017-03-17 11:27 ` [RFC PATCH 12/23] X86/vvtd: Set Interrupt Remapping Table Pointer through GCMD Lan Tianyu
2017-03-17 11:27 ` [RFC PATCH 13/23] X86/vvtd: Process interrupt remapping request Lan Tianyu
2017-03-17 11:27 ` [RFC PATCH 14/23] X86/vvtd: decode interrupt attribute from IRTE Lan Tianyu
2017-03-17 11:27 ` [RFC PATCH 15/23] X86/vioapic: Hook interrupt delivery of vIOAPIC Lan Tianyu
2017-04-17 14:43 ` Konrad Rzeszutek Wilk
2017-04-18 8:34 ` Lan Tianyu
2017-04-18 13:37 ` Konrad Rzeszutek Wilk
2017-03-17 11:27 ` [RFC PATCH 16/23] X86/vvtd: Enable Queued Invalidation through GCMD Lan Tianyu
2017-03-17 11:27 ` [RFC PATCH 17/23] X86/vvtd: Enable Interrupt Remapping " Lan Tianyu
2017-03-17 11:27 ` [RFC PATCH 18/23] x86/vpt: Get interrupt vector through a vioapic interface Lan Tianyu
2017-03-17 11:27 ` [RFC PATCH 19/23] passthrough: move some fields of hvm_gmsi_info to a sub-structure Lan Tianyu
2017-03-17 11:27 ` [RFC PATCH 20/23] Tools/libxc: Add a new interface to bind msi-ir with pirq Lan Tianyu
2017-03-17 11:27 ` [RFC PATCH 21/23] X86/vmsi: Hook guest MSI injection Lan Tianyu
2017-03-17 11:27 ` [RFC PATCH 22/23] X86/vvtd: Handle interrupt translation faults Lan Tianyu
2017-03-17 11:27 ` [RFC PATCH 23/23] X86/vvtd: Add queued invalidation (QI) support Lan Tianyu
2017-03-20 14:23 ` [RFC PATCH 00/23] xen/vIOMMU: Add vIOMMU support with irq remapping fucntion on Intel platform Roger Pau Monné
2017-03-21 2:28 ` Lan Tianyu
2017-03-21 5:29 ` Lan Tianyu
2017-03-29 8:00 ` Roger Pau Monné
2017-03-29 3:52 ` Chao Gao
2017-04-17 14:41 ` Konrad Rzeszutek Wilk
2017-04-18 8:19 ` Lan Tianyu
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=20170417143900.GE3137@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=chao.gao@intel.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=kevin.tian@intel.com \
--cc=sstabellini@kernel.org \
--cc=tianyu.lan@intel.com \
--cc=xen-devel@lists.xen.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).