From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org, stefano.stabellini@eu.citrix.com,
wei.liu2@citrix.com, samuel.thibault@ens-lyon.org,
Eric Shelton <eshelton@pobox.com>
Subject: Re: [PATCH V2 1/1] libxl: set stub domain size based on VRAM size
Date: Mon, 13 Jul 2015 11:37:37 +0100 [thread overview]
Message-ID: <1436783857.7019.84.camel@citrix.com> (raw)
In-Reply-To: <21923.37235.852479.985765@mariner.uk.xensource.com>
On Mon, 2015-07-13 at 11:22 +0100, Ian Jackson wrote:
> Ian Jackson writes ("Re: [PATCH V2 1/1] libxl: set stub domain size based on VRAM size"):
> > Eric Shelton writes ("[PATCH V2 1/1] libxl: set stub domain size based on VRAM size"):
> > > Allocate additional memory to the stub domain for qemu-traditional if
> > > more than 4 MB is assigned to the video adapter to avoid out of memory
> > > condition for QEMU.
> >
> > Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
> >
> > This is IMO a bugfix so I am queueing it for 4.6.
>
> My build test failed. It turns out that max() is no good because the
> types of `4096' and `guest_config->b_info.video_memkb' are not the
> same.
>
> In a moment I am going to send a v3 which uses max_t and uint64_t
> (which is the type of the memkb fields and also obviously correct).
Eric already sent a v3 in
<1436650242-1067-2-git-send-email-eshelton@pobox.com> which avoids the
use of max in a different way.
I think his approach looked fine.
Ian.
next prev parent reply other threads:[~2015-07-13 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 22:14 [PATCH V2 0/1] libxl: set stub domain size based on VRAM size Eric Shelton
2015-07-10 22:14 ` [PATCH V2 1/1] " Eric Shelton
2015-07-10 22:27 ` Samuel Thibault
2015-07-13 10:16 ` Ian Jackson
2015-07-13 10:22 ` Ian Jackson
2015-07-13 10:24 ` [PATCH for-4.6 v3] " Ian Jackson
2015-07-13 10:37 ` Ian Campbell [this message]
2015-07-13 11:14 ` [PATCH V2 1/1] " Ian Jackson
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=1436783857.7019.84.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=eshelton@pobox.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=stefano.stabellini@eu.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).