From: <vrd@amazon.com>
To: Simon Horman <horms@verge.net.au>, Varad Gautam <vrd@amazon.de>
Cc: kexec@lists.infradead.org, David Woodhouse <dwmw@amazon.co.uk>
Subject: Re: [PATCH 1/3] xen: Avoid overlapping segments in low memory
Date: Mon, 24 Jun 2019 21:02:21 +0200 [thread overview]
Message-ID: <38c53c73-30ad-0985-c08b-6b29b4ab8698@amazon.com> (raw)
In-Reply-To: <20190531090746.ozf6kyezmj77gqyo@verge.net.au>
On 5/31/19 11:07 AM, Simon Horman wrote:
> On Tue, May 21, 2019 at 09:32:26AM +0200, Varad Gautam wrote:
>> From: David Woodhouse <dwmw@amazon.co.uk>
>>
>> Unlike Linux which creates a full identity mapping, Xen only maps those
>> segments which are explicitly requested. Therefore, xen_kexec_load()
>> silently adds in a segment from zero to 1MiB to ensure that VGA memory
>> and other things are accessible.
>>
>> However, this doesn't work when there are already segments to be loaded
>> under 1MiB, because the overlap causes Xen to reject the kexec_load.
>>
>> Be more careful and just infill the ranges which are required instead
>> of naïvely adding a full 0-1MiB segment at the end.
>>
>> Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
> This patch appears to be present in the kexec-tools tree as:
>
> eff53089523c xen: Avoid overlapping segments in low memory
Ah, please ignore this one. I had an earlier checkout.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2019-06-24 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 7:32 [PATCH 1/3] xen: Avoid overlapping segments in low memory Varad Gautam
2019-05-21 7:32 ` [PATCH 2/3] elf: Support ELF loading with relocation Varad Gautam
2019-06-25 8:11 ` [PATCH 2/3 RESEND] " Varad Gautam
2019-05-21 7:32 ` [PATCH 3/3] x86: Support multiboot2 images Varad Gautam
2019-05-31 9:22 ` Simon Horman
2019-06-24 18:59 ` [PATCH v2] " Varad Gautam
2019-05-31 9:07 ` [PATCH 1/3] xen: Avoid overlapping segments in low memory Simon Horman
2019-06-24 19:02 ` vrd [this message]
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=38c53c73-30ad-0985-c08b-6b29b4ab8698@amazon.com \
--to=vrd@amazon.com \
--cc=dwmw@amazon.co.uk \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=vrd@amazon.de \
/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.