From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <JBeulich@suse.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel <xen-devel@lists.xen.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH v4] xen PVonHVM: move shared_info to reserved memory area
Date: Tue, 30 Oct 2012 18:03:21 +0100 [thread overview]
Message-ID: <20121030170321.GA1251@aepfle.de> (raw)
In-Reply-To: <5090124C02000078000A58AC@nat28.tlf.novell.com>
On Tue, Oct 30, Jan Beulich wrote:
> And iirc you're doing this relocation because otherwise the newly
> booting kernel image may get overwritten at an (from its
> perspective) arbitrary location. What I'm trying to point out is
> that the shared info structure is not the only thing (potentially)
> inside the kernel image that might get overwritten - the relocated
> (by the old kernel) vCPU info may as well. Plus I think the new
> kernel has no way of relocating it a second time (including back
> into the shared info structure) with how the hypervisor works at
> present.
Thanks, I have not looked at this, nor was I aware of it until now.
I will see what needs to be done.
Is this also an issue with the xenlinux based PVonHVM code?
Olaf
next prev parent reply other threads:[~2012-10-30 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 15:47 [PATCH v4] xen PVonHVM: move shared_info to reserved memory area Olaf Hering
2012-10-30 16:15 ` [Xen-devel] " Jan Beulich
2012-10-30 16:30 ` Olaf Hering
2012-10-30 16:45 ` Jan Beulich
2012-10-30 17:03 ` Olaf Hering [this message]
2012-10-31 8:02 ` Jan Beulich
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=20121030170321.GA1251@aepfle.de \
--to=olaf@aepfle.de \
--cc=JBeulich@suse.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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