From: Shreyas B Prabhu <shreyas@linux.vnet.ibm.com>
To: Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: Scott Wood <scottwood@freescale.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
andreas.faerber@web.de, bharata@linux.vnet.ibm.com,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] ppc: memory: Replace memory_region_init_ram with memory_region_allocate_system_memory
Date: Thu, 10 Jul 2014 17:41:05 +0530 [thread overview]
Message-ID: <53BE82D9.9060709@linux.vnet.ibm.com> (raw)
In-Reply-To: <53BE8133.7040005@suse.de>
On Thursday 10 July 2014 05:34 PM, Alexander Graf wrote:
>
> On 10.07.14 14:01, Shreyas B. Prabhu wrote:
>> Commit 0b183fc871:"memory: move mem_path handling to
>> memory_region_allocate_system_memory" split memory_region_init_ram and
>> memory_region_init_ram_from_file. Also it moved mem-path handling a step
>> up from memory_region_init_ram to memory_region_allocate_system_memory.
>>
>> Therefore for any board that uses memory_region_init_ram directly,
>> -mem-path is not supported.
>>
>> Fix this by replacing memory_region_init_ram with
>> memory_region_allocate_system_memory.
>>
>> Signed-off-by: Shreyas B. Prabhu <shreyas@linux.vnet.ibm.com>
>
> Thanks, applied to ppc-next (for 2.1 - it's a regression after all).
>
Thanks!
>
> Alex
>
prev parent reply other threads:[~2014-07-10 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 7:01 [Qemu-devel] [PATCH] ppc: memory: Replace memory_region_init_ram with memory_region_allocate_system_memory Shreyas B. Prabhu
2014-07-10 10:26 ` Alexander Graf
2014-07-10 12:01 ` [Qemu-devel] [PATCH v2] " Shreyas B. Prabhu
2014-07-10 12:04 ` Alexander Graf
2014-07-10 12:11 ` Shreyas B Prabhu [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=53BE82D9.9060709@linux.vnet.ibm.com \
--to=shreyas@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=andreas.faerber@web.de \
--cc=bharata@linux.vnet.ibm.com \
--cc=edgar.iglesias@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=scottwood@freescale.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;
as well as URLs for NNTP newsgroup(s).