From: "Roger Pau Monné" <roger.pau@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
andrei.semenov@bertin.fr, Wei Liu <wei.liu2@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v2 2/2] x86/dom0: improve paging memory usage calculations
Date: Wed, 12 Dec 2018 12:19:51 +0100 [thread overview]
Message-ID: <20181212111951.4g5oh7fgextqdlhi@mac> (raw)
In-Reply-To: <20181212111453.xr4teivupq2k3ggx@mac>
On Wed, Dec 12, 2018 at 12:14:53PM +0100, Roger Pau Monné wrote:
> On Wed, Dec 12, 2018 at 03:57:41AM -0700, Jan Beulich wrote:
> > >>> On 12.12.18 at 11:16, <roger.pau@citrix.com> wrote:
> > > There are also further issues that I wanted to discuss in a separate
> > > thread, what about foreign mappings? Dom0 will likely map a non
> > > trivial amount of grants and foreign mappings, which will also require
> > > p2m/IOMMU page table entries.
> >
> > Hmm, good point. Then again this is a runtime requirement,
> > whereas here we want to get the boot time estimate right. At
> > runtime lack of memory for P2M tables will simply result in
> > -ENOMEM.
>
> But Xen runtime memory is also tied to the boot estimates if there's
> no dom0_mem parameter specified on the command line. I would expect
^ wouldn't
> Dom0 to balloon down memory when it attempts to map BARs, even at
> runtime.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2018-12-12 11:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 14:54 [PATCH v2 0/2] x86/dom0: improve PVH paging memory calculation Roger Pau Monne
2018-12-05 14:54 ` [PATCH v2 1/2] x86/dom0: rename paging function Roger Pau Monne
2018-12-06 12:31 ` Wei Liu
2018-12-11 15:08 ` Jan Beulich
2018-12-11 15:19 ` Roger Pau Monné
2018-12-11 15:33 ` Jan Beulich
2018-12-12 9:14 ` Roger Pau Monné
2018-12-12 9:53 ` Jan Beulich
2018-12-12 10:04 ` Roger Pau Monné
2018-12-12 10:32 ` Jan Beulich
2018-12-12 15:56 ` Roger Pau Monné
2018-12-12 16:15 ` Jan Beulich
2018-12-12 17:05 ` Roger Pau Monné
[not found] ` <3F7E1F6E020000A10063616D@prv1-mh.provo.novell.com>
2018-12-13 7:45 ` Jan Beulich
2018-12-13 9:14 ` Roger Pau Monné
[not found] ` <12305AED020000300063616D@prv1-mh.provo.novell.com>
2018-12-13 10:17 ` Jan Beulich
2018-12-13 14:20 ` Roger Pau Monné
[not found] ` <7320EEF8020000C00063616D@prv1-mh.provo.novell.com>
2018-12-13 14:47 ` Jan Beulich
2019-01-29 15:02 ` Roger Pau Monné
[not found] ` <812B19D1020000B00063616D@prv1-mh.provo.novell.com>
2019-01-29 15:38 ` Jan Beulich
2018-12-05 14:55 ` [PATCH v2 2/2] x86/dom0: improve paging memory usage calculations Roger Pau Monne
2018-12-06 12:42 ` Wei Liu
2018-12-10 10:33 ` Roger Pau Monné
2018-12-11 12:17 ` Wei Liu
2018-12-11 15:19 ` Jan Beulich
2018-12-11 15:36 ` Roger Pau Monné
2018-12-11 16:21 ` Jan Beulich
2018-12-12 9:37 ` Roger Pau Monné
2018-12-12 9:59 ` Jan Beulich
2018-12-12 10:16 ` Roger Pau Monné
2018-12-12 10:57 ` Jan Beulich
2018-12-12 11:14 ` Roger Pau Monné
2018-12-12 11:19 ` Roger Pau Monné [this message]
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=20181212111951.4g5oh7fgextqdlhi@mac \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrei.semenov@bertin.fr \
--cc=andrew.cooper3@citrix.com \
--cc=wei.liu2@citrix.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).