From: Andrew Donnellan <ajd@linux.ibm.com>
To: Haren Myneni <haren@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, devicetree@vger.kernel.org,
mpe@ellerman.id.au, npiggin@gmail.com, mikey@neuling.org,
herbert@gondor.apana.org.au
Cc: sukadev@linux.vnet.ibm.com
Subject: Re: [PATCH 00/14] powerpc/vas: Page fault handling for user space NX requests
Date: Wed, 27 Nov 2019 12:27:48 +1100 [thread overview]
Message-ID: <9bcb59f3-17cf-1726-4e6c-3cabd6e4af4d@linux.ibm.com> (raw)
In-Reply-To: <1574816450.13250.2.camel@hbabu-laptop>
Hi Haren,
On 27/11/19 12:00 pm, Haren Myneni wrote:
> Haren Myneni (14):
> powerpc/vas: Describe vas-port and interrupts properties
> Revert "powerpc/powernv: remove the unused vas_win_paste_addr and
> vas_win_id functions"
> powerpc/vas: Define nx_fault_stamp in coprocessor_request_block
> powerpc/vas: Setup IRQ mapping and register port for each window
> powerpc/vas: Setup fault window per VAS instance
> powerpc/VAS: Setup fault handler per VAS instance
> powerpc/vas: Read and process fault CRBs
> powerpc/vas: Take reference to PID and mm for user space windows
> powerpc/vas: Update CSB and notify process for fault CRBs
> powerpc/vas: Print CRB and FIFO values
> powerpc/vas: Do not use default credits for receive window
> powerpc/VAS: Return credits after handling fault
> powerpc/vas: Display process stuck message
> powerpc/vas: Free send window in VAS instance after credits returned
In future, please send the patches in reply to the cover letter (and for
series that don't have a cover letter, send patch 2 onwards as a reply
to patch 1).
You may want to consider using git send-email which automates all this
for you.
Thanks,
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@linux.ibm.com IBM Australia Limited
prev parent reply other threads:[~2019-11-27 1:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 1:00 [PATCH 00/14] powerpc/vas: Page fault handling for user space NX requests Haren Myneni
2019-11-27 1:27 ` Andrew Donnellan [this message]
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=9bcb59f3-17cf-1726-4e6c-3cabd6e4af4d@linux.ibm.com \
--to=ajd@linux.ibm.com \
--cc=devicetree@vger.kernel.org \
--cc=haren@linux.vnet.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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).