From: Anthony Liguori <anthony@codemonkey.ws>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 7/7] Refactor target specific handling, compile vl.c only once
Date: Wed, 31 Mar 2010 14:27:44 -0500 [thread overview]
Message-ID: <4BB3A230.4080606@codemonkey.ws> (raw)
In-Reply-To: <r2of43fc5581003311219x1152c2cbz6c718a1528fff7d9@mail.gmail.com>
On 03/31/2010 02:19 PM, Blue Swirl wrote:
> On 3/31/10, Anthony Liguori<anthony@codemonkey.ws> wrote:
>
>> On 03/27/2010 05:11 PM, Blue Swirl wrote:
>>
>>
>>> Move target specific functions and RAM handling to arch_init.c.
>>>
>>> Add a flag to QEMUOptions structure to indicate for which
>>> architectures the option is allowed, check the flag
>>> in run time and remove conditional code in option handling.
>>>
>>> Now that no target dependencies remain, compile vl.c only once
>>> for all targets.
>>>
>>> Signed-off-by: Blue Swirl<blauwirbel@gmail.com>
>>>
>>>
>>>
>> This causes -enable-kvm to seg fault.
>>
> Variable kvm_state is used but it has not been initialized. This is
> because kvm_init is not called. And this happens because CONFIG_KVM is
> not set by config.h when included from vl.c.
>
I spoke too soon before. A lot of code depends on if (kvm_enabled())
going to 0 so it's a bigger refactoring to fix this once you start
compiling targets that !defined(CONFIG_KVM)
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-03-31 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-27 22:11 [Qemu-devel] [PATCH 7/7] Refactor target specific handling, compile vl.c only once Blue Swirl
2010-03-31 18:42 ` Anthony Liguori
2010-03-31 19:19 ` Blue Swirl
2010-03-31 19:23 ` Anthony Liguori
2010-03-31 19:27 ` Anthony Liguori [this message]
2010-04-01 8:14 ` [Qemu-devel] " Paolo Bonzini
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=4BB3A230.4080606@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--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 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.