From: "Jan Beulich" <JBeulich@suse.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
andrei.semenov@bertin.fr, Wei Liu <wei.liu2@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v2 1/2] x86/dom0: rename paging function
Date: Thu, 13 Dec 2018 03:17:05 -0700 [thread overview]
Message-ID: <5C1231A10200007800205C65@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <12305AED020000300063616D@prv1-mh.provo.novell.com>
>>> On 13.12.18 at 10:14, <roger.pau@citrix.com> wrote:
> On Thu, Dec 13, 2018 at 12:45:07AM -0700, Jan Beulich wrote:
>> >>> On 12.12.18 at 18:05, <roger.pau@citrix.com> wrote:
>> > On Wed, Dec 12, 2018 at 09:15:09AM -0700, Jan Beulich wrote:
>> >> The MMIO side of things of course still remains unclear.
>> >
>> > Right, for the MMIO and the handling of grant and foreign mappings it's
>> > not clear how we want to proceed.
>> >
>> > Maybe account for all host RAM (total_pages) plus MMIO BARs?
>>
>> Well, I thought we've already settled on it being impossible to
>> account for all MMIO BARs at this point.
>
> Well, I could iterate over all the registered PCI devices and size
> the BARs (without VF BARs at least initially). This is quite
> cumbersome, my other option would be using max_page and hope that
> there are enough holes to make up for BAR MMIO regions.
Well, maybe we could live with this for now. I certainly would
prefer to have a 3rd opinion though, as I continue to feel uneasy
with this rather imprecise estimation (i.e. I'd much prefer a more
dynamic / on-demand approach).
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-12-13 10:17 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 [this message]
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é
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=5C1231A10200007800205C65@prv1-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=andrei.semenov@bertin.fr \
--cc=andrew.cooper3@citrix.com \
--cc=roger.pau@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).