commit | 64dc0d1354d65e0cb3e42294429275a0d3b7209d | [log] [tgz] |
---|---|---|
author | timothy_horton@apple.com <timothy_horton@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Wed Dec 04 09:58:21 2019 +0000 |
committer | timothy_horton@apple.com <timothy_horton@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Wed Dec 04 09:58:21 2019 +0000 |
tree | 2c4f3120ea5ea0952dad383888dd61e95cdf349c | |
parent | 2f096c6dc197a4cd20445551911de7da29b5a61c [diff] |
Introduce a GPU process https://bugs.webkit.org/show_bug.cgi?id=204343 Reviewed by Simon Fraser. Source/JavaScriptCore: * Configurations/FeatureDefines.xcconfig: Add ENABLE(GPU_PROCESS). Source/WebCore: * Configurations/FeatureDefines.xcconfig: Add ENABLE(GPU_PROCESS). * en.lproj/Localizable.strings: Add a string for the user-visible name of the GPU process. Source/WebCore/PAL: * Configurations/FeatureDefines.xcconfig: Source/WebKit: Add a GPU process. This process is destined to be used as a proxy between WebKit and the underlying graphics mechanisms; in the case of the Cocoa ports, it will specifically gate access to IOKit and a few media-related daemons. In this patch, the process is a UI-process singleton; the WebKit client application gets a single GPU process for all rendering, regardless of the number of Web Content processes, process pools, or web views. For now, it is just a shell of a process; functionality will be added in future patches! * Configurations/FeatureDefines.xcconfig: Add ENABLE(GPU_PROCESS). * Configurations/GPUService.xcconfig: Added. * GPUProcess/EntryPoint/Cocoa/XPCService/GPUService/Info-OSX.plist: Added. * GPUProcess/EntryPoint/Cocoa/XPCService/GPUService/Info-iOS.plist: Added. * GPUProcess/EntryPoint/Cocoa/XPCService/GPUServiceEntryPoint.mm: Added. * Shared/AuxiliaryProcess.h: * Shared/EntryPointUtilities/Cocoa/XPCService/XPCServiceEntryPoint.h: * Shared/EntryPointUtilities/Cocoa/XPCService/XPCServiceMain.mm: * Platform/ExtraPrivateSymbolsForTAPI.h: * Shared/mac/AuxiliaryProcessMac.mm: * Sources.txt: * SourcesCocoa.txt: * WebKit.xcodeproj/project.pbxproj: * Configurations/WebKit.xcconfig: * DerivedSources-input.xcfilelist: * DerivedSources-output.xcfilelist: * DerivedSources.make: * UIProcess/AuxiliaryProcessProxy.cpp: (WebKit::AuxiliaryProcessProxy::getLaunchOptions): * UIProcess/Launcher/ProcessLauncher.h: * UIProcess/Launcher/mac/ProcessLauncherMac.mm: (WebKit::serviceName): (WebKit::shouldLeakBoost): Add a new target for the XPC service, and do the paperwork to launch it. * GPUProcess/GPUConnectionToWebProcess.cpp: Added. * GPUProcess/GPUConnectionToWebProcess.h: Added. * GPUProcess/GPUConnectionToWebProcess.messages.in: Added. On the GPU process side, the incoming connection from the Web Content process. * GPUProcess/GPUProcess.cpp: Added. * GPUProcess/GPUProcess.h: Added. * GPUProcess/GPUProcess.messages.in: Added. * GPUProcess/GPUProcessCreationParameters.cpp: Added. * GPUProcess/GPUProcessCreationParameters.h: Added. * GPUProcess/cocoa/GPUProcessCocoa.mm: Added. * GPUProcess/ios/GPUProcessIOS.mm: Added. * GPUProcess/mac/GPUProcessMac.mm: Added. Add the shell of the GPU process. Mostly stolen from the Networking process. * UIProcess/GPU/GPUProcessProxy.cpp: Added. (WebKit::GPUProcessProxy::singleton): (WebKit::GPUProcessProxy::GPUProcessProxy): (WebKit::GPUProcessProxy::~GPUProcessProxy): (WebKit::GPUProcessProxy::getLaunchOptions): (WebKit::GPUProcessProxy::connectionWillOpen): (WebKit::GPUProcessProxy::processWillShutDown): (WebKit::GPUProcessProxy::getGPUProcessConnection): (WebKit::GPUProcessProxy::openGPUProcessConnection): (WebKit::GPUProcessProxy::gpuProcessCrashed): (WebKit::GPUProcessProxy::didReceiveMessage): (WebKit::GPUProcessProxy::didReceiveSyncMessage): (WebKit::GPUProcessProxy::didClose): (WebKit::GPUProcessProxy::didReceiveInvalidMessage): (WebKit::GPUProcessProxy::didFinishLaunching): (WebKit::GPUProcessProxy::updateProcessAssertion): * UIProcess/GPU/GPUProcessProxy.h: Added. * UIProcess/GPU/GPUProcessProxy.messages.in: Added. On the UI process side, the GPUProcessProxy is the singleton that owns the GPU process for the process. * GPUProcess/mac/com.apple.WebKit.GPUProcess.sb.in: Added. This sandbox profile is copied from the Web Content process. We will cut it down in the future, but this is a sensible starting point, since the code that is moving to the GPU process is code that currently lives in the Web Content process. * UIProcess/Network/NetworkProcessProxy.cpp: (WebKit::NetworkProcessProxy::updateProcessAssertion): Fix a logging typo I stumbled upon. * UIProcess/WebProcessPool.cpp: (WebKit::WebProcessPool::getGPUProcessConnection): * UIProcess/WebProcessPool.h: * UIProcess/WebProcessProxy.cpp: (WebKit::WebProcessProxy::getGPUProcessConnection): * UIProcess/WebProcessProxy.h: * UIProcess/WebProcessProxy.messages.in: Add a message from Web->UI to retrieve the GPU process connection. In the future, we should send this along with the Web Content process initialization message, but this mechanism doesn't exist yet. * WebProcess/GPU/GPUProcessConnection.cpp: Added. (WebKit::GPUProcessConnection::GPUProcessConnection): (WebKit::GPUProcessConnection::~GPUProcessConnection): (WebKit::GPUProcessConnection::didReceiveMessage): (WebKit::GPUProcessConnection::didReceiveSyncMessage): (WebKit::GPUProcessConnection::didClose): (WebKit::GPUProcessConnection::didReceiveInvalidMessage): * WebProcess/GPU/GPUProcessConnection.h: Added. (WebKit::GPUProcessConnection::create): (WebKit::GPUProcessConnection::connection): * WebProcess/GPU/GPUProcessConnection.messages.in: Added. * WebProcess/GPU/GPUProcessConnectionInfo.h: Added. (WebKit::GPUProcessConnectionInfo::identifier): (WebKit::GPUProcessConnectionInfo::releaseIdentifier): (WebKit::GPUProcessConnectionInfo::encode const): (WebKit::GPUProcessConnectionInfo::decode): In the Web Content process, GPUProcessConnection is the process-wide connection to the GPU process. All pages in a given Web Content process use the same connection to talk to the singleton GPU process. * WebProcess/WebProcess.cpp: (WebKit::getGPUProcessConnection): (WebKit::WebProcess::ensureGPUProcessConnection): (WebKit::WebProcess::gpuProcessConnectionClosed): * WebProcess/WebProcess.h: (WebKit::WebProcess::existingGPUProcessConnection): In the Web Content process, make it possible for clients to retrieve the GPU process connection. Source/WebKitLegacy/mac: * Configurations/FeatureDefines.xcconfig: Tools: * TestWebKitAPI/Configurations/FeatureDefines.xcconfig: git-svn-id: http://svn.webkit.org/repository/webkit/trunk@253098 268f45cc-cd09-0410-ab3c-d52691b4dbfc
WebKit is a cross-platform web browser engine. On iOS and macOS, it powers Safari, Mail, iBooks, and many other applications.
Visit WebKit Feature Status page to see which Web API has been implemented, in development, or under consideration.
On macOS, download Safari Technology Preview to test the latest version of WebKit. On Linux, download Epiphany Technology Preview. On Windows, you'll have to build it yourself.
Once your bug is filed, you will receive email when it is updated at each stage in the bug life cycle. After the bug is considered fixed, you may be asked to download the latest nightly and confirm that the fix works for you.
On Windows, follow the instructions on our website.
Run the following command to clone WebKit's Git SVN repository:
git clone git://git.webkit.org/WebKit.git WebKit
or
git clone https://git.webkit.org/git/WebKit.git WebKit
If you want to be able to commit changes to the repository, or just want to check out branches that aren’t contained in WebKit.git, you will need track WebKit's Subversion repository. You can run the following command to configure this and other options of the new Git clone for WebKit development.
Tools/Scripts/webkit-patch setup-git-clone
For information about this, and other aspects of using Git with WebKit, read the wiki page.
If you don‘t want to use Git, run the following command to check out WebKit’s Subversion repository:
svn checkout https://svn.webkit.org/repository/webkit/trunk WebKit
Install Xcode and its command line tools if you haven't done so already:
xcode-select --install
Run the following command to build a debug build with debugging symbols and assertions:
Tools/Scripts/build-webkit --debug
For performance testing, and other purposes, use --release
instead.
You can open WebKit.xcworkspace
to build and debug WebKit within Xcode.
If you don't use a custom build location in Xcode preferences, you have to update the workspace settings to use WebKitBuild
directory. In menu bar, choose File > Workspace Settings, then click the Advanced button, select “Custom”, “Relative to Workspace”, and enter WebKitBuild
for both Products and Intermediates.
The first time after you install a new Xcode, you will need to run the following command to enable Xcode to build command line tools for iOS Simulator:
sudo Tools/Scripts/configure-xcode-for-ios-development
Without this step, you will see the error message: “target specifies product type ‘com.apple.product-type.tool’, but there’s no such product type for the ‘iphonesimulator’ platform.
” when building target JSCLLIntOffsetsExtractor
of project JavaScriptCore
.
Run the following command to build a debug build with debugging symbols and assertions for iOS:
Tools/Scripts/build-webkit --debug --ios-simulator
For production builds:
cmake -DPORT=GTK -DCMAKE_BUILD_TYPE=RelWithDebInfo -GNinja ninja sudo ninja install
For development builds:
Tools/gtk/install-dependencies Tools/Scripts/update-webkitgtk-libs Tools/Scripts/build-webkit --gtk --debug
For more information on building WebKitGTK+, see the wiki page.
For production builds:
cmake -DPORT=WPE -DCMAKE_BUILD_TYPE=RelWithDebInfo -GNinja ninja sudo ninja install
For development builds:
Tools/wpe/install-dependencies Tools/Scripts/update-webkitwpe-libs Tools/Scripts/build-webkit --wpe --debug
For building WebKit on Windows, see the wiki page.
Run the following command to launch Safari with your local build of WebKit:
Tools/Scripts/run-safari --debug
The run-safari
script sets the DYLD_FRAMEWORK_PATH
environment variable to point to your build products, and then launches /Applications/Safari.app
. DYLD_FRAMEWORK_PATH
tells the system loader to prefer your build products over the frameworks installed in /System/Library/Frameworks
.
To run other applications with your local build of WebKit, run the following command:
Tools/Scripts/run-webkit-app <application-path>
Run the following command to launch iOS simulator with your local build of WebKit:
run-safari --debug --ios-simulator
In both cases, if you have built release builds instead, use --release
instead of --debug
.
If you have a development build, you can use the run-minibrowser script, e.g.:
run-minibrowser --debug --wpe
Pass one of --gtk
, --jsc-only
, or --wpe
to indicate the port to use.
Congratulations! You’re up and running. Now you can begin coding in WebKit and contribute your fixes and new features to the project. For details on submitting your code to the project, read Contributing Code.