All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Adam Jacobvitz <jacobvi123@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] unmapping and remapping /dev/rtheap
Date: Wed, 04 Sep 2013 12:53:28 +0200	[thread overview]
Message-ID: <52271128.9010401@siemens.com> (raw)
In-Reply-To: <CAC3AHr+NOAqPNAFnxGvcMxuJRorotv0O0WrGHCUGuV0zBZYEhw@mail.gmail.com>

On 2013-09-04 12:39, Adam Jacobvitz wrote:
> Yeah...I suppose that's the fundamental issue. I'm brand new to xenomai and
> I'm not really familiar to what state xenomai maintains for an application.
> 
> Do you know what state I would need to checkpoint and if its even possible
> to checkpoint it?

There is a lot, starting with core thread objects, sync objects etc.,
then there are skin-specific extensions of those and also objects that
are shared between processes. But even if you export all this, Xenomai
wasn't designed with this use case in mind. So you may find many tricky
corner cases around checkpoint/restart - just like in Linux...

What overall use case are you aiming at with CRIU for your RT
process(es)? What states would your processes be in when
saving/restoring? And what Xenomai version do you consider for this, 2.6
or upcoming 3.0?

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux


  reply	other threads:[~2013-09-04 10:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 10:04 [Xenomai] unmapping and remapping /dev/rtheap Adam Jacobvitz
2013-09-04 10:34 ` Jan Kiszka
2013-09-04 10:39   ` Adam Jacobvitz
2013-09-04 10:53     ` Jan Kiszka [this message]
2013-09-04 11:50       ` Adam J
2013-09-04 12:03         ` Gilles Chanteperdrix
2013-09-04 12:06           ` Adam J

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=52271128.9010401@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=jacobvi123@gmail.com \
    --cc=xenomai@xenomai.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.