qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.landwerlin@openwide.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Modular qemu?
Date: Sat, 06 Dec 2008 14:23:51 +0100	[thread overview]
Message-ID: <1228569831.3948.6.camel@cocoduo.atr> (raw)
In-Reply-To: <20081205221007.GB25555@edgar.se.axis.com>

[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]

Le vendredi 05 décembre 2008 à 23:10 +0100, Edgar E. Iglesias a écrit :
> On Fri, Dec 05, 2008 at 08:32:45AM -0600, Anthony Liguori wrote:
> > Joop Boonen wrote:
> >> Hello All,
> >>
> 
> Personnaly I would welcome some kind of plugin interface for some parts of
> QEMU but only if someone comes up wiht a an interface that does not hurt
> performace. I'd definitely have a use to plugin callbacks for every memory
> accesse in system-mode and I've noticed a reocurring request for hooks to
> trap syscalls while user-mode emulating.
> 
> Best regards
> Edgar
> 
> 

Hello everyone,

Edgar,

that's exactly what I implemented the past week. I needed to simulate a
proprietary driver from a syscall point of view.

I added hooks for syscalls with basic priorities.

Here a few patch (it's a work in progress).

I'm also interrested in splitting the big sys.call.c (~6k lines) using
theses hooks.

Regards,

-- 
Lione Landwerlin                                         

O p e n W i d e                    14, rue Gaillon 75002 Paris

[-- Attachment #2: 0001-Added-syscall-hooks.patch --]
[-- Type: application/mbox, Size: 6858 bytes --]

[-- Attachment #3: 0002-Rename-syscall_hook-functions.patch --]
[-- Type: application/mbox, Size: 5565 bytes --]

[-- Attachment #4: 0003-Integration-of-syscall-hooks.patch --]
[-- Type: application/mbox, Size: 3881 bytes --]

[-- Attachment #5: 0004-hooks-integration.patch --]
[-- Type: application/mbox, Size: 3221 bytes --]

[-- Attachment #6: 0005-Splitted-syscalls-static-arrays.patch --]
[-- Type: application/mbox, Size: 1869 bytes --]

  reply	other threads:[~2008-12-06 13:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05 10:53 [Qemu-devel] Modular qemu? Joop Boonen
2008-12-05 12:40 ` Carl-Daniel Hailfinger
2008-12-05 14:32 ` Anthony Liguori
2008-12-05 14:52   ` Laurent Desnogues
2008-12-05 15:07     ` Glauber Costa
2008-12-05 15:29       ` Anthony Liguori
2008-12-05 15:25     ` Anthony Liguori
2008-12-05 18:19   ` Avi Kivity
2008-12-05 18:54     ` Thiemo Seufer
2008-12-05 19:02       ` Avi Kivity
2008-12-05 19:27         ` Anthony Liguori
2008-12-05 19:37           ` Avi Kivity
2008-12-05 19:58             ` Anthony Liguori
2008-12-05 18:56     ` [Qemu-devel] " Jan Kiszka
2008-12-05 18:57     ` [Qemu-devel] " Anthony Liguori
2008-12-05 19:12       ` Avi Kivity
2008-12-09 13:06         ` Jun Koi
2008-12-09 13:17           ` Stefano Stabellini
2008-12-09 13:44           ` Avi Kivity
2008-12-05 22:10   ` Edgar E. Iglesias
2008-12-06 13:23     ` Lionel Landwerlin [this message]
2008-12-08 10:15   ` Stefano Stabellini
2008-12-17 13:34   ` Ian Jackson
  -- strict thread matches above, loose matches on Subject: below --
2008-12-08 23:58 Salvatore Lionetti

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=1228569831.3948.6.camel@cocoduo.atr \
    --to=lionel.landwerlin@openwide.fr \
    --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).