From: Juergen Gross <jgross@suse.com>
To: Jan Beulich <JBeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
David Vrabel <david.vrabel@citrix.com>
Subject: Re: dom0 pvops and rearranging memory layout
Date: Fri, 23 Jan 2015 13:08:00 +0100 [thread overview]
Message-ID: <54C239A0.9050605@suse.com> (raw)
In-Reply-To: <54C246980200007800058C51@suse.com>
On 01/23/2015 01:03 PM, Jan Beulich wrote:
>>>> On 23.01.15 at 12:35, <andrew.cooper3@citrix.com> wrote:
>> I wonder whether it might be reasonable to extend contruct_dom0/libelf
>> to avoid constructing a p2m where pfns of built data (kernel, initrd,
>> p2m and initial pagetables) aliased with host io regions.
>
> For one, the problem goes away to 99.999% if using the advanced
> capabilities of relocating the P2M and not mapping the initrd at all.
No, it does not. I'm doing both and the systems dies at once.
Even relocating the P2M to another virtual address and not mapping
the initrd won't help if the related PFNs are relocated and, even worse,
are made available for new memory allocations.
> And then, such a change could easily end up being incompatible with
> older kernels, which may (and do) build on the initial memory map
> being a single chunk.
Yes, I fear so, too.
Juergen
next prev parent reply other threads:[~2015-01-23 12:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 10:32 dom0 pvops and rearranging memory layout Juergen Gross
2015-01-23 11:35 ` Andrew Cooper
2015-01-23 11:41 ` Juergen Gross
2015-01-23 12:03 ` Jan Beulich
[not found] ` <54C246980200007800058C51@suse.com>
2015-01-23 12:08 ` Juergen Gross [this message]
2015-01-23 12:42 ` Jan Beulich
2015-01-23 11:58 ` David Vrabel
2015-01-23 15:09 ` Konrad Rzeszutek Wilk
2015-01-23 15:16 ` Juergen Gross
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=54C239A0.9050605@suse.com \
--to=jgross@suse.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=xen-devel@lists.xenproject.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.