From: Keir Fraser <keir.xen@gmail.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: xen-devel@lists.xen.org
Subject: Re: fixed location of share info page in HVM guests
Date: Mon, 27 Aug 2012 22:51:52 +0100 [thread overview]
Message-ID: <CC61AA88.3CEFA%keir.xen@gmail.com> (raw)
In-Reply-To: <20120827213226.GA17915@aepfle.de>
On 27/08/2012 22:32, "Olaf Hering" <olaf@aepfle.de> wrote:
>>> Recently I tried to move the shared_info page in the pvops kernel during
>>> shutdown, see "xen PVonHVM: move shared_info to MMIO before kexec"
>>> patch. But this change was reverted because it caused reboot failures
>>> because the actual moving of the shared page is fragile.
>>
>> How was it fragile? Moving it into MMIO should just work?
>
> The moving itself is not the issue, but the possible access to the page
> during the move. Its not atomic, nor can it easily be atomic.
Why not map it into MMIO in the first place, rather than into the middle of
RAM? Do that early during boot, and early during resume from
save/restore/migrate (i.e., places you presumably already map the
shared_info page, but into the middle of RAM)?
-- Keir
next prev parent reply other threads:[~2012-08-27 21:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 17:55 fixed location of share info page in HVM guests Olaf Hering
2012-08-27 18:10 ` Keir Fraser
2012-08-27 21:32 ` Olaf Hering
2012-08-27 21:51 ` Keir Fraser [this message]
2012-08-27 21:56 ` Olaf Hering
2012-08-28 0:13 ` Keir Fraser
2012-08-28 8:23 ` Olaf Hering
2012-08-28 11:40 ` Keir Fraser
2012-08-28 12:42 ` Olaf Hering
2012-08-28 13:35 ` Keir Fraser
2012-08-31 23:43 ` Konrad Rzeszutek Wilk
2012-10-23 19:49 ` Olaf Hering
2012-10-24 7:31 ` Jan Beulich
2012-10-24 14:54 ` Olaf Hering
2012-10-22 18:50 ` Olaf Hering
2012-10-22 12:15 ` Keir Fraser
2012-10-23 7:34 ` Jan Beulich
2012-10-23 20:27 ` 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=CC61AA88.3CEFA%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=olaf@aepfle.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).