All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <iwj@xenproject.org>
To: Oleksandr Tyshchenko <olekstysh@gmail.com>
Cc: xen-devel@lists.xenproject.org,
	"Oleksandr Tyshchenko" <oleksandr_tyshchenko@epam.com>,
	"Ian Jackson" <iwj@xenproject.org>, "Wei Liu" <wl@xen.org>,
	"Anthony PERARD" <anthony.perard@citrix.com>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"George Dunlap" <george.dunlap@citrix.com>,
	"Jan Beulich" <jbeulich@suse.com>,
	"Julien Grall" <julien@xen.org>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Juergen Gross" <jgross@suse.com>,
	"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH V6 1/2] xen/arm: Introduce gpaddr_bits field to struct xen_domctl_getdomaininfo
Date: Tue, 12 Oct 2021 16:15:55 +0100	[thread overview]
Message-ID: <24933.42667.311553.565032@mariner.uk.xensource.com> (raw)
In-Reply-To: <1633974539-7380-2-git-send-email-olekstysh@gmail.com>

Oleksandr Tyshchenko writes ("[PATCH V6 1/2] xen/arm: Introduce gpaddr_bits field to struct xen_domctl_getdomaininfo"):
> From: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
> 
> We need to pass info about maximum supported guest physical
> address space size to the toolstack on Arm in order to properly
> calculate the base and size of the extended region (safe range)
> for the guest. The extended region is unused address space which
> could be safely used by domain for foreign/grant mappings on Arm.
> The extended region itself will be handled by the subsequent
> patch.

You say "to the toolstack", but you are exposing this information up
to callers of libxl.  Do you mean some higher-layer toolstack that
uses libxl ?  What does it use this information for ?

FTAOD I am not opposed to exposing this in this way; indeed it seems
likely to be useful.  I just want to fully understand before I give
this my tools ack.

> +        info->gpaddr_bits = domctl.u.getdomaininfo.gpaddr_bits;

I'm pleased to find that this is not arch-specific.

Thanks,
Ian.


  parent reply	other threads:[~2021-10-12 15:16 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-11 17:48 [PATCH V6 0/2] Add handling of extended regions (safe ranges) on Arm (Was "xen/memory: Introduce a hypercall to provide unallocated space") Oleksandr Tyshchenko
2021-10-11 17:48 ` [PATCH V6 1/2] xen/arm: Introduce gpaddr_bits field to struct xen_domctl_getdomaininfo Oleksandr Tyshchenko
2021-10-11 20:01   ` Stefano Stabellini
2021-10-12  9:24   ` Jan Beulich
2021-10-12 11:28     ` Oleksandr
2021-10-12 11:49       ` Jan Beulich
2021-10-12 13:18         ` Oleksandr
2021-10-12 13:26           ` Jan Beulich
2021-10-12 15:15   ` Ian Jackson [this message]
2021-10-12 15:48     ` Oleksandr
2021-10-12 16:18       ` Ian Jackson
2021-10-12 17:57         ` Oleksandr
2021-10-12 18:07           ` Ian Jackson
2021-10-12 18:22             ` Oleksandr
2021-10-12 21:22               ` Oleksandr Tyshchenko
2021-10-13 13:50                 ` Oleksandr
2021-10-13 13:56                 ` Jan Beulich
2021-10-13 15:05                   ` Oleksandr
2021-10-13 15:17                     ` Julien Grall
2021-10-13 15:24                       ` Oleksandr
2021-10-11 17:48 ` [PATCH V6 2/2] libxl/arm: Add handling of extended regions for DomU Oleksandr Tyshchenko
2021-10-11 20:00   ` Stefano Stabellini
2021-10-12 15:11     ` Ian Jackson
2021-10-12 15:22   ` Oleksandr
2021-10-12 15:32     ` Ian Jackson
2021-10-12 15:38       ` Oleksandr
2021-10-12 16:05   ` Julien Grall
2021-10-12 17:42     ` Oleksandr
2021-10-12 21:22       ` Julien Grall
2021-10-12 21:43         ` Oleksandr
2021-10-13 13:46           ` Oleksandr
2021-10-13 15:15             ` Julien Grall
2021-10-13 15:49               ` Oleksandr
2021-10-13 16:24                 ` Julien Grall
2021-10-13 16:44                   ` Oleksandr
2021-10-13 17:07                     ` Julien Grall
2021-10-13 18:26                       ` Oleksandr
2021-10-13 20:19                         ` Oleksandr
2021-10-13 20:24                           ` Stefano Stabellini
2021-10-14 11:44                             ` Oleksandr

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=24933.42667.311553.565032@mariner.uk.xensource.com \
    --to=iwj@xenproject.org \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jgross@suse.com \
    --cc=julien@xen.org \
    --cc=oleksandr_tyshchenko@epam.com \
    --cc=olekstysh@gmail.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=wl@xen.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.