From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Gerd Knorr <kraxel@bytesex.org>
Subject: Re: address space reorganization
Date: Wed, 13 Apr 2005 19:18:28 -0700 [thread overview]
Message-ID: <425DD2F4.7070400@diku.dk> (raw)
In-Reply-To: <08282afe301ad10a5073e6b2522be52c@cl.cam.ac.uk>
Keir Fraser wrote:
> We need generally to think about how flexible we want to be in allowing
> migration between different machine configurations. Shoudl we require
> identical h/w specs, or allow differences in I/O devices, CPU and/or
> memory? We will already have to be careful about downgrading cpu specs
> when we migrate (e.g., Linux locks onto using multimedia instructions
> for software raid that are unavailable post-migrate).
Why not treat the functions that use special mm-instructions (like the
software RAID code) as critical sections that cannot overlap with
migration, and then have the guestOS re-calibrate its use of these
features upon arrival?
[ insert standard plug of self-migration here :-) ]
Jacob
next prev parent reply other threads:[~2005-04-14 2:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 17:59 address space reorganization Gerd Knorr
2005-04-13 19:29 ` Keir Fraser
2005-04-14 1:45 ` Keir Fraser
2005-04-14 2:18 ` Jacob Gorm Hansen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-14 2:26 Ian Pratt
2005-04-14 3:08 ` Jacob Gorm Hansen
2005-04-14 3:14 ` Kip Macy
2005-04-14 3:38 ` Jacob Gorm Hansen
2005-04-14 16:00 ` Adam Heath
2005-04-14 17:54 ` Rik van Riel
2005-04-14 18:15 ` Kip Macy
2005-04-14 18:20 ` Rik van Riel
2005-04-14 19:03 Ian Pratt
2005-04-19 19:52 ` Chris Wedgwood
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=425DD2F4.7070400@diku.dk \
--to=jacobg@diku.dk \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=kraxel@bytesex.org \
--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.