All of lore.kernel.org
 help / color / mirror / Atom feed
From: oleksii.kurochko@gmail.com
To: Jan Beulich <jbeulich@suse.com>
Cc: Alistair Francis <alistair.francis@wdc.com>,
	Bob Eshleman <bobbyeshleman@gmail.com>,
	Connor Davis <connojdavis@gmail.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Julien Grall <julien@xen.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v7 3/8] xen/riscv: set up fixmap mappings
Date: Mon, 16 Sep 2024 11:50:01 +0200	[thread overview]
Message-ID: <20c2ebafcdb5e036969f02dd7dac39ff8a6b9dd4.camel@gmail.com> (raw)
In-Reply-To: <1b62f8bf-1dab-47a7-9016-b495757132f9@suse.com>

On Mon, 2024-09-16 at 08:32 +0200, Jan Beulich wrote:
> On 13.09.2024 17:57, Oleksii Kurochko wrote:
> > Set up fixmap mappings and the L0 page table for fixmap support.
> > 
> > {set, clear}_fixmap() is expected to be implemented using
> > map_pages_to_xen(), which, in turn, is only expected to use
> > arch_pmap_map().
> 
> Now you've left out what you actually mean to justify here: The
> exposure / direct access to xen_fixmap[]. I'd also suggest to
> drop "only" - I guess I used that in a reply to v6 to emphasize
> what I wanted to get across, but it makes not as much sense here.
> Instead adding "during early boot" at the end of the sentence may
> provide additional context.

Agree, it will be better to  return details:
   Modify the PTEs (xen_fixmap[]) directly in arch_pmap_map() instead
   of using set_fixmap() which is expected to be implemented using
   map_pages_to_xen(), which, in turn, is expected to use
   arch_pmap_map() during early boot, resulting in a loop.

Probably it would be better just:
   Modify xen_fixmap[] ...

> 
> > Define new macros in riscv/config.h for calculating
> > the FIXMAP_BASE address, including BOOT_FDT_VIRT_{START, SIZE},
> > XEN_VIRT_SIZE, and XEN_VIRT_END.
> > 
> > Update the check for Xen size in riscv/lds.S to use
> 
> Nit: xen.lds.S
> 
> > XEN_VIRT_SIZE instead of a hardcoded constant.
> > 
> > Signed-off-by: Oleksii Kurochko <oleksii.kurochko@gmail.com>
> 
> With the adjustments (again doable while committing)
That would be great.

> Acked-by: Jan Beulich <jbeulich@suse.com>
Thanks a lot.

~ Oleksii


  reply	other threads:[~2024-09-16  9:50 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-13 15:57 [PATCH v7 0/8] device tree mapping Oleksii Kurochko
2024-09-13 15:57 ` [PATCH v7 1/8] xen/riscv: use {read,write}{b,w,l,q}_cpu() to define {read,write}_atomic() Oleksii Kurochko
2024-09-16  6:17   ` Jan Beulich
2024-09-13 15:57 ` [PATCH v7 2/8] xen/riscv: allow write_atomic() to work with non-scalar types Oleksii Kurochko
2024-09-16  6:25   ` Jan Beulich
2024-09-16  8:54     ` oleksii.kurochko
2024-09-13 15:57 ` [PATCH v7 3/8] xen/riscv: set up fixmap mappings Oleksii Kurochko
2024-09-16  6:32   ` Jan Beulich
2024-09-16  9:50     ` oleksii.kurochko [this message]
2024-09-13 15:57 ` [PATCH v7 4/8] xen/riscv: introduce asm/pmap.h header Oleksii Kurochko
2024-09-13 15:57 ` [PATCH v7 5/8] xen/riscv: introduce functionality to work with CPU info Oleksii Kurochko
2024-09-16  6:48   ` Jan Beulich
2024-09-16 10:07     ` oleksii.kurochko
2024-09-13 15:57 ` [PATCH v7 6/8] xen/riscv: introduce and initialize SBI RFENCE extension Oleksii Kurochko
2024-09-13 15:57 ` [PATCH v7 7/8] xen/riscv: page table handling Oleksii Kurochko
2024-09-24 10:49   ` Jan Beulich
2024-09-24 11:30     ` oleksii.kurochko
2024-09-24 13:31       ` Jan Beulich
2024-09-25 10:07         ` oleksii.kurochko
2024-09-25 14:22           ` Jan Beulich
2024-09-25 14:50             ` oleksii.kurochko
2024-09-25 14:58               ` Jan Beulich
2024-09-27  8:49                 ` oleksii.kurochko
2024-09-27  9:15                   ` Jan Beulich
2024-09-27 11:32                     ` oleksii.kurochko
2024-09-27 12:00                       ` Jan Beulich
2024-09-13 15:57 ` [PATCH v7 8/8] xen/riscv: introduce early_fdt_map() Oleksii Kurochko

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=20c2ebafcdb5e036969f02dd7dac39ff8a6b9dd4.camel@gmail.com \
    --to=oleksii.kurochko@gmail.com \
    --cc=alistair.francis@wdc.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=bobbyeshleman@gmail.com \
    --cc=connojdavis@gmail.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.