- 10 Dec, 2020 1 commit
-
-
Clemens Backes authored
So far we reported the script ID, but DevTools ignores that and uses the source url instead. That url was just set to "wasm ", which the frontend couldn't make any sense of. This CL fixes this by passing the source URL to the code create event, and also setting the position of the code inside the script (i.e. wasm module). R=thibaudm@chromium.org, petermarshall@chromium.org Bug: chromium:1125986 Change-Id: Ic41dcd2768c60fd6748468d3a89fc4ffccb35932 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2581543 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
Thibaud Michaud <thibaudm@chromium.org> Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#71695}
-
- 09 Dec, 2020 1 commit
-
-
Clemens Backes authored
We currently report "wasm " as the source URL on all wasm code, with no position information. This will change in a follow-up CL. To make that difference visible, extend a test to show the URL and position reported for wasm code. R=thibaudm@chromium.org Bug: chromium:1125986 Change-Id: I09f1820d591f27c1ff3c2acb41f8e279ac08a9e7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2575071Reviewed-by:
Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#71680}
-
- 08 Dec, 2020 3 commits
-
-
Clemens Backes authored
This is a reland of ab4d9717. The original CL did a std::move before the final use of the NativeModule. PS2 removes that. TBR=petermarshall@chromium.org, thibaudm@chromium.org Original change's description: > [wasm] Pass the script ID to code logging > > We didn't pass a script ID with the code creation events for profiling. > This made DevTools lose the connection to the wasm script, hence > jumping from the profiler entry to the source did not work. > > This CL changes the timing of code logging a bit such that the script is > always allocated before logging. In the queue of code to be logged we > then also store the script ID, and finally set it on the {CodeEntry} > object. > > R=thibaudm@chromium.org > > Bug: chromium:1125986 > Change-Id: I2248c1d520bc819436bbe732373f7a3446b64f48 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2575057 > Commit-Queue: Clemens Backes <clemensb@chromium.org> > Reviewed-by: Peter Marshall <petermarshall@chromium.org> > Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> > Cr-Commit-Position: refs/heads/master@{#71654} Bug: chromium:1125986 Cq-Include-Trybots: luci.v8.try:v8_linux64_ubsan_rel_ng Change-Id: I2a7c5fe04fff726836b1279e3d05b1702a4efb76 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2578980Reviewed-by:
Clemens Backes <clemensb@chromium.org> Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Reviewed-by:
Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#71663}
-
Clemens Backes authored
This reverts commit ab4d9717. Reason for revert: UBSan issues: https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Linux64%20UBSan/14184/overview Original change's description: > [wasm] Pass the script ID to code logging > > We didn't pass a script ID with the code creation events for profiling. > This made DevTools lose the connection to the wasm script, hence > jumping from the profiler entry to the source did not work. > > This CL changes the timing of code logging a bit such that the script is > always allocated before logging. In the queue of code to be logged we > then also store the script ID, and finally set it on the {CodeEntry} > object. > > R=thibaudm@chromium.org > > Bug: chromium:1125986 > Change-Id: I2248c1d520bc819436bbe732373f7a3446b64f48 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2575057 > Commit-Queue: Clemens Backes <clemensb@chromium.org> > Reviewed-by: Peter Marshall <petermarshall@chromium.org> > Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> > Cr-Commit-Position: refs/heads/master@{#71654} TBR=petermarshall@chromium.org,clemensb@chromium.org,thibaudm@chromium.org Change-Id: I03c90c77b55e770797a6d66b1d778992a047e07a No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:1125986 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2575070Reviewed-by:
Clemens Backes <clemensb@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#71660}
-
Clemens Backes authored
We didn't pass a script ID with the code creation events for profiling. This made DevTools lose the connection to the wasm script, hence jumping from the profiler entry to the source did not work. This CL changes the timing of code logging a bit such that the script is always allocated before logging. In the queue of code to be logged we then also store the script ID, and finally set it on the {CodeEntry} object. R=thibaudm@chromium.org Bug: chromium:1125986 Change-Id: I2248c1d520bc819436bbe732373f7a3446b64f48 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2575057 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Reviewed-by:
Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/master@{#71654}
-
- 07 Dec, 2020 1 commit
-
-
Clemens Backes authored
Import wrappers were only logged if logging was enabled during compilation. If the profiler is enabled later, and regular wasm code is logged via {NativeModule::LogWasmCodes}, the import wrappers were missing. This CL fixes the long-standing TODO, and adds tests which triggered that code path. Those tests were hanging before because the expected functions did never appear in the profile. Drive-by: If {WasmEngine::LogOutstandingCodesForIsolate} detects that code logging is disabled by now, it should still clear the {code_to_log} vector. R=thibaudm@chromium.org Bug: chromium:1125986, chromium:1141787 Change-Id: I2566ef369bb61a09488f2d932b6c10d92e4cb12f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2574696Reviewed-by:
Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#71645}
-
- 04 Dec, 2020 1 commit
-
-
Clemens Backes authored
We currently do not report a script ID for wasm code, i.e. the script id is 0. We cannot just print the script ID itself, as it is considered unstable. Thus this CL only makes us print whether it is set or not. In a follow-up CL where we fix setting script IDs for wasm code events the output will change. R=thibaudm@chromium.org Bug: chromium:1125986 Change-Id: Ibc52829ea8a5a5c9506e36390eb4c608bcab4624 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2571120 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/master@{#71616}
-
- 20 Nov, 2020 1 commit
-
-
Clemens Backes authored
We had a test which first enabled the profiler, and then compiled wasm code. In this case, all code objects were registered correctly and the profile looked as expected. This CL extends the test for also test another order: First compile the wasm code, then enable the profiler. In that case, we were reporting a wrong debug name of the exported wasm function. The name of that function is spec'ed to be the string representation of the function index. But for debugging, we want to see a more meaningful name, identical to the name we show when reporting the code during compilation. This fix requires handlifying the {SharedFunctionInfo::DebugName} method, because for exported wasm functions, it needs to allocate a new name on the JS heap. In order to avoid this allocation where possible, a second variant is added which returns a unique_ptr directly. This can be used in all places where the name is just being printed, which turned out to be the majority of cases ({DebugName().ToCString()}). R=petermarshall@chromium.org Bug: chromium:1141787 Change-Id: I0343c2f06f0b852007535ff07459b712801ead01 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2543931 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
Andreas Haas <ahaas@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#71308}
-
- 25 Feb, 2020 1 commit
-
-
Clemens Backes authored
This is a reland of 78defee4 Original change's description: > [inspector] Check that wasm wrappers appear in profiles > > This extends the existing wasm profiling test to also check that > wasm-to-js and js-to-wasm wrappers appear in the profiles as expected. > It thus serves as a regression test for the status quo. > > R=bmeurer@chromium.org > > Bug: chromium:1054386 > Change-Id: I5d4d8e6a252c6eb266b910621fca43a6ff0837bd > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2066970 > Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> > Commit-Queue: Clemens Backes <clemensb@chromium.org> > Cr-Commit-Position: refs/heads/master@{#66401} TBR=bmeurer@chromium.org Bug: chromium:1054386, v8:10266 Change-Id: Iae04c0564ee8f0330d61ce954d895a41497c5a85 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2071260Reviewed-by:
Clemens Backes <clemensb@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#66424}
-
- 24 Feb, 2020 2 commits
-
-
Clemens Backes authored
This reverts commit 78defee4. Reason for revert: Timeout on TSan: https://ci.chromium.org/p/v8/builders/ci/V8%20Linux64%20TSAN/30410 Original change's description: > [inspector] Check that wasm wrappers appear in profiles > > This extends the existing wasm profiling test to also check that > wasm-to-js and js-to-wasm wrappers appear in the profiles as expected. > It thus serves as a regression test for the status quo. > > R=bmeurer@chromium.org > > Bug: chromium:1054386 > Change-Id: I5d4d8e6a252c6eb266b910621fca43a6ff0837bd > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2066970 > Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> > Commit-Queue: Clemens Backes <clemensb@chromium.org> > Cr-Commit-Position: refs/heads/master@{#66401} TBR=clemensb@chromium.org,bmeurer@chromium.org Change-Id: Iac4299d5a4dc74041fbceac98cd2c2b96b9425df No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:1054386 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2069328Reviewed-by:
Clemens Backes <clemensb@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#66406}
-
Clemens Backes authored
This extends the existing wasm profiling test to also check that wasm-to-js and js-to-wasm wrappers appear in the profiles as expected. It thus serves as a regression test for the status quo. R=bmeurer@chromium.org Bug: chromium:1054386 Change-Id: I5d4d8e6a252c6eb266b910621fca43a6ff0837bd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2066970Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#66401}
-
- 20 Feb, 2019 1 commit
-
-
Clemens Hammacher authored
This is a reland of 6202c445. Moved skipped test from 'variant == jitless' to 'lite_mode or variant == jitless'. Original change's description: > [inspector] Add wasm profiling test > > This adds a first simple test to check that CPU profiles contain wasm > function names. > > R=herhut@chromium.org, kozyatinskiy@chromium.org > > Bug: v8:8783 > Change-Id: I26b1fd2b7ec555c073d80a464ee8a799b017b07a > Reviewed-on: https://chromium-review.googlesource.com/c/1454597 > Commit-Queue: Clemens Hammacher <clemensh@chromium.org> > Reviewed-by: Stephan Herhut <herhut@chromium.org> > Cr-Commit-Position: refs/heads/master@{#59703} TBR=herhut@chromium.org Bug: v8:8783 Change-Id: I4f68db86bf1caa4f0d68dd4fa227ded25bf5145a Reviewed-on: https://chromium-review.googlesource.com/c/1477678Reviewed-by:
Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#59730}
-
- 19 Feb, 2019 2 commits
-
-
Sathya Gunasekaran authored
This reverts commit 6202c445. Reason for revert: times out on arm https://logs.chromium.org/logs/v8/buildbucket/cr-buildbucket.appspot.com/8921075891748393232/+/steps/Check_-_default/0/logs/console-profile-wasm/0 Original change's description: > [inspector] Add wasm profiling test > > This adds a first simple test to check that CPU profiles contain wasm > function names. > > R=herhut@chromium.org, kozyatinskiy@chromium.org > > Bug: v8:8783 > Change-Id: I26b1fd2b7ec555c073d80a464ee8a799b017b07a > Reviewed-on: https://chromium-review.googlesource.com/c/1454597 > Commit-Queue: Clemens Hammacher <clemensh@chromium.org> > Reviewed-by: Stephan Herhut <herhut@chromium.org> > Cr-Commit-Position: refs/heads/master@{#59703} TBR=yangguo@chromium.org,kozyatinskiy@chromium.org,clemensh@chromium.org,herhut@chromium.org Change-Id: Ib211a38a32ee08c18e4a19f05d9fc68d6a2d2901 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:8783 Reviewed-on: https://chromium-review.googlesource.com/c/1475914Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Cr-Commit-Position: refs/heads/master@{#59704}
-
Clemens Hammacher authored
This adds a first simple test to check that CPU profiles contain wasm function names. R=herhut@chromium.org, kozyatinskiy@chromium.org Bug: v8:8783 Change-Id: I26b1fd2b7ec555c073d80a464ee8a799b017b07a Reviewed-on: https://chromium-review.googlesource.com/c/1454597 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by:
Stephan Herhut <herhut@chromium.org> Cr-Commit-Position: refs/heads/master@{#59703}
-