From: Conor Dooley <conor.dooley@microchip.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Conor Dooley <conor@kernel.org>, <linux-doc@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alexandre.ghiti@canonical.com>
Subject: Re: [PATCH] Documentation: riscv: tableize memory layout
Date: Mon, 7 Nov 2022 07:26:23 +0000 [thread overview]
Message-ID: <Y2izHzwaYLDCOECc@wendy> (raw)
In-Reply-To: <aebae1eb-ed56-00a9-101f-c4e5ab0af91a@gmail.com>
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.
next prev parent reply other threads:[~2022-11-07 7:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 10:02 [PATCH] Documentation: riscv: tableize memory layout Bagas Sanjaya
2022-11-06 11:22 ` Conor Dooley
2022-11-07 2:55 ` Bagas Sanjaya
2022-11-07 7:26 ` Conor Dooley [this message]
2022-11-06 12:04 ` Akira Yokosawa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y2izHzwaYLDCOECc@wendy \
--to=conor.dooley@microchip.com \
--cc=alexandre.ghiti@canonical.com \
--cc=aou@eecs.berkeley.edu \
--cc=bagasdotme@gmail.com \
--cc=conor@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).