All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
Subject: Re: Trivial patch to fix logging level output by XendCheckpoint.py
Date: Mon, 20 Nov 2006 22:43:23 +0000	[thread overview]
Message-ID: <20061120224323.GF15703@redhat.com> (raw)
In-Reply-To: <45622D6E.9020607@us.ibm.com>

On Mon, Nov 20, 2006 at 04:34:22PM -0600, Anthony Liguori wrote:
> Daniel P. Berrange wrote:
> >On Mon, Nov 20, 2006 at 04:34:25PM -0500, Graham, Simon wrote:
> >>Signed-off by: Simon Graham <Simon.Graham@stratus.com>
> 
> >And even more importantly, once we get the error reporting patches 
> >integrated
> >into libxc, having the xc_linux_save/restore calls made by XenD directly
> >would ensure we get reliable error handling for save/restore operations.
> 
> It used to work that way.  xc_linux_save/restore were factored out of 
> Xend late in the 3.0 dev process.  I believe the idea was that they 
> should be executed with lower privileges (which is why they take file 
> descriptors as command line arguments instead of just calling 
> xc_interface_open() like you would expect).
>
> I believe it was Christian who was driving this.  Perhaps he has a few 
> more details?

Ok, looking back at the HG logs it appears  # 5099 

 "Execute xc_linux_restore in a seperate process so that it can't
  crash xend.  Also handle errors passed from xc_linux_restore and
  log info messages from xc_linux_restore."

and # 5121:

 "Implement the parts of vm save which need interaction with xend
  as part of xend, instead of using xfrd.
  Execute xc_linux_save in a seperate process so that it can't
  crash xend. Also handle errors passed from xc_linux_save.

are where these programs came into existance.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

  reply	other threads:[~2006-11-20 22:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-20 21:34 Trivial patch to fix logging level output by XendCheckpoint.py Graham, Simon
2006-11-20 21:56 ` Daniel P. Berrange
2006-11-20 22:34   ` Anthony Liguori
2006-11-20 22:43     ` Daniel P. Berrange [this message]
2006-11-20 22:40   ` Ewan Mellor
2006-11-20 22:53     ` John Levon
2006-11-21 10:19 ` Ewan Mellor
  -- strict thread matches above, loose matches on Subject: below --
2006-11-21  1:23 Graham, Simon
2006-11-21  9:20 ` Ewan Mellor
2006-11-21 12:29   ` Daniel P. Berrange
2006-11-21 14:58 Graham, Simon
2006-11-21 15:04 ` Daniel P. Berrange
2006-11-21 15:05 ` Ewan Mellor

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=20061120224323.GF15703@redhat.com \
    --to=berrange@redhat.com \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --cc=aliguori@us.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    /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.