From: Andre <andre.muller-S0/GAf8tV78@public.gmane.org>
To: linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org,
Ulf Winkelvos <ulf-rS3t9PEbhQ0OIzVOb1FTxg@public.gmane.org>
Subject: Re: [PATCH 1/1] arch/x86: Add better error logging to efi main
Date: Sun, 7 Sep 2014 02:11:33 +0200 [thread overview]
Message-ID: <20140907021133.7184c28c@bert> (raw)
In-Reply-To: <20140906230251.140a99c9@bert>
On Sat, 6 Sep 2014 23:02:51 +0200
Andre <andre.muller-S0/GAf8tV78@public.gmane.org> wrote:
> With a Thinkpad T420 (pre-2.0 EFI), I do run into the failure condition for another reason:
>
> setup_efi_pci64 gets called,
> the loop therein is executed nr_pci=11 (!?) times.
> The second call run calls into __setup_efi_pci64 successfully, the memcpy takes place; the free_struct: path is not used. Back in setup_efi_pci64, the non-data path is walked.
>
> For all the other 10 runs of the loop, __setup_efi_pci64 fails at
> if (!pci->romimage || !pci->romsize)
> return EFI_INVALID_PARAMETER;
> so that is the status here for any run but the second.
Following up with code...
If it is OK to just leave the loop in setup_efi_pci64,
this can be done simply by
--- arch/x86/boot/compressed/eboot.c 2014-09-07 01:54:41.761008645 +0200
+++ arch/x86/boot/compressed/eboot_break.c 2014-09-07 01:52:06.321004951 +0200
@@ -504,6 +504,7 @@
params->hdr.setup_data = (unsigned long)rom;
data = (struct setup_data *)rom;
+ break;
}
But I've got severe doubts about this.
A solution limited to this particular failure mode
could look like the below. It has all the charm of
introducing a helper var. Hmpf.
--- arch/x86/boot/compressed/eboot.c 2014-09-07 01:54:41.761008645 +0200
+++ arch/x86/boot/compressed/eboot_preserve.c 2014-09-07 01:56:18.529010945 +0200
@@ -474,6 +474,7 @@
unsigned long nr_pci;
struct setup_data *data;
int i;
+ int setup_pci_worked_once = 0;
data = (struct setup_data *)(unsigned long)params->hdr.setup_data;
@@ -495,7 +496,13 @@
continue;
status = __setup_efi_pci64(pci, &rom);
- if (status != EFI_SUCCESS)
+ if (status == EFI_SUCCESS)
+ setup_pci_worked_once = 1;
+ else if (status == EFI_INVALID_PARAMETER && setup_pci_worked_once == 1 && i == nr_pci - 1) {
+ status = EFI_SUCCESS;
+ continue;
+ }
+ else if (status != EFI_SUCCESS)
continue;
if (data)
Regards,
Andre
next prev parent reply other threads:[~2014-09-07 0:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-06 21:02 [PATCH 1/1] arch/x86: Add better error logging to efi main Andre
2014-09-07 0:11 ` Andre [this message]
2014-09-08 21:18 ` Matt Fleming
[not found] ` <20140908211856.GC18582-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2014-09-09 22:54 ` Andre
2014-09-09 23:00 ` [RFC] [PATCH] x86/efi: Adding efi_printks on memory allocationa and pci.reads Andre
2014-09-11 8:08 ` Matt Fleming
-- strict thread matches above, loose matches on Subject: below --
2014-07-10 0:12 [PATCH 1/1] arch/x86: Add better error logging to efi main ulf-rS3t9PEbhQ0OIzVOb1FTxg
[not found] ` <1404951161-2677-1-git-send-email-ulf-rS3t9PEbhQ0OIzVOb1FTxg@public.gmane.org>
2014-07-10 18:36 ` Matt Fleming
2014-08-13 17:56 ` Matt Fleming
[not found] ` <20140813175611.GU15082-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2014-08-14 22:56 ` Ulf Winkelvos
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=20140907021133.7184c28c@bert \
--to=andre.muller-s0/gaf8tv78@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org \
--cc=ulf-rS3t9PEbhQ0OIzVOb1FTxg@public.gmane.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.