From: Nile Geisinger <nile@dloo.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Trivial (but useful) patch to save qemu pid to file
Date: Mon, 13 Dec 2004 13:20:39 +0000 [thread overview]
Message-ID: <200412131320.40243.nile@dloo.com> (raw)
In-Reply-To: <41B779A0.5050601@bellard.org>
Hi Fabrice,
First, thanks for QEMU!
I find it useful and the previous patcher found it useful, but I'm fine
patching for now. When a third person posts a patch, though,
it should probably be included since it would be a sign that QEMU
is being increasingly instrumented by other programs,
cheers,
Nile
On Wednesday 08 December 2004 10:01 pm, Fabrice Bellard wrote:
> Felipe Sanchez wrote:
> > On Wed, 8 Dec 2004, Nile Geisinger wrote:
> >>Here's a very trivial patch that allows qemu's pid to be saved to a
> >>file. This is useful if you're using qemu as a service, instrumenting
> >>it with other code, or doing other unixy things,
> >
> > Hello Nile, a somewhat more complete patch for doing this was already
> > posted a while ago:
> >
> > http://lists.gnu.org/archive/html/qemu-devel/2004-11/msg00450.html
> >
> >
> > Any comments are very welcome :-)
>
> I can include this patch if it helps some people as it seems rather non
> intrusive.
>
> Fabrice.
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
prev parent reply other threads:[~2004-12-13 22:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 9:38 [Qemu-devel] Syscall 269 James Pellow
2004-11-18 13:03 ` Paul Brook
2004-11-18 18:24 ` James Pellow
2004-12-04 0:05 ` James Pellow
2004-12-04 15:09 ` Paul Brook
2004-12-06 1:16 ` James Pellow
2004-12-06 1:26 ` Paul Brook
2004-12-06 2:58 ` James Pellow
2004-12-08 0:07 ` [Qemu-devel] Trivial (but useful) patch to save qemu pid to file Nile Geisinger
2004-12-08 18:12 ` Felipe Sanchez
2004-12-08 22:01 ` Fabrice Bellard
2004-12-09 2:11 ` Tim
2004-12-13 13:20 ` Nile Geisinger [this message]
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=200412131320.40243.nile@dloo.com \
--to=nile@dloo.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).