All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: oleksii.kurochko@gmail.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: Fri, 27 Sep 2024 14:00:33 +0200	[thread overview]
Message-ID: <82a81ef3-9502-4891-841f-9946f44ff2eb@suse.com> (raw)
In-Reply-To: <edc8bda6d7cf67b370652ea17b5d3ce462adf962.camel@gmail.com>

On 27.09.2024 13:32, oleksii.kurochko@gmail.com wrote:
> Just to be sure. Do you mean the following:
> 
> diff --git a/xen/arch/riscv/pt.c b/xen/arch/riscv/pt.c
> index d7eb207ddc..6cd2e595b6 100644
> --- a/xen/arch/riscv/pt.c
> +++ b/xen/arch/riscv/pt.c
> @@ -209,24 +209,15 @@ 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_NOMEM )
>          {
> -            rc = 0;
> -
> -            /*
> -             * We are here because pt_next_level has failed to map
> -             * the intermediate page table (e.g the table does not
> exist
> -             * and the pt couldn't be allocated). It is a valid case
> when
> -             * removing a mapping as it may not exist in the page
> table.
> -             * In this case, just ignore it.
> -             */
> -            if ( flags & (PTE_VALID | PTE_POPULATE) )
> -            {
> -                dprintk(XENLOG_ERR,
> -                        "%s: Unable to map level %u\n", __func__,
> level);
> -                rc = -ENOMEM;
> -            }
> +            rc = -ENOMEM;
> +            goto out;
> +        }
>  
> +        if ( rc == XEN_TABLE_MAP_NONE )
> +        {
> +            rc = 0;
>              goto out;
>          }

Yes.

Jan


  reply	other threads:[~2024-09-27 12:01 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
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 [this message]
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=82a81ef3-9502-4891-841f-9946f44ff2eb@suse.com \
    --to=jbeulich@suse.com \
    --cc=alistair.francis@wdc.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=bobbyeshleman@gmail.com \
    --cc=connojdavis@gmail.com \
    --cc=julien@xen.org \
    --cc=oleksii.kurochko@gmail.com \
    --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.