public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, igt-dev@lists.freedesktop.org
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [igt-dev] [Intel-gfx] [PATCH i-g-t 2/5] gem_wsim: Round mmap to page size
Date: Thu, 28 Feb 2019 14:41:23 +0000	[thread overview]
Message-ID: <5eded0ef-6b8c-06ff-9be7-00e66eb71076@linux.intel.com> (raw)
In-Reply-To: <155136395323.5847.13177410525767591837@skylake-alporthouse-com>


On 28/02/2019 14:25, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2019-02-28 14:18:25)
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> mmap(2) mandates size is page aligned.
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> ---
>>   benchmarks/gem_wsim.c | 7 ++++---
>>   1 file changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/benchmarks/gem_wsim.c b/benchmarks/gem_wsim.c
>> index 0a5abc08d8c2..57ceb983cf82 100644
>> --- a/benchmarks/gem_wsim.c
>> +++ b/benchmarks/gem_wsim.c
>> @@ -737,6 +737,7 @@ init_bb(struct w_step *w, unsigned int flags)
>>   {
>>          const unsigned int arb_period =
>>                          get_bb_sz(w->preempt_us) / sizeof(uint32_t);
>> +       const unsigned int mmap_len = ALIGN(w->bb_sz, 4096);
>>          unsigned int i;
>>          uint32_t *ptr;
> 
> You only need to do it for
> 
> ww->bb_sz = ALIGN(get_bb_sz(), 4096);
> 
> All batch lengths are start = ww->bb_sz - get_bb_sz() and so remain
> correct. Right?

I think so. I have one more assignment site of w->bb_sz in the upcoming 
code so it was 2 : 2 and I flipped a coin. Actually I wanted to make it 
explicit what I am fixing - the mmap size. But now you'll say batch size 
is also implicitly rounded.. oh well.. I prefer the explicit round up at 
mmap time.

Regards,

Tvrtko
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-02-28 14:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-28 14:18 [igt-dev] [PATCH i-g-t 1/5] lib/i915: Assert mmap size alignment Tvrtko Ursulin
2019-02-28 14:18 ` [Intel-gfx] [PATCH i-g-t 2/5] gem_wsim: Round mmap to page size Tvrtko Ursulin
2019-02-28 14:25   ` Chris Wilson
2019-02-28 14:41     ` Tvrtko Ursulin [this message]
2019-02-28 14:44       ` [igt-dev] " Chris Wilson
2019-02-28 14:18 ` [igt-dev] [PATCH i-g-t 3/5] gem_wsim: Remove some unused struct members Tvrtko Ursulin
2019-02-28 14:30   ` Chris Wilson
2019-02-28 14:18 ` [igt-dev] [PATCH i-g-t 4/5] autoconf: Silence void pointer arithmetic warnings Tvrtko Ursulin
2019-02-28 14:31   ` Chris Wilson
2019-02-28 14:42     ` Tvrtko Ursulin
2019-02-28 14:18 ` [Intel-gfx] [PATCH i-g-t 5/5] tests/i915/pm_rc6_residency: Fix linking Tvrtko Ursulin
2019-02-28 14:33   ` [igt-dev] " Chris Wilson
2019-02-28 14:48     ` Tvrtko Ursulin
2019-02-28 14:24 ` [igt-dev] [PATCH i-g-t 1/5] lib/i915: Assert mmap size alignment Chris Wilson
2019-02-28 14:38   ` Tvrtko Ursulin
2019-02-28 15:17 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/5] " Patchwork

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=5eded0ef-6b8c-06ff-9be7-00e66eb71076@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    --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