Please note: We are aware of an issue affecting replies on the Arm Community forums, which may not be loading as expected.

We apologize for any inconvenience and appreciate your patience while we investigate and work to resolve the issue.

Thank you for your understanding.

  • State Accepted Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 20 subscribers
  • Views 22473 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to understand Device-nGRE?

ocean

Hi, experts,

Re-Orderingis a new attribute in ARMv8.

Can you explain Device-nGRE, and How to distinguish Device-nGRE and Device-nGnRE?

Thanks.

Parents
  • 0 in reply to Ash Wilding

    Hi Ash,

    in the case of Device-nGnRE, what does IMPLEMENTATION DEFINED block size means?

    Is it related to (according to the Armv8 architecture specification)

    A Memory-mapped peripheral occupies a memory region of IMPLEMENTATION DEFINED size and
    can be accessed using load and store instructions.

     

    My misunderstanding comes from the Armv7a specification which states:

     

    in A3.8.2 Ordering requirements for memory accesses:

    The size of a memory mapped peripheral, or a block of memory, is IMPLEMENTATION DEFINED, but is not smaller
    than 1KByte.

    Note: This implies that the maximum memory-mapped peripheral size for which the architecture guarantees order for all
    implementations is 1KB.

     

    If the pheriperal has a memory map greater than 1KB, the Armv7 architecture doesn't guarantee ordering? If true, does the same limitation

    exist for Armv8, for the Device-nGnRE? 

     

    Bas

     

     

     

     

     

     

     

Reply
  • 0 in reply to Ash Wilding

    Hi Ash,

    in the case of Device-nGnRE, what does IMPLEMENTATION DEFINED block size means?

    Is it related to (according to the Armv8 architecture specification)

    A Memory-mapped peripheral occupies a memory region of IMPLEMENTATION DEFINED size and
    can be accessed using load and store instructions.

     

    My misunderstanding comes from the Armv7a specification which states:

     

    in A3.8.2 Ordering requirements for memory accesses:

    The size of a memory mapped peripheral, or a block of memory, is IMPLEMENTATION DEFINED, but is not smaller
    than 1KByte.

    Note: This implies that the maximum memory-mapped peripheral size for which the architecture guarantees order for all
    implementations is 1KB.

     

    If the pheriperal has a memory map greater than 1KB, the Armv7 architecture doesn't guarantee ordering? If true, does the same limitation

    exist for Armv8, for the Device-nGnRE? 

     

    Bas

     

     

     

     

     

     

     

Children
No data