From: Manoj Kumar <manoj@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v5 08/18] cxl: IRQ allocation for guests
Date: Tue, 23 Feb 2016 13:16:51 -0600 [thread overview]
Message-ID: <56CCB023.3090704@linux.vnet.ibm.com> (raw)
In-Reply-To: <1456244519-18934-9-git-send-email-fbarrat@linux.vnet.ibm.com>
Fred: Thanks for revising the commit message.
Reviewed-by: Manoj Kumar <manoj@linux.vnet.ibm.com>
---
Manoj Kumar
On 2/23/2016 10:21 AM, Frederic Barrat wrote:
> The PSL interrupt cannot be multiplexed in a guest, as it is not
> supported by the hypervisor. So an interrupt will be allocated
> for it for each context. It will still be the first interrupt found in
> the first interrupt range, but is treated almost like any other AFU
> interrupt when creating/deleting the context. Only the handler is
> different. Rework the code so that the range 0 is treated like the
> other ranges.
>
> Co-authored-by: Christophe Lombard<clombard@linux.vnet.ibm.com>
> Signed-off-by: Frederic Barrat<fbarrat@linux.vnet.ibm.com>
> Signed-off-by: Christophe Lombard<clombard@linux.vnet.ibm.com>
> ---
> drivers/misc/cxl/irq.c | 78 +++++++++++++++++++++++++++++++++++++++++---------
> 1 file changed, 64 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/misc/cxl/irq.c b/drivers/misc/cxl/irq.c
> index 5033869..3c04c14 100644
> --- a/drivers/misc/cxl/irq.c
> +++ b/drivers/misc/cxl/irq.c
> @@ -19,6 +19,13 @@
> #include "cxl.h"
> #include "trace.h"
>
> +static int afu_irq_range_start(void)
> +{
> + if (cpu_has_feature(CPU_FTR_HVMODE))
> + return 1;
> + return 0;
> +}
> +
> static irqreturn_t schedule_cxl_fault(struct cxl_context *ctx, u64 dsisr, u64 dar)
> {
> ctx->dsisr = dsisr;
> @@ -117,11 +124,23 @@ static irqreturn_t cxl_irq_afu(int irq, void *data)
> {
> struct cxl_context *ctx = data;
> irq_hw_number_t hwirq = irqd_to_hwirq(irq_get_irq_data(irq));
> - int irq_off, afu_irq = 1;
> + int irq_off, afu_irq = 0;
> __u16 range;
> int r;
>
> - for (r = 1; r < CXL_IRQ_RANGES; r++) {
> + /*
> + * Look for the interrupt number.
> + * On bare-metal, we know range 0 only contains the PSL
> + * interrupt so we could start counting at range 1 and initialize
> + * afu_irq at 1.
> + * In a guest, range 0 also contains AFU interrupts, so it must
> + * be counted for. Therefore we initialize afu_irq at 0 to take into
> + * account the PSL interrupt.
> + *
> + * For code-readability, it just seems easier to go over all
> + * the ranges on bare-metal and guest. The end result is the same.
> + */
> + for (r = 0; r < CXL_IRQ_RANGES; r++) {
> irq_off = hwirq - ctx->irqs.offset[r];
> range = ctx->irqs.range[r];
> if (irq_off >= 0 && irq_off < range) {
> @@ -131,7 +150,7 @@ static irqreturn_t cxl_irq_afu(int irq, void *data)
> afu_irq += range;
> }
> if (unlikely(r >= CXL_IRQ_RANGES)) {
> - WARN(1, "Recieved AFU IRQ out of range for pe %i (virq %i hwirq %lx)\n",
> + WARN(1, "Received AFU IRQ out of range for pe %i (virq %i hwirq %lx)\n",
> ctx->pe, irq, hwirq);
> return IRQ_HANDLED;
> }
> @@ -141,7 +160,7 @@ static irqreturn_t cxl_irq_afu(int irq, void *data)
> afu_irq, ctx->pe, irq, hwirq);
>
> if (unlikely(!ctx->irq_bitmap)) {
> - WARN(1, "Recieved AFU IRQ for context with no IRQ bitmap\n");
> + WARN(1, "Received AFU IRQ for context with no IRQ bitmap\n");
> return IRQ_HANDLED;
> }
> spin_lock(&ctx->lock);
> @@ -227,17 +246,33 @@ int afu_allocate_irqs(struct cxl_context *ctx, u32 count)
> {
> int rc, r, i, j = 1;
> struct cxl_irq_name *irq_name;
> + int alloc_count;
> +
> + /*
> + * In native mode, range 0 is reserved for the multiplexed
> + * PSL interrupt. It has been allocated when the AFU was initialized.
> + *
> + * In a guest, the PSL interrupt is not mutliplexed, but per-context,
> + * and is the first interrupt from range 0. It still needs to be
> + * allocated, so bump the count by one.
> + */
> + if (cpu_has_feature(CPU_FTR_HVMODE))
> + alloc_count = count;
> + else
> + alloc_count = count + 1;
>
> /* Initialize the list head to hold irq names */
> INIT_LIST_HEAD(&ctx->irq_names);
>
> if ((rc = cxl_ops->alloc_irq_ranges(&ctx->irqs, ctx->afu->adapter,
> - count)))
> + alloc_count)))
> return rc;
>
> - /* Multiplexed PSL Interrupt */
> - ctx->irqs.offset[0] = ctx->afu->psl_hwirq;
> - ctx->irqs.range[0] = 1;
> + if (cpu_has_feature(CPU_FTR_HVMODE)) {
> + /* Multiplexed PSL Interrupt */
> + ctx->irqs.offset[0] = ctx->afu->psl_hwirq;
> + ctx->irqs.range[0] = 1;
> + }
>
> ctx->irq_count = count;
> ctx->irq_bitmap = kcalloc(BITS_TO_LONGS(count),
> @@ -249,7 +284,7 @@ int afu_allocate_irqs(struct cxl_context *ctx, u32 count)
> * Allocate names first. If any fail, bail out before allocating
> * actual hardware IRQs.
> */
> - for (r = 1; r < CXL_IRQ_RANGES; r++) {
> + for (r = afu_irq_range_start(); r < CXL_IRQ_RANGES; r++) {
> for (i = 0; i < ctx->irqs.range[r]; i++) {
> irq_name = kmalloc(sizeof(struct cxl_irq_name),
> GFP_KERNEL);
> @@ -279,15 +314,30 @@ static void afu_register_hwirqs(struct cxl_context *ctx)
> {
> irq_hw_number_t hwirq;
> struct cxl_irq_name *irq_name;
> - int r,i;
> + int r, i;
> + irqreturn_t (*handler)(int irq, void *data);
>
> /* We've allocated all memory now, so let's do the irq allocations */
> irq_name = list_first_entry(&ctx->irq_names, struct cxl_irq_name, list);
> - for (r = 1; r < CXL_IRQ_RANGES; r++) {
> + for (r = afu_irq_range_start(); r < CXL_IRQ_RANGES; r++) {
> hwirq = ctx->irqs.offset[r];
> for (i = 0; i < ctx->irqs.range[r]; hwirq++, i++) {
> - cxl_map_irq(ctx->afu->adapter, hwirq,
> - cxl_irq_afu, ctx, irq_name->name);
> + if (r == 0 && i == 0)
> + /*
> + * The very first interrupt of range 0 is
> + * always the PSL interrupt, but we only
> + * need to connect a handler for guests,
> + * because there's one PSL interrupt per
> + * context.
> + * On bare-metal, the PSL interrupt is
> + * multiplexed and was setup when the AFU
> + * was configured.
> + */
> + handler = cxl_ops->psl_interrupt;
> + else
> + handler = cxl_irq_afu;
> + cxl_map_irq(ctx->afu->adapter, hwirq, handler, ctx,
> + irq_name->name);
> irq_name = list_next_entry(irq_name, list);
> }
> }
> @@ -311,7 +361,7 @@ void afu_release_irqs(struct cxl_context *ctx, void *cookie)
> unsigned int virq;
> int r, i;
>
> - for (r = 1; r < CXL_IRQ_RANGES; r++) {
> + for (r = afu_irq_range_start(); r < CXL_IRQ_RANGES; r++) {
> hwirq = ctx->irqs.offset[r];
> for (i = 0; i < ctx->irqs.range[r]; hwirq++, i++) {
> virq = irq_find_mapping(NULL, hwirq);
next prev parent reply other threads:[~2016-02-23 19:16 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 16:21 [PATCH v5 00/18] cxl: Add support for powerVM guest Frederic Barrat
2016-02-23 16:21 ` [PATCH v5 01/18] cxl: Move common code away from bare-metal-specific files Frederic Barrat
2016-02-23 19:08 ` Manoj Kumar
2016-02-23 16:21 ` [PATCH v5 02/18] cxl: Move bare-metal specific code to specialized files Frederic Barrat
2016-02-23 19:09 ` Manoj Kumar
2016-02-23 16:21 ` [PATCH v5 03/18] cxl: Define process problem state area at attach time only Frederic Barrat
2016-02-23 19:09 ` Manoj Kumar
2016-03-03 3:55 ` Ian Munsie
2016-02-23 16:21 ` [PATCH v5 04/18] cxl: Introduce implementation-specific API Frederic Barrat
2016-02-23 19:09 ` Manoj Kumar
2016-02-23 16:21 ` [PATCH v5 05/18] cxl: Rename some bare-metal specific functions Frederic Barrat
2016-02-23 19:11 ` Manoj Kumar
2016-03-03 4:56 ` Ian Munsie
2016-02-23 16:21 ` [PATCH v5 06/18] cxl: Isolate a few bare-metal-specific calls Frederic Barrat
2016-02-23 19:12 ` Manoj Kumar
2016-02-23 16:21 ` [PATCH v5 07/18] cxl: Update cxl_irq() prototype Frederic Barrat
2016-02-23 19:13 ` Manoj Kumar
2016-02-23 16:21 ` [PATCH v5 08/18] cxl: IRQ allocation for guests Frederic Barrat
2016-02-23 19:16 ` Manoj Kumar [this message]
2016-03-03 4:59 ` Ian Munsie
2016-02-23 16:21 ` [PATCH v5 09/18] cxl: New possible return value from hcall Frederic Barrat
2016-02-23 19:18 ` Manoj Kumar
2016-02-23 19:28 ` Michael Neuling
2016-02-23 16:21 ` [PATCH v5 10/18] cxl: New hcalls to support cxl adapters Frederic Barrat
2016-02-23 19:23 ` Manoj Kumar
2016-03-03 4:04 ` Ian Munsie
2016-02-23 16:21 ` [PATCH v5 11/18] cxl: Separate bare-metal fields in adapter and AFU data structures Frederic Barrat
2016-02-24 16:50 ` Manoj Kumar
2016-03-03 4:09 ` Ian Munsie
2016-02-23 16:21 ` [PATCH v5 12/18] cxl: Add guest-specific code Frederic Barrat
2016-02-24 18:55 ` Manoj Kumar
2016-03-03 5:02 ` Ian Munsie
2016-02-23 16:21 ` [PATCH v5 13/18] cxl: sysfs support for guests Frederic Barrat
2016-02-24 19:03 ` Manoj Kumar
2016-03-03 5:04 ` Ian Munsie
2016-02-23 16:21 ` [PATCH v5 14/18] cxl: Support to flash a new image on the adapter from a guest Frederic Barrat
2016-02-24 20:03 ` Manoj Kumar
2016-02-25 13:11 ` Frederic Barrat
2016-02-25 16:59 ` Manoj Kumar
2016-03-03 4:52 ` Ian Munsie
2016-02-23 16:21 ` [PATCH v5 15/18] cxl: Parse device tree and create cxl device(s) at boot Frederic Barrat
2016-02-24 20:15 ` Manoj Kumar
2016-02-25 13:19 ` Frederic Barrat
2016-02-25 16:44 ` Manoj Kumar
2016-02-23 16:21 ` [PATCH v5 16/18] cxl: Support the cxl kernel API from a guest Frederic Barrat
2016-02-24 21:09 ` Manoj Kumar
2016-03-03 5:08 ` Ian Munsie
2016-02-23 16:21 ` [PATCH v5 17/18] cxl: Adapter failure handling Frederic Barrat
2016-02-24 21:41 ` Manoj Kumar
2016-02-23 16:21 ` [PATCH v5 18/18] cxl: Add tracepoints around the cxl hcall Frederic Barrat
2016-02-24 21:49 ` Manoj Kumar
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=56CCB023.3090704@linux.vnet.ibm.com \
--to=manoj@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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).