Note: lists.riscv.org will be down for maintenance on Wednesday, October 5th, starting at 9AM Pacific Time (4PM Wednesday October 5, 2022 UTC), for approximately one hour.
- RISC-V Vector Extension post-public review updates - fault flagging
Re: RISC-V Vector Extension post-public review updates - fault flagging
On 2021-11-17 8:45 p.m., Andrew
On Wed, Nov 17, 2021 at 5:41
PM Jonathan Behrens <behrensj@...
On Wed, Nov 17,
2021 at 4:19 PM Jonathan Behrens <behrensj@...
security concern was being able to probe
addresses to find accessible regions without
free of being killed on touching a
prohibited region. It was noted that this
is still present even for unit-stride in
supervisor mode when using translation to
arbitrarily probe supervisor physical space.
However, I believe these security concerns
are manageable through control mechanisms at
higher privilege levels
Could someone say what these control
mechanisms are? In particular, it seems like
a VS-mode guest operating system could probe
the entire guest physical address space
using fault-on-first load without triggering
any intervention from HS-mode or M-mode.
Perhaps I'm being obtuse, but I'm having
trouble understanding why this specific case is
a concern: it's within VS-mode's purview to know
anything and everything about the guest physical
address space. (The situation is materially
different than S vs. U, because those two share
a VA space, whereas VS' GPA space is disjoint
from HS' VA space.)
The physical address space that the hypervisor
tells the guest about may not match the one installed
in hgatp. For instance, some pages of the guest's
memory might be marked copy-on-write or swapped out to
disk. Or a particular device may supposedly be mapped
into the guest VM, but actually just be an unmapped
region so the host can trap-and-emulate any accesses
to it. Even today it is possible for a guest VM to
indirectly learn that these things might be happening,
but directly being able to check whether a page is
mapped adds a new level.
Yeah, agreed that detecting paged-out pages is a similar
The VS having this awareness can be very beneficial.
It allows the OS to better manage its resources. It can switch to
handling other supervisory actions while that data is paged/staged
Never the less, the control mechanisms I previously mentioned
apply here as well. The VS is in control, it can "leak" or not as
it sees fit.
(Though I think COW is not relevant here, since we're
only talking about load instructions.)
Join firstname.lastname@example.org to automatically receive all group messages.