All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adel Amani <adel.amani66@yahoo.com>
To: Olaf Hering <olaf@aepfle.de>, Xen <xen-devel@lists.xen.org>
Subject: Re: function snprintf() in xen_save_domain.c for debugged
Date: Mon, 3 Feb 2014 04:56:10 -0800 (PST)	[thread overview]
Message-ID: <1391432170.33697.YahooMailNeo@web161806.mail.bf1.yahoo.com> (raw)
In-Reply-To: <20140202100044.GA5898@aepfle.de>


[-- Attachment #1.1: Type: text/plain, Size: 1097 bytes --]

Thanks, how i define logger for xc_interface_open to output print?!
can i use of code xc_save.c in xen 4.3.1 for logger in xen 4.1.2?!
 
Adel Amani
M.Sc. Candidate@Computer Engineering Department, University of Isfahan
Email: A.Amani@eng.ui.ac.ir



On Sunday, February 2, 2014 1:30 PM, Olaf Hering <olaf@aepfle.de> wrote:
 
On Sun, Feb 02, Adel Amani wrote:


> I check this function xc_domain_save.c, and attention at line 1185,
> function snprintf() amounts iter, sent_this_iter, skip_this_iter for
> print. (in xen 4.1.2 ) but i don't know where in amounts print!!! :-( 
> Are except file xend.log where is another for print and debugged?

The output in 4.1 is sent to xend.log, but only if a logger function is
registered. Please follow the code from tools/xcutils/xc_save.c:main to
the actual xc_report_progress_start call in
tools/libxc/xc_domain_save.c, as you will note xc_interface_open is
called without logger which means no output is printed.

For an example how a logger could look like see the xc_interface_open
call in tools/xenpaging/xenpaging.c.

Olaf

[-- Attachment #1.2: Type: text/html, Size: 2835 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2014-02-03 12:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-02  8:51 function snprintf() in xen_save_domain.c for debugged Adel Amani
2014-02-02 10:00 ` Olaf Hering
2014-02-03 12:56   ` Adel Amani [this message]
2014-02-03 13:11     ` Olaf Hering
2014-02-05  6:50       ` Adel Amani
2014-02-05 12:39         ` Olaf Hering
2014-02-06 12:28           ` Adel Amani
2014-02-06 21:40             ` Olaf Hering
     [not found]               ` <1391807749.53657.YahooMailNeo@web161801.mail.bf1.yahoo.com>
2014-02-07 22:22                 ` Olaf Hering
     [not found]                   ` <1392796739.73315.YahooMailNeo@web161801.mail.bf1.yahoo.com>
2014-02-19 14:12                     ` Olaf Hering
2014-02-21  7:18                       ` Adel Amani
2014-02-21  9:30                         ` Olaf Hering
2014-02-21 16:34                           ` Adel Amani
2014-02-24  9:02                             ` Olaf Hering

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=1391432170.33697.YahooMailNeo@web161806.mail.bf1.yahoo.com \
    --to=adel.amani66@yahoo.com \
    --cc=olaf@aepfle.de \
    --cc=xen-devel@lists.xen.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.