platform_hardware_interfaces/neuralnetworks/1.2/IPreparedModel.hal

191 lines
10 KiB
Text
Raw Normal View History

/*
* Copyright (C) 2018 The Android Open Source Project
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package android.hardware.neuralnetworks@1.2;
import @1.0::ErrorStatus;
import @1.0::IPreparedModel;
import @1.0::Request;
NNAPI Burst -- HAL interface FastMessageQueue is a Treble-compliant data structure that enables fast communication between two processes. The FMQ object itself is an atomic circular buffer that is optionally synchronized with a futex. However, FMQ has no notion of ownership or lifetime across processes, so it must be paired with higher-level constructs to manage the lifetime and ownership. The NNAPI is introducing the notion of an "Execution Burst" object (or more simply a "Burst" object), which is similar to an ANeuralNetworksExecution, but is intended to be reused across multiple executions and has lower IPC overheads. It achieves this low IPC overhead by replacing HIDL HwBinder calls with FMQ messages. Specifically, it replaces IPreparedModel::executeSynchronously's call from the client into the service with fmq_sync<FmqRequestDatum> (an FMQ channel used to pass a serialized Request object) and it replaces the return from the service into the client with fmq_sync<FmqResultDatum> (an FMQ channel used to return serialized result status and OutputShapes information). Each channel is a unidirectional flow of information with exactly one producer and exactly one consumer. The channels are created by the NN runtime and passed to the service via IPreparedModel::configureExecutionBurst. This CL defines the FmqRequestDatum and FmqResultDatum types in types.hal. IBurstContext.hal defines IBurstContext, a HIDL object used by the service to manage the resources of a Burst. IBurstCallback.hal defines IBurstCallback, a HIDL callback object that can be used to retrieve the handle to a resource the service has either not yet seen or has evicted from its cache. Finally, IPreparedModel.hal is extended with IPreparedModel::configureExecutionBurst to create the burst object. Bug: 119570067 Test: mma Change-Id: I333da70201531b1396efc714d096c277e8e1d47b Merged-In: I333da70201531b1396efc714d096c277e8e1d47b (cherry picked from commit 7e91e24fe155de15c677c48ca5a2c141ba2246dc)
2019-01-15 19:52:41 +01:00
import IBurstCallback;
import IBurstContext;
import IExecutionCallback;
/**
* IPreparedModel describes a model that has been prepared for execution and
* is used to launch executions.
*/
interface IPreparedModel extends @1.0::IPreparedModel {
/**
* Launches an asynchronous execution on a prepared model.
*
* The execution is performed asynchronously with respect to the caller.
* execute_1_2 must verify the inputs to the function are correct. If there is
* an error, execute_1_2 must immediately invoke the callback with the
* appropriate ErrorStatus value, then return with the same ErrorStatus. If
* the inputs to the function are valid and there is no error, execute_1_2 must
* launch an asynchronous task to perform the execution in the background,
* and immediately return with ErrorStatus::NONE. If the asynchronous task
* fails to launch, execute_1_2 must immediately invoke the callback with
* ErrorStatus::GENERAL_FAILURE, then return with
* ErrorStatus::GENERAL_FAILURE.
*
* When the asynchronous task has finished its execution, it must
* immediately invoke the callback object provided as an input to the
* execute_1_2 function. This callback must be provided with the ErrorStatus of
* the execution.
*
* If the launch is successful, the caller must not change the content of
* any data object referenced by 'request' (described by the
* {@link @1.0::DataLocation} of a {@link @1.0::RequestArgument}) until the
* asynchronous task has invoked the callback object. The asynchronous task
* must not change the content of any of the data objects corresponding to
* 'request' inputs.
*
* If the prepared model was prepared from a model wherein all tensor
* operands have fully specified dimensions, and the inputs to the function
* are valid, then:
* - the execution should launch successfully (ErrorStatus::NONE): There
* must be no failure unless the device itself is in a bad state.
* - if at execution time every operation's input operands have legal
* values, the execution should complete successfully (ErrorStatus::NONE):
* There must be no failure unless the device itself is in a bad state.
*
* Any number of calls to the execute, execute_1_2, and executeSynchronously
* functions, in any combination, may be made concurrently, even on the same
* IPreparedModel object.
*
* @param request The input and output information on which the prepared
* model is to be executed.
* @param measure Specifies whether or not to measure duration of the execution.
* The duration runs from the time the driver sees the call
* to the execute_1_2 function to the time the driver invokes
* the callback.
* @param callback A callback object used to return the error status of
* the execution. The callback object's notify function must
* be called exactly once, even if the execution was
* unsuccessful.
* @return status Error status of the call, must be:
* - NONE if task is successfully launched
* - DEVICE_UNAVAILABLE if driver is offline or busy
* - GENERAL_FAILURE if there is an unspecified error
* - OUTPUT_INSUFFICIENT_SIZE if provided output buffer is
* not large enough to store the resultant values
* - INVALID_ARGUMENT if one of the input arguments is
* invalid
*/
execute_1_2(Request request, MeasureTiming measure, IExecutionCallback callback)
generates (ErrorStatus status);
/**
* Performs a synchronous execution on a prepared model.
*
* The execution is performed synchronously with respect to the caller.
* executeSynchronously must verify the inputs to the function are
* correct. If there is an error, executeSynchronously must immediately
* return with the appropriate ErrorStatus value. If the inputs to the
* function are valid and there is no error, executeSynchronously must
* perform the execution, and must not return until the execution is
* complete.
*
* The caller must not change the content of any data object referenced by
* 'request' (described by the {@link @1.0::DataLocation} of a
* {@link @1.0::RequestArgument}) until executeSynchronously
* returns. executeSynchronously must not change the content of any of the
* data objects corresponding to 'request' inputs.
*
* If the prepared model was prepared from a model wherein all tensor
* operands have fully specified dimensions, and the inputs to the function
* are valid, and at execution time every operation's input operands have
* legal values, then the execution should complete successfully
* (ErrorStatus::NONE): There must be no failure unless the device itself is
* in a bad state.
*
* Any number of calls to the execute, execute_1_2, and executeSynchronously
* functions, in any combination, may be made concurrently, even on the same
* IPreparedModel object.
*
* @param request The input and output information on which the prepared
* model is to be executed.
* @param measure Specifies whether or not to measure duration of the execution.
* The duration runs from the time the driver sees the call
* to the executeSynchronously function to the time the driver
* returns from the function.
* @return status Error status of the execution, must be:
* - NONE if execution is performed successfully
* - DEVICE_UNAVAILABLE if driver is offline or busy
* - GENERAL_FAILURE if there is an unspecified error
NNAPI Burst -- HAL interface FastMessageQueue is a Treble-compliant data structure that enables fast communication between two processes. The FMQ object itself is an atomic circular buffer that is optionally synchronized with a futex. However, FMQ has no notion of ownership or lifetime across processes, so it must be paired with higher-level constructs to manage the lifetime and ownership. The NNAPI is introducing the notion of an "Execution Burst" object (or more simply a "Burst" object), which is similar to an ANeuralNetworksExecution, but is intended to be reused across multiple executions and has lower IPC overheads. It achieves this low IPC overhead by replacing HIDL HwBinder calls with FMQ messages. Specifically, it replaces IPreparedModel::executeSynchronously's call from the client into the service with fmq_sync<FmqRequestDatum> (an FMQ channel used to pass a serialized Request object) and it replaces the return from the service into the client with fmq_sync<FmqResultDatum> (an FMQ channel used to return serialized result status and OutputShapes information). Each channel is a unidirectional flow of information with exactly one producer and exactly one consumer. The channels are created by the NN runtime and passed to the service via IPreparedModel::configureExecutionBurst. This CL defines the FmqRequestDatum and FmqResultDatum types in types.hal. IBurstContext.hal defines IBurstContext, a HIDL object used by the service to manage the resources of a Burst. IBurstCallback.hal defines IBurstCallback, a HIDL callback object that can be used to retrieve the handle to a resource the service has either not yet seen or has evicted from its cache. Finally, IPreparedModel.hal is extended with IPreparedModel::configureExecutionBurst to create the burst object. Bug: 119570067 Test: mma Change-Id: I333da70201531b1396efc714d096c277e8e1d47b Merged-In: I333da70201531b1396efc714d096c277e8e1d47b (cherry picked from commit 7e91e24fe155de15c677c48ca5a2c141ba2246dc)
2019-01-15 19:52:41 +01:00
* - OUTPUT_INSUFFICIENT_SIZE if at least one output
* operand buffer is not large enough to store the
* corresponding output
* - INVALID_ARGUMENT if one of the input arguments is
* invalid
NNAPI Burst -- HAL interface FastMessageQueue is a Treble-compliant data structure that enables fast communication between two processes. The FMQ object itself is an atomic circular buffer that is optionally synchronized with a futex. However, FMQ has no notion of ownership or lifetime across processes, so it must be paired with higher-level constructs to manage the lifetime and ownership. The NNAPI is introducing the notion of an "Execution Burst" object (or more simply a "Burst" object), which is similar to an ANeuralNetworksExecution, but is intended to be reused across multiple executions and has lower IPC overheads. It achieves this low IPC overhead by replacing HIDL HwBinder calls with FMQ messages. Specifically, it replaces IPreparedModel::executeSynchronously's call from the client into the service with fmq_sync<FmqRequestDatum> (an FMQ channel used to pass a serialized Request object) and it replaces the return from the service into the client with fmq_sync<FmqResultDatum> (an FMQ channel used to return serialized result status and OutputShapes information). Each channel is a unidirectional flow of information with exactly one producer and exactly one consumer. The channels are created by the NN runtime and passed to the service via IPreparedModel::configureExecutionBurst. This CL defines the FmqRequestDatum and FmqResultDatum types in types.hal. IBurstContext.hal defines IBurstContext, a HIDL object used by the service to manage the resources of a Burst. IBurstCallback.hal defines IBurstCallback, a HIDL callback object that can be used to retrieve the handle to a resource the service has either not yet seen or has evicted from its cache. Finally, IPreparedModel.hal is extended with IPreparedModel::configureExecutionBurst to create the burst object. Bug: 119570067 Test: mma Change-Id: I333da70201531b1396efc714d096c277e8e1d47b Merged-In: I333da70201531b1396efc714d096c277e8e1d47b (cherry picked from commit 7e91e24fe155de15c677c48ca5a2c141ba2246dc)
2019-01-15 19:52:41 +01:00
* @return outputShapes A list of shape information of model output operands.
* The index into "outputShapes" corresponds to the index
* of the output operand in the Request outputs vector.
* outputShapes must be empty unless the status is either
* NONE or OUTPUT_INSUFFICIENT_SIZE.
* @return Timing Duration of execution. Unless measure is YES and status is
* NONE, all times must be reported as UINT64_MAX. A driver may
* choose to report any time as UINT64_MAX, indicating that
* measurement is not available.
*/
executeSynchronously(Request request, MeasureTiming measure)
generates (ErrorStatus status, vec<OutputShape> outputShapes, Timing timing);
NNAPI Burst -- HAL interface FastMessageQueue is a Treble-compliant data structure that enables fast communication between two processes. The FMQ object itself is an atomic circular buffer that is optionally synchronized with a futex. However, FMQ has no notion of ownership or lifetime across processes, so it must be paired with higher-level constructs to manage the lifetime and ownership. The NNAPI is introducing the notion of an "Execution Burst" object (or more simply a "Burst" object), which is similar to an ANeuralNetworksExecution, but is intended to be reused across multiple executions and has lower IPC overheads. It achieves this low IPC overhead by replacing HIDL HwBinder calls with FMQ messages. Specifically, it replaces IPreparedModel::executeSynchronously's call from the client into the service with fmq_sync<FmqRequestDatum> (an FMQ channel used to pass a serialized Request object) and it replaces the return from the service into the client with fmq_sync<FmqResultDatum> (an FMQ channel used to return serialized result status and OutputShapes information). Each channel is a unidirectional flow of information with exactly one producer and exactly one consumer. The channels are created by the NN runtime and passed to the service via IPreparedModel::configureExecutionBurst. This CL defines the FmqRequestDatum and FmqResultDatum types in types.hal. IBurstContext.hal defines IBurstContext, a HIDL object used by the service to manage the resources of a Burst. IBurstCallback.hal defines IBurstCallback, a HIDL callback object that can be used to retrieve the handle to a resource the service has either not yet seen or has evicted from its cache. Finally, IPreparedModel.hal is extended with IPreparedModel::configureExecutionBurst to create the burst object. Bug: 119570067 Test: mma Change-Id: I333da70201531b1396efc714d096c277e8e1d47b Merged-In: I333da70201531b1396efc714d096c277e8e1d47b (cherry picked from commit 7e91e24fe155de15c677c48ca5a2c141ba2246dc)
2019-01-15 19:52:41 +01:00
/**
* Configure a Burst object used to execute multiple inferences on a
* prepared model in rapid succession.
*
* If the prepared model was prepared from a model wherein all tensor
* operands have fully specified dimensions, and a valid serialized Request
* is sent to the Burst for execution, and at execution time every
* operation's input operands have legal values, then the execution should
* complete successfully (ErrorStatus::NONE): There must be no failure
* unless the device itself is in a bad state.
*
NNAPI Burst -- HAL interface FastMessageQueue is a Treble-compliant data structure that enables fast communication between two processes. The FMQ object itself is an atomic circular buffer that is optionally synchronized with a futex. However, FMQ has no notion of ownership or lifetime across processes, so it must be paired with higher-level constructs to manage the lifetime and ownership. The NNAPI is introducing the notion of an "Execution Burst" object (or more simply a "Burst" object), which is similar to an ANeuralNetworksExecution, but is intended to be reused across multiple executions and has lower IPC overheads. It achieves this low IPC overhead by replacing HIDL HwBinder calls with FMQ messages. Specifically, it replaces IPreparedModel::executeSynchronously's call from the client into the service with fmq_sync<FmqRequestDatum> (an FMQ channel used to pass a serialized Request object) and it replaces the return from the service into the client with fmq_sync<FmqResultDatum> (an FMQ channel used to return serialized result status and OutputShapes information). Each channel is a unidirectional flow of information with exactly one producer and exactly one consumer. The channels are created by the NN runtime and passed to the service via IPreparedModel::configureExecutionBurst. This CL defines the FmqRequestDatum and FmqResultDatum types in types.hal. IBurstContext.hal defines IBurstContext, a HIDL object used by the service to manage the resources of a Burst. IBurstCallback.hal defines IBurstCallback, a HIDL callback object that can be used to retrieve the handle to a resource the service has either not yet seen or has evicted from its cache. Finally, IPreparedModel.hal is extended with IPreparedModel::configureExecutionBurst to create the burst object. Bug: 119570067 Test: mma Change-Id: I333da70201531b1396efc714d096c277e8e1d47b Merged-In: I333da70201531b1396efc714d096c277e8e1d47b (cherry picked from commit 7e91e24fe155de15c677c48ca5a2c141ba2246dc)
2019-01-15 19:52:41 +01:00
* @param callback A callback object used to retrieve memory resources
* corresponding to a unique identifiers ("slots").
* @param requestChannel Used by the client to send a serialized Request to
* the Burst for execution. The client must not change
* the content of any data object referenced by the
* Request (described by the {@link @1.0::DataLocation}
* of an {@link OperandInformation}) until a result
* has been received from resultChannel. Execution
* must not change the content of any of the data
* objects corresponding to Request inputs. requestChannel
* must not be used to pass a second Request object
* until a result has been received from resultChannel.
NNAPI Burst -- HAL interface FastMessageQueue is a Treble-compliant data structure that enables fast communication between two processes. The FMQ object itself is an atomic circular buffer that is optionally synchronized with a futex. However, FMQ has no notion of ownership or lifetime across processes, so it must be paired with higher-level constructs to manage the lifetime and ownership. The NNAPI is introducing the notion of an "Execution Burst" object (or more simply a "Burst" object), which is similar to an ANeuralNetworksExecution, but is intended to be reused across multiple executions and has lower IPC overheads. It achieves this low IPC overhead by replacing HIDL HwBinder calls with FMQ messages. Specifically, it replaces IPreparedModel::executeSynchronously's call from the client into the service with fmq_sync<FmqRequestDatum> (an FMQ channel used to pass a serialized Request object) and it replaces the return from the service into the client with fmq_sync<FmqResultDatum> (an FMQ channel used to return serialized result status and OutputShapes information). Each channel is a unidirectional flow of information with exactly one producer and exactly one consumer. The channels are created by the NN runtime and passed to the service via IPreparedModel::configureExecutionBurst. This CL defines the FmqRequestDatum and FmqResultDatum types in types.hal. IBurstContext.hal defines IBurstContext, a HIDL object used by the service to manage the resources of a Burst. IBurstCallback.hal defines IBurstCallback, a HIDL callback object that can be used to retrieve the handle to a resource the service has either not yet seen or has evicted from its cache. Finally, IPreparedModel.hal is extended with IPreparedModel::configureExecutionBurst to create the burst object. Bug: 119570067 Test: mma Change-Id: I333da70201531b1396efc714d096c277e8e1d47b Merged-In: I333da70201531b1396efc714d096c277e8e1d47b (cherry picked from commit 7e91e24fe155de15c677c48ca5a2c141ba2246dc)
2019-01-15 19:52:41 +01:00
* @param resultChannel Used by the service to return the results of an
* execution to the client: the status of the execution
* and OutputShape of all output tensors. resultChannel
* must be used to return the results if a Request was
* sent through the requestChannel.
* @return status Error status of configuring the execution burst, must be:
* - NONE if the burst is successfully configured
* - DEVICE_UNAVAILABLE if driver is offline or busy
* - GENERAL_FAILURE if there is an unspecified error
* - INVALID_ARGUMENT if one of the input arguments is
* invalid
* @return context Object containing all resources (such as cached
* hidl_memory) related to a Burst if successful, otherwise
* nullptr.
*/
configureExecutionBurst(IBurstCallback callback,
fmq_sync<FmqRequestDatum> requestChannel,
fmq_sync<FmqResultDatum> resultChannel)
generates (ErrorStatus status, IBurstContext context);
};