linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
To: Christophe Lombard <clombard@linux.vnet.ibm.com>,
	linuxppc-dev@lists.ozlabs.org, vaibhav@linux.vnet.ibm.com,
	andrew.donnellan@au1.ibm.com
Subject: Re: [PATCH V3] cxl: Export library to support IBM XSL
Date: Thu, 22 Jun 2017 14:25:51 +0200	[thread overview]
Message-ID: <0ae158b6-3e80-0730-83ae-15bccf40d113@linux.vnet.ibm.com> (raw)
In-Reply-To: <1498039393-10656-1-git-send-email-clombard@linux.vnet.ibm.com>

Salut Christophe,

Since there's a respin, 2 details below.


> diff --git a/drivers/misc/cxl/cxllib.c b/drivers/misc/cxl/cxllib.c
> new file mode 100644
> index 0000000..4f4c5ca
> --- /dev/null
> +++ b/drivers/misc/cxl/cxllib.c
> @@ -0,0 +1,246 @@
> +/*
> + * Copyright 2017 IBM Corp.
> + *
> + * This program is free software; you can redistribute it and/or
> + * modify it under the terms of the GNU General Public License
> + * as published by the Free Software Foundation; either version
> + * 2 of the License, or (at your option) any later version.
> + */
> +
> +#include <asm/pnv-pci.h>
> +#include <linux/hugetlb.h>
> +#include <linux/sched/mm.h>
> +#include <misc/cxllib.h>

Maybe somebody can comment on this, but I believe the usual order is the 
'linux' headers first, then the 'asm'. Though I don't know if there's a 
valid reason behind it, or just tradition...


> diff --git a/drivers/misc/cxl/fault.c b/drivers/misc/cxl/fault.c
> index c79e39b..077370f 100644
> --- a/drivers/misc/cxl/fault.c
> +++ b/drivers/misc/cxl/fault.c

> +static int cxl_handle_page_fault(struct cxl_context *ctx,
> +				 struct mm_struct *mm,
> +				 u64 dsisr, u64 dar)
> +{
> +	trace_cxl_pte_miss(ctx, dsisr, dar);
> +
> +	if (cxl_handle_mm_fault(mm, dsisr, dar)) {
> +		cxl_ack_ae(ctx);
> +	} else {
> +		pr_devel("Page fault successfully handled for pe: %i!\n", ctx->pe);
> +		cxl_ops->ack_irq(ctx, CXL_PSL_TFC_An_R, 0);
> +	}
> +
> +	return IRQ_HANDLED;
>   }

Why return IRQ_HANDLED? it's not called from an interrupt handler but 
from the bottom half (actually, I think it's coming from 
cxl_handle_segment_miss(), but it's wrong there as well).

   Fred

  parent reply	other threads:[~2017-06-22 12:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21 10:03 [PATCH V3] cxl: Export library to support IBM XSL Christophe Lombard
2017-06-22 11:20 ` Michael Ellerman
2017-06-22 12:18   ` christophe lombard
2017-06-22 12:25 ` Frederic Barrat [this message]
2017-06-23  5:25   ` Michael Ellerman

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=0ae158b6-3e80-0730-83ae-15bccf40d113@linux.vnet.ibm.com \
    --to=fbarrat@linux.vnet.ibm.com \
    --cc=andrew.donnellan@au1.ibm.com \
    --cc=clombard@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=vaibhav@linux.vnet.ibm.com \
    /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).