From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>
Cc: Blue Swirl <blauwirbel@gmail.com>,
kwolf@redhat.com, rene@exactcode.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/4] Expose fw_cfg
Date: Wed, 17 Jun 2009 10:59:13 -0500 [thread overview]
Message-ID: <4A3912D1.3000604@codemonkey.ws> (raw)
In-Reply-To: <687B8C48-A0DB-4D2E-9D79-20706DB23C2B@suse.de>
Alexander Graf wrote:
>
> On 17.06.2009, at 17:30, Blue Swirl wrote:
>
>> On 6/17/09, Alexander Graf <agraf@suse.de> wrote:
>>> Multiboot passes options to the option rom using the fw_cfg device.
>>> Right now, that device is local to the bochs_bios_init function.
>>>
>>> Let's change that and expose it to env, so everyone may put data
>>> in there.
>>
>> Env is a wrong place for device data.
>
> So what is the right place? Last time I checked there wasn't anything
> like a global pc machine state struct, but I could be wrong.
Return fw_cfg from bochs_bios_init, then pass it to the kernel loading
functions.
Regards,
Anthony Liguori
> Alex
>
>
prev parent reply other threads:[~2009-06-17 15:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 14:56 [Qemu-devel] [PATCH 0/4] Add multiboot support (x86) Alexander Graf
2009-06-17 14:56 ` [Qemu-devel] [PATCH 1/4] Change bochs bios init order Alexander Graf
2009-06-17 14:56 ` [Qemu-devel] [PATCH 2/4] Expose fw_cfg Alexander Graf
2009-06-17 14:56 ` [Qemu-devel] [PATCH 3/4] Multiboot support Alexander Graf
2009-06-17 14:56 ` [Qemu-devel] [PATCH 4/4] Multiboot build system Alexander Graf
2009-06-17 15:16 ` Paul Brook
2009-06-17 15:23 ` Alexander Graf
2009-06-18 7:57 ` [Qemu-devel] " Paolo Bonzini
2009-06-18 10:16 ` Alexander Graf
2009-06-18 10:19 ` Paolo Bonzini
2009-06-17 15:30 ` [Qemu-devel] [PATCH 2/4] Expose fw_cfg Blue Swirl
2009-06-17 15:32 ` Alexander Graf
2009-06-17 15:59 ` Anthony Liguori [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=4A3912D1.3000604@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=agraf@suse.de \
--cc=blauwirbel@gmail.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rene@exactcode.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.