From: Richard Henderson <richard.henderson@linaro.org>
To: "Ilya Leoshkevich" <iii@linux.ibm.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Laurent Vivier" <laurent@vivier.eu>,
"Taylor Simpson" <tsimpson@quicinc.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v3 0/5] linux-user: Passthrough MADV_DONTNEED for certain file mappings
Date: Tue, 6 Sep 2022 08:35:39 +0100 [thread overview]
Message-ID: <7d31b5bc-65a1-db1a-b7ac-b462e802e5cb@linaro.org> (raw)
In-Reply-To: <20220906000839.1672934-1-iii@linux.ibm.com>
On 9/6/22 01:08, Ilya Leoshkevich wrote:
> Hi,
>
> This series is made of patches from [1]. I've added a test and noticed
> that madvise(MADV_DONTNEED) was broken on alpha, fixing which required
> adding per-arch MADV_* definitions. This in turn affected the strace
> patch, so it made sense to make a series out of the results.
>
> Patch 1 adds MADV_* constants for all architectures.
> Patch 2 fixes the alpha bug.
> Patch 3 adds madvise() support to strace.
> Patch 4 adds MADV_DONTNEED support for file mappings.
> Patch 5 adds a test.
Thanks for that, series
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
prev parent reply other threads:[~2022-09-06 7:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 0:08 [PATCH v3 0/5] linux-user: Passthrough MADV_DONTNEED for certain file mappings Ilya Leoshkevich
2022-09-06 0:08 ` [PATCH v3 1/5] linux-user: Provide MADV_* definitions Ilya Leoshkevich
2022-09-23 21:51 ` Laurent Vivier
2022-09-06 0:08 ` [PATCH v3 2/5] linux-user: Fix madvise(MADV_DONTNEED) on alpha Ilya Leoshkevich
2022-09-23 21:51 ` Laurent Vivier
2022-09-06 0:08 ` [PATCH v3 3/5] linux-user: Implement stracing madvise() Ilya Leoshkevich
2022-09-23 21:51 ` Laurent Vivier
2022-09-06 0:08 ` [PATCH v3 4/5] linux-user: Passthrough MADV_DONTNEED for certain file mappings Ilya Leoshkevich
2022-09-23 21:51 ` Laurent Vivier
2022-09-06 0:08 ` [PATCH v3 5/5] tests/tcg/linux-test: Add linux-madvise test Ilya Leoshkevich
2022-09-23 21:52 ` Laurent Vivier
2022-09-06 7:35 ` Richard Henderson [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=7d31b5bc-65a1-db1a-b7ac-b462e802e5cb@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=iii@linux.ibm.com \
--cc=laurent@vivier.eu \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tsimpson@quicinc.com \
/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 NNTP newsgroup(s).