All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: "Moese, Michael" <michael.moese@men.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Subject: Re: [Qemu-devel] Qemu Unix-Signals
Date: Wed, 17 Apr 2013 15:04:48 +0200	[thread overview]
Message-ID: <516E9DF0.7010708@suse.de> (raw)
In-Reply-To: <2DF74D4E746FF14C8697D5041AAE72D56A01D74E@MEN-EX2.intra.men.de>

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

  reply	other threads:[~2013-04-17 13:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17  8:02 [Qemu-devel] Qemu Unix-Signals Moese, Michael
2013-04-17  9:00 ` Peter Maydell
2013-04-17  9:21   ` Moese, Michael
2013-04-17 13:04     ` Andreas Färber [this message]
2013-04-17 17:07       ` Edgar E. Iglesias

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=516E9DF0.7010708@suse.de \
    --to=afaerber@suse.de \
    --cc=edgar.iglesias@gmail.com \
    --cc=michael.moese@men.de \
    --cc=pbonzini@redhat.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.