All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleksii Kurochko <inisider@gmail.com>
To: Julien Grall <julien@xen.org>, 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>,
	Stefano Stabellini <sstabellini@kernel.org>,
	 xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 5/8] xen/riscv: introduce asm/pmap.h header
Date: Mon, 22 Jul 2024 19:09:51 +0200	[thread overview]
Message-ID: <a53ef38e044db149bb37b70f1e56a33c6a3e7c83.camel@gmail.com> (raw)
In-Reply-To: <623da862-8e76-4d40-9aa9-b02c8fd9944d@xen.org>

On Mon, 2024-07-22 at 15:48 +0100, Julien Grall wrote:
> Hi,
> 
> On 22/07/2024 15:44, Oleksii Kurochko wrote:
> > On Mon, 2024-07-22 at 14:54 +0200, Jan Beulich wrote:
> > > On 12.07.2024 18:22, Oleksii Kurochko wrote:
> > > > --- /dev/null
> > > > +++ b/xen/arch/riscv/include/asm/pmap.h
> > > > @@ -0,0 +1,28 @@
> > > > +#ifndef __ASM_PMAP_H__
> > > > +#define __ASM_PMAP_H__
> > > > +
> > > > +#include <xen/bug.h>
> > > > +#include <xen/mm.h>
> > > > +
> > > > +#include <asm/fixmap.h>
> > > > +
> > > > +static inline void arch_pmap_map(unsigned int slot, mfn_t mfn)
> > > > +{
> > > > +    pte_t *entry = &xen_fixmap[slot];
> > > > +    pte_t pte;
> > > > +
> > > > +    ASSERT(!pte_is_valid(*entry));
> > > > +
> > > > +    pte = mfn_to_xen_entry(mfn, PAGE_HYPERVISOR_RW);
> > > > +    pte.pte |= PTE_LEAF_DEFAULT;
> > > > +    write_pte(entry, pte);
> > > > +}
> > > > +
> > > > +static inline void arch_pmap_unmap(unsigned int slot)
> > > > +{
> > > > +    pte_t pte = {};
> > > > +
> > > > +    write_pte(&xen_fixmap[slot], pte);
> > > > +}
> > > 
> > > Why are these not using set_fixmap() / clear_fixmap()
> > > respectively?
> > They haven't been introduced yet. And I thought that these fucntion
> > are
> > used only in pmap_{un}map() and that is the reason why I decided to
> > not
> > introduce them. But while writing the answer on another comment, I
> > found other places where set_fixmap() / clear_fixmap() are used, so
> > I
> > will introduce them and reuse here.
> 
> I am guessing you are going to implement set_fixmap()/clear_fixmap() 
> using map_pages_to_xen(). If so, for early boot you are going to end
> up 
> in a circular loop because map_pages_to_xen() will likely use pmap() 
> which will call set_fixmap().
I am going to implement that in the following way as I faced the
described by you issue when I first time tried to implement it using
map_pages_to_xen():
   /* Map a 4k page in a fixmap entry */
   void set_fixmap(unsigned map, mfn_t mfn, unsigned int flags)
   {
       pte_t pte;
   
       pte = mfn_to_xen_entry(mfn, flags);
       pte.pte |= PTE_LEAF_DEFAULT;
       write_pte(&xen_fixmap[pt_index(0, FIXMAP_ADDR(map))], pte);
   }
   
   /* Remove a mapping from a fixmap entry */
   void clear_fixmap(unsigned map)
   {
       pte_t pte = {0};
       write_pte(&xen_fixmap[pt_index(0, FIXMAP_ADDR(map))], pte);
   }
   
~ Oleksii

> 
> There is a big comment in common/pmap.c which explain why arch_pmap_*
> was introduced rather than calling *_fixmap() directly:
> 
>      /*
>       * We cannot use set_fixmap() here. We use PMAP when the domain
> map
>       * page infrastructure is not yet initialized, so 
> map_pages_to_xen() called
>       * by set_fixmap() needs to map pages on demand, which then
> calls 
> pmap()
>       * again, resulting in a loop. Modify the PTEs directly instead.
> The same
>       * is true for pmap_unmap().
>       */
> 
> Cheers,
> 



  reply	other threads:[~2024-07-22 17:10 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-12 16:22 [PATCH v2 0/8] RISCV device tree mapping Oleksii Kurochko
2024-07-12 16:22 ` [PATCH v6 1/8] xen/device-tree: Move Arm's setup.c bootinfo functions to common Oleksii Kurochko
2024-07-15  8:36   ` Jan Beulich
2024-07-15 10:15   ` Michal Orzel
2024-07-15 13:42     ` Oleksii
2024-07-12 16:22 ` [PATCH v6 2/8] xen/common: Move Arm's bootfdt.c " Oleksii Kurochko
2024-07-12 16:22 ` [PATCH v2 3/8] xen/riscv: enable CONFIG_HAS_DEVICE_TREE Oleksii Kurochko
2024-07-15  8:40   ` Jan Beulich
2024-07-12 16:22 ` [PATCH v2 4/8] xen/riscv: setup fixmap mapping Oleksii Kurochko
2024-07-21  8:46   ` Julien Grall
2024-07-22 14:31     ` Oleksii
2024-07-22 14:44       ` Julien Grall
2024-07-23 12:58     ` oleksii.kurochko
2024-07-23 13:32       ` Julien Grall
2024-07-23 13:27     ` oleksii.kurochko
2024-07-23 13:33       ` Julien Grall
2024-07-23 13:38         ` oleksii.kurochko
2024-07-22 12:42   ` Jan Beulich
2024-07-22 14:36     ` Oleksii
2024-07-22 15:25       ` Jan Beulich
2024-07-22 17:04         ` oleksii.kurochko
2024-07-23 13:34           ` oleksii.kurochko
2024-07-12 16:22 ` [PATCH v2 5/8] xen/riscv: introduce asm/pmap.h header Oleksii Kurochko
2024-07-21  8:51   ` Julien Grall
2024-07-22 12:58     ` Jan Beulich
2024-07-22 14:57       ` Julien Grall
2024-07-22 14:40     ` Oleksii
2024-07-22 12:54   ` Jan Beulich
2024-07-22 14:44     ` Oleksii Kurochko
2024-07-22 14:48       ` Julien Grall
2024-07-22 17:09         ` Oleksii Kurochko [this message]
2024-07-22 17:21           ` Julien Grall
2024-07-23  8:02             ` Oleksii Kurochko
2024-07-23  8:36               ` Jan Beulich
2024-07-23  8:55                 ` oleksii.kurochko
2024-07-23 10:02                   ` Jan Beulich
2024-07-23 15:36                     ` oleksii.kurochko
2024-07-23 15:49                       ` Julien Grall
2024-07-23 17:25                         ` oleksii.kurochko
2024-07-23 17:28                           ` oleksii.kurochko
2024-07-23 18:44                             ` Julien Grall
2024-07-12 16:22 ` [PATCH v2 6/8] xen/riscv: introduce generic Xen page table handling Oleksii Kurochko
2024-07-21  9:02   ` Julien Grall
2024-07-22  6:59     ` Jan Beulich
2024-07-22 14:51     ` Oleksii
2024-07-12 16:22 ` [PATCH v2 7/8] xen/riscv: select CONFIG_GENREIC_PT Oleksii Kurochko
2024-07-12 16:22 ` [PATCH v2 8/8] xen/riscv: introduce early_fdt_map() Oleksii Kurochko
2024-07-15  8:52   ` Jan Beulich
2024-07-15 13:58     ` Oleksii
2024-07-15 14:58       ` Jan Beulich
2024-07-15 15:00         ` Jan Beulich

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=a53ef38e044db149bb37b70f1e56a33c6a3e7c83.camel@gmail.com \
    --to=inisider@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.