From: Anthony Liguori <anthony@codemonkey.ws>
To: Peter Crosthwaite <peter.crosthwaite@petalogix.com>
Cc: qemu-devel@nongnu.org, peter.maydell@linaro.org,
aliguori@us.ibm.com, Paul Brook <paul@codesourcery.com>,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [RFC PATCH] arm boot: added QOM device definition
Date: Wed, 08 Feb 2012 10:20:55 -0600 [thread overview]
Message-ID: <4F32A0E7.9000009@codemonkey.ws> (raw)
In-Reply-To: <CAEgOgz57+a9U5FUhQyk4rWRsOwtyNGONfUUL+69VbASXZnO6Ew@mail.gmail.com>
On 02/08/2012 10:03 AM, Peter Crosthwaite wrote:
> 2012/2/9 Paul Brook<paul@codesourcery.com>
>
>>> So here are some of the problems im trying to solve with the bootloader:
>>>
>>> Smp bootstrap secondary CPUs while loading an elf (currently elfs will be
>>> assumed to be not kernels).
>>> Change the kernel, initrd and dtb load address on the command line.
>>> Use my own SMP secondary bootloop.
>>>
>>> My intention with this patch was to set myself to do boot
>> parameterizations
>>> on the command line by just adding them as qdev props to the
>>> arm_linux_loader and set them using -device instantiation. E.G. -device
>>> arm_boot_loader,initrd_addr=0x10000000. But if I take the approach you
>> are
>>> suggesting, the for this initrd load address option, I would need to add
>>> myself a command line option, fetch that command line option in every arm
>>> machine model and then pass it to arm_load_kernel.
>>
>> No. You just set/override properties on the device that the machine
>> created.
>> I thought we already had this, but it looks like the closest we have is
>> -global.
>>
>> Something like "-property /devicepath/propertyname=value".
A lot of refactoring is needed to make this a reality. Please read through the
various QOM threads for details of what needs to be done.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2012-02-08 16:21 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 7:55 [Qemu-devel] [RFC PATCH] arm boot: added QOM device definition Peter A. G. Crosthwaite
2012-02-08 9:06 ` Paul Brook
2012-02-08 10:11 ` Peter Crosthwaite
2012-02-08 10:44 ` Paul Brook
2012-02-08 11:10 ` Peter Crosthwaite
2012-02-08 11:39 ` Paul Brook
2012-02-08 11:59 ` Peter Crosthwaite
2012-02-08 12:27 ` Paul Brook
2012-02-08 12:41 ` Alexander Graf
2012-02-08 13:04 ` Peter Crosthwaite
2012-02-08 13:10 ` Alexander Graf
2012-02-08 13:30 ` Peter Crosthwaite
2012-02-08 13:35 ` Alexander Graf
2012-02-08 14:05 ` Peter Crosthwaite
2012-02-08 14:17 ` Alexander Graf
2012-02-08 14:20 ` Paul Brook
2012-02-08 14:39 ` Peter Crosthwaite
2012-02-08 14:56 ` Paul Brook
2012-02-08 15:14 ` Peter Crosthwaite
2012-02-08 15:57 ` Paul Brook
2012-02-08 16:03 ` Peter Crosthwaite
2012-02-08 16:15 ` Paul Brook
2012-02-08 16:35 ` Anthony Liguori
2012-02-09 1:22 ` Peter Crosthwaite
2012-02-09 12:03 ` Paul Brook
2012-02-08 16:20 ` Anthony Liguori [this message]
2012-02-08 13:47 ` Anthony Liguori
2012-02-20 19:43 ` Peter Maydell
2012-02-20 19:51 ` Andreas Färber
2012-02-20 19:56 ` Peter Maydell
2012-02-21 9:15 ` Peter Crosthwaite
2012-02-21 10:20 ` Peter Maydell
2012-02-08 13:41 ` Anthony Liguori
2012-02-09 13:22 ` Andreas Färber
2012-02-10 2:11 ` Peter Crosthwaite
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=4F32A0E7.9000009@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=paul@codesourcery.com \
--cc=peter.crosthwaite@petalogix.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).