From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Eric Shelton <eshelton@pobox.com>
Cc: xen-devel@lists.xenproject.org, wei.liu2@citrix.com,
ian.jackson@eu.citrix.com, ian.campbell@citrix.com,
stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH 0/1] libxl: set stub domain size based on VRAM size
Date: Fri, 10 Jul 2015 17:58:43 +0200 [thread overview]
Message-ID: <20150710155843.GA5645@type.lan> (raw)
In-Reply-To: <1436542562-1118-1-git-send-email-eshelton@pobox.com>
Eric Shelton, le Fri 10 Jul 2015 11:36:01 -0400, a écrit :
> Assuming the the original value of 32 MB was based on having a 4 MB
> video adapter,
In my memory that was the case, yes.
Samuel
prev parent reply other threads:[~2015-07-10 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 15:36 [PATCH 0/1] libxl: set stub domain size based on VRAM size Eric Shelton
2015-07-10 15:36 ` [PATCH 1/1] " Eric Shelton
2015-07-10 15:48 ` Ian Jackson
2015-07-10 15:59 ` Samuel Thibault
2015-07-10 15:58 ` Samuel Thibault [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=20150710155843.GA5645@type.lan \
--to=samuel.thibault@ens-lyon.org \
--cc=eshelton@pobox.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--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).