All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Adel Amani <adel.amani66@yahoo.com>
Cc: Xen <xen-devel@lists.xen.org>
Subject: Re: function snprintf() in xen_save_domain.c for debugged
Date: Thu, 6 Feb 2014 22:40:18 +0100	[thread overview]
Message-ID: <20140206214018.GA14658@aepfle.de> (raw)
In-Reply-To: <1391689706.75705.YahooMailNeo@web161806.mail.bf1.yahoo.com>

On Thu, Feb 06, Adel Amani wrote:

> I check XCFLAGS_DEBUG that definition at line 27 of file xenguest.h that
> mean's 
> #define XCFLAGS_DEBUG (1 << 1)
> I done 2 migration to amount lvl = XTL_DEBUG; and lvl = XTL_DETAIL; that result
> attached But until i have not log of dirty page(dirty memory)and downtime :-(

Did you already follow the code paths to see why nothing is printed?
Does a simpe 'fprintf(stderr,"STDERR\n"); fprintf(stdout,"STDOUT\n");'
appear in xend.log?

The downtime is the time during domU suspend/resume. Its best measuered
by looking at domU dmesg. Boot the domU with 'initcall_debug' to get an
understanding whats going on during such a suspend/resume cycle.

Olaf

  reply	other threads:[~2014-02-06 21:40 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
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 [this message]
     [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=20140206214018.GA14658@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=adel.amani66@yahoo.com \
    --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.