From: Andrew Donnellan <ajd@linux.ibm.com>
To: Frederic Barrat <fbarrat@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org, clg@kaod.org,
christophe_lombard@fr.ibm.com, ukrishn@linux.ibm.com,
mrochs@linux.ibm.com
Cc: haren@linux.ibm.com, groug@kaod.org
Subject: Re: [PATCH v2 3/4] ocxl: Don't return trigger page when allocating an interrupt
Date: Sat, 4 Apr 2020 03:08:50 +1100 [thread overview]
Message-ID: <4e1fbd6d-764f-d9bd-bfce-a208485f6b14@linux.ibm.com> (raw)
In-Reply-To: <20200403153838.29224-4-fbarrat@linux.ibm.com>
On 4/4/20 2:38 am, Frederic Barrat wrote:
> Existing users of ocxl_link_irq_alloc() have been converted to obtain
> the trigger page of an interrupt through xive directly, we therefore
> have no need to return the trigger page when allocating an interrupt.
>
> It also allows ocxl to use the xive native interface to allocate
> interrupts, instead of its custom service.
>
> Reviewed-by: Cédric Le Goater <clg@kaod.org>
> Reviewed-by: Greg Kurz <groug@kaod.org>
> Signed-off-by: Frederic Barrat <fbarrat@linux.ibm.com>
No obvious issues on a cursory review
Acked-by: Andrew Donnellan <ajd@linux.ibm.com>
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@linux.ibm.com IBM Australia Limited
next prev parent reply other threads:[~2020-04-03 16:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 15:38 [PATCH v2 0/4] ocxl: Cleanup AFU interrupt allocation Frederic Barrat
2020-04-03 15:38 ` [PATCH v2 1/4] scsi: cxlflash: Access interrupt trigger page from xive directly Frederic Barrat
2020-04-03 15:48 ` Cédric Le Goater
2020-04-03 15:51 ` Matthew R. Ochs
2020-04-03 15:38 ` [PATCH v2 2/4] ocxl: " Frederic Barrat
2020-04-03 15:38 ` [PATCH v2 3/4] ocxl: Don't return trigger page when allocating an interrupt Frederic Barrat
2020-04-03 16:08 ` Andrew Donnellan [this message]
2020-04-03 15:38 ` [PATCH v2 4/4] ocxl: Remove custom service to allocate interrupts Frederic Barrat
2020-04-03 16:09 ` Andrew Donnellan
2020-09-09 13:37 ` [PATCH v2 0/4] ocxl: Cleanup AFU interrupt allocation 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=4e1fbd6d-764f-d9bd-bfce-a208485f6b14@linux.ibm.com \
--to=ajd@linux.ibm.com \
--cc=christophe_lombard@fr.ibm.com \
--cc=clg@kaod.org \
--cc=fbarrat@linux.ibm.com \
--cc=groug@kaod.org \
--cc=haren@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mrochs@linux.ibm.com \
--cc=ukrishn@linux.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).