From: Ashutosh Dixit <ashutosh.dixit@intel.com>
To: Caz Yokoyama <caz.yokoyama@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [igt PATCH v2 1/1] lib: Incrementally mlock()
Date: Fri, 22 Feb 2019 08:12:34 -0800 [thread overview]
Message-ID: <87bm33hkel.fsf@intel.com> (raw)
In-Reply-To: <53135e5acf3668084a7f8453add2bd04bf2481ed.1550800923.git.caz.yokoyama@intel.com> (Caz Yokoyama's message of "Thu, 21 Feb 2019 19:03:57 -0700")
On Thu, Feb 21 2019 at 07:03:57 PM, Caz Yokoyama <caz.yokoyama@intel.com> wrote:
> __igt_waitchildren();
> - igt_assert(!mlock(can_mlock, *can_mlock));
This is also wrong. The parent process needs to lock the memory for the
calculation of the amount of locked memory to be correct. Also explains
why this tests runs for so long with this patch.
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-02-22 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 2:03 [igt-dev] [igt PATCH v2 1/1] lib: Incrementally mlock() Caz Yokoyama
2019-02-21 20:25 ` Chris Wilson
2019-02-22 16:12 ` Ashutosh Dixit [this message]
2019-02-22 17:28 ` Caz Yokoyama
2019-02-26 16:06 ` Caz Yokoyama
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=87bm33hkel.fsf@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=caz.yokoyama@intel.com \
--cc=igt-dev@lists.freedesktop.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