qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Improve symbol lookup for system and user mode
Date: Mon, 20 Oct 2008 20:16:13 +0300	[thread overview]
Message-ID: <f43fc5580810201016g60d1f6f9i28c30ddb9a26e74c@mail.gmail.com> (raw)
In-Reply-To: <48F8CB4C.30800@mail.berlios.de>

On 10/17/08, Stefan Weil <weil@mail.berlios.de> wrote:
>
>  > Stefan Weil schrieb:
>  >> Here is a short summary of my new patch:
>  >>
>  >> * Use function pointers for symbol lookup (currently for elf32 and
>  >> elf64, could be expanded).
>  >> This also fixes the bug with mips elf64 symbols in current Qemu trunk.
>  >>
>  >> * Use quicksort and binary search for symbol lookup.
>  >>
>  >> * Remove unneeded entries from symbol table.
>  >> This reduced a typical table size (linux mips kernel) from 1764487 to
>  >> 11656 entries.
>  >>
>  >> * In disas.c, the patch also fixes some warnings from old fashioned
>  >> function prototypes.

This should be a separate patch.

>  >>
>  >> In loader.c, two defines control some compile time options (could be
>  >> removed in
>  >> production code):
>  >> #define CONFIG_BINARY_SYMBOL_SEARCH
>  >> #define CONFIG_REDUCE_SYMBOL_TABLE
>  >>
>  >> I tested the new code using 32 bit and 64 bit linux mips kernels and
>  >> Qemu logging (-d in_asm).
>  >> The speed improvement is extremely large - both because of the much
>  >> smaller table and
>  >> the binary search.
>  >>
>  >> Stefan
>  >>
>  > Please note:
>  >
>  > The current patch only supports system emulation.
>  > User emulation needs more fixes to compile again.
>  >
>  > Stefan
>  >
>  >
>
>
>  Here is an updated patch which now supports binary symbol lookup
>  for both system emulation and user emulation.
>
>  User emulation was tested using qemu-x86_64 and a simple application
>  with symbol information.
>
>  The new patch no longer includes compile time options for the old
>  linear symbol search.
>
>  I hope this new patch will be included in Qemu trunk.

There are some white space only changes, these should be taken out.

For some reason, loading a bios with symbols on Sparc32 corrupts the
bios but Sparc64 works. This happens also without your patch.

  reply	other threads:[~2008-10-20 17:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02 19:26 [Qemu-devel] [PATCH] Fix symbol lookup for mips64* targets Stefan Weil
2008-10-02 19:53 ` Blue Swirl
2008-10-16 19:57   ` [Qemu-devel] [PATCH] Improve symbol lookup (was: Re: [Qemu-devel] [PATCH] Fix symbol lookup for mips64* targets) Stefan Weil
2008-10-16 20:32     ` [Qemu-devel] [PATCH] Improve symbol lookup Stefan Weil
2008-10-16 20:41       ` Laurent Desnogues
2008-10-17 17:28       ` [Qemu-devel] [PATCH] Improve symbol lookup for system and user mode Stefan Weil
2008-10-20 17:16         ` Blue Swirl [this message]
2008-10-16 20:38     ` [Qemu-devel] [PATCH] Improve symbol lookup (was: Re: [Qemu-devel] [PATCH] Fix symbol lookup for mips64* targets) Laurent Desnogues
2008-10-02 21:52 ` [Qemu-devel] [PATCH] Fix symbol lookup for mips64* targets Thiemo Seufer
2008-10-03 10:09   ` Stefan Weil
2008-10-03 10:29     ` Laurent Desnogues
2008-10-03 17:14       ` Blue Swirl
2008-10-03 17:13     ` Blue Swirl

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=f43fc5580810201016g60d1f6f9i28c30ddb9a26e74c@mail.gmail.com \
    --to=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 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).