From: "tiejun.chen" <tiejun.chen@windriver.com>
To: Caraman Mihai Claudiu-B02008 <B02008@freescale.com>
Cc: "kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 8/8 v3] KVM: PPC: e500: Add e6500 core to Kconfig description
Date: Fri, 26 Apr 2013 11:11:29 +0800 [thread overview]
Message-ID: <5179F061.2040603@windriver.com> (raw)
In-Reply-To: <300B73AA675FCE4A93EB4FC1D42459FF3D9A8A@039-SN2MPN1-013.039d.mgd.msft.net>
On 04/25/2013 07:32 PM, Caraman Mihai Claudiu-B02008 wrote:
>> Is the flowing is fine with that generic machine, ppce500, to boot
>> P5040DS with
>> 64bit,
>>
>> ./qemu-system-ppc64 -enable-kvm -m 1048 -nographic -M ppce500 -kernel
>> uImage
>> -initrd ramdisk.gz -L . -append "root=/dev/ram rw console=ttyS0,115200"
>> -cpu
>> e5500 -dtb p5040ds.dtb
>>
>> Thanks,
>>
>> Tiejun
>
> There is no need for -dtb.
With your comment, I use kvm-ppc-queue which top commit is be28a27c, "kvm/ppc:
don't call complete_mmio_load when it's a store", in plus that patch you
pointed to build one uImage based on corenet64_smp_defconfig, but we need to
enable CONFIG_PPC_QEMU_E500 manually, and select CONFIG_TICK_CPU_ACCOUNTING
since the default CONFIG_VIRT_CPU_ACCOUNTING_NATIVE would introduce some trace
when boot VM.
And perform as follows:
./qemu-system-ppc64 -enable-kvm -m 1048 -nographic -M ppce500 -kernel uImage
-initrd ramdisk.gz -L . -append "root=/dev/ram rw console=ttyS0,115200" -cpu e5500
But I can't see anything in the serial port.
Tiejun
next prev parent reply other threads:[~2013-04-26 3:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 9:09 [PATCH 8/8 v3] KVM: PPC: e500: Add e6500 core to Kconfig description Caraman Mihai Claudiu-B02008
2013-04-25 9:16 ` tiejun.chen
[not found] ` <300B73AA675FCE4A93EB4FC1D42459FF3D967A@039-SN2MPN1-013.039d.mgd.msft.net>
2013-04-25 9:49 ` tiejun.chen
[not found] ` <300B73AA675FCE4A93EB4FC1D42459FF3D997F@039-SN2MPN1-013.039d.mgd.msft.net>
[not found] ` <51791195.7090909@windriver.com>
[not found] ` <300B73AA675FCE4A93EB4FC1D42459FF3D9A8A@039-SN2MPN1-013.039d.mgd.msft.net>
2013-04-26 3:11 ` tiejun.chen [this message]
2013-04-26 9:38 ` tiejun.chen
-- strict thread matches above, loose matches on Subject: below --
2013-04-11 10:03 [PATCH 0/8 v3] KVM: PPC: e500: Enable FSL e6500 core Mihai Caraman
2013-04-11 10:03 ` [PATCH 8/8 v3] KVM: PPC: e500: Add e6500 core to Kconfig description Mihai Caraman
2013-04-19 10:03 ` tiejun.chen
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=5179F061.2040603@windriver.com \
--to=tiejun.chen@windriver.com \
--cc=B02008@freescale.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.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