- 13 Jul, 2018 1 commit
-
-
Hannes Payer authored
Bug: chromium:842083 Change-Id: I7f3d7cb64c1263e081d1f9bd36939aaf1a0e3da8 Reviewed-on: https://chromium-review.googlesource.com/1135322 Commit-Queue: Hannes Payer <hpayer@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#54443}
-
- 12 Jul, 2018 2 commits
-
-
Maya Lekova authored
This reverts commit 770ace07. Reason for revert: Breaking the V8 Arm and V8 Arm - debug builds https://ci.chromium.org/p/v8/builders/luci.v8.ci/V8%20Arm%20-%20debug/7260 Original change's description: > [heap] Cleanup: Use std::atomic<T> instead of base::AtomicValue<T> in heap/*. > > Bug: chromium:842083 > Change-Id: Idc04f9ddea326df4ac48a8c58321620660b21549 > Reviewed-on: https://chromium-review.googlesource.com/1129520 > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Commit-Queue: Hannes Payer <hpayer@chromium.org> > Cr-Commit-Position: refs/heads/master@{#54389} TBR=ulan@chromium.org,hpayer@chromium.org,mlippautz@chromium.org Change-Id: I108bc5386ea825c2700f9b830b85a1ca8c10bf4b No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:842083 Reviewed-on: https://chromium-review.googlesource.com/1134966Reviewed-by:
Maya Lekova <mslekova@chromium.org> Commit-Queue: Maya Lekova <mslekova@chromium.org> Cr-Commit-Position: refs/heads/master@{#54398}
-
Hannes Payer authored
Bug: chromium:842083 Change-Id: Idc04f9ddea326df4ac48a8c58321620660b21549 Reviewed-on: https://chromium-review.googlesource.com/1129520Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Hannes Payer <hpayer@chromium.org> Cr-Commit-Position: refs/heads/master@{#54389}
-
- 27 Jun, 2018 4 commits
-
-
Dominik Inführ authored
This is a reland of 91f113e2 Original change's description: > Reland "[heap] Visit individual ephemerons instead of collections" > > This is a reland of 9aba0159 > > Original change's description: > > [heap] Visit individual ephemerons instead of collections > > > > When marking ephemerons visit individual ephemerons with key and value > > unreachable instead of simply iterating all ephemerons in all weak > > collections. Also visit ephemerons at end of concurrent marking to do > > work we would otherwise need to do in the atomic pause. > > > > Bug: chromium:844008 > > Change-Id: I3400ad1f81c0cdc0fe6506a1f1146a6743a7fcd7 > > Reviewed-on: https://chromium-review.googlesource.com/1113934 > > Commit-Queue: Dominik Inführ <dinfuehr@google.com> > > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#54039} > > Bug: chromium:844008 > Change-Id: I4c44e74c7cf5fe380ffa4ce9f106bebb57bc023d > Reviewed-on: https://chromium-review.googlesource.com/1116438 > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Commit-Queue: Dominik Inführ <dinfuehr@google.com> > Cr-Commit-Position: refs/heads/master@{#54046} Bug: chromium:844008 Change-Id: Ie9d606c51aacdfa9ffe77fe4cf780e30dd445d52 Reviewed-on: https://chromium-review.googlesource.com/1116639Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@google.com> Cr-Commit-Position: refs/heads/master@{#54053}
-
Dominik Inführ authored
This reverts commit 91f113e2. Reason for revert: still causes breakage on Chromium-integrated builds, failing here: CHECK_EQ(0, heap()->local_embedder_heap_tracer()->NumberOfWrappersToTrace()); Original change's description: > Reland "[heap] Visit individual ephemerons instead of collections" > > This is a reland of 9aba0159 > > Original change's description: > > [heap] Visit individual ephemerons instead of collections > > > > When marking ephemerons visit individual ephemerons with key and value > > unreachable instead of simply iterating all ephemerons in all weak > > collections. Also visit ephemerons at end of concurrent marking to do > > work we would otherwise need to do in the atomic pause. > > > > Bug: chromium:844008 > > Change-Id: I3400ad1f81c0cdc0fe6506a1f1146a6743a7fcd7 > > Reviewed-on: https://chromium-review.googlesource.com/1113934 > > Commit-Queue: Dominik Inführ <dinfuehr@google.com> > > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#54039} > > Bug: chromium:844008 > Change-Id: I4c44e74c7cf5fe380ffa4ce9f106bebb57bc023d > Reviewed-on: https://chromium-review.googlesource.com/1116438 > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Commit-Queue: Dominik Inführ <dinfuehr@google.com> > Cr-Commit-Position: refs/heads/master@{#54046} TBR=ulan@chromium.org,dinfuehr@google.com Change-Id: I4a059e86ba06e0b2562afc311b12d397cd78e857 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:844008 Reviewed-on: https://chromium-review.googlesource.com/1116718Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#54047}
-
Dominik Inführ authored
This is a reland of 9aba0159 Original change's description: > [heap] Visit individual ephemerons instead of collections > > When marking ephemerons visit individual ephemerons with key and value > unreachable instead of simply iterating all ephemerons in all weak > collections. Also visit ephemerons at end of concurrent marking to do > work we would otherwise need to do in the atomic pause. > > Bug: chromium:844008 > Change-Id: I3400ad1f81c0cdc0fe6506a1f1146a6743a7fcd7 > Reviewed-on: https://chromium-review.googlesource.com/1113934 > Commit-Queue: Dominik Inführ <dinfuehr@google.com> > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#54039} Bug: chromium:844008 Change-Id: I4c44e74c7cf5fe380ffa4ce9f106bebb57bc023d Reviewed-on: https://chromium-review.googlesource.com/1116438Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@google.com> Cr-Commit-Position: refs/heads/master@{#54046}
-
Jakob Kummerow authored
This reverts commit 9aba0159. Reason for revert: causes widespread breakage on Chromium-integrated builds, failing here: CHECK_EQ(0, heap()->local_embedder_heap_tracer()->NumberOfWrappersToTrace()); in MarkCompactCollector::ProcessEphemeronMarking(). See e.g. https://logs.chromium.org/v/?s=chromium%2Fbb%2Fclient.v8.fyi%2FV8-Blink_Linux_64__dbg_%2F12321%2F%2B%2Frecipes%2Fsteps%2Fwebkit_unit_tests%2F0%2Fstdout and more on https://ci.chromium.org/p/v8/g/fyi/console Original change's description: > [heap] Visit individual ephemerons instead of collections > > When marking ephemerons visit individual ephemerons with key and value > unreachable instead of simply iterating all ephemerons in all weak > collections. Also visit ephemerons at end of concurrent marking to do > work we would otherwise need to do in the atomic pause. > > Bug: chromium:844008 > Change-Id: I3400ad1f81c0cdc0fe6506a1f1146a6743a7fcd7 > Reviewed-on: https://chromium-review.googlesource.com/1113934 > Commit-Queue: Dominik Inführ <dinfuehr@google.com> > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#54039} TBR=ulan@chromium.org,dinfuehr@google.com Change-Id: Ib44bfe8c49e8fc30c3d0f2beba03a2895530dfd6 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:844008 Reviewed-on: https://chromium-review.googlesource.com/1116118Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#54045}
-
- 26 Jun, 2018 1 commit
-
-
Dominik Inführ authored
When marking ephemerons visit individual ephemerons with key and value unreachable instead of simply iterating all ephemerons in all weak collections. Also visit ephemerons at end of concurrent marking to do work we would otherwise need to do in the atomic pause. Bug: chromium:844008 Change-Id: I3400ad1f81c0cdc0fe6506a1f1146a6743a7fcd7 Reviewed-on: https://chromium-review.googlesource.com/1113934 Commit-Queue: Dominik Inführ <dinfuehr@google.com> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#54039}
-
- 14 Jun, 2018 1 commit
-
-
Dominik Inführ authored
Use ItemParallelJob to walk ephemerons in parallel. Bug: chromium:844008 Change-Id: Iffc72422f7577458437764f42d13d3f2ee020758 Reviewed-on: https://chromium-review.googlesource.com/1100825 Commit-Queue: Dominik Inführ <dinfuehr@google.com> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#53736}
-
- 11 May, 2018 1 commit
-
-
Hannes Payer authored
Bug: chromium:842083 Change-Id: I4ce2b58aa7fcafe7e886a3c80d3ddf7bfe3e4415 Reviewed-on: https://chromium-review.googlesource.com/1055389 Commit-Queue: Hannes Payer <hpayer@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#53120}
-
- 26 Feb, 2018 1 commit
-
-
Gabriel Charette authored
This reverts commit c41c7a09. Reason for revert: relanding now that the perf waterfall has had a stab at this revert. Original change's description: > Revert "Use all available workers for concurrent marking." > > This reverts commit 3c62f7ae. > (and commit 4939463c) > > The goal of this revert is to contrast the effect on perf bots of > landing it vs reverting it to more easily attribute its impact. > > R=hpayer@chromium.org > > Bug: chromium:812178 > Change-Id: I7c977b1b0b587f787263272400d87f6aae7af634 > Reviewed-on: https://chromium-review.googlesource.com/936761 > Commit-Queue: Hannes Payer <hpayer@chromium.org> > Reviewed-by: Hannes Payer <hpayer@chromium.org> > Cr-Commit-Position: refs/heads/master@{#51546} TBR=gab@chromium.org,hpayer@chromium.org Change-Id: I1ecfc70867dc5424cba1a9ecd229ae031c3e9aa4 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:812178 Reviewed-on: https://chromium-review.googlesource.com/937725Reviewed-by:
Hannes Payer <hpayer@chromium.org> Commit-Queue: Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#51577}
-
- 25 Feb, 2018 1 commit
-
-
Gabriel Charette authored
This reverts commit 3c62f7ae. (and commit 4939463c) The goal of this revert is to contrast the effect on perf bots of landing it vs reverting it to more easily attribute its impact. R=hpayer@chromium.org Bug: chromium:812178 Change-Id: I7c977b1b0b587f787263272400d87f6aae7af634 Reviewed-on: https://chromium-review.googlesource.com/936761 Commit-Queue: Hannes Payer <hpayer@chromium.org> Reviewed-by:
Hannes Payer <hpayer@chromium.org> Cr-Commit-Position: refs/heads/master@{#51546}
-
- 22 Feb, 2018 2 commits
-
-
Gabriel Charette authored
This is an unfortunate restriction imposed by Worklist::kMaxNumTasks for now. This CL unbreaks tests for developers. The CQ didn't catch this breakage because bots have 8 cores and concurrent marking uses num_cores-1. R=hpayer@chromium.org TEST=All tests passed on dev machine (was super broken without this change) NOTRY=True (to unbreak devs) Bug: v8:7477,chromium:812178 Change-Id: I644613857c74d1ae00965f3e6d1d7692a4303062 Reviewed-on: https://chromium-review.googlesource.com/931461 Commit-Queue: Gabriel Charette <gab@chromium.org> Reviewed-by:
Yang Guo <yangguo@chromium.org> Reviewed-by:
Hannes Payer <hpayer@chromium.org> Cr-Commit-Position: refs/heads/master@{#51473}
-
Gabriel Charette authored
R=ulan@chromium.org Bug: chromium:812178 Change-Id: I35a727cb6c663bbd5f1beab98324e5d1b1ecf5c7 Reviewed-on: https://chromium-review.googlesource.com/918663 Commit-Queue: Gabriel Charette <gab@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#51458}
-
- 21 Feb, 2018 1 commit
-
-
Gabriel Charette authored
Reland reason : fixed errors, see PS1->PS4 diff. Follow-up to https://chromium-review.googlesource.com/c/v8/v8/+/924867 This is the core goal of the initial CL @ https://chromium-review.googlesource.com/c/v8/v8/+/922103 which was since split into multiple to diagnose a bots-only failure. R=ulan@chromium.org (cherry picked from commit e9750cb8) Bug: chromium:812178 Change-Id: Ib9474b5c90bf11f4741a93ac35c99b4979e8b4f9 Reviewed-on: https://chromium-review.googlesource.com/925267 Commit-Queue: Gabriel Charette <gab@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#51423}
-
- 19 Feb, 2018 6 commits
-
-
Gabriel Charette authored
This is a reland of f4b41099. Not expected to be the culprit of the 4 CL revert. Original change's description: > Introduce ConcurrentMarking::StopRequest API. > > This was extracted from https://chromium-review.googlesource.com/c/v8/v8/+/924073/10 > after it became clear that using COMPLETE_TASKS/PREEMPT_TASKS where > it should make sense to doesn't work in practice for now. > > Experimental CLs which led to the above conclusion: > - https://chromium-review.googlesource.com/c/v8/v8/+/924865 > (COMPLETE or CANCEL -- still broken) > - https://chromium-review.googlesource.com/c/v8/v8/+/924866 > (CANCEL only, as before, works) > - https://chromium-review.googlesource.com/c/v8/v8/+/924028 > (CANCEL and PREEMPT -- broken as well) > > Introducing this unittested API allows to reduce the size > of the CLs causing hard-to-diagnose bots-only failures > and fix them individually follow-ups @ > > 1) https://chromium-review.googlesource.com/c/v8/v8/+/924029 > 2) https://chromium-review.googlesource.com/c/v8/v8/+/924031 > 3) https://chromium-review.googlesource.com/c/v8/v8/+/924030 > > Bug: chromium:812178 > Change-Id: Icdac456e9f7874b0c4b321ccdb8898297dad7d73 > Reviewed-on: https://chromium-review.googlesource.com/924867 > Commit-Queue: Gabriel Charette <gab@chromium.org> > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#51353} Bug: chromium:812178 Change-Id: Iaa32f9cc6b2fa7004c7fae1f79aa4b00f5f8f34c Reviewed-on: https://chromium-review.googlesource.com/924006Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#51371}
-
Clemens Hammacher authored
This reverts commit f4b41099. Reason for revert: Several GC failures, e.g. https://build.chromium.org/p/client.v8/builders/V8%20Linux/builds/23236, https://build.chromium.org/p/client.v8/builders/V8%20Mac/builds/18390 Original change's description: > Introduce ConcurrentMarking::StopRequest API. > > This was extracted from https://chromium-review.googlesource.com/c/v8/v8/+/924073/10 > after it became clear that using COMPLETE_TASKS/PREEMPT_TASKS where > it should make sense to doesn't work in practice for now. > > Experimental CLs which led to the above conclusion: > - https://chromium-review.googlesource.com/c/v8/v8/+/924865 > (COMPLETE or CANCEL -- still broken) > - https://chromium-review.googlesource.com/c/v8/v8/+/924866 > (CANCEL only, as before, works) > - https://chromium-review.googlesource.com/c/v8/v8/+/924028 > (CANCEL and PREEMPT -- broken as well) > > Introducing this unittested API allows to reduce the size > of the CLs causing hard-to-diagnose bots-only failures > and fix them individually follow-ups @ > > 1) https://chromium-review.googlesource.com/c/v8/v8/+/924029 > 2) https://chromium-review.googlesource.com/c/v8/v8/+/924031 > 3) https://chromium-review.googlesource.com/c/v8/v8/+/924030 > > Bug: chromium:812178 > Change-Id: Icdac456e9f7874b0c4b321ccdb8898297dad7d73 > Reviewed-on: https://chromium-review.googlesource.com/924867 > Commit-Queue: Gabriel Charette <gab@chromium.org> > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#51353} TBR=gab@chromium.org,ulan@chromium.org,mlippautz@chromium.org Change-Id: Ia001cc81c6a7bc030b54d3aa9b9bcecc833300e6 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:812178 Reviewed-on: https://chromium-review.googlesource.com/925302Reviewed-by:
Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#51365}
-
Clemens Hammacher authored
This reverts commit e9750cb8. Reason for revert: Several GC failures, e.g. https://build.chromium.org/p/client.v8/builders/V8%20Linux/builds/23236, https://build.chromium.org/p/client.v8/builders/V8%20Mac/builds/18390 Original change's description: > Preempt ConcurrentMarking tasks instead of merely pausing in PauseScope. > > Follow-up to https://chromium-review.googlesource.com/c/v8/v8/+/924867 > > This is the core goal of the initial CL @ > https://chromium-review.googlesource.com/c/v8/v8/+/922103 > which was since split into multiple to diagnose a bots-only failure. > > Bug: chromium:812178 > Change-Id: I4c4e0b517737e020862917bd89fa6ce38244e597 > Reviewed-on: https://chromium-review.googlesource.com/924031 > Commit-Queue: Gabriel Charette <gab@chromium.org> > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Cr-Commit-Position: refs/heads/master@{#51356} TBR=gab@chromium.org,ulan@chromium.org,mlippautz@chromium.org Change-Id: Ic095e32708e58acbe5955bf29e65af34c59d321e No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:812178 Reviewed-on: https://chromium-review.googlesource.com/925301Reviewed-by:
Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#51363}
-
Gabriel Charette authored
Follow-up to https://chromium-review.googlesource.com/c/v8/v8/+/924867 This is the core goal of the initial CL @ https://chromium-review.googlesource.com/c/v8/v8/+/922103 which was since split into multiple to diagnose a bots-only failure. Bug: chromium:812178 Change-Id: I4c4e0b517737e020862917bd89fa6ce38244e597 Reviewed-on: https://chromium-review.googlesource.com/924031 Commit-Queue: Gabriel Charette <gab@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#51356}
-
Gabriel Charette authored
This was extracted from https://chromium-review.googlesource.com/c/v8/v8/+/924073/10 after it became clear that using COMPLETE_TASKS/PREEMPT_TASKS where it should make sense to doesn't work in practice for now. Experimental CLs which led to the above conclusion: - https://chromium-review.googlesource.com/c/v8/v8/+/924865 (COMPLETE or CANCEL -- still broken) - https://chromium-review.googlesource.com/c/v8/v8/+/924866 (CANCEL only, as before, works) - https://chromium-review.googlesource.com/c/v8/v8/+/924028 (CANCEL and PREEMPT -- broken as well) Introducing this unittested API allows to reduce the size of the CLs causing hard-to-diagnose bots-only failures and fix them individually follow-ups @ 1) https://chromium-review.googlesource.com/c/v8/v8/+/924029 2) https://chromium-review.googlesource.com/c/v8/v8/+/924031 3) https://chromium-review.googlesource.com/c/v8/v8/+/924030 Bug: chromium:812178 Change-Id: Icdac456e9f7874b0c4b321ccdb8898297dad7d73 Reviewed-on: https://chromium-review.googlesource.com/924867 Commit-Queue: Gabriel Charette <gab@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#51353}
-
https://chromium-review.googlesource.com/c/v8/v8/+/924073/10Gabriel Charette authored
This is an attempt to isolate what's causing the hard-to-diagnose bots only failures with that CL. Bug: chromium:812178 Change-Id: I50ffe8953bebbbc6b5a5e2f689718662a537acb4 Reviewed-on: https://chromium-review.googlesource.com/924864Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#51348}
-
- 02 Feb, 2018 1 commit
-
-
jgruber authored
This check verifies that all .h files in the src/ directory have an include guard of the form #ifndef V8_PATH_TO_FILE_H_ #define V8_PATH_TO_FILE_H_ // ... #endif // V8_PATH_TO_FILE_H_ The check can be skipped with a magic comment: // PRESUBMIT_INTENTIONALLY_MISSING_INCLUDE_GUARD Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I0a7b96abec289ad60f64ba8418f1892a6969596d Reviewed-on: https://chromium-review.googlesource.com/897487Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Reviewed-by:
Georg Neis <neis@chromium.org> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:
Andreas Haas <ahaas@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#51079}
-
- 10 Oct, 2017 1 commit
-
-
Michael Lippautz authored
When hitting objects that are allocated in the most recent lienar allocation area, the concurrent marker currently has to bail out to the main thread. However, we only have to delay processing those objects until we are at a safepoint, e.g. IM::Step(). With this change we flush those on-hold-objects back to the shared queue upon performing an incremental marking step. Bug: chromium:694255 Change-Id: I25647d0fc581a5c4de0346bc394dc51062f65f70 Reviewed-on: https://chromium-review.googlesource.com/707315 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#48424}
-
- 09 Oct, 2017 2 commits
-
-
Ulan Degenbaev authored
Bug: chromium:694255 Change-Id: I5c0c0b58cdcf3cf745670148724e3c6ecc34d485 Reviewed-on: https://chromium-review.googlesource.com/707149Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#48395}
-
Ulan Degenbaev authored
Each concurrent marking task maintains task_state[i]->marked_bytes. When a task finishes, its local counter is flushed into global total_marked_bytes_ atomic counter. Bug: chromium:694255 Change-Id: I629467385e80bf229e06a4231673ceb5ef8e4aea Reviewed-on: https://chromium-review.googlesource.com/704823 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#48374}
-
- 26 Sep, 2017 1 commit
-
-
Ulan Degenbaev authored
After 52e8d0ab incremental marking observer is invoked ~8 times more often than before. This patch increases the allocation observer threshold for incremental marking and scales the step size based on the number of concurrent marking tasks. Bug: chromium:768664 TBR: mlippautz@chromium.org Change-Id: I0afd5dccd55f32c7f545d9c3a47edc20c6fd83db Reviewed-on: https://chromium-review.googlesource.com/683955Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#48154}
-
- 25 Sep, 2017 1 commit
-
-
Ulan Degenbaev authored
This patch ensures that the concurrent marking tasks do not use more than the half of the available background threads. Bug: chromium:694255 Change-Id: I67d6eb3e717945f777d0711bd094630573c78661 Reviewed-on: https://chromium-review.googlesource.com/678636 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#48130}
-
- 21 Aug, 2017 1 commit
-
-
Ulan Degenbaev authored
This makes live byte count updates on the main thread non-atomic. Bug: chromium:694255 TBR: mlippautz@chromium.org Change-Id: I84da2b0647f63ad9d8f2be757d305d58945a00ff Reviewed-on: https://chromium-review.googlesource.com/613623 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#47468}
-
- 11 Aug, 2017 1 commit
-
-
Ulan Degenbaev authored
This allows handling transitions arrays in concurrent marking Bug: chromium:694255 Change-Id: I28196fccbf03bfba7d7dada1884813be372ddb54 Reviewed-on: https://chromium-review.googlesource.com/610961 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#47303}
-
- 07 Aug, 2017 3 commits
-
-
Ulan Degenbaev authored
This reverts commit 20d4840e. Bug: chromium:694255 TBR: mlippautz@chromium.rg Change-Id: Ie7743ca5607e6ab6d7f5683180c698d0c08fcd66 Reviewed-on: https://chromium-review.googlesource.com/603367Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#47189}
-
Jakob Gruber authored
This reverts commit 82202251. Reason for revert: https://build.chromium.org/p/client.v8/builders/V8%20Linux64%20GC%20Stress%20-%20custom%20snapshot/builds/14346/steps/Mjsunit/logs/large-object-literal-.. Original change's description: > [heap] Improve concurrent marking pausing protocol. > > This patch allows the concurrent marker to process more objects before > checking for the interrupt request from the main thread. > > Bug: chromium:694255 > TBR: mlippautz@chromium.org > Change-Id: I876d3156ca9843196f2fdddbd8bd28d1a3f472b1 > Reviewed-on: https://chromium-review.googlesource.com/602131 > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Commit-Queue: Ulan Degenbaev <ulan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#47182} TBR=ulan@chromium.org,mlippautz@chromium.org Change-Id: I92ef49c4fb51468d5b5d689abbe5323f3637f1e6 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:694255 Reviewed-on: https://chromium-review.googlesource.com/603327Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#47187}
-
Ulan Degenbaev authored
This patch allows the concurrent marker to process more objects before checking for the interrupt request from the main thread. Bug: chromium:694255 TBR: mlippautz@chromium.org Change-Id: I876d3156ca9843196f2fdddbd8bd28d1a3f472b1 Reviewed-on: https://chromium-review.googlesource.com/602131Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#47182}
-
- 28 Jul, 2017 1 commit
-
-
Ulan Degenbaev authored
BUG=chromium:694255 Change-Id: I6684850ae9759f719e3ed665157eaea2581a65cf Reviewed-on: https://chromium-review.googlesource.com/590008 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#46964}
-
- 17 Jul, 2017 1 commit
-
-
Ulan Degenbaev authored
If the incremental marker discovers more marking work and the concurrent marking tasks have already exited, then new concurrent marking tasks are scheduled to help the main thread marker. BUG=chromium:694255 Change-Id: I559af62790e6034b23a412d3308ba8b6ae3d27c9 Reviewed-on: https://chromium-review.googlesource.com/574170Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#46703}
-
- 14 Jul, 2017 2 commits
-
-
Ulan Degenbaev authored
This reverts commit 20d5048a. Revert "[heap] Ensure that concurrent marking tasks exit before heap tear down." This reverts commit 387f65d4. Reason: concurrent marking tasks waiting for a signal from the main thread is susceptible to deadlocks. We should instead re-schedule concurrent marking threads once they exit. BUG=chromium:694255 Change-Id: I20db2f26b42e960f4cc04506d9598c1187b8a003 Reviewed-on: https://chromium-review.googlesource.com/571800 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#46671}
-
Michael Lippautz authored
Bug: chromium:738865 Change-Id: I663be62e73e9ba4e2f1aaededc6937d5ca1db179 Reviewed-on: https://chromium-review.googlesource.com/571780 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#46665}
-
- 13 Jul, 2017 1 commit
-
-
Ulan Degenbaev authored
BUG=chromium:694255 Change-Id: Id874d7427b52f5c2d1d7ae72d321cad8277f8082 Reviewed-on: https://chromium-review.googlesource.com/570035 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#46639}
-
- 10 Jul, 2017 1 commit
-
-
Ulan Degenbaev authored
BUG=chromium:694255 Change-Id: Ib0403a2d406428d2cd7896521abb6e95c3841c1c Reviewed-on: https://chromium-review.googlesource.com/563364 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#46505}
-
- 05 Jul, 2017 1 commit
-
-
Michael Lippautz authored
To be used with tuples of heap objects and sizes. Bug: chromium:738865 Change-Id: I29d9cf98bb2097cc8e1616aaf19a251507ffbd9e Reviewed-on: https://chromium-review.googlesource.com/559050Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#46407}
-
- 04 Jul, 2017 1 commit
-
-
Michael Lippautz authored
Bug: chromium:738865 Change-Id: I67b65f3006d6fe7e88854806f364d9863076b49b Reviewed-on: https://chromium-review.googlesource.com/558969 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#46397}
-