On 5/31/23 10:08, Richard Henderson wrote:
On 5/31/23 09:47, Ard Biesheuvel wrote:
On Wed, 31 May 2023 at 18:33, Richard Henderson
Thanks. I spent some time yesterday looking at this, with an encrypted disk
test case and
could only measure 0.6% and 0.5% for total overhead of decrypt and encry
On 5/31/23 09:47, Ard Biesheuvel wrote:
On Wed, 31 May 2023 at 18:33, Richard Henderson
wrote:
On 5/31/23 04:22, Ard Biesheuvel wrote:
Use the host native instructions to implement the AES instructions
exposed by the emulated target. The mapping is not 1:1, so it requires a
bit of fiddling to
On Wed, 31 May 2023 at 18:33, Richard Henderson
wrote:
>
> On 5/31/23 04:22, Ard Biesheuvel wrote:
> > Use the host native instructions to implement the AES instructions
> > exposed by the emulated target. The mapping is not 1:1, so it requires a
> > bit of fiddling to get the right result.
> >
>
On 5/31/23 04:22, Ard Biesheuvel wrote:
Use the host native instructions to implement the AES instructions
exposed by the emulated target. The mapping is not 1:1, so it requires a
bit of fiddling to get the right result.
This is still RFC material - the current approach feels too ad-hoc, but
giv
Use the host native instructions to implement the AES instructions
exposed by the emulated target. The mapping is not 1:1, so it requires a
bit of fiddling to get the right result.
This is still RFC material - the current approach feels too ad-hoc, but
given the non-1:1 correspondence, doing a pro
