Support offset-TypedArray in futex API

Support offset-TypedArray in futex API

BUG=v8:4555
LOG=N

Committed: https://crrev.com/154ddde42b99cdacdc50d93ad7db7f6d7640f28c
Cr-Commit-Position: refs/heads/master@{#32142}

[Pan, 2015-11-19 09:16:58]

Patchset #1 (id:1) has been deleted

[Pan, 2015-11-19 09:17:17]

Patchset #1 (id:20001) has been deleted

[Pan, 2015-11-19 09:19:58]

Description was changed from

==========
Support offset-TypedArray in futex API

BUG=
==========

to

==========
Support offset-TypedArray in futex API

BUG=4555
log=n
==========

[Pan, 2015-11-19 09:20:47]

Description was changed from

==========
Support offset-TypedArray in futex API

BUG=4555
log=n
==========

to

==========
Support offset-TypedArray in futex API

BUG=v8:4555
log=n
==========

[Pan, 2015-11-19 10:36:56]

pan.deng@intel.com changed reviewers:
+ binji@chromium.org, jarin@chromium.org

[Pan, 2015-11-19 10:36:56]

@binji, @jarin, PTAL.

thanks
Pan

[Jarin, 2015-11-19 12:05:38]

On 2015/11/19 10:36:56, Pan wrote:
> @binji, @jarin, PTAL.
> 
> thanks
> Pan

Should not the futexes work also if we use two views with different offsets?
(When the real addresses for the wait & wake are aliased?) Could we test this
case?

[Pan, 2015-11-20 06:19:13]

On 2015/11/19 12:05:38, Jarin wrote:
> On 2015/11/19 10:36:56, Pan wrote:
> > @binji, @jarin, PTAL.
> > 
> > thanks
> > Pan
> 
> Should not the futexes work also if we use two views with different offsets?
> (When the real addresses for the wait & wake are aliased?) Could we test this
> case?

It should.
Add a case in wait/wake, WakeOrRequeue is also covered.

thanks
Pan

[Jarin, 2015-11-20 08:49:22]

On 2015/11/20 06:19:13, Pan wrote:
> On 2015/11/19 12:05:38, Jarin wrote:
> > On 2015/11/19 10:36:56, Pan wrote:
> > > @binji, @jarin, PTAL.
> > > 
> > > thanks
> > > Pan
> > 
> > Should not the futexes work also if we use two views with different offsets?
> > (When the real addresses for the wait & wake are aliased?) Could we test
this
> > case?
> 
> It should.
> Add a case in wait/wake, WakeOrRequeue is also covered.
> 
> thanks
> Pan

Awesome, thanks! LGTM.

[Jarin, 2015-11-20 08:49:36]

The CQ bit was checked by jarin@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-11-20 08:49:40]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1462833002/60001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1462833002/60001

[commit-bot: I haz the power, 2015-11-20 08:52:11]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-11-20 08:52:11]

Dry run: Try jobs failed on following builders:
  v8_presubmit on tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_presubmit/builds/7932)

[Pan, 2015-11-20 11:37:55]

Description was changed from

==========
Support offset-TypedArray in futex API

BUG=v8:4555
log=n
==========

to

==========
Support offset-TypedArray in futex API

BUG=v8:4555
LOG=N
==========

[Pan, 2015-11-20 11:38:08]

The CQ bit was checked by pan.deng@intel.com

[commit-bot: I haz the power, 2015-11-20 11:38:18]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1462833002/60001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1462833002/60001

[commit-bot: I haz the power, 2015-11-20 11:39:28]

Committed patchset #2 (id:60001)

[commit-bot: I haz the power, 2015-11-20 11:40:09]

Patchset 2 (id:??) landed as
https://crrev.com/154ddde42b99cdacdc50d93ad7db7f6d7640f28c
Cr-Commit-Position: refs/heads/master@{#32142}