public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: william.roche@oracle.com
To: rpalethorpe@suse.de, ltp@lists.linux.it
Cc: william.roche@oracle.com
Subject: [LTP] [LTP PATCH v3 0/1] Add some memory page soft-offlining control
Date: Mon, 20 Feb 2023 10:26:44 +0000	[thread overview]
Message-ID: <20230220102645.16842-1-william.roche@oracle.com> (raw)
In-Reply-To: <87h6vpq2lk.fsf@suse.de>

From: William Roche <william.roche@oracle.com>

Thank you very much Richard for your feedback about my previous patch version
proposal.
In this new version I made the changes you suggested:

- Changed the signal handler to avoid using unsafe code like "tst_res", and use
  a variable (with its mutex and cv) to inform an additional thread to end the
  test on a SIGBUS. The signal handler doesn't return to avoid a loop of SIGBUS
  delivery.

- Changed the code to use SAFE_MMAP and SAFE_MUNMAP

- The find_in_file() function could not be removed as I use it to verify if the
  hwpoison_inject module is already loaded or not, but I simplified it.

- And I'm now using getmntent() code to identify the debugfs mount point on the
  machine, and open the <debug_fs>/hwpoison/unpoison-pfn location.

Compile and check-madvise11 are clean, code tested on x86 and ARM.

Cheers,
William.


William Roche (1):
  madvise11: Add test for memory allocation / Soft-offlining possible
    race

 runtest/syscalls                              |   1 +
 testcases/kernel/syscalls/madvise/.gitignore  |   1 +
 testcases/kernel/syscalls/madvise/Makefile    |   2 +
 testcases/kernel/syscalls/madvise/madvise11.c | 424 ++++++++++++++++++
 4 files changed, 428 insertions(+)
 create mode 100644 testcases/kernel/syscalls/madvise/madvise11.c

-- 
2.31.1


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2023-02-20 10:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 16:11 [LTP] [LTP PATCH v1 0/1] Add some memory page soft-offlining control William Roche
2022-08-08 16:11 ` [LTP] [LTP PATCH v1 1/1] syscalls/madvise11: " William Roche
2022-08-10 17:00   ` Petr Vorel
2022-08-10 20:18     ` William Roche
2022-08-11  7:34       ` Petr Vorel
2022-08-13 19:59   ` Petr Vorel
2022-08-13 20:28   ` Petr Vorel
2022-08-16  9:18   ` Richard Palethorpe
2023-01-27 10:05     ` [LTP] [LTP PATCH v2 0/1] " william.roche
2023-01-27 10:05       ` [LTP] [LTP PATCH v2 1/1] madvise11: Add test for memory allocation / Soft-offlining possible race william.roche
2023-02-13 10:00         ` Richard Palethorpe
2023-02-20 10:26           ` william.roche [this message]
2023-02-20 10:26             ` [LTP] [LTP PATCH v3 " william.roche
2023-02-27 10:16               ` Richard Palethorpe
2023-02-13  9:34       ` [LTP] [LTP PATCH v2 0/1] Add some memory page soft-offlining control Richard Palethorpe

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=20230220102645.16842-1-william.roche@oracle.com \
    --to=william.roche@oracle.com \
    --cc=ltp@lists.linux.it \
    --cc=rpalethorpe@suse.de \
    /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