blob: 38f428e90aaa185f59cefe4fee46d9a5ed6546f4 [file] [log] [blame]
[email protected]7de84042012-02-21 16:04:501// Copyright (c) 2012 The Chromium Authors. All rights reserved.
license.botbf09a502008-08-24 00:55:552// Use of this source code is governed by a BSD-style license that can be
3// found in the LICENSE file.
initial.commit09911bf2008-07-26 23:55:294
[email protected]6476c72c2011-02-11 18:46:195// Defining IPC Messages
initial.commit09911bf2008-07-26 23:55:296//
[email protected]6476c72c2011-02-11 18:46:197// Your IPC messages will be defined by macros inside of an XXX_messages.h
8// header file. Most of the time, the system can automatically generate all
9// of messaging mechanism from these definitions, but sometimes some manual
10// coding is required. In these cases, you will also have an XXX_messages.cc
philipjb3b3f8e2015-08-12 08:30:0111// implementation file as well.
[email protected]6476c72c2011-02-11 18:46:1912//
13// The senders of your messages will include your XXX_messages.h file to
14// get the full set of definitions they need to send your messages.
15//
16// Each XXX_messages.h file must be registered with the IPC system. This
17// requires adding two things:
[email protected]f9509812012-10-23 23:03:3518// - An XXXMsgStart value to the IPCMessageStart enum in ipc_message_start.h
[email protected]6476c72c2011-02-11 18:46:1919// - An inclusion of XXX_messages.h file in a message generator .h file
20//
21// The XXXMsgStart value is an enumeration that ensures uniqueness for
22// each different message file. Later, you will use this inside your
[email protected]e86a2552011-11-11 00:21:0223// XXX_messages.h file before invoking message declaration macros:
[email protected]6476c72c2011-02-11 18:46:1924// #define IPC_MESSAGE_START XXXMsgStart
25// ( ... your macro invocations go here ... )
26//
27// Message Generator Files
28//
29// A message generator .h header file pulls in all other message-declaring
30// headers for a given component. It is included by a message generator
31// .cc file, which is where all the generated code will wind up. Typically,
[email protected]d7a5e3e2011-03-12 16:28:3632// you will use an existing generator (e.g. common_message_generator.cc
33// in /chrome/common), but there are circumstances where you may add a
34// new one.
[email protected]6476c72c2011-02-11 18:46:1935//
philipjb3b3f8e2015-08-12 08:30:0136// In the rare circumstances where you can't re-use an existing file,
[email protected]6476c72c2011-02-11 18:46:1937// your YYY_message_generator.cc file for a component YYY would contain
38// the following code:
39// // Get basic type definitions.
[email protected]21fa3a12010-12-08 23:34:1640// #define IPC_MESSAGE_IMPL
[email protected]6476c72c2011-02-11 18:46:1941// #include "path/to/YYY_message_generator.h"
42// // Generate constructors.
43// #include "ipc/struct_constructor_macros.h"
44// #include "path/to/YYY_message_generator.h"
45// // Generate destructors.
46// #include "ipc/struct_destructor_macros.h"
47// #include "path/to/YYY_message_generator.h"
rockot0457af102016-02-05 02:12:3248// // Generate param traits size methods.
49// #include "ipc/param_traits_size_macros.h"
50// namespace IPC {
51// #include "path/to/YYY_message_generator.h"
52// } // namespace IPC
[email protected]6476c72c2011-02-11 18:46:1953// // Generate param traits write methods.
54// #include "ipc/param_traits_write_macros.h"
[email protected]d7a5e3e2011-03-12 16:28:3655// namespace IPC {
[email protected]6476c72c2011-02-11 18:46:1956// #include "path/to/YYY_message_generator.h"
[email protected]d7a5e3e2011-03-12 16:28:3657// } // namespace IPC
[email protected]6476c72c2011-02-11 18:46:1958// // Generate param traits read methods.
59// #include "ipc/param_traits_read_macros.h"
[email protected]d7a5e3e2011-03-12 16:28:3660// namespace IPC {
[email protected]6476c72c2011-02-11 18:46:1961// #include "path/to/YYY_message_generator.h"
[email protected]d7a5e3e2011-03-12 16:28:3662// } // namespace IPC
[email protected]6476c72c2011-02-11 18:46:1963// // Generate param traits log methods.
64// #include "ipc/param_traits_log_macros.h"
[email protected]d7a5e3e2011-03-12 16:28:3665// namespace IPC {
[email protected]6476c72c2011-02-11 18:46:1966// #include "path/to/YYY_message_generator.h"
67// } // namespace IPC
initial.commit09911bf2008-07-26 23:55:2968//
[email protected]6476c72c2011-02-11 18:46:1969// In cases where manual generation is required, in your XXX_messages.cc
70// file, put the following after all the includes for param types:
71// #define IPC_MESSAGE_IMPL
72// #include "XXX_messages.h"
73// (... implementation of traits not auto-generated ...)
74//
75// Multiple Inclusion
76//
77// The XXX_messages.h file will be multiply-included by the
78// YYY_message_generator.cc file, so your XXX_messages file can't be
79// guarded in the usual manner. Ideally, there will be no need for any
philipjb3b3f8e2015-08-12 08:30:0180// inclusion guard, since the XXX_messages.h file should consist solely
[email protected]6476c72c2011-02-11 18:46:1981// of inclusions of other headers (which are self-guarding) and IPC
82// macros (which are multiply evaluating).
83//
[email protected]01c86ec2012-07-11 19:01:4384// Note that #pragma once cannot be used here; doing so would mark the whole
[email protected]6476c72c2011-02-11 18:46:1985// file as being singly-included. Since your XXX_messages.h file is only
86// partially-guarded, care must be taken to ensure that it is only included
87// by other .cc files (and the YYY_message_generator.h file). Including an
88// XXX_messages.h file in some other .h file may result in duplicate
89// declarations and a compilation failure.
90//
91// Type Declarations
92//
93// It is generally a bad idea to have type definitions in a XXX_messages.h
94// file; most likely the typedef will then be used in the message, as opposed
philipjb3b3f8e2015-08-12 08:30:0195// to the struct itself. Later, an IPC message dispatcher will need to call
[email protected]6476c72c2011-02-11 18:46:1996// a function taking that type, and that function is declared in some other
97// header. Thus, in order to get the type definition, the other header
98// would have to include the XXX_messages.h file, violating the rule above
99// about not including XXX_messages.h file in other .h files.
100//
101// One approach here is to move these type definitions to another (guarded)
102// .h file and include this second .h in your XXX_messages.h file. This
103// is still less than ideal, because the dispatched function would have to
104// redeclare the typedef or include this second header. This may be
105// reasonable in a few cases.
106//
107// Failing all of the above, then you will want to bracket the smallest
108// possible section of your XXX_messages.h file containing these types
109// with an include guard macro. Be aware that providing an incomplete
110// class type declaration to avoid pulling in a long chain of headers is
111// acceptable when your XXX_messages.h header is being included by the
112// message sending caller's code, but not when the YYY_message_generator.c
philipjb3b3f8e2015-08-12 08:30:01113// is building the messages. In addition, due to the multiple inclusion
[email protected]6476c72c2011-02-11 18:46:19114// restriction, these type ought to be guarded. Follow a convention like:
115// #ifndef SOME_GUARD_MACRO
116// #define SOME_GUARD_MACRO
117// class some_class; // One incomplete class declaration
118// class_some_other_class; // Another incomplete class declaration
119// #endif // SOME_GUARD_MACRO
120// #ifdef IPC_MESSAGE_IMPL
[email protected]c13849c2014-06-18 17:32:42121// #include "path/to/some_class.h" // Full class declaration
122// #include "path/to/some_other_class.h" // Full class declaration
[email protected]6476c72c2011-02-11 18:46:19123// #endif // IPC_MESSAGE_IMPL
124// (.. IPC macros using some_class and some_other_class ...)
125//
126// Macro Invocations
127//
128// You will use IPC message macro invocations for three things:
129// - New struct definitions for IPC
130// - Registering existing struct and enum definitions with IPC
131// - Defining the messages themselves
132//
133// New structs are defined with IPC_STRUCT_BEGIN(), IPC_STRUCT_MEMBER(),
134// IPC_STRUCT_END() family of macros. These cause the XXX_messages.h
135// to proclaim equivalent struct declarations for use by callers, as well
136// as later registering the type with the message generation. Note that
137// IPC_STRUCT_MEMBER() is only permitted inside matching calls to
[email protected]dedd0a92013-06-04 07:20:32138// IPC_STRUCT_BEGIN() / IPC_STRUCT_END(). There is also an
139// IPC_STRUCT_BEGIN_WITH_PARENT(), which behaves like IPC_STRUCT_BEGIN(),
philipjb3b3f8e2015-08-12 08:30:01140// but also accommodates structs that inherit from other structs.
[email protected]6476c72c2011-02-11 18:46:19141//
142// Externally-defined structs are registered with IPC_STRUCT_TRAITS_BEGIN(),
143// IPC_STRUCT_TRAITS_MEMBER(), and IPC_STRUCT_TRAITS_END() macros. These
[email protected]94dc971d2011-03-05 19:08:32144// cause registration of the types with message generation only.
145// There's also IPC_STRUCT_TRAITS_PARENT, which is used to register a parent
146// class (whose own traits are already defined). Note that
147// IPC_STRUCT_TRAITS_MEMBER() and IPC_STRUCT_TRAITS_PARENT are only permitted
[email protected]e503a122011-03-17 18:20:52148// inside matching calls to IPC_STRUCT_TRAITS_BEGIN() /
149// IPC_STRUCT_TRAITS_END().
[email protected]6476c72c2011-02-11 18:46:19150//
[email protected]dedd0a92013-06-04 07:20:32151// Enum types are registered with a single IPC_ENUM_TRAITS_VALIDATE() macro.
152// There is no need to enumerate each value to the IPC mechanism. Instead,
153// pass an expression in terms of the parameter |value| to provide
154// range-checking. For convenience, the IPC_ENUM_TRAITS() is provided which
155// performs no checking, passing everything including out-of-range values.
156// Its use is discouraged. The IPC_ENUM_TRAITS_MAX_VALUE() macro can be used
157// for the typical case where the enum must be in the range 0..maxvalue
158// inclusive. The IPC_ENUM_TRAITS_MIN_MAX_VALUE() macro can be used for the
159// less typical case where the enum must be in the range minvalue..maxvalue
160// inclusive.
[email protected]6476c72c2011-02-11 18:46:19161//
[email protected]e503a122011-03-17 18:20:52162// Do not place semicolons following these IPC_ macro invocations. There
163// is no reason to expect that their expansion corresponds one-to-one with
164// C++ statements.
165//
[email protected]6476c72c2011-02-11 18:46:19166// Once the types have been declared / registered, message definitions follow.
initial.commit09911bf2008-07-26 23:55:29167// "Sync" messages are just synchronous calls, the Send() call doesn't return
[email protected]7f994182011-08-23 10:18:10168// until a reply comes back. To declare a sync message, use the IPC_SYNC_
169// macros. The numbers at the end show how many input/output parameters there
170// are (i.e. 1_2 is 1 in, 2 out). Input parameters are first, followed by
171// output parameters. The caller uses Send([route id, ], in1, &out1, &out2).
initial.commit09911bf2008-07-26 23:55:29172// The receiver's handler function will be
173// void OnSyncMessageName(const type1& in1, type2* out1, type3* out2)
174//
initial.commit09911bf2008-07-26 23:55:29175// A caller can also send a synchronous message, while the receiver can respond
[email protected]d4240352009-12-10 17:32:31176// at a later time. This is transparent from the sender's side. The receiver
initial.commit09911bf2008-07-26 23:55:29177// needs to use a different handler that takes in a IPC::Message* as the output
178// type, stash the message, and when it has the data it can Send the message.
179//
180// Use the IPC_MESSAGE_HANDLER_DELAY_REPLY macro instead of IPC_MESSAGE_HANDLER
[email protected]d3216442009-03-05 21:07:27181// IPC_MESSAGE_HANDLER_DELAY_REPLY(ViewHostMsg_SyncMessageName,
182// OnSyncMessageName)
initial.commit09911bf2008-07-26 23:55:29183//
184// The handler function will look like:
185// void OnSyncMessageName(const type1& in1, IPC::Message* reply_msg);
186//
187// Receiver stashes the IPC::Message* pointer, and when it's ready, it does:
188// ViewHostMsg_SyncMessageName::WriteReplyParams(reply_msg, out1, out2);
189// Send(reply_msg);
190
[email protected]7de84042012-02-21 16:04:50191// Files that want to export their ipc messages should do
192// #undef IPC_MESSAGE_EXPORT
193// #define IPC_MESSAGE_EXPORT VISIBILITY_MACRO
194// after including this header, but before using any of the macros below.
195// (This needs to be before the include guard.)
196#undef IPC_MESSAGE_EXPORT
197#define IPC_MESSAGE_EXPORT
198
[email protected]6476c72c2011-02-11 18:46:19199#ifndef IPC_IPC_MESSAGE_MACROS_H_
200#define IPC_IPC_MESSAGE_MACROS_H_
[email protected]82e5ee82009-04-03 02:29:45201
tfarina10a5c062015-09-04 18:47:57202#include <stdint.h>
203
tzik55e3e4d2016-03-08 05:47:44204#include <tuple>
205
[email protected]e86a2552011-11-11 00:21:02206#include "base/profiler/scoped_profile.h"
mdempsky8a519042016-02-09 05:41:47207#include "ipc/export_template.h"
208#include "ipc/ipc_message_templates.h"
[email protected]6476c72c2011-02-11 18:46:19209#include "ipc/ipc_message_utils.h"
210#include "ipc/param_traits_macros.h"
[email protected]f91cb992009-02-04 20:10:12211
[email protected]600cdb7c2013-11-05 04:24:58212// Convenience macro for defining structs without inheritance. Should not need
[email protected]dedd0a92013-06-04 07:20:32213// to be subsequently redefined.
[email protected]8a8c9c72011-03-01 20:35:47214#define IPC_STRUCT_BEGIN(struct_name) \
[email protected]6766b172011-11-21 18:29:36215 IPC_STRUCT_BEGIN_WITH_PARENT(struct_name, IPC::NoParams)
[email protected]dedd0a92013-06-04 07:20:32216
217// Macros for defining structs. Will be subsequently redefined.
[email protected]6766b172011-11-21 18:29:36218#define IPC_STRUCT_BEGIN_WITH_PARENT(struct_name, parent) \
[email protected]8a8c9c72011-03-01 20:35:47219 struct struct_name; \
220 IPC_STRUCT_TRAITS_BEGIN(struct_name) \
221 IPC_STRUCT_TRAITS_END() \
[email protected]6766b172011-11-21 18:29:36222 struct IPC_MESSAGE_EXPORT struct_name : parent { \
[email protected]8a8c9c72011-03-01 20:35:47223 struct_name(); \
224 ~struct_name();
[email protected]01cca0042012-04-16 19:13:02225// Optional variadic parameters specify the default value for this struct
226// member. They are passed through to the constructor for |type|.
227#define IPC_STRUCT_MEMBER(type, name, ...) type name;
[email protected]8a8c9c72011-03-01 20:35:47228#define IPC_STRUCT_END() };
229
mdempsky8a519042016-02-09 05:41:47230// Message macros collect arguments and funnel them into the common message
231// generation macro. These should never be redefined.
[email protected]8a8c9c72011-03-01 20:35:47232
mdempsky8a519042016-02-09 05:41:47233// Asynchronous messages have only in parameters and are declared like:
234// IPC_MESSAGE_CONTROL(FooMsg, int, float)
235#define IPC_MESSAGE_CONTROL(msg_class, ...) \
236 IPC_MESSAGE_DECL(msg_class, CONTROL, IPC_TUPLE(__VA_ARGS__), void)
237#define IPC_MESSAGE_ROUTED(msg_class, ...) \
238 IPC_MESSAGE_DECL(msg_class, ROUTED, IPC_TUPLE(__VA_ARGS__), void)
[email protected]8a8c9c72011-03-01 20:35:47239
mdempsky8a519042016-02-09 05:41:47240// Synchronous messages have both in and out parameters, so the lists need to
241// be parenthesized to disambiguate:
242// IPC_SYNC_MESSAGE_CONTROL(BarMsg, (int, int), (bool))
243//
244// Implementation detail: The parentheses supplied by the caller for
245// disambiguation are also used to trigger the IPC_TUPLE invocations below,
246// so "IPC_TUPLE in" and "IPC_TUPLE out" are intentional.
247#define IPC_SYNC_MESSAGE_CONTROL(msg_class, in, out) \
248 IPC_MESSAGE_DECL(msg_class, CONTROL, IPC_TUPLE in, IPC_TUPLE out)
249#define IPC_SYNC_MESSAGE_ROUTED(msg_class, in, out) \
250 IPC_MESSAGE_DECL(msg_class, ROUTED, IPC_TUPLE in, IPC_TUPLE out)
[email protected]8a8c9c72011-03-01 20:35:47251
dskiba2bc89462016-04-06 15:51:06252#define IPC_TUPLE(...) IPC::CheckedTuple<__VA_ARGS__>::Tuple
[email protected]8a8c9c72011-03-01 20:35:47253
mdempsky8a519042016-02-09 05:41:47254#define IPC_MESSAGE_DECL(msg_name, kind, in_tuple, out_tuple) \
255 struct IPC_MESSAGE_EXPORT msg_name##_Meta { \
256 using InTuple = in_tuple; \
257 using OutTuple = out_tuple; \
258 enum { ID = IPC_MESSAGE_ID() }; \
259 static const IPC::MessageKind kKind = IPC::MessageKind::kind; \
260 static const char kName[]; \
261 }; \
262 extern template class EXPORT_TEMPLATE_DECLARE(IPC_MESSAGE_EXPORT) \
263 IPC::MessageT<msg_name##_Meta>; \
264 using msg_name = IPC::MessageT<msg_name##_Meta>; \
265 IPC_MESSAGE_EXTRA(msg_name)
[email protected]8a8c9c72011-03-01 20:35:47266
267#if defined(IPC_MESSAGE_IMPL)
268
mdempsky8a519042016-02-09 05:41:47269// "Implementation" inclusion provides the explicit template definition
270// for msg_name.
271#define IPC_MESSAGE_EXTRA(msg_name) \
272 const char msg_name##_Meta::kName[] = #msg_name; \
273 IPC_MESSAGE_DEFINE_KIND(msg_name) \
274 template class EXPORT_TEMPLATE_DEFINE(IPC_MESSAGE_EXPORT) \
275 IPC::MessageT<msg_name##_Meta>;
[email protected]8a8c9c72011-03-01 20:35:47276
mdempsky8a519042016-02-09 05:41:47277// MSVC has an intentionally non-compliant "feature" that results in LNK2005
278// ("symbol already defined") errors if we provide an out-of-line definition
279// for kKind. Microsoft's official response is to test for _MSC_EXTENSIONS:
280// https://connect.microsoft.com/VisualStudio/feedback/details/786583/
281#if defined(_MSC_EXTENSIONS)
282#define IPC_MESSAGE_DEFINE_KIND(msg_name)
283#else
284#define IPC_MESSAGE_DEFINE_KIND(msg_name) \
285 const IPC::MessageKind msg_name##_Meta::kKind;
286#endif
[email protected]8a8c9c72011-03-01 20:35:47287
[email protected]21fa3a12010-12-08 23:34:16288#elif defined(IPC_MESSAGE_MACROS_LOG_ENABLED)
[email protected]f91cb992009-02-04 20:10:12289
[email protected]4f68ed72012-10-30 05:24:07290#ifndef IPC_LOG_TABLE_ADD_ENTRY
291#error You need to define IPC_LOG_TABLE_ADD_ENTRY(msg_id, logger)
292#endif
[email protected]f91cb992009-02-04 20:10:12293
[email protected]8a8c9c72011-03-01 20:35:47294// "Log table" inclusion produces extra logging registration code.
mdempsky8a519042016-02-09 05:41:47295#define IPC_MESSAGE_EXTRA(msg_name) \
296 class LoggerRegisterHelper##msg_name { \
297 public: \
298 LoggerRegisterHelper##msg_name() { \
299 const uint32_t msg_id = static_cast<uint32_t>(msg_name::ID); \
300 IPC_LOG_TABLE_ADD_ENTRY(msg_id, msg_name::Log); \
301 } \
302 }; \
303 LoggerRegisterHelper##msg_name g_LoggerRegisterHelper##msg_name;
[email protected]f91cb992009-02-04 20:10:12304
[email protected]8a8c9c72011-03-01 20:35:47305#else
initial.commit09911bf2008-07-26 23:55:29306
[email protected]8a8c9c72011-03-01 20:35:47307// Normal inclusion produces nothing extra.
mdempsky8a519042016-02-09 05:41:47308#define IPC_MESSAGE_EXTRA(msg_name)
initial.commit09911bf2008-07-26 23:55:29309
mdempsky8a519042016-02-09 05:41:47310#endif // defined(IPC_MESSAGE_IMPL)
[email protected]6d8ffc9f2010-03-12 18:27:53311
[email protected]d7a5e3e2011-03-12 16:28:36312// Message IDs
313// Note: we currently use __LINE__ to give unique IDs to messages within
314// a file. They're globally unique since each file defines its own
[email protected]3b3ec7212011-10-21 17:35:08315// IPC_MESSAGE_START.
[email protected]d7a5e3e2011-03-12 16:28:36316#define IPC_MESSAGE_ID() ((IPC_MESSAGE_START << 16) + __LINE__)
317#define IPC_MESSAGE_ID_CLASS(id) ((id) >> 16)
318#define IPC_MESSAGE_ID_LINE(id) ((id) & 0xffff)
319
[email protected]e44d1342014-05-16 21:29:33320// Message crackers and handlers. Usage:
initial.commit09911bf2008-07-26 23:55:29321//
[email protected]a95986a82010-12-24 06:19:28322// bool MyClass::OnMessageReceived(const IPC::Message& msg) {
323// bool handled = true;
[email protected]e44d1342014-05-16 21:29:33324// IPC_BEGIN_MESSAGE_MAP(MyClass, msg)
initial.commit09911bf2008-07-26 23:55:29325// IPC_MESSAGE_HANDLER(MsgClassOne, OnMsgClassOne)
326// ...more handlers here ...
327// IPC_MESSAGE_HANDLER(MsgClassTen, OnMsgClassTen)
[email protected]a95986a82010-12-24 06:19:28328// IPC_MESSAGE_UNHANDLED(handled = false)
[email protected]e44d1342014-05-16 21:29:33329// IPC_END_MESSAGE_MAP()
[email protected]a95986a82010-12-24 06:19:28330// return handled;
initial.commit09911bf2008-07-26 23:55:29331// }
332
[email protected]21fa3a12010-12-08 23:34:16333
initial.commit09911bf2008-07-26 23:55:29334#define IPC_BEGIN_MESSAGE_MAP(class_name, msg) \
335 { \
pkasting99867ef2014-10-16 23:49:24336 typedef class_name _IpcMessageHandlerClass ALLOW_UNUSED_TYPE; \
[email protected]9d77dd4122014-05-14 21:43:59337 void* param__ = NULL; \
sunnypsb3c862b2016-02-05 01:55:08338 (void)param__; \
initial.commit09911bf2008-07-26 23:55:29339 const IPC::Message& ipc_message__ = msg; \
[email protected]9d77dd4122014-05-14 21:43:59340 switch (ipc_message__.type()) {
initial.commit09911bf2008-07-26 23:55:29341
pkasting99867ef2014-10-16 23:49:24342#define IPC_BEGIN_MESSAGE_MAP_WITH_PARAM(class_name, msg, param) \
343 { \
344 typedef class_name _IpcMessageHandlerClass ALLOW_UNUSED_TYPE; \
thakise6e95d92014-10-29 22:04:47345 decltype(param) param__ = param; \
pkasting99867ef2014-10-16 23:49:24346 const IPC::Message& ipc_message__ = msg; \
[email protected]9d77dd4122014-05-14 21:43:59347 switch (ipc_message__.type()) {
[email protected]5636d902014-05-13 23:19:10348
[email protected]e86a2552011-11-11 00:21:02349#define IPC_MESSAGE_FORWARD(msg_class, obj, member_func) \
350 case msg_class::ID: { \
vadimta19e48772014-09-25 22:08:59351 TRACK_RUN_IN_THIS_SCOPED_REGION(member_func); \
[email protected]e44d1342014-05-16 21:29:33352 if (!msg_class::Dispatch(&ipc_message__, obj, this, param__, \
353 &member_func)) \
[email protected]ef2f6ba2014-05-15 23:06:07354 ipc_message__.set_dispatch_error(); \
[email protected]e86a2552011-11-11 00:21:02355 } \
356 break;
initial.commit09911bf2008-07-26 23:55:29357
358#define IPC_MESSAGE_HANDLER(msg_class, member_func) \
359 IPC_MESSAGE_FORWARD(msg_class, this, _IpcMessageHandlerClass::member_func)
360
[email protected]e86a2552011-11-11 00:21:02361#define IPC_MESSAGE_FORWARD_DELAY_REPLY(msg_class, obj, member_func) \
362 case msg_class::ID: { \
vadimta19e48772014-09-25 22:08:59363 TRACK_RUN_IN_THIS_SCOPED_REGION(member_func); \
[email protected]e44d1342014-05-16 21:29:33364 if (!msg_class::DispatchDelayReply(&ipc_message__, obj, param__, \
365 &member_func)) \
[email protected]ef2f6ba2014-05-15 23:06:07366 ipc_message__.set_dispatch_error(); \
[email protected]e86a2552011-11-11 00:21:02367 } \
368 break;
initial.commit09911bf2008-07-26 23:55:29369
[email protected]e86a2552011-11-11 00:21:02370#define IPC_MESSAGE_HANDLER_DELAY_REPLY(msg_class, member_func) \
371 IPC_MESSAGE_FORWARD_DELAY_REPLY(msg_class, this, \
372 _IpcMessageHandlerClass::member_func)
initial.commit09911bf2008-07-26 23:55:29373
[email protected]562016342011-11-15 17:51:43374// TODO(jar): fix chrome frame to always supply |code| argument.
[email protected]e86a2552011-11-11 00:21:02375#define IPC_MESSAGE_HANDLER_GENERIC(msg_class, code) \
376 case msg_class::ID: { \
vadimta19e48772014-09-25 22:08:59377 /* TRACK_RUN_IN_THIS_SCOPED_REGION(code); TODO(jar) */ \
[email protected]e86a2552011-11-11 00:21:02378 code; \
379 } \
380 break;
initial.commit09911bf2008-07-26 23:55:29381
[email protected]e86a2552011-11-11 00:21:02382#define IPC_REPLY_HANDLER(func) \
383 case IPC_REPLY_ID: { \
vadimta19e48772014-09-25 22:08:59384 TRACK_RUN_IN_THIS_SCOPED_REGION(func); \
[email protected]e86a2552011-11-11 00:21:02385 func(ipc_message__); \
386 } \
387 break;
initial.commit09911bf2008-07-26 23:55:29388
389
[email protected]e86a2552011-11-11 00:21:02390#define IPC_MESSAGE_UNHANDLED(code) \
391 default: { \
[email protected]e86a2552011-11-11 00:21:02392 code; \
393 } \
394 break;
initial.commit09911bf2008-07-26 23:55:29395
396#define IPC_MESSAGE_UNHANDLED_ERROR() \
397 IPC_MESSAGE_UNHANDLED(NOTREACHED() << \
398 "Invalid message with type = " << \
399 ipc_message__.type())
400
401#define IPC_END_MESSAGE_MAP() \
initial.commit09911bf2008-07-26 23:55:29402 } \
[email protected]8d70d5f2010-12-08 23:41:08403}
[email protected]9f547bf2010-12-13 17:00:42404
405// This corresponds to an enum value from IPCMessageStart.
lfgdb5c4ed2016-03-04 23:09:07406#define IPC_MESSAGE_CLASS(message) IPC_MESSAGE_ID_CLASS((message).type())
[email protected]6476c72c2011-02-11 18:46:19407
mdempsky8a519042016-02-09 05:41:47408// Deprecated legacy macro names.
409// TODO(mdempsky): Replace uses with generic names.
410
411#define IPC_MESSAGE_CONTROL0(msg) IPC_MESSAGE_CONTROL(msg)
412#define IPC_MESSAGE_CONTROL1(msg, a) IPC_MESSAGE_CONTROL(msg, a)
413#define IPC_MESSAGE_CONTROL2(msg, a, b) IPC_MESSAGE_CONTROL(msg, a, b)
414#define IPC_MESSAGE_CONTROL3(msg, a, b, c) IPC_MESSAGE_CONTROL(msg, a, b, c)
415#define IPC_MESSAGE_CONTROL4(msg, a, b, c, d) \
416 IPC_MESSAGE_CONTROL(msg, a, b, c, d)
417#define IPC_MESSAGE_CONTROL5(msg, a, b, c, d, e) \
418 IPC_MESSAGE_CONTROL(msg, a, b, c, d, e)
419
420#define IPC_MESSAGE_ROUTED0(msg) IPC_MESSAGE_ROUTED(msg)
421#define IPC_MESSAGE_ROUTED1(msg, a) IPC_MESSAGE_ROUTED(msg, a)
422#define IPC_MESSAGE_ROUTED2(msg, a, b) IPC_MESSAGE_ROUTED(msg, a, b)
423#define IPC_MESSAGE_ROUTED3(msg, a, b, c) IPC_MESSAGE_ROUTED(msg, a, b, c)
424#define IPC_MESSAGE_ROUTED4(msg, a, b, c, d) IPC_MESSAGE_ROUTED(msg, a, b, c, d)
425#define IPC_MESSAGE_ROUTED5(msg, a, b, c, d, e) \
426 IPC_MESSAGE_ROUTED(msg, a, b, c, d, e)
427
428#define IPC_SYNC_MESSAGE_CONTROL0_0(msg) IPC_SYNC_MESSAGE_CONTROL(msg, (), ())
429#define IPC_SYNC_MESSAGE_CONTROL0_1(msg, a) \
430 IPC_SYNC_MESSAGE_CONTROL(msg, (), (a))
431#define IPC_SYNC_MESSAGE_CONTROL0_2(msg, a, b) \
432 IPC_SYNC_MESSAGE_CONTROL(msg, (), (a, b))
433#define IPC_SYNC_MESSAGE_CONTROL0_3(msg, a, b, c) \
434 IPC_SYNC_MESSAGE_CONTROL(msg, (), (a, b, c))
435#define IPC_SYNC_MESSAGE_CONTROL0_4(msg, a, b, c, d) \
436 IPC_SYNC_MESSAGE_CONTROL(msg, (), (a, b, c, d))
437#define IPC_SYNC_MESSAGE_CONTROL1_0(msg, a) \
438 IPC_SYNC_MESSAGE_CONTROL(msg, (a), ())
439#define IPC_SYNC_MESSAGE_CONTROL1_1(msg, a, b) \
440 IPC_SYNC_MESSAGE_CONTROL(msg, (a), (b))
441#define IPC_SYNC_MESSAGE_CONTROL1_2(msg, a, b, c) \
442 IPC_SYNC_MESSAGE_CONTROL(msg, (a), (b, c))
443#define IPC_SYNC_MESSAGE_CONTROL1_3(msg, a, b, c, d) \
444 IPC_SYNC_MESSAGE_CONTROL(msg, (a), (b, c, d))
445#define IPC_SYNC_MESSAGE_CONTROL1_4(msg, a, b, c, d, e) \
446 IPC_SYNC_MESSAGE_CONTROL(msg, (a), (b, c, d, e))
447#define IPC_SYNC_MESSAGE_CONTROL2_0(msg, a, b) \
448 IPC_SYNC_MESSAGE_CONTROL(msg, (a, b), ())
449#define IPC_SYNC_MESSAGE_CONTROL2_1(msg, a, b, c) \
450 IPC_SYNC_MESSAGE_CONTROL(msg, (a, b), (c))
451#define IPC_SYNC_MESSAGE_CONTROL2_2(msg, a, b, c, d) \
452 IPC_SYNC_MESSAGE_CONTROL(msg, (a, b), (c, d))
453#define IPC_SYNC_MESSAGE_CONTROL2_3(msg, a, b, c, d, e) \
454 IPC_SYNC_MESSAGE_CONTROL(msg, (a, b), (c, d, e))
455#define IPC_SYNC_MESSAGE_CONTROL2_4(msg, a, b, c, d, e, f) \
456 IPC_SYNC_MESSAGE_CONTROL(msg, (a, b), (c, d, e, f))
457#define IPC_SYNC_MESSAGE_CONTROL3_0(msg, a, b, c) \
458 IPC_SYNC_MESSAGE_CONTROL(msg, (a, b, c), ())
459#define IPC_SYNC_MESSAGE_CONTROL3_1(msg, a, b, c, d) \
460 IPC_SYNC_MESSAGE_CONTROL(msg, (a, b, c), (d))
461#define IPC_SYNC_MESSAGE_CONTROL3_2(msg, a, b, c, d, e) \
462 IPC_SYNC_MESSAGE_CONTROL(msg, (a, b, c), (d, e))
463#define IPC_SYNC_MESSAGE_CONTROL3_3(msg, a, b, c, d, e, f) \
464 IPC_SYNC_MESSAGE_CONTROL(msg, (a, b, c), (d, e, f))
465#define IPC_SYNC_MESSAGE_CONTROL3_4(msg, a, b, c, d, e, f, g) \
466 IPC_SYNC_MESSAGE_CONTROL(msg, (a, b, c), (d, e, f, g))
467#define IPC_SYNC_MESSAGE_CONTROL4_0(msg, a, b, c, d) \
468 IPC_SYNC_MESSAGE_CONTROL(msg, (a, b, c, d), ())
469#define IPC_SYNC_MESSAGE_CONTROL4_1(msg, a, b, c, d, e) \
470 IPC_SYNC_MESSAGE_CONTROL(msg, (a, b, c, d), (e))
471#define IPC_SYNC_MESSAGE_CONTROL4_2(msg, a, b, c, d, e, f) \
472 IPC_SYNC_MESSAGE_CONTROL(msg, (a, b, c, d), (e, f))
473#define IPC_SYNC_MESSAGE_CONTROL4_3(msg, a, b, c, d, e, f, g) \
474 IPC_SYNC_MESSAGE_CONTROL(msg, (a, b, c, d), (e, f, g))
475#define IPC_SYNC_MESSAGE_CONTROL4_4(msg, a, b, c, d, e, f, g, h) \
476 IPC_SYNC_MESSAGE_CONTROL(msg, (a, b, c, d), (e, f, g, h))
477#define IPC_SYNC_MESSAGE_CONTROL5_0(msg, a, b, c, d, e) \
478 IPC_SYNC_MESSAGE_CONTROL(msg, (a, b, c, d, e), ())
479#define IPC_SYNC_MESSAGE_CONTROL5_1(msg, a, b, c, d, e, f) \
480 IPC_SYNC_MESSAGE_CONTROL(msg, (a, b, c, d, e), (f))
481#define IPC_SYNC_MESSAGE_CONTROL5_2(msg, a, b, c, d, e, f, g) \
482 IPC_SYNC_MESSAGE_CONTROL(msg, (a, b, c, d, e), (f, g))
483#define IPC_SYNC_MESSAGE_CONTROL5_3(msg, a, b, c, d, e, f, g, h) \
484 IPC_SYNC_MESSAGE_CONTROL(msg, (a, b, c, d, e), (f, g, h))
485#define IPC_SYNC_MESSAGE_CONTROL5_4(msg, a, b, c, d, e, f, g, h, i) \
486 IPC_SYNC_MESSAGE_CONTROL(msg, (a, b, c, d, e), (f, g, h, i))
487
488#define IPC_SYNC_MESSAGE_ROUTED0_0(msg) IPC_SYNC_MESSAGE_ROUTED(msg, (), ())
489#define IPC_SYNC_MESSAGE_ROUTED0_1(msg, a) IPC_SYNC_MESSAGE_ROUTED(msg, (), (a))
490#define IPC_SYNC_MESSAGE_ROUTED0_2(msg, a, b) \
491 IPC_SYNC_MESSAGE_ROUTED(msg, (), (a, b))
492#define IPC_SYNC_MESSAGE_ROUTED0_3(msg, a, b, c) \
493 IPC_SYNC_MESSAGE_ROUTED(msg, (), (a, b, c))
494#define IPC_SYNC_MESSAGE_ROUTED0_4(msg, a, b, c, d) \
495 IPC_SYNC_MESSAGE_ROUTED(msg, (), (a, b, c, d))
496#define IPC_SYNC_MESSAGE_ROUTED1_0(msg, a) IPC_SYNC_MESSAGE_ROUTED(msg, (a), ())
497#define IPC_SYNC_MESSAGE_ROUTED1_1(msg, a, b) \
498 IPC_SYNC_MESSAGE_ROUTED(msg, (a), (b))
499#define IPC_SYNC_MESSAGE_ROUTED1_2(msg, a, b, c) \
500 IPC_SYNC_MESSAGE_ROUTED(msg, (a), (b, c))
501#define IPC_SYNC_MESSAGE_ROUTED1_3(msg, a, b, c, d) \
502 IPC_SYNC_MESSAGE_ROUTED(msg, (a), (b, c, d))
503#define IPC_SYNC_MESSAGE_ROUTED1_4(msg, a, b, c, d, e) \
504 IPC_SYNC_MESSAGE_ROUTED(msg, (a), (b, c, d, e))
505#define IPC_SYNC_MESSAGE_ROUTED2_0(msg, a, b) \
506 IPC_SYNC_MESSAGE_ROUTED(msg, (a, b), ())
507#define IPC_SYNC_MESSAGE_ROUTED2_1(msg, a, b, c) \
508 IPC_SYNC_MESSAGE_ROUTED(msg, (a, b), (c))
509#define IPC_SYNC_MESSAGE_ROUTED2_2(msg, a, b, c, d) \
510 IPC_SYNC_MESSAGE_ROUTED(msg, (a, b), (c, d))
511#define IPC_SYNC_MESSAGE_ROUTED2_3(msg, a, b, c, d, e) \
512 IPC_SYNC_MESSAGE_ROUTED(msg, (a, b), (c, d, e))
513#define IPC_SYNC_MESSAGE_ROUTED2_4(msg, a, b, c, d, e, f) \
514 IPC_SYNC_MESSAGE_ROUTED(msg, (a, b), (c, d, e, f))
515#define IPC_SYNC_MESSAGE_ROUTED3_0(msg, a, b, c) \
516 IPC_SYNC_MESSAGE_ROUTED(msg, (a, b, c), ())
517#define IPC_SYNC_MESSAGE_ROUTED3_1(msg, a, b, c, d) \
518 IPC_SYNC_MESSAGE_ROUTED(msg, (a, b, c), (d))
519#define IPC_SYNC_MESSAGE_ROUTED3_2(msg, a, b, c, d, e) \
520 IPC_SYNC_MESSAGE_ROUTED(msg, (a, b, c), (d, e))
521#define IPC_SYNC_MESSAGE_ROUTED3_3(msg, a, b, c, d, e, f) \
522 IPC_SYNC_MESSAGE_ROUTED(msg, (a, b, c), (d, e, f))
523#define IPC_SYNC_MESSAGE_ROUTED3_4(msg, a, b, c, d, e, f, g) \
524 IPC_SYNC_MESSAGE_ROUTED(msg, (a, b, c), (d, e, f, g))
525#define IPC_SYNC_MESSAGE_ROUTED4_0(msg, a, b, c, d) \
526 IPC_SYNC_MESSAGE_ROUTED(msg, (a, b, c, d), ())
527#define IPC_SYNC_MESSAGE_ROUTED4_1(msg, a, b, c, d, e) \
528 IPC_SYNC_MESSAGE_ROUTED(msg, (a, b, c, d), (e))
529#define IPC_SYNC_MESSAGE_ROUTED4_2(msg, a, b, c, d, e, f) \
530 IPC_SYNC_MESSAGE_ROUTED(msg, (a, b, c, d), (e, f))
531#define IPC_SYNC_MESSAGE_ROUTED4_3(msg, a, b, c, d, e, f, g) \
532 IPC_SYNC_MESSAGE_ROUTED(msg, (a, b, c, d), (e, f, g))
533#define IPC_SYNC_MESSAGE_ROUTED4_4(msg, a, b, c, d, e, f, g, h) \
534 IPC_SYNC_MESSAGE_ROUTED(msg, (a, b, c, d), (e, f, g, h))
535#define IPC_SYNC_MESSAGE_ROUTED5_0(msg, a, b, c, d, e) \
536 IPC_SYNC_MESSAGE_ROUTED(msg, (a, b, c, d, e), ())
537#define IPC_SYNC_MESSAGE_ROUTED5_1(msg, a, b, c, d, e, f) \
538 IPC_SYNC_MESSAGE_ROUTED(msg, (a, b, c, d, e), (f))
539#define IPC_SYNC_MESSAGE_ROUTED5_2(msg, a, b, c, d, e, f, g) \
540 IPC_SYNC_MESSAGE_ROUTED(msg, (a, b, c, d, e), (f, g))
541#define IPC_SYNC_MESSAGE_ROUTED5_3(msg, a, b, c, d, e, f, g, h) \
542 IPC_SYNC_MESSAGE_ROUTED(msg, (a, b, c, d, e), (f, g, h))
543#define IPC_SYNC_MESSAGE_ROUTED5_4(msg, a, b, c, d, e, f, g, h, i) \
544 IPC_SYNC_MESSAGE_ROUTED(msg, (a, b, c, d, e), (f, g, h, i))
545
[email protected]6476c72c2011-02-11 18:46:19546#endif // IPC_IPC_MESSAGE_MACROS_H_
547
548// Clean up IPC_MESSAGE_START in this unguarded section so that the
549// XXX_messages.h files need not do so themselves. This makes the
550// XXX_messages.h files easier to write.
551#undef IPC_MESSAGE_START