From: Jan Kiszka <jan.kiszka@siemens.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Xenomai <xenomai@lists.linux.dev>,
David Oberhollenzer <david.oberhollenzer@sigma-star.at>
Subject: Re: ARM64 prefault weirdness
Date: Tue, 5 Mar 2024 17:58:26 +0100 [thread overview]
Message-ID: <a635b867-7224-4dd7-84ad-e2c2630d14cc@siemens.com> (raw)
In-Reply-To: <CAFLxGvxaEf-XBAo=NMEt5jpAnnDCA_YQV1Cq_Nd5J4Bd26LY-w@mail.gmail.com>
On 05.03.24 16:39, Richard Weinberger wrote:
> On Tue, Mar 5, 2024 at 4:00 PM Jan Kiszka <jan.kiszka@siemens.com> wrote:
>> On 28.02.24 14:44, Richard Weinberger wrote:
>>> On Tue, Feb 27, 2024 at 10:24 AM Richard Weinberger
>> If prefault was only about breaking copy-on-write early, this would be
>> fine. But we just readded it to iomem mapping helper. Something still
>> does not fit together for me.
>
> Well, this is not iomem. It's vmalloc memory.
> But I agree, still many lose ends...
>
Yes, my point is why should it by safe to skip prefaulting completely
when a vmalloc'ed region is just readable. What should make this safe?
Jan
--
Siemens AG, Technology
Linux Expert Center
prev parent reply other threads:[~2024-03-05 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 9:24 ARM64 prefault weirdness Richard Weinberger
2024-02-28 13:44 ` Richard Weinberger
2024-03-05 15:00 ` Jan Kiszka
2024-03-05 15:39 ` Richard Weinberger
2024-03-05 16:58 ` Jan Kiszka [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=a635b867-7224-4dd7-84ad-e2c2630d14cc@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=david.oberhollenzer@sigma-star.at \
--cc=richard.weinberger@gmail.com \
--cc=xenomai@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).