[Good First Issue] [Snippets] [ARM]: Enable Power, Select, Xor tokenization in CPU Plugin

[a-sidorova]

Context

Snippets is a highly specialized JIT (just-in-time) compiler for computational graphs. It provides a scalable approach to operations' fusions and enablement. As a typical compiler, Snippets have frontend (tokenizer), optimizer and backend (generator).

The first of the Snippets pipeline, Tokenization, identifies parts of the initial ov::Model that can be lowered by Snippets efficiently, and tokenizes them into one whole node - Subgraph.
The second step of the pipeline (Optimizer) is applying common and device-specific optimizations to Subgraph and getting lowered representation of tokenized Subgraph.
Finally, the last stage is code emission. The target generator maps every operation in the IR to a binary code emitter JIT Emitter, which is then used to produce a piece of executable code. As a result, we produce an executable that performs calculations described by the initial input ov::Model.

The purpose of this issue is enabling tokenization of some elementwise operations (Power, Select, Xor) in Snippets for ARM devices. All JIT Emitters are already implemented in the CPU Plugin, so no need to write JIT Emitters.

Prerequisites

Recommended to use ARM CPU based platform for development (e.g. Mac, Raspberry Pi etc). The cross-compilation with an emulator (e.g. QEMU) using is still option: cmake -DCMAKE_TOOLCHAIN_FILE=../cmake/arm64.toolchain.cmake ...

What needs to be done?

• Add elementwise op Power in CPU eltwise test instantiation with Snippets if it is missed. Please launch the tests using the paragraph Tests below. The tests should be failed.
• Need to enable Snippets tokenization of these operations (Power, Select, Xor) on AArch64 devices. Add them to the list in the is_supported_op in the tokenization pass callback.
• Register the operations with the corresponding JIT emitters in CPUTargetMachine.

Tests

Tests are disabled in default build, so ensure to add -DENABLE_TESTS=ON into cmake command.

GoogleTest is used for testing. CPU functional test target is ov_cpu_func_tests. You can use GoogleTest filter:

./bin/[platform]/[build_type]/ov_cpu_func_tests --gtest_filter="*smoke*Snippets*EltwiseLayerCPUTest*"
./bin/[platform]/[build_type]/ov_cpu_func_tests --gtest_filter="*smoke*SelectLayerCPUTest*"
./bin/[platform]/[build_type]/ov_cpu_func_tests --gtest_filter="*smoke*LogicalLayerTest*"

Examples

• Enabled Ceiling and FloorMod tokenization: [Snippets][AArch64] Enabled Ceiling and FloorMod tokenization #28092
• The JIT Emitter implementation for Equal operation: [CPU] [ARM64] jit equal #23266
• CPU Target machine for x64 platforms: link.

Resources

• Contribution guide - start here!
• What is OpenVINO?
• Snippets - JIT compiler for computational graphs
• CPU plugin JIT emitters
• Blog post on contributing to OpenVINO
• User documentation
• Intel DevHub Discord channel - engage in discussions, ask questions and talk to OpenVINO developers
• How to link your Pull Request to an issue

Contact points

@a-sidorova, @dmitry-gorokhov

[sramichetty20019]

.take

[github-actions]

Thank you for looking into this issue! Please let us know if you have any questions or require any help.

[geeky33]

@sramichetty20019 hey can u please tell are u still working on this issue?
if not please let me know asap

[a-sidorova]

@geeky33 I assigned it to you due to no activity of the previous assignee. Have a fun! 😄

[PIKABOLTCODER]

Here’s the updated comment:

Hi @a-sidorova,

I am new to open-source and OpenVINO, and I’m eager to learn and contribute. If possible, could you assign me to this issue along with @geeky? I believe collaborating on this would be a great opportunity for me to learn and contribute effectively.

@geeky, would you be okay with me joining you on this?

Thank you! 😊

[a-sidorova]

Here’s the updated comment:

Hi @a-sidorova,

I am new to open-source and OpenVINO, and I’m eager to learn and contribute. If possible, could you assign me to this issue along with @geeky? I believe collaborating on this would be a great opportunity for me to learn and contribute effectively.

@geeky, would you be okay with me joining you on this?

Thank you! 😊

Hi @PIKABOLTCODER! Thank you for the interest! Unfortunately, this issue can have only one assignee - this task is quite simple and one contributor is enough to implement it. However, if you're interested in any another task in CPU Plugin, please take a look at the board. For example, we have 4 open GoodFirstIssues' for now. If you have time, you can try you hand at issue #24415 if this is open still 😊