public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] Fix mmap01 testcase on hppa architecture
Date: Fri, 16 Jun 2017 10:03:29 -0400 (EDT)	[thread overview]
Message-ID: <1366594617.36983858.1497621809398.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <0a7d9ad3-c1fc-1936-15e2-cef6e0b8e56e@gmx.de>



----- Original Message -----
> On 13.06.2017 13:18, Jan Stancek wrote:
> >> The mmap() syscall to map a file at any given page-aligned address (via
> >> the
> >> MAP_FIXED flag) can fail on the hppa architecture due to cache colouring
> >> requirements of the architecture.
> >>
> >> This patch drops the MAP_FIXED flag and thus maps the file instead at
> >> some convenient address based on the hint as given by the addr
> >> parameter.
> > 
> > It looks like we don't need addr at all. Test is remapping part
> > of heap with MAP_FIXED, which looks risky. I'd drop that page
> > initialisation inside heap too. Now, without MAP_FIXED, it's
> > just completely unrelated page. What do you think?
> 
> Yes, that's probably the best choice.
> The original code tries to initialize the area where the file is going
> to be mapped with non-zero values to be able to check if after the mapping
> the memory area beyond the EOF was zero-initialized by the kernel.
> This part of the check was already changed by my initial patch, with
> your suggestion we would now drop the initialization completely.
> I think your suggestion is fair.
> 
> New patch is attached.

Pushed.

Thanks,
Jan


      reply	other threads:[~2017-06-16 14:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-09 14:53 [LTP] [PATCH] Fix mmap01 testcase on hppa architecture Helge Deller
2017-06-13 11:18 ` Jan Stancek
2017-06-16 13:55   ` Helge Deller
2017-06-16 14:03     ` Jan Stancek [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=1366594617.36983858.1497621809398.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=ltp@lists.linux.it \
    /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