Dropping VMLA tests in as many places as possible. (#5898)

diff --git a/docs/developers/developing_iree/benchmarking.md b/docs/developers/developing_iree/benchmarking.md
index 6956b67..ff08628 100644
--- a/docs/developers/developing_iree/benchmarking.md
+++ b/docs/developers/developing_iree/benchmarking.md
@@ -21,7 +21,7 @@
 ```shell
 $ bazel run //iree/tools:iree-translate -- \
   -iree-mlir-to-vm-bytecode-module \
-  --iree-hal-target-backends=vmla \
+  -iree-hal-target-backends=vmvx \
   $PWD/iree/tools/test/iree-benchmark-module.mlir \
   -o /tmp/module.fb
 ```
@@ -31,7 +31,7 @@
 ```shell
 $ bazel run //iree/tools:iree-benchmark-module -- \
   --module_file=/tmp/module.fb \
-  --driver=vmla \
+  --driver=vmvx \
   --entry_function=abs \
   --function_input=i32=-2
 ```
@@ -78,7 +78,7 @@
 ```shell
 $ ./bazel-bin/iree/tools/iree-benchmark-module \
   --module_file=/tmp/module.fb \
-  --driver=vmla \
+  --driver=vmvx \
   --entry_function=abs \
   --function_input=i32=-2
 ```
@@ -110,7 +110,7 @@
 $ build/iree/tools/iree-translate \
   -iree-mlir-to-vm-bytecode-module \
   -iree-flow-export-benchmark-funcs \
-  -iree-hal-target-backends=vmla \
+  -iree-hal-target-backends=vmvx \
   iree/test/e2e/models/fullyconnected.mlir \
   -o /tmp/fullyconnected.vmfb
 ```
@@ -121,7 +121,7 @@
 ```shell
 $ build/iree/tools/iree-benchmark-module
   --module_file=/tmp/fullyconnected.vmfb
-  --driver=vmla
+  --driver=vmvx
 ```
 
 If no `entry_function` is specified, `iree-benchmark-module` will register a
diff --git a/docs/developers/developing_iree/developer_overview.md b/docs/developers/developing_iree/developer_overview.md
index e0caae5..eb7347a 100644
--- a/docs/developers/developing_iree/developer_overview.md
+++ b/docs/developers/developing_iree/developer_overview.md
@@ -95,7 +95,7 @@
 ```shell
 $ ../iree-build/iree/tools/iree-opt \
   -iree-transformation-pipeline \
-  -iree-hal-target-backends=vmla \
+  -iree-hal-target-backends=vmvx \
   $PWD/iree/test/e2e/models/fullyconnected.mlir
 ```
 
@@ -117,7 +117,7 @@
 ```shell
 $ ../iree-build/iree/tools/iree-translate \
   -iree-mlir-to-vm-bytecode-module \
-  -iree-hal-target-backends=vmla \
+  -iree-hal-target-backends=vmvx \
   $PWD/iree/tools/test/iree-run-module.mlir \
   -o /tmp/simple.vmfb
 ```
@@ -139,7 +139,7 @@
 ```shell
 $ ../iree-build/iree/tools/iree-run-module \
   --module_file=/tmp/simple.vmfb \
-  --driver=vmla \
+  --driver=vmvx \
   --entry_function=abs \
   --function_input=i32=-2
 ```
@@ -155,7 +155,7 @@
 ```shell
 $ ../iree-build/iree/tools/iree-translate \
   -iree-mlir-to-vm-bytecode-module \
-  -iree-hal-target-backends=vmla \
+  -iree-hal-target-backends=vmvx \
   $PWD/iree/test/e2e/xla_ops/abs.mlir \
   -o /tmp/abs.vmfb
 ```
@@ -163,7 +163,7 @@
 ```shell
 $ ../iree-build/iree/tools/iree-check-module \
   /tmp/abs.vmfb \
-  --driver=vmla
+  --driver=vmvx
 ```
 
 ### iree-run-mlir
@@ -182,7 +182,7 @@
 $ ../iree-build/iree/tools/iree-run-mlir \
   $PWD/iree/tools/test/iree-run-mlir.mlir \
   -function-input="i32=-2" \
-  -iree-hal-target-backends=vmla
+  -iree-hal-target-backends=vmvx
 ```
 
 ### iree-dump-module
diff --git a/docs/developers/developing_iree/e2e_benchmarking.md b/docs/developers/developing_iree/e2e_benchmarking.md
index 8b624e9..f2791bf 100644
--- a/docs/developers/developing_iree/e2e_benchmarking.md
+++ b/docs/developers/developing_iree/e2e_benchmarking.md
@@ -42,7 +42,7 @@
 # This is a Python 3 program. On some systems, such as Debian derivatives,
 # use 'python3' instead of 'python'.
 $ python ../iree/integrations/tensorflow/e2e/matrix_ops_static_test.py \
-    --target_backends=iree_vmla
+    --target_backends=iree_vmvx
 # View the generated artifacts:
 $ tree /tmp/iree/modules/MatrixOpsStaticModule/
 ```
@@ -52,7 +52,7 @@
 # --model: the tf.keras.applications model to test
 # --data: the dataset (and corresponding image shapes) to create the model for
 $ python ../iree/integrations/tensorflow/e2e/keras/applications/applications_test.py \
-    --target_backends=iree_vmla \
+    --target_backends=iree_vmvx \
     --model=MobileNetV3Small \
     --data=imagenet
 # View the generated artifacts:
@@ -65,7 +65,7 @@
 ```shell
 # Example for a generic module `ModuleName`:
 /tmp/iree/modules/ModuleName
-  ├── iree_vmla  # Or any other IREE backend.
+  ├── iree_vmvx  # Or any other IREE backend.
   │   ├── compiled.vmfb
   │   │   # A flatbuffer containing IREE's compiled code.
   │   └── traces
@@ -106,7 +106,7 @@
   │       │   └── flagfile
   │       └── matmul_rhs_batch
   │           └── flagfile
-  ├── iree_vmla
+  ├── iree_vmvx
   │   ├── compiled.vmfb
   │   └── traces  # ...same as iree_llvmaot/traces above.
   ├── iree_vulkan
@@ -168,7 +168,7 @@
 
 ```shell
 $ ./bazel-bin/iree/tools/iree-benchmark-module \
-  --flagfile="/tmp/iree/modules/MatrixOpsStaticModule/iree_vmla/traces/matmul_lhs_batch/flagfile"
+  --flagfile="/tmp/iree/modules/MatrixOpsStaticModule/iree_vmvx/traces/matmul_lhs_batch/flagfile"
 ```
 
 If you ran `applications_test.py` then you'll be able to benchmark
@@ -176,7 +176,7 @@
 
 ```shell
 $ ./bazel-bin/iree/tools/iree-benchmark-module \
-  --flagfile="/tmp/iree/modules/MobileNetV3Small/imagenet/iree_vmla/traces/predict/flagfile"
+  --flagfile="/tmp/iree/modules/MobileNetV3Small/imagenet/iree_vmvx/traces/predict/flagfile"
 ```
 
 ## 3. Benchmarking TFLite on desktop
@@ -254,19 +254,19 @@
 
 ```shell
 # Make a directory for the module/backend pair we want to benchmark.
-$ adb shell mkdir -p /data/local/tmp/MatrixOpsStaticModule/iree_vmla/
+$ adb shell mkdir -p /data/local/tmp/MatrixOpsStaticModule/iree_vmvx/
 
 # Transfer the files.
-$ adb push /tmp/iree/modules/MatrixOpsStaticModule/iree_vmla/* \
-  /data/local/tmp/MatrixOpsStaticModule/iree_vmla/
+$ adb push /tmp/iree/modules/MatrixOpsStaticModule/iree_vmvx/* \
+  /data/local/tmp/MatrixOpsStaticModule/iree_vmvx/
 ```
 
 ### 4.3 Benchmark the module
 
 ```shell
 $ adb shell /data/local/tmp/iree-benchmark-module \
-  --flagfile="/data/local/tmp/MatrixOpsStaticModule/iree_vmla/traces/matmul_lhs_batch/flagfile" \
-  --module_file="/data/local/tmp/MatrixOpsStaticModule/iree_vmla/compiled.vmfb"
+  --flagfile="/data/local/tmp/MatrixOpsStaticModule/iree_vmvx/traces/matmul_lhs_batch/flagfile" \
+  --module_file="/data/local/tmp/MatrixOpsStaticModule/iree_vmvx/compiled.vmfb"
 ```
 
 Note: Because the flagfile uses absolute paths, the `--module_file` flag must be
diff --git a/docs/developers/developing_iree/testing_guide.md b/docs/developers/developing_iree/testing_guide.md
index 9c69d0d..3cf8ded 100644
--- a/docs/developers/developing_iree/testing_guide.md
+++ b/docs/developers/developing_iree/testing_guide.md
@@ -199,13 +199,13 @@
 With CMake, run this from the build directory:
 
 ```shell
-$ ctest -R iree/test/e2e/xla_ops/check_vmla_vmla_floor.mlir
+$ ctest -R iree/test/e2e/xla_ops/check_vmvx_vmvx_floor.mlir
 ```
 
 With Bazel, run this from the repo root:
 
 ```shell
-$ bazel test iree/test/e2e/xla_ops:check_vmla_vmla_floor.mlir
+$ bazel test iree/test/e2e/xla_ops:check_vmvx_vmvx_floor.mlir
 ```
 
 ### Setting test environments
@@ -316,15 +316,15 @@
 load("//build_tools/bazel:iree_check_test.bzl", "iree_check_test")
 
 iree_check_test(
-    name = "check_vmla_vmla_floor.mlir",
+    name = "check_vmvx_vmvx_floor.mlir",
     src = "floor.mlir",
-    driver = "vmla",
-    target_backend = "vmla",
+    driver = "vmvx",
+    target_backend = "vmvx",
 )
 ```
 
 The target naming convention is "check_backend_driver_src". The generated test
-will automatically be tagged with a "driver=vmla" tag, which can help filter
+will automatically be tagged with a "driver=vmvx" tag, which can help filter
 tests by backend (especially when many tests are generated, as below).
 
 Usually we want to create a suite of tests across many backends and drivers.
@@ -335,17 +335,17 @@
 load("//build_tools/bazel:iree_check_test.bzl", "iree_check_single_backend_test_suite")
 
 iree_check_single_backend_test_suite(
-    name = "check_vmla_vmla",
+    name = "check_vmvx_vmvx",
     srcs = glob(["*.mlir"]),
-    driver = "vmla",
-    target_backend = "vmla",
+    driver = "vmvx",
+    target_backend = "vmvx",
 )
 ```
 
 This will generate a separate test target for each file in `srcs` with a name
 following the convention above as well as a Bazel
 [test_suite](https://docs.bazel.build/versions/master/be/general.html#test_suite)
-called "check_vmla_vmla" that will run all the generated tests.
+called "check_vmvx_vmvx" that will run all the generated tests.
 
 You can also generate suites across multiple pairs:
 
@@ -357,7 +357,7 @@
     srcs = ["success.mlir"],
     # Leave this argument off to run on all supported backend/driver pairs.
     target_backends_and_drivers = [
-        ("vmla", "vmla"),
+        ("vmvx", "vmvx"),
         ("vulkan-spirv", "vulkan"),
     ],
 )