From: Sasha Levin <sasha.levin@oracle.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: penberg@kernel.org, will.deacon@arm.com, marc.zyngier@arm.com,
kvm@vger.kernel.org, asias@redhat.com
Subject: Re: [PATCH] kvm tools: remove arbitrary minimum RAM limitation
Date: Wed, 24 Apr 2013 13:50:54 -0400 [thread overview]
Message-ID: <51781B7E.7080004@oracle.com> (raw)
In-Reply-To: <1366791930.18639.15.camel@concordia>
On 04/24/2013 04:25 AM, Michael Ellerman wrote:
> On Tue, 2013-04-23 at 10:57 -0400, Sasha Levin wrote:
>> We don't really need 64MB of RAM to boot, it's a nice default if we don't
>> have anything else - but it's not actually required for anything:
>
> Nice, I am carrying something similar locally so I can boot in 4K :)
Feel free to send stuff you carry locally over! :)
Thanks,
Sasha
prev parent reply other threads:[~2013-04-24 17:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 14:57 [PATCH] kvm tools: remove arbitrary minimum RAM limitation Sasha Levin
2013-04-23 15:04 ` Will Deacon
2013-04-24 7:32 ` Pekka Enberg
2013-04-24 8:25 ` Michael Ellerman
2013-04-24 9:18 ` Asias He
2013-04-24 17:50 ` Sasha Levin [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=51781B7E.7080004@oracle.com \
--to=sasha.levin@oracle.com \
--cc=asias@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=michael@ellerman.id.au \
--cc=penberg@kernel.org \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox