Marks all unreleased changes as 1.12.0.

Signed-off-by: Takahiro Itazuri <itazur@amazon.com>

Adds v1.12 to the release status table and marks v1.10 as unsupported.

Signed-off-by: Takahiro Itazuri <itazur@amazon.com>

Intel Sapphire Rapids and ARM Graviton4 are now supported.

Signed-off-by: Takahiro Itazuri <itazur@amazon.com>

Update version number / CREDITS

Signed-off-by: Takahiro Itazuri <itazur@amazon.com>

`set -x` shows what commands ran, which helps us identify what failed
in the release process.

Signed-off-by: Takahiro Itazuri <itazur@amazon.com>

I renamed the custom CPU template files uppercase, but I forgot to
update their names in release.sh.

Fixes: 2862941 ("chore: Use uppercase for custom CPU templates")
Signed-off-by: Takahiro Itazuri <itazur@amazon.com>

The current metric dimensions are so that we have 13k+ different sets of
dimensions for each metric, which makes it impossible to plot in
CloudWatch.
This change adds a new set of dimensions with just the test name so that
we reduce it to a few hundreds and are able to plot them (CW limit is
500).

Signed-off-by: Riccardo Mancini <mancio@amazon.com>
Signed-off-by: Patrick Roy <roypat@amazon.co.uk>

The `max_size` field is public, so no need for a getter.

Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>

The size of queue set by the driver must be always less or equal to the
queue size in FC. This is checked before device activation.
This removes the need for `actual_size` function.

Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>

Currently block device has a guest notification logic
inside it's request processing loop. This can create a
situation when guest can continuously add more requests to the
queue, making the whole request processing loop arbitrary long.
This is an issue, since it block any other IO from being processed.

The solution is to simply notify guest one time, after all current
requests are processed.

Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
Signed-off-by: Riccardo Mancini <mancio@amazon.com>

VIRTIO spec states:
```
After the device writes a descriptor index into the used ring:
  If the idx field in the used ring (which determined where that
  descriptor index was placed) was equal to used_event, the device
  MUST send a notification.
```
The current implementation does not follow this very precisely. It
bumps used ring index when new descriptors are added to the used
ring. But the check if the notification is needed is postponed to
later processing stage.
To be more VIRTIO spec compliant simply move the logic for updating
the used ring index into the later processing stage as well, just
before the check if the notification should be send.

Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>

Add a new changelog entry for the block device fairness fix.

Signed-off-by: Riccardo Mancini <mancio@amazon.com>

Update version number / CHANGELOG / CREDITS

Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>

Nested virtualization is now disabled and some cpu features/MSRs now
should be marked as host only.

These cpu features/MSRs are described the AMD reference manual at
"SVM Revision and Feature Identification" section.

Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>

Now this MSR is host only and not available in the guest.
Check AMD reference manual at "SVM Revision and Feature Identification"
section for more information.

Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>

The link we were using to download the Spectre/Meltdown checker script
stopped working and caused our CI to fail consistently.

Use this alternative link to download the script.

(cherry picked from commit e5b4f26)

Signed-off-by: Babis Chalios <bchalios@amazon.es>