From: Nithish R <nithishr@gmail.com>
To: Mulyadi Santosa <mulyadi.santosa@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] VNC server running on `127.0.0.1:5900'
Date: Mon, 15 Aug 2011 11:45:23 +0530 [thread overview]
Message-ID: <CAJdxfnVMO-MwHMGXBmdMZJ6e6rrThUYDP2z_PPrVmQG-AyX0MQ@mail.gmail.com> (raw)
In-Reply-To: <CAGdaadYfyEQrRoNg7wfpZL=7=0M8ZOLq8Bwp8kj83UEc8NQcMw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
On Sat, Aug 13, 2011 at 11:13 PM, Mulyadi Santosa <mulyadi.santosa@gmail.com
> wrote:
> On Sat, Aug 13, 2011 at 21:54, Nithish R <nithishr@gmail.com> wrote:
> > Hi
> > Thanx a lot... It worked...
>
> nice, btw, please reply to the list too, I don't want to take it as
> private discussion....
>
> > By the way do u know how the log file is generated in the qemu monitor
> when
> > we give the commands like log out_asm, in_asm, op, etc? I am working on a
> > project which involves providing network support for virtualization. So
> as
> > proof of concept, I have to generate the assembly codes. I need to
> modify
> > it but as of now I am not getting anything about logging in monitor.c
> file
> > apart from lots of functions involving log but none has out_asm or any
> > command associated with it.
>
> the log? AFAICT, it's a continous dump of current running TB
> (translated block). Can't tell much...sorry
> Its okay... Thanks a lot for helping out..
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com
> training: mulyaditraining.blogspot.com
>
[-- Attachment #2: Type: text/html, Size: 1757 bytes --]
prev parent reply other threads:[~2011-08-15 6:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 17:01 [Qemu-devel] VNC server running on `127.0.0.1:5900' Nithish R
2011-08-10 7:40 ` Mulyadi Santosa
[not found] ` <CAJdxfnVBHCgz5dd41Ft6s9MAocXL_SzKJ7GgBJ=0Rm6Evx18bQ@mail.gmail.com>
[not found] ` <CAGdaada5LO2FQni_mxcVoW=WhhVC4Vot70=nvBVUo6x_kKetJg@mail.gmail.com>
2011-08-10 17:43 ` [Qemu-devel] Fwd: " Mulyadi Santosa
[not found] ` <CAJdxfnW6CHsnrzLWPQ_3iALSQttfYV0zUYdE-dumfDVLLOwSrQ@mail.gmail.com>
2011-08-11 5:27 ` [Qemu-devel] " Mulyadi Santosa
[not found] ` <CAJdxfnUe6zZ=BsUHNMfE7vXWsTLoh0F2GCa8otDX=Q3v9FxDFQ@mail.gmail.com>
2011-08-13 17:43 ` Mulyadi Santosa
2011-08-15 6:15 ` Nithish R [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=CAJdxfnVMO-MwHMGXBmdMZJ6e6rrThUYDP2z_PPrVmQG-AyX0MQ@mail.gmail.com \
--to=nithishr@gmail.com \
--cc=mulyadi.santosa@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).