[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Qemu Unix-Signals
From: |
Andreas Färber |
Subject: |
Re: [Qemu-devel] Qemu Unix-Signals |
Date: |
Wed, 17 Apr 2013 15:04:48 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5 |
Hi,
Am 17.04.2013 11:21, schrieb Moese, Michael:
>> I think your best bet is to ask GreenSocs if you need support for this
>> codebase.
>
> I think you'd be right when you point me to GreenSocs, but.. they don't seem
> to support all this anymore.
>
>
>> This is really ancient in QEMU terms, and how the internals work has changed
>> enormously since then.
>
> Given I'd port their work over to a current QEMU source tree, would it be
> save then to use a signal, like SIGUSR2?
> I cannot find any use of these signals in the (old) sources, but I want to be
> sure not to add unwanted side effects
> when I just change the signal handler in my initialization code.
> The differences seem to be only in some files of the sources, maybe I can
> port this stuff over to the current version,
> as this might be useful not only to me for my thesis right now but to some
> other developer for hardware-software-
> co-simulation.
If you were to rebase onto the latest git version, you could as of
yesterday use the qtest protocol interface outside of qtest to inject
IRQs, IIUC. :-)
Do note that either SIGUSR1 or SIGUSR2 is in use for timers or something
(and our Wiki page on debugging listed the wrong one last time I ran
into it ;)).
Regards,
Andreas
P.S. x.y.5 would be a development version, so there's no telling what
exactly it did.
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg