linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Haren Myneni <haren@linux.ibm.com>
Cc: mikey@neuling.org, ajd@linux.ibm.com, frederic.barrat@fr.ibm.com,
	linux-kernel@vger.kernel.org, npiggin@gmail.com,
	hch@infradead.org, oohall@gmail.com, clg@kaod.org,
	herbert@gondor.apana.org.au, sukadev@linux.vnet.ibm.com,
	linuxppc-dev@lists.ozlabs.org, srikar@linux.vnet.ibm.com
Subject: Re: [PATCH v11 01/14] powerpc/xive: Define xive_native_alloc_irq_on_chip()
Date: Wed, 22 Apr 2020 00:09:43 +1000 (AEST)	[thread overview]
Message-ID: <49656b64Szz9sSx@ozlabs.org> (raw)
In-Reply-To: <1587016720.2275.1047.camel@hbabu-laptop>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 416 bytes --]

On Thu, 2020-04-16 at 05:58:40 UTC, Haren Myneni wrote:
> 
> This function allocates IRQ on a specific chip. VAS needs per chip
> IRQ allocation and will have IRQ handler per VAS instance.
> 
> Signed-off-by: Haren Myneni <haren@linux.ibm.com>
> Reviewed-by: Cédric Le Goater <clg@kaod.org>

Series applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/8d0ea29db5aefd0d94fa4b6ca6124c68998f3c6a

cheers

  reply	other threads:[~2020-04-21 15:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16  5:50 [PATCH v11 00/14] powerpc/vas: Page fault handling for user space NX requests Haren Myneni
2020-04-16  5:58 ` [PATCH v11 01/14] powerpc/xive: Define xive_native_alloc_irq_on_chip() Haren Myneni
2020-04-21 14:09   ` Michael Ellerman [this message]
2020-04-16  5:59 ` [PATCH v11 02/14] powerpc/vas: Define nx_fault_stamp in coprocessor_request_block Haren Myneni
2020-04-16  6:00 ` [PATCH v11 03/14] powerpc/vas: Alloc and setup IRQ and trigger port address Haren Myneni
2020-04-16  6:00 ` [PATCH v11 04/14] powerpc/vas: Setup fault window per VAS instance Haren Myneni
2020-04-16  6:01 ` [PATCH v11 05/14] powerpc/vas: Register NX with fault window ID and IRQ port value Haren Myneni
2020-04-16  6:02 ` [PATCH v11 06/14] powerpc/vas: Take reference to PID and mm for user space windows Haren Myneni
2020-04-16  6:03 ` [PATCH v11 07/14] powerpc/vas: Setup thread IRQ handler per VAS instance Haren Myneni
2020-04-16  6:03 ` [PATCH v11 08/14] powerpc/vas: Update CSB and notify process for fault CRBs Haren Myneni
2020-04-16  6:04 ` [PATCH v11 09/14] powerpc/vas: Return credits after handling fault Haren Myneni
2020-04-16  6:04 ` [PATCH v11 10/14] powerpc/vas: Print CRB and FIFO values Haren Myneni
2020-04-16  6:05 ` [PATCH v11 11/14] powerpc/vas: Do not use default credits for receive window Haren Myneni
2020-04-16  6:06 ` [PATCH v11 12/14] powerpc/vas: Display process stuck message Haren Myneni
2020-04-16  6:07 ` [PATCH v11 13/14] powerpc/vas: Free send window in VAS instance after credits returned Haren Myneni
2020-04-16  6:08 ` [PATCH v11 14/14] powerpc: Use mm_context vas_windows counter to issue CP_ABORT Haren Myneni

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=49656b64Szz9sSx@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=ajd@linux.ibm.com \
    --cc=clg@kaod.org \
    --cc=frederic.barrat@fr.ibm.com \
    --cc=haren@linux.ibm.com \
    --cc=hch@infradead.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=npiggin@gmail.com \
    --cc=oohall@gmail.com \
    --cc=srikar@linux.vnet.ibm.com \
    --cc=sukadev@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).