From: Anthony Liguori <aliguori@us.ibm.com>
To: "Daniel P. Berrange" <berrange@redhat.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 16:34:22 -0600 [thread overview]
Message-ID: <45622D6E.9020607@us.ibm.com> (raw)
In-Reply-To: <20061120215600.GE15703@redhat.com>
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?
Regards,
Anthony Liguori
> So, is there any good reason for xc_save & xc_restore to exist as separate
> processes - it just seems like a huge complication to me, increasing
> fragility of the system & reducing the quality of error reporting we can
> get
>
> Regards,
> Dan.
next prev parent reply other threads:[~2006-11-20 22:34 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 [this message]
2006-11-20 22:43 ` Daniel P. Berrange
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=45622D6E.9020607@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=berrange@redhat.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.