Linux PARISC architecture development
 help / color / mirror / Atom feed
From: matoro <matoro_mailinglist_kernel@matoro.tk>
To: Helge Deller <deller@gmx.de>
Cc: Jens Axboe <axboe@kernel.dk>,
	io-uring@vger.kernel.org, linux-ia64@vger.kernel.org,
	linux-parisc@vger.kernel.org
Subject: Re: [PATCH][RFC] io_uring: Fix io_uring_mmu_get_unmapped_area() for IA-64
Date: Thu, 20 Jul 2023 18:39:46 -0400	[thread overview]
Message-ID: <ab42ee876fbab9cf10d6c1dde3164945@matoro.tk> (raw)
In-Reply-To: <be208704-b312-f04d-4548-90853a638752@gmx.de>

On 2023-07-20 18:38, Helge Deller wrote:
> On 7/21/23 00:30, Jens Axboe wrote:
>> On 7/19/23 3:20?PM, Helge Deller wrote:
>>> The io_uring testcase is broken on IA-64 since commit d808459b2e31
>>> ("io_uring: Adjust mapping wrt architecture aliasing requirements").
>>> 
>>> The reason is, that this commit introduced an own architecture
>>> independend get_unmapped_area() search algorithm which doesn't suite 
>>> the
>>> memory region requirements for IA-64.
>>> 
>>> To avoid similar problems in the future it's better to switch back to
>>> the architecture-provided get_unmapped_area() function and adjust the
>>> needed input parameters before the call.  Additionally
>>> io_uring_mmu_get_unmapped_area() will now become easier to understand
>>> and maintain.
>>> 
>>> This patch has been tested on physical IA-64 and PA-RISC machines,
>>> without any failures in the io_uring testcases. On PA-RISC the
>>> LTP mmmap testcases did not report any regressions either.
>>> 
>>> I don't expect issues for other architectures, but it would be nice 
>>> if
>>> this patch could be tested on other machines too.
>> 
>> Any comments from the IA64 folks?
> 
> matoro tested it on ia64 at least...
> 
>> Helge, should this be split into three patches? One for hppa, one for
>> ia64, and then the io_uring one?
> 
> If we split up, I would prefer to split it into 2 patches:
> One for io_uring together with the hppa patch, since they should go in 
> together.
> 
> The ia64 patch is probably unrelated, and can go seperately. But
> there doesn't seem to be any ia64 maintainer...?
> 
> Do you have a chance to test this patch on the other io_uring 
> platforms,
> without applying it into your tree? I think some testing would be good.
> 
> Helge

I tested this on ppc64le last night just to be sure, still had 100% pass 
on test suite.

  reply	other threads:[~2023-07-20 22:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-19 21:20 [PATCH][RFC] io_uring: Fix io_uring_mmu_get_unmapped_area() for IA-64 Helge Deller
2023-07-20  0:14 ` matoro
2023-07-20 22:30 ` Jens Axboe
2023-07-20 22:38   ` Helge Deller
2023-07-20 22:39     ` matoro [this message]
2023-07-20 22:43       ` Jens Axboe
2023-07-20 22:43     ` Jens Axboe
2023-07-20 22:57       ` Jens Axboe
2023-07-20 23:01       ` Helge Deller

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=ab42ee876fbab9cf10d6c1dde3164945@matoro.tk \
    --to=matoro_mailinglist_kernel@matoro.tk \
    --cc=axboe@kernel.dk \
    --cc=deller@gmx.de \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    /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