From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Nathan Lynch <nathanl@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: tyreld@linux.ibm.com, ajd@linux.ibm.com, aik@ozlabs.ru,
aneesh.kumar@linux.ibm.com, npiggin@gmail.com,
brking@linux.ibm.com
Subject: Re: [PATCH v2 0/5] powerpc/rtas: miscellaneous cleanups
Date: Wed, 14 Apr 2021 19:02:02 +0200 [thread overview]
Message-ID: <231da5db-efdd-0ddd-9ad8-4ddd2bc03ddf@csgroup.eu> (raw)
In-Reply-To: <20210408140630.205502-1-nathanl@linux.ibm.com>
Le 08/04/2021 à 16:06, Nathan Lynch a écrit :
> This is a reroll of the series posted here:
> https://lore.kernel.org/linuxppc-dev/20210114220004.1138993-1-nathanl@linux.ibm.com/
>
> Originally this work was prompted by failures on radix MMU PowerVM
> guests when passing buffers to RTAS that lay outside of its idea of
> the RMA. In v1 I approached this as a problem to be solved in Linux,
> but RTAS development has since decided to change their code so that
> the RMA restriction does not apply with radix.
>
> So in v2 I retain the cleanups and discard the more significant change
> which accommodated the misbehaving RTAS versions.
Is there a link with https://github.com/linuxppc/issues/issues/252 ?
>
> Changes since v1:
> - Correct missing conversion of RTAS_RMOBUF_MAX ->
> RTAS_USER_REGION_SIZE in in_rmo_buf().
> - Remove unnecessary braces in rtas_syscall_filter_init().
> - Leave expression of RTAS_WORK_AREA_SIZE as-is instead of changing
> the factors in a confusing way, per discussion with Alexey.
> - Drop "powerpc/rtas: constrain user region allocation to RMA"
>
> Nathan Lynch (5):
> powerpc/rtas: improve ppc_rtas_rmo_buf_show documentation
> powerpc/rtas-proc: remove unused RMO_READ_BUF_MAX
> powerpc/rtas: remove ibm_suspend_me_token
> powerpc/rtas: move syscall filter setup into separate function
> powerpc/rtas: rename RTAS_RMOBUF_MAX to RTAS_USER_REGION_SIZE
>
> arch/powerpc/include/asm/rtas.h | 6 +++---
> arch/powerpc/kernel/rtas-proc.c | 15 +++++++++++----
> arch/powerpc/kernel/rtas.c | 34 +++++++++++++++++----------------
> 3 files changed, 32 insertions(+), 23 deletions(-)
>
next prev parent reply other threads:[~2021-04-14 17:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 14:06 [PATCH v2 0/5] powerpc/rtas: miscellaneous cleanups Nathan Lynch
2021-04-08 14:06 ` [PATCH v2 1/5] powerpc/rtas: improve ppc_rtas_rmo_buf_show documentation Nathan Lynch
2021-04-08 14:06 ` [PATCH v2 2/5] powerpc/rtas-proc: remove unused RMO_READ_BUF_MAX Nathan Lynch
2021-04-08 14:06 ` [PATCH v2 3/5] powerpc/rtas: remove ibm_suspend_me_token Nathan Lynch
2021-04-08 14:06 ` [PATCH v2 4/5] powerpc/rtas: move syscall filter setup into separate function Nathan Lynch
2021-04-08 14:06 ` [PATCH v2 5/5] powerpc/rtas: rename RTAS_RMOBUF_MAX to RTAS_USER_REGION_SIZE Nathan Lynch
2021-04-12 7:45 ` Andrew Donnellan
2021-04-14 17:02 ` Christophe Leroy [this message]
2021-04-15 0:23 ` [PATCH v2 0/5] powerpc/rtas: miscellaneous cleanups Nathan Lynch
2021-04-19 3:59 ` 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=231da5db-efdd-0ddd-9ad8-4ddd2bc03ddf@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=aik@ozlabs.ru \
--cc=ajd@linux.ibm.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=brking@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nathanl@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=tyreld@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).