class SecureHeapProperties

Defined at line 6494 of file fidling/gen/sdk/fidl/fuchsia.sysmem2/fuchsia.sysmem2/cpp/fidl/fuchsia.sysmem2/cpp/natural_types.h

Public Methods

void SecureHeapProperties ()

Defined at line 6499 of file fidling/gen/sdk/fidl/fuchsia.sysmem2/fuchsia.sysmem2/cpp/fidl/fuchsia.sysmem2/cpp/natural_types.h

void SecureHeapProperties (SecureHeapProperties && )

Defined at line 6500 of file fidling/gen/sdk/fidl/fuchsia.sysmem2/fuchsia.sysmem2/cpp/fidl/fuchsia.sysmem2/cpp/natural_types.h

void SecureHeapProperties (Storage_ storage)

void SecureHeapProperties (const SecureHeapProperties & other)

SecureHeapProperties & operator= (const SecureHeapProperties & other)

bool operator== (const SecureHeapProperties & other)

bool operator!= (const SecureHeapProperties & other)

bool IsEmpty ()

const std::optional< ::fuchsia_sysmem2::Heap> & heap ()

The Heap is repeated here for convenience.

::std::optional< ::fuchsia_sysmem2::Heap> & heap ()

The Heap is repeated here for convenience.

SecureHeapProperties & heap (std::optional< ::fuchsia_sysmem2::Heap> value)

The Heap is repeated here for convenience.

const std::optional<bool> & dynamic_protection_ranges ()

If true, more than one call to SetPhysicalSecureHeap() for the same

heap is allowed. If false, only one SetPhyscialSecureHeap() call is

allowed, and no calls to DeleteSecureHeapPhysicalRange() or

ModifySecureHeapPhysicalRange() are allowed. Even when this is false,

the SecureMem server (driver) is still responsible for de-protecting

just before warm reboot if protected ranges would not otherwise be

cleaned up during a warm reboot.

::std::optional<bool> & dynamic_protection_ranges ()

If true, more than one call to SetPhysicalSecureHeap() for the same

heap is allowed. If false, only one SetPhyscialSecureHeap() call is

allowed, and no calls to DeleteSecureHeapPhysicalRange() or

ModifySecureHeapPhysicalRange() are allowed. Even when this is false,

the SecureMem server (driver) is still responsible for de-protecting

just before warm reboot if protected ranges would not otherwise be

cleaned up during a warm reboot.

SecureHeapProperties & dynamic_protection_ranges (std::optional<bool> value)

If true, more than one call to SetPhysicalSecureHeap() for the same

heap is allowed. If false, only one SetPhyscialSecureHeap() call is

allowed, and no calls to DeleteSecureHeapPhysicalRange() or

ModifySecureHeapPhysicalRange() are allowed. Even when this is false,

the SecureMem server (driver) is still responsible for de-protecting

just before warm reboot if protected ranges would not otherwise be

cleaned up during a warm reboot.

SecureHeapProperties & operator= (SecureHeapProperties && )

Defined at line 6501 of file fidling/gen/sdk/fidl/fuchsia.sysmem2/fuchsia.sysmem2/cpp/fidl/fuchsia.sysmem2/cpp/natural_types.h

const std::optional<uint32_t> & protected_range_granularity ()

The granularity of protection ranges. If the granularity of start is

different than granularity of end or length, then this is the max

granularity value among those values.

This must be a power of 2. The client must not request ranges that

specify smaller granularity.

This must be at least zx_system_page_size() even if the HW can do

smaller granularity.

::std::optional<uint32_t> & protected_range_granularity ()

The granularity of protection ranges. If the granularity of start is

different than granularity of end or length, then this is the max

granularity value among those values.

This must be a power of 2. The client must not request ranges that

specify smaller granularity.

This must be at least zx_system_page_size() even if the HW can do

smaller granularity.

SecureHeapProperties & protected_range_granularity (std::optional<uint32_t> value)

The granularity of protection ranges. If the granularity of start is

different than granularity of end or length, then this is the max

granularity value among those values.

This must be a power of 2. The client must not request ranges that

specify smaller granularity.

This must be at least zx_system_page_size() even if the HW can do

smaller granularity.

const std::optional<uint64_t> & max_protected_range_count ()

The SecureMem server should not count reserved ranges that the SecureMem

server uses internally to get from range set A to range set B, if the

SecureMem server needs to do any emulation of that sort. Normally such

emulation by the SecureMem server is unnecessary. If any ranges are

reserved by the SecureMem server, those reserved ranges are not

available for use by the SecureMem client.

If the number of ranges is limited only by available memory, it's ok for

the SecureMem server to report 0xFFFFFFFFFFFFFFFF for this value. The

field must still be set. As usual, the SecureMem server should ensure

that SetPhysicalSecureHeapRanges() succeeds or fails atomically (either

fully updates or rolls back before completing).

::std::optional<uint64_t> & max_protected_range_count ()

The SecureMem server should not count reserved ranges that the SecureMem

server uses internally to get from range set A to range set B, if the

SecureMem server needs to do any emulation of that sort. Normally such

emulation by the SecureMem server is unnecessary. If any ranges are

reserved by the SecureMem server, those reserved ranges are not

available for use by the SecureMem client.

If the number of ranges is limited only by available memory, it's ok for

the SecureMem server to report 0xFFFFFFFFFFFFFFFF for this value. The

field must still be set. As usual, the SecureMem server should ensure

that SetPhysicalSecureHeapRanges() succeeds or fails atomically (either

fully updates or rolls back before completing).

SecureHeapProperties & max_protected_range_count (std::optional<uint64_t> value)

The SecureMem server should not count reserved ranges that the SecureMem

server uses internally to get from range set A to range set B, if the

SecureMem server needs to do any emulation of that sort. Normally such

emulation by the SecureMem server is unnecessary. If any ranges are

reserved by the SecureMem server, those reserved ranges are not

available for use by the SecureMem client.

If the number of ranges is limited only by available memory, it's ok for

the SecureMem server to report 0xFFFFFFFFFFFFFFFF for this value. The

field must still be set. As usual, the SecureMem server should ensure

that SetPhysicalSecureHeapRanges() succeeds or fails atomically (either

fully updates or rolls back before completing).

const std::optional<bool> & is_mod_protected_range_available ()

Iff true, ModifySecureHeapPhysicalRange() is implemented. Calling

ModifySecureHeapPhysicalRange() when is_mod_protected_range_available

is false is prohibited. Don't attempt to detect availability of

ModifySecureHeapPhysicalRange() by calling it to see if it fails; it

may ZX_PANIC().

::std::optional<bool> & is_mod_protected_range_available ()

Iff true, ModifySecureHeapPhysicalRange() is implemented. Calling

ModifySecureHeapPhysicalRange() when is_mod_protected_range_available

is false is prohibited. Don't attempt to detect availability of

ModifySecureHeapPhysicalRange() by calling it to see if it fails; it

may ZX_PANIC().

SecureHeapProperties & is_mod_protected_range_available (std::optional<bool> value)

Iff true, ModifySecureHeapPhysicalRange() is implemented. Calling

ModifySecureHeapPhysicalRange() when is_mod_protected_range_available

is false is prohibited. Don't attempt to detect availability of

ModifySecureHeapPhysicalRange() by calling it to see if it fails; it

may ZX_PANIC().

void SecureHeapProperties (::fidl::internal::DefaultConstructPossiblyInvalidObjectTag )

Friends

class MemberVisitor

class NaturalTableCodingTraits