| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
Separates ETW Stack Walking Events from Generic ETW Events All ETW Events are controlled by v8_enable_system_instrumentation. This flag is turned off when perfetto is enabled since traces events flowing through TRACE_EVENT macros can't be intercepted by Recorder. Since, stack walking Events don't use TRACE_EVENT it can be turned back on, when using perfetto. Hence, creating a separate Build Flag for emitting stack walking event until the recorder is ported. Bug: v8:11043 Change-Id: I6cdb81400780e54fddf6d6e2476cad29c60483d2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3704465 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Commit-Queue: Suraj Sharma <surshar@microsoft.com> Cr-Commit-Position: refs/heads/main@{#81879} | 3 年前 | |
2026.03.30 arkweb_144代码蓝黄同步 Signed-off-by: jiujiaoxiaogula <sujiahao10@huawei.com> Change-Id: I00194d339064f999dedfc211cd5af5501cbed0fb | 3 个月前 | |
Reland "[tracing] Remove base/trace_event/common dependency" This reland additionally removes base from generate-header-include-checks.py, as the root directory got removed. See https://crrev.com/c/5529240/1..3. Original change's description: > Revert "[tracing] Remove base/trace_event/common dependency" > > This reverts commit 993b79e7f5121bc1ff81cbc31ccdd42729b4f054. > > Reason for revert: > https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Linux64%20-%20debug%20-%20header%20includes%20-%20builder/15361/overview > > And this, but not consistent it seems. Maybe an incremental > build problem: > https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Linux%20-%20builder/73951/overview > > Original change's description: > > [tracing] Remove base/trace_event/common dependency > > > > Currently, V8 depends on base/trace_event/common which includes a single > > file being shared. It contains two tracing macro implementations: one > > which is based on perfetto, and a second legacy one. > > > > V8 is the only client of the legacy version, which got removed in > > https://crrev.com/c/5505657 and causes a failure of our roll (e.g. > > https://crrev.com/c/5512234). > > > > This change moves the legacy code into V8, removes the obsolete > > dependency, and refactors the build configurations. > > > > Bug: 338608342 > > Change-Id: I9254592b5c581d64807fe25c92ac931356569453 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5522493 > > Commit-Queue: Alexander Schulze <alexschulze@chromium.org> > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > Reviewed-by: Michael Achenbach <machenbach@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#93823} > > Bug: 338608342 > Change-Id: Iefbd2c7e9a8c0af0f437a60faa345db72879d50d > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5529239 > Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> > Commit-Queue: Alexander Schulze <alexschulze@chromium.org> > Owners-Override: Michael Achenbach <machenbach@chromium.org> > Auto-Submit: Michael Achenbach <machenbach@chromium.org> > Cr-Commit-Position: refs/heads/main@{#93825} Bug: 338608342 Change-Id: I90b8def2f3bf0142b3bc545b95cb3ebb689ec46c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5529240 Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Alexander Schulze <alexschulze@chromium.org> Cr-Commit-Position: refs/heads/main@{#93832} | 2 年前 | |
buganizer: fix component IDs in DIR_METADATA This only matches the old monorail components. Bug: 341800538 Change-Id: Id74fbdb3b9be0c858b77af84966c6c37adf78c5c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6025833 Reviewed-by: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Auto-Submit: Paul Semel <paulsemel@chromium.org> Commit-Queue: Paul Semel <paulsemel@chromium.org> Cr-Commit-Position: refs/heads/main@{#97252} | 1 年前 | |
Remove ulan@ from OWNERS Change-Id: I4a30e0f01e35eb0824f5abeec62d55d62970b59f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2910781 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Hannes Payer <hpayer@chromium.org> Commit-Queue: Hannes Payer <hpayer@chromium.org> Cr-Commit-Position: refs/heads/master@{#75016} | 4 年前 | |
heap: Force GC on teardown with --stress-compaction GC on teardown is sometimes necessary with unified heap. Add a stress flag to flush out potential issues with a GC right before teardown. Most fixes are in tests. The exception is that Oilpan's sweeper needs to post non-nestable tasks to prevent sweeping finalization while sweeping scopes are still open. Change-Id: I599af0d7594425ff07adcbfee4d828302dd7afc8 Fixed: 408234438 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6430028 Reviewed-by: Igor Sheludko <ishell@chromium.org> Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#99673} | 1 年前 | |
heap: Force GC on teardown with --stress-compaction GC on teardown is sometimes necessary with unified heap. Add a stress flag to flush out potential issues with a GC right before teardown. Most fixes are in tests. The exception is that Oilpan's sweeper needs to post non-nestable tasks to prevent sweeping finalization while sweeping scopes are still open. Change-Id: I599af0d7594425ff07adcbfee4d828302dd7afc8 Fixed: 408234438 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6430028 Reviewed-by: Igor Sheludko <ishell@chromium.org> Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#99673} | 1 年前 | |
[platform] Rename Call[Blocking/LowPriority]OnWorkerThread() to PostTaskOnWorkerThread PostTaskOnWorkerThread takes a priority argument, instead of exposing multiple methods. CallOnWorkerThread is kept around because Chrome codebase has a call to it that needs to be switched. It will be removed in a follow-up. This should address https://chromium-review.googlesource.com/c/v8/v8/+/5952524 Change-Id: Ie45941b6996737a7ef04994c32dfa775717f4aa3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5350692 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org> Cr-Commit-Position: refs/heads/main@{#97426} | 1 年前 | |
[libplatform] Spawn more tasks from DefaultJobState::Join If DefaultJobState::Join is called before any worker tasks were spawned (e.g. right after Platform::CreateJob), it should spawn the required number of worker tasks (mimicing what Platform::PostJob followed by Join would do, but with less context switches). This fixes regressions we got from switching from Platform::PostJob to Platform::CreateJob. R=mlippautz@chromium.org CC=etiennep@chromium.org Bug: chromium:1348512 Change-Id: Ic7984d12a28fc67f4b2f51ddc2ba5a406e43c127 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3804600 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#82178} | 3 年前 | |
[wasm] Fix crash with --single-threaded If --single-threaded is specified, we should not spawn a background job for caching, but instead execute the callbacks immediately. R=mliedtke@chromium.org Fixed: 388934347 Change-Id: Idb3dfd7529716c411bd44ef875f9fab19fe71a3f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6343292 Reviewed-by: Matthias Liedtke <mliedtke@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#99218} | 1 年前 | |
[base] Merge SpinningMutex back into Mutex They are now the same; beyond that we can't do ave THREAD_SAFETY_ANALYSIS on a bunch of previous SpinningMutex cases, so we'll need to propagate this into Mutex. Bug: 384940357 Change-Id: Ifbd4ffc4090738455036f32d9a5cf813b9f15781 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6244422 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#98597} | 1 年前 | |
[pku] do pkey kernel version check in default platform Change-Id: Iae7a1394c58648227767789b3165d41f2136159d Bug: v8:13355 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4561369 Reviewed-by: Clemens Backes <clemensb@chromium.org> Commit-Queue: Stephen Röttger <sroettger@google.com> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#87876} | 3 年前 | |
Reland "[api] Implement basic ThreadIsolatedAllocator" This is a reland of commit b910cff3d43e8d7408b7c03cbb4cfb0539d212b7 Fix: somehow the android bot doesn't like the pkey_alloc syscall. I replaced it with a conditional call to the libc function (declaring the pkey_ fns as weak and checking for existence). I also added a pkey_free in the destructor. Original change's description: > [api] Implement basic ThreadIsolatedAllocator > > Change-Id: If95dfce5b8bd0fcbf1445e470f7d243c0b361582 > Bug: v8:13355 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4518774 > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Commit-Queue: Stephen Röttger <sroettger@google.com> > Cr-Commit-Position: refs/heads/main@{#87643} Bug: v8:13355 Change-Id: Id9da6e3ee064807b934e9b2ed6f9f8956ead21f2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4535935 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Stephen Röttger <sroettger@google.com> Cr-Commit-Position: refs/heads/main@{#87714} | 3 年前 | |
[v8-tasks] Add source location to v8::TaskRunner, step 1/4. Steps: 1. Add Post*TaskImpl variants of v8::TaskRunner::Post*Task methods, which take a v8::SourceLocation argument. Embedders should override these methods. 2. Override Post*TaskImpl instead of Post*Task in Chromium. 3. Override Post*TaskImpl instead of Post*Task in Node.js. 4. Make Post*Task methods non-virtual and add a v8::SourceLocation argument which defaults to SourceLocation::Current(). Bug: chromium:1424158 Change-Id: I0606308d31d1f060e3f7ecc1a123759fb91ba8fa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5300502 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Francois Pierre Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/main@{#92411} | 2 年前 | |
[v8-tasks] Add source location to v8::TaskRunner, step 1/4. Steps: 1. Add Post*TaskImpl variants of v8::TaskRunner::Post*Task methods, which take a v8::SourceLocation argument. Embedders should override these methods. 2. Override Post*TaskImpl instead of Post*Task in Chromium. 3. Override Post*TaskImpl instead of Post*Task in Node.js. 4. Make Post*Task methods non-virtual and add a v8::SourceLocation argument which defaults to SourceLocation::Current(). Bug: chromium:1424158 Change-Id: I0606308d31d1f060e3f7ecc1a123759fb91ba8fa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5300502 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Francois Pierre Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/main@{#92411} | 2 年前 | |
[platform] Move DelayedTaskQueue lock to parent runner Avoid the second lock inside DelayedTaskQueue by moving the locking and waiting logic to the DefaultWorkerThreadsTaskRunner. Change-Id: Ied5d6e387113fdd7704b7be4f325cdb9f0924bb8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4665345 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#88641} | 2 年前 | |
Remove superfluous mutex.h include Remove src/base/platform/mutex.h includes in headers that do not mention "Mutex". Bug: 40318405 Change-Id: I6cb94b56a22b438387457ecd9c09d4fb2653a525 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6282736 Commit-Queue: Lei Zhang <thestig@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#98845} | 1 年前 | |
[base] Merge SpinningMutex back into Mutex They are now the same; beyond that we can't do ave THREAD_SAFETY_ANALYSIS on a bunch of previous SpinningMutex cases, so we'll need to propagate this into Mutex. Bug: 384940357 Change-Id: Ifbd4ffc4090738455036f32d9a5cf813b9f15781 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6244422 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#98597} | 1 年前 | |
[base] Merge SpinningMutex back into Mutex They are now the same; beyond that we can't do ave THREAD_SAFETY_ANALYSIS on a bunch of previous SpinningMutex cases, so we'll need to propagate this into Mutex. Bug: 384940357 Change-Id: Ifbd4ffc4090738455036f32d9a5cf813b9f15781 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6244422 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#98597} | 1 年前 | |
Reland "[d8] Remove maximum workers limitation" This is a reland of a0728e869b87f604945388e2fe2a5bf2f565733c Original change's description: > [d8] Remove maximum workers limitation > > This CL refactors the lifetime management of the v8::Worker C++ object > and in the process lifts the 100 maximum worker limitation. To do this, > it uses a Managed<v8::Worker> heap object and attaches the managed to > the API worker object. > > R=mstarzinger@chromium.org > BUG=v8:9524 > > Change-Id: I279b7aeb6645a87f9108ee6f572105739721cef4 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1715453 > Commit-Queue: Ben Titzer <titzer@chromium.org> > Reviewed-by: Clemens Hammacher <clemensh@chromium.org> > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> > Cr-Commit-Position: refs/heads/master@{#62932} Bug: v8:9524 Change-Id: I7d903fb12ddb00909a9429455f46c55db2fd02de Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1722562 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Ben Titzer <titzer@chromium.org> Cr-Commit-Position: refs/heads/master@{#62974} | 6 年前 | |
Remove some unused includes (4) Mostly src/codegen, src/compiler, src/interpreter, src/libplatform. Drive-by: Remove some unreachable code. Bug: v8:13006 Change-Id: I1a9467f7e42531c545f660d35416c388e8ef9d3c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3749193 Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#81613} | 3 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 3 年前 | ||
| 3 个月前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 4 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 3 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 6 年前 | ||
| 3 年前 |