From: Oleksandr <olekstysh@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Oleksandr Tyshchenko" <oleksandr_tyshchenko@epam.com>,
"Daniel De Graaf" <dgdegra@tycho.nsa.gov>,
"Daniel P. Smith" <dpsmith@apertussolutions.com>,
"Ian Jackson" <iwj@xenproject.org>, "Wei Liu" <wl@xen.org>,
"George Dunlap" <george.dunlap@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Bertrand Marquis" <bertrand.marquis@arm.com>,
"Wei Chen" <Wei.Chen@arm.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
xen-devel@lists.xenproject.org, "Julien Grall" <julien@xen.org>
Subject: Re: [RFC PATCH] xen/memory: Introduce a hypercall to provide unallocated space
Date: Thu, 5 Aug 2021 18:10:44 +0300 [thread overview]
Message-ID: <abbd7901-e9df-baa3-cbbd-f915b5953688@gmail.com> (raw)
In-Reply-To: <11ba67a9-23a1-87e1-3db5-e9040af42a60@suse.com>
On 05.08.21 08:58, Jan Beulich wrote:
Hi Jan.
> On 04.08.2021 21:18, Oleksandr wrote:
>> On 03.08.21 15:53, Jan Beulich wrote:
>>> On 30.07.2021 18:13, Oleksandr wrote:
>>>> - Where that range should be located in guest address space, should that
>>>> range be the same for all domains (how GUEST_GNTTAB_BASE(SIZE) for example)
>>>> or it should be calculated based on actual guest_ram_base(size) for a
>>>> particular domain?
>>> The default size may well be fixed or amount-of-memory-dependent, but
>>> I think there will need to be a way to enlarge the region for guests
>>> with particular needs.
>> Well, but why we couldn't just make a large chunk by default which would
>> satisfy all guests, as it was mentioned earlier in this thread "as it
>> doesn't consume resource when not being used"
>> to avoid an extra configuration option, etc?
> Because experience tells me that no static upper limit will ever please
> everyone.
ok, thank you for the explanation.
>
> Jan
>
--
Regards,
Oleksandr Tyshchenko
next prev parent reply other threads:[~2021-08-05 15:11 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 16:18 [RFC PATCH] xen/memory: Introduce a hypercall to provide unallocated space Oleksandr Tyshchenko
2021-07-28 17:06 ` Oleksandr
2021-07-28 17:19 ` Andrew Cooper
2021-07-28 17:27 ` Julien Grall
2021-07-28 19:00 ` Andrew Cooper
2021-07-28 19:53 ` Julien Grall
2021-07-30 16:13 ` Oleksandr
2021-07-30 23:57 ` Stefano Stabellini
2021-08-02 19:12 ` Oleksandr
2021-08-04 20:56 ` Oleksandr
2021-08-04 22:00 ` Julien Grall
2021-08-05 14:52 ` Oleksandr
2021-08-05 17:25 ` Julien Grall
2021-08-05 20:48 ` Oleksandr
2021-08-06 0:20 ` Stefano Stabellini
2021-08-06 18:03 ` Oleksandr
2021-08-13 23:49 ` Oleksandr
2021-08-06 0:30 ` Stefano Stabellini
2021-08-07 17:03 ` Oleksandr
2021-08-09 15:42 ` Julien Grall
2021-08-09 18:24 ` Oleksandr
2021-08-09 20:45 ` Julien Grall
2021-08-09 21:18 ` Oleksandr
2021-08-10 16:28 ` Julien Grall
2021-08-10 17:03 ` Oleksandr
2021-08-17 17:53 ` Julien Grall
2021-08-17 17:54 ` Julien Grall
2021-08-27 20:34 ` Oleksandr
2021-08-10 6:34 ` Wei Chen
2021-08-10 11:58 ` Oleksandr
2021-08-10 16:21 ` Julien Grall
2021-08-10 16:49 ` Oleksandr
2021-08-09 14:51 ` Julien Grall
2021-08-09 17:14 ` Oleksandr
2021-08-09 17:18 ` Julien Grall
2021-08-09 17:49 ` Oleksandr
2021-08-13 21:45 ` Oleksandr
2021-08-03 12:53 ` Jan Beulich
2021-08-04 19:18 ` Oleksandr
2021-08-05 5:58 ` Jan Beulich
2021-08-05 15:10 ` Oleksandr [this message]
2021-08-03 12:49 ` Jan Beulich
2021-08-03 12:53 ` Julien Grall
2021-08-17 17:59 ` Julien Grall
2021-08-05 15:03 ` Daniel P. Smith
2021-08-05 15:59 ` Oleksandr
2021-08-05 16:37 ` Daniel P. Smith
2021-08-05 21:56 ` Oleksandr
2021-08-06 6:09 ` Jan Beulich
2021-08-06 15:08 ` Daniel P. Smith
2021-09-07 8:53 ` Henry Wang
2021-09-07 21:34 ` 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=abbd7901-e9df-baa3-cbbd-f915b5953688@gmail.com \
--to=olekstysh@gmail.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=Wei.Chen@arm.com \
--cc=andrew.cooper3@citrix.com \
--cc=bertrand.marquis@arm.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=dpsmith@apertussolutions.com \
--cc=george.dunlap@citrix.com \
--cc=iwj@xenproject.org \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=oleksandr_tyshchenko@epam.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.