From: John David Anglin <dave.anglin@bell.net>
To: Jens Axboe <axboe@kernel.dk>, Helge Deller <deller@gmx.de>,
io-uring@vger.kernel.org,
linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: [PATCHSET 0/5] User mapped provided buffer rings
Date: Fri, 17 Mar 2023 12:15:10 -0400 [thread overview]
Message-ID: <e8c78c0f-b94a-2ac8-b827-e7938182347f@bell.net> (raw)
In-Reply-To: <f4da7453-49ef-73fb-7feb-fcca543bd37e@kernel.dk>
On 2023-03-17 11:57 a.m., Jens Axboe wrote:
>> Running test buf-ring.t register buf ring failed -22
>> test_full_page_reg failed
>> Test buf-ring.t failed with ret 1
> The buf-ring failure with the patch from my previous message is because
> it manually tries to set up a ring with an address that won't work. The
> test case itself never uses the ring, it's just a basic
> register/unregister test. So would just need updating if that patch goes
> in to pass on hppa, there's nothing inherently wrong here.
>
I would suggest it. From page F-7 of the PA-RISC 2.0 Architecture:
All other uses of non-equivalent aliasing (including simultaneously enabling multiple non-equivalently
aliased translations where one or more allow for write access) are prohibited, and can cause machine
checks or silent data corruption, including data corruption of unrelated memory on unrelated pages.
Dave
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2023-03-17 16:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230314171641.10542-1-axboe@kernel.dk>
2023-03-15 20:03 ` [PATCHSET 0/5] User mapped provided buffer rings Helge Deller
2023-03-15 20:07 ` Helge Deller
2023-03-15 20:38 ` Jens Axboe
2023-03-15 21:04 ` John David Anglin
2023-03-15 21:08 ` Jens Axboe
2023-03-15 21:18 ` Jens Axboe
2023-03-16 10:18 ` Helge Deller
2023-03-16 17:00 ` Jens Axboe
2023-03-16 19:08 ` John David Anglin
2023-03-16 19:46 ` Jens Axboe
2023-03-17 2:09 ` Jens Axboe
2023-03-17 2:17 ` Jens Axboe
2023-03-17 15:36 ` John David Anglin
2023-03-17 15:57 ` Jens Axboe
2023-03-17 16:15 ` John David Anglin [this message]
2023-03-17 16:37 ` Jens Axboe
2023-03-15 20:11 ` Jens Axboe
[not found] ` <20230314171641.10542-6-axboe@kernel.dk>
2023-03-16 18:07 ` [PATCH 5/5] io_uring: add support for user mapped provided buffer ring Ammar Faizi
2023-03-16 18:42 ` Jens Axboe
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=e8c78c0f-b94a-2ac8-b827-e7938182347f@bell.net \
--to=dave.anglin@bell.net \
--cc=axboe@kernel.dk \
--cc=deller@gmx.de \
--cc=io-uring@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