From: Jan Kiszka <jan.kiszka@web.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: KQEMU code organization
Date: Tue, 27 May 2008 20:25:33 +0200 [thread overview]
Message-ID: <483C521D.6080700@web.de> (raw)
In-Reply-To: <cef699d70805271020wd6633d5v7323ccb5fc7b6f4@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1778 bytes --]
Ben Taylor wrote:
> On Tue, May 27, 2008 at 12:56 PM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>> Hi,
>>
>> is there a technical reason why the kqemu kernel module is built out of
>> a binary blob (monitor-image.bin->monitor-image.h)? Does this simply
>> date back to the time when wrapper and core were distributed under
>> different licenses?
>>
>> I'm currently trying to hunt down a (probable) bug in kqemu, and the
>> monitor is now unfortunately a white spot for the source-level debugger.
>> So far I only managed to make the rest visible.
>>
>> BTW, am I missing an official code repository of kqemu? Why is there no
>> subfolder, e.g., in the qemu svn repos? So patches should be provided
>> against 1.3.0pre11, right?
>
> I maintain a version of the repository at
>
> http://svn9.cvsdude.com/kdesolaris/kqemu/trunk/1.0.3pre11/kqemu
>
> that includes the Solaris changes and other patches posted to the
> list that I've been able to test and integrate.
So this is the de-facto official development version? Quite a few
changes in that tree, also to core stuff. Hmm. But nothing that fixes my
spurious CPL degeneration. What a pity.
However, you could merge another (minor) patch:
Index: Makefile
===================================================================
--- Makefile (Revision 17)
+++ Makefile (Arbeitskopie)
@@ -47,7 +47,7 @@ endif # !CONFIG_WIN32
clean:
$(MAKE) -C common clean
- rm -f kqemu.ko *.o *~
+ rm -rf kqemu.ko *.o *~ .kqemu* Module.* modules.order kqemu.mod.c .tmp_versions
endif # !CONFIG_SOLARIS
Actually, more needs to be cleaned up /wrt Linux module building. But
I'm reluctant to touch common/Makefile until the (current) reason for
this code organization is known.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
next prev parent reply other threads:[~2008-05-27 18:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 16:56 [Qemu-devel] KQEMU code organization Jan Kiszka
2008-05-27 17:20 ` Ben Taylor
2008-05-27 18:25 ` Jan Kiszka [this message]
2008-05-27 20:58 ` Fabrice Bellard
2008-05-27 21:40 ` [Qemu-devel] " Jan Kiszka
2008-05-27 22:11 ` [Qemu-devel] " Fabrice Bellard
2008-05-28 16:02 ` [Qemu-devel] " Jan Kiszka
2008-05-28 16:37 ` Fabrice Bellard
2008-05-28 16:55 ` Jan Kiszka
2008-05-28 18:34 ` Jan Kiszka
2008-05-29 12:29 ` Fabrice Bellard
2008-05-29 13:16 ` Jan Kiszka
2008-05-29 16:13 ` Jamie Lokier
2008-05-29 16:26 ` Paul Brook
2008-05-29 16:35 ` Jamie Lokier
2008-05-29 17:43 ` Anthony Liguori
2008-05-29 21:46 ` Fabrice Bellard
2008-05-30 3:32 ` Mulyadi Santosa
2008-05-30 8:14 ` Andreas Färber
2008-05-29 16:26 ` Anthony Liguori
2008-05-29 16:53 ` Jan Kiszka
2008-05-29 17:48 ` Anthony Liguori
2008-05-31 10:18 ` Avi Kivity
2008-06-02 16:34 ` Jamie Lokier
2008-05-29 21:52 ` Fabrice Bellard
2008-05-31 10:06 ` Avi Kivity
2008-06-01 22:58 ` Anthony Liguori
2008-06-02 9:02 ` Fabrice Bellard
2008-06-02 13:25 ` Anthony Liguori
2008-05-29 16:48 ` Jan Kiszka
2008-05-29 17:47 ` Anthony Liguori
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=483C521D.6080700@web.de \
--to=jan.kiszka@web.de \
--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.