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 7/8] xen/riscv: page table handling
Date: Wed, 25 Sep 2024 12:07:45 +0200	[thread overview]
Message-ID: <ecab08fbbe1a1e364cf6d4bf9dafa42ced4faef4.camel@gmail.com> (raw)
In-Reply-To: <9371e8fd-a1de-40df-8994-814dd6196953@suse.com>

On Tue, 2024-09-24 at 15:31 +0200, Jan Beulich wrote:
> On 24.09.2024 13:30, oleksii.kurochko@gmail.com wrote:
> > On Tue, 2024-09-24 at 12:49 +0200, Jan Beulich wrote:
> > > On 13.09.2024 17:57, Oleksii Kurochko wrote:
> > > > +static int pt_next_level(bool alloc_tbl, pte_t **table,
> > > > unsigned
> > > > int offset)
> > > > +{
> > > > +    pte_t *entry;
> > > > +    mfn_t mfn;
> > > > +
> > > > +    entry = *table + offset;
> > > > +
> > > > +    if ( !pte_is_valid(*entry) )
> > > > +    {
> > > > +        if ( !alloc_tbl )
> > > > +            return XEN_TABLE_MAP_FAILED;
> > > > +
> > > > +        if ( create_table(entry) )
> > > > +            return XEN_TABLE_MAP_FAILED;
> > > 
> > > You're still losing the -ENOMEM here.
> > Agree, I will save the return value of create_table and return it.
> 
> That won't work very well, will it? 
I think it will work, just will be needed another one check in
pt_update_entry() where pt_next_level() is called:
        if ( (rc == XEN_TABLE_MAP_FAILED) || (rc == -ENOMEM) )
        ...

> Imo you need a new XEN_TABLE_MAP_NOMEM.
> (And then XEN_TABLE_MAP_FAILED may want renaming to e.g.
> XEN_TABLE_MAP_NONE).
I am still curious if we really need this separation. If to in this way
then it should be updated the check in pt_update_entry():
   --- a/xen/arch/riscv/pt.c
   +++ b/xen/arch/riscv/pt.c
   @@ -165,10 +165,10 @@ static int pt_next_level(bool alloc_tbl, pte_t
   **table, unsigned int offset)
        if ( !pte_is_valid(*entry) )
        {
            if ( !alloc_tbl )
   -            return XEN_TABLE_MAP_FAILED;
   +            return XEN_TABLE_MAP_NONE;
    
            if ( create_table(entry) )
   -            return XEN_TABLE_MAP_FAILED;
   +            return XEN_TABLE_MAP_NOMEM;
        }
    
        if ( pte_is_mapping(*entry) )
   @@ -209,7 +209,7 @@ static int pt_update_entry(mfn_t root, unsigned
   long virt,
        for ( ; level > target; level-- )
        {
            rc = pt_next_level(alloc_tbl, &table, offsets[level]);
   -        if ( rc == XEN_TABLE_MAP_FAILED )
   +        if ( (rc == XEN_TABLE_MAP_NONE) && (rc == XEN_TABLE_MAP_NOMEM)
   )
            {
                rc = 0;
But the handling of XEN_TABLE_MAP_NONE and XEN_TABLE_MAP_NOMEM seems to
me should be left the same as this one part of the code actually
catching the case when create_table() returns -ENOMEM:
   pt_next_level()
   {
   ...
               if ( flags & (PTE_VALID | PTE_POPULATE) )
               {
                   dprintk(XENLOG_ERR,
                           "%s: Unable to map level %u\n", __func__,
   level);
                   rc = -ENOMEM;
               }
   ...
   
~ Oleksii


  reply	other threads:[~2024-09-25 10:08 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
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 [this message]
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=ecab08fbbe1a1e364cf6d4bf9dafa42ced4faef4.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.