On Mon, Nov 07, 2022 at 09:55:31AM +0700, Bagas Sanjaya wrote: > On 11/6/22 18:22, Conor Dooley wrote: > >> + +------------------+---------+------------------+---------+----------------------------------------------------------+ > >> + | Start addr | Offset | End addr | Size | VM area description | > >> + +==================+=========+==================+=========+==========================================================+ > >> + | 0000000000000000 | 0 | 0000003fffffffff | 256 GB | user-space virtual memory, different per mm | > >> + +------------------+---------+------------------+---------+----------------------------------------------------------+ > >> + | 0000004000000000 | +256 GB | ffffffbfffffffff | ~16M TB | ... huge, almost 64 bits wide hole of non-canonical | > >> + | | | | | virtual memory addresses up to the -256 GB | > >> + | | | | | starting offset of kernel mappings. | > >> + +------------------+---------+------------------+---------+----------------------------------------------------------+ > >> + | Kernel-space virtual memory, shared between all processes: | > >> + +------------------+---------+------------------+---------+----------------------------------------------------------+ > >> + | ffffffc6fee00000 | -228 GB | ffffffc6feffffff | 2 MB | fixmap | > >> + +------------------+---------+------------------+---------+----------------------------------------------------------+ > >> + | ffffffc6ff000000 | -228 GB | ffffffc6ffffffff | 16 MB | PCI io | > >> + +------------------+---------+------------------+---------+----------------------------------------------------------+ > > ^ > > Will these numbers remain right-aligned in the formatted doc? They were > > aligned before in the text form & no longer appear to be. > > > > These numbers also become wrapped in their cells. > > However, in order to fix alignment of these, custom CSS is needed, similar > to one in StackOverflow [1]. Hmm. In that case I'd be inclined to agree with Akira that this should be left as is. Thanks, Conor.
