All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@novell.com>,
	David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] x86: use 'dom0_mem' to limit the number of pages for dom0
Date: Tue, 23 Aug 2011 13:03:10 +0100	[thread overview]
Message-ID: <CA79558E.1FA41%keir.xen@gmail.com> (raw)
In-Reply-To: <4E5391E00200007800052B9A@nat28.tlf.novell.com>

On 23/08/2011 10:41, "Jan Beulich" <JBeulich@novell.com> wrote:

>>> Besides that the assignment needs to be saturating, as struct domain's
>>> max_pages member is only "unsigned int", whereas the local variables
>>> are all "unsigned long". So in the end this should really be an equivalent
>>> of
>>> 
>>>     d->max_pages = min(max_pages, UINT_MAX);
>> 
>> We should make d->max_pages a ulong or u64.
> 
> I'd rather not, as for now there's no good reason for this to be a
> 64-bit variable (as we can't get even close to the 16Tb it would
> take to overflow this). But then again I expect you to say that
> the few extra REX prefixes don't matter all that much...

Ha, you'd be right! :-)

I'll leave it to David to champion his patch. I'll note I added it for 4.1.2
as well, if we decide there is a better way we will need to change it there
in advance of that release, and preferably -rc1 as well.

 -- Keir

  reply	other threads:[~2011-08-23 12:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-15 18:08 [PATCH] x86: use 'dom0_mem' to limit the number of pages for dom0 David Vrabel
2011-08-16  0:31 ` Konrad Rzeszutek Wilk
2011-08-16 12:29   ` David Vrabel
2011-08-16 12:51     ` Ian Campbell
2011-08-16 13:11       ` David Vrabel
2011-08-19 15:35 ` David Vrabel
2011-08-23  9:01 ` Jan Beulich
2011-08-23  9:26   ` Keir Fraser
2011-08-23  9:41     ` Jan Beulich
2011-08-23 12:03       ` Keir Fraser [this message]
2011-08-23 15:54   ` David Vrabel

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=CA79558E.1FA41%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=JBeulich@novell.com \
    --cc=david.vrabel@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.