All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: StefanoStabellini <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>,
	Konrad Wilk <konrad.wilk@oracle.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Tim Deegan <tim@xen.org>, Ian Jackson <ian.jackson@citrix.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3 16/17] SUPPORT.md: Add limits RFC
Date: Fri, 24 Nov 2017 01:14:31 -0700	[thread overview]
Message-ID: <5A17E2F70200007800191937@prv-mh.provo.novell.com> (raw)
In-Reply-To: <72015cfa-3a5b-99e0-ef58-4782151eaa77@citrix.com>

>>> On 23.11.17 at 18:21, <george.dunlap@citrix.com> wrote:
> On 11/23/2017 11:21 AM, Jan Beulich wrote:
>>>>> On 22.11.17 at 20:20, <george.dunlap@citrix.com> wrote:
>>> +### Virtual RAM
>>> +
>>> +    Limit-security, x86 PV 64-bit: 2047GiB
>>> +    Limit-security, x86 PV 32-bit: 168GiB (see below)
>>> +    Limit-security, x86 HVM: 1.5TiB
>>> +    Limit, ARM32: 16GiB
>>> +    Limit, ARM64: 1TiB
>>> +
>>> +Note that there are no theoretical limits to 64-bit PV or HVM guest sizes
>>> +other than those determined by the processor architecture.
>>> +
>>> +All 32-bit PV guest memory must be under 168GiB;
>>> +this means the total memory for all 32-bit PV guests cannot exced 168GiB.
>> 
>> While certainly harder to grok for the reader, I think we need to be
>> precise here: The factor isn't the amount of memory, but the
>> addresses at which it surfaces. Host memory must not extend
>> beyond the 168MiB boundary for that to also be the limit for
>> 32-bit PV guests.
> 
> Yes, I'd intended "under 168GiB" to more clearly imply physical
> addresses; but I agree as written that's unlikely to be picked up by
> anyone not already familiar with the concept.
> 
> What about something like this:
> 
> "32-bit PV guests can only access physical addresses below 168GiB;
> this means that the total memory of all 32-bit PV guests cannot exceed
> 168GiB.  For hosts with more than 168GiB RAM, this limit becomes 128GiB."

Better, but I'd still prefer the last sentence to be something like
"For hosts with memory above the 168GiB boundary, ...". I'm
not going to insist on such an adjustment, though, if you feel
what you have is easier to understand by the intended audience.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2017-11-24  8:14 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22 19:20 [PATCH v3 01/17] Introduce skeleton SUPPORT.md George Dunlap
2017-11-22 19:20 ` [PATCH v3 02/17] SUPPORT.md: Add core functionality George Dunlap
2017-11-23 10:46   ` Jan Beulich
2017-11-22 19:20 ` [PATCH v3 03/17] SUPPORT.md: Add some x86 features George Dunlap
2017-11-23 10:47   ` Jan Beulich
2017-11-22 19:20 ` [PATCH v3 04/17] SUPPORT.md: Add core ARM features George Dunlap
2017-11-23 11:11   ` Julien Grall
2017-11-23 11:13     ` George Dunlap
2017-11-23 11:15       ` Julien Grall
2017-11-22 19:20 ` [PATCH v3 05/17] SUPPORT.md: Toolstack core George Dunlap
2017-11-24 16:26   ` Ian Jackson
2017-11-27 10:27     ` George Dunlap
2017-11-27 11:43   ` Roger Pau Monné
2017-11-27 14:12     ` George Dunlap
2017-11-27 14:39       ` Roger Pau Monné
2017-11-27 14:40         ` George Dunlap
2017-11-27 14:58         ` George Dunlap
2017-11-27 15:02           ` Roger Pau Monné
2017-11-27 14:15     ` George Dunlap
2017-11-27 14:36       ` Roger Pau Monné
2017-11-22 19:20 ` [PATCH v3 06/17] SUPPORT.md: Add scalability features George Dunlap
2017-11-23 10:50   ` Jan Beulich
2017-11-23 16:52     ` George Dunlap
2017-11-23 11:12   ` Julien Grall
2017-11-22 19:20 ` [PATCH v3 07/17] SUPPORT.md: Add virtual devices common to ARM and x86 George Dunlap
2017-11-23  8:50   ` Paul Durrant
2017-11-23 10:59   ` Jan Beulich
2017-11-23 17:02     ` George Dunlap
2017-11-22 19:20 ` [PATCH v3 08/17] SUPPORT.md: Add x86-specific virtual hardware George Dunlap
2017-11-23 11:07   ` Jan Beulich
2017-11-27 15:12   ` Anthony PERARD
2017-11-27 16:30     ` George Dunlap
2017-11-27 16:43       ` Anthony PERARD
2017-11-22 19:20 ` [PATCH v3 09/17] SUPPORT.md: Add ARM-specific " George Dunlap
2017-11-23 11:14   ` Julien Grall
2017-11-22 19:20 ` [PATCH v3 10/17] SUPPORT.md: Add Debugging, analysis, crash post-portem George Dunlap
2017-11-23 11:15   ` Jan Beulich
2017-11-23 17:08     ` George Dunlap
2017-11-24  8:04       ` Jan Beulich
2017-11-27 14:18         ` George Dunlap
2017-11-22 19:20 ` [PATCH v3 11/17] SUPPORT.md: Add 'easy' HA / FT features George Dunlap
2017-11-22 19:20 ` [PATCH v3 12/17] SUPPORT.md: Add Security-releated features George Dunlap
2017-11-23 11:16   ` Jan Beulich
2017-11-23 17:14     ` George Dunlap
2017-11-22 19:20 ` [PATCH v3 13/17] SUPPORT.md: Add secondary memory management features George Dunlap
2017-11-22 19:20 ` [PATCH v3 14/17] SUPPORT.md: Add statement on PCI passthrough George Dunlap
2017-11-23 11:17   ` Jan Beulich
2017-11-27 14:48     ` George Dunlap
2017-11-27 15:04       ` Jan Beulich
2017-11-27 15:05         ` George Dunlap
2017-11-22 19:20 ` [PATCH v3 15/17] SUPPORT.md: Add statement on migration RFC George Dunlap
2017-11-23 11:19   ` Jan Beulich
2017-11-22 19:20 ` [PATCH v3 16/17] SUPPORT.md: Add limits RFC George Dunlap
2017-11-23 11:21   ` Jan Beulich
2017-11-23 17:21     ` George Dunlap
2017-11-24  8:14       ` Jan Beulich [this message]
2017-11-27 14:35         ` George Dunlap
2017-11-22 19:20 ` [PATCH v3 17/17] SUPPORT.md: Miscellaneous additions George Dunlap

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=5A17E2F70200007800191937@prv-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --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 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.