From: Linn Crosetto <linn@hp.com>
To: Matt Fleming <matt@console-pimps.org>
Cc: matt.fleming@intel.com, hpa@zytor.com, tglx@linutronix.de,
mingo@redhat.com, x86@kernel.org, yinghai@kernel.org,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2] x86: EFI stub support for large memory maps
Date: Sun, 22 Sep 2013 18:23:28 -0600 [thread overview]
Message-ID: <20130923002328.GC24764@oranje.fc.hp.com> (raw)
In-Reply-To: <20130917201452.GI3409@console-pimps.org>
On Tue, Sep 17, 2013 at 09:14:52PM +0100, Matt Fleming wrote:
> > +static efi_status_t alloc_e820ext(u32 nr_desc, struct setup_data **e820ext,
> > + u32 *e820ext_size)
> > +{
> > + efi_status_t status;
> > + unsigned long size;
> > +
> > + size = sizeof(struct setup_data) +
> > + sizeof(struct e820entry) * nr_desc;
> > +
> > + if (*e820ext && size <= *e820ext_size)
> > + return EFI_SUCCESS; /* Already allocated */
>
> Do we actually need this check? I thought the 'prev_nr_desc' below
> ensures we only allocate 'e820ext' if we need more memory.
I am okay with removing the check. There is another bug in exit_boot, when
jumping to get_map the call to get the memory map is passed the previous map
size instead of the size of the allocated buffer. I'll make the changes and
resend.
>
> [...]
>
> > @@ -1016,6 +1157,19 @@ get_map:
> > if (status != EFI_SUCCESS)
> > goto free_mem_map;
> >
> > + prev_nr_desc = nr_desc;
> > + nr_desc = size / desc_size;
> > + if (nr_desc > prev_nr_desc &&
> > + nr_desc > ARRAY_SIZE(boot_params->e820_map)) {
> > + u32 nr_e820ext = nr_desc - ARRAY_SIZE(boot_params->e820_map);
> > +
> > + status = alloc_e820ext(nr_e820ext, &e820ext, &e820ext_size);
> > + if (status != EFI_SUCCESS)
> > + goto free_mem_map;
> > +
> > + goto get_map; /* Allocated memory, get map again */
> > + }
> > +
next prev parent reply other threads:[~2013-09-23 0:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 21:02 [PATCH] " Linn Crosetto
2013-09-06 10:03 ` Matt Fleming
2013-09-06 17:04 ` [PATCHv2] " Linn Crosetto
2013-09-17 20:14 ` Matt Fleming
2013-09-23 0:23 ` Linn Crosetto [this message]
2013-09-23 1:59 ` [PATCHv3] " Linn Crosetto
2013-09-25 12:58 ` Matt Fleming
2013-09-25 22:45 ` Linn Crosetto
2013-09-26 11:34 ` Matt Fleming
2013-09-27 23:46 ` Linn Crosetto
2013-09-30 9:22 ` Matt Fleming
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=20130923002328.GC24764@oranje.fc.hp.com \
--to=linn@hp.com \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matt@console-pimps.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@kernel.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
Powered by JetHome