From: Alex Thorlton <athorlton@sgi.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Alex Thorlton <athorlton@sgi.com>,
linux-kernel@vger.kernel.org, Dimitri Sivanich <sivanich@sgi.com>,
Russ Anderson <rja@sgi.com>, Mike Travis <travis@sgi.com>,
Matt Fleming <matt@codeblueprint.co.uk>,
Borislav Petkov <bp@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-efi@vger.kernel.org
Subject: Re: [PATCH 2/2] Fix efi_call
Date: Mon, 16 May 2016 11:24:55 -0500 [thread overview]
Message-ID: <20160516162455.GD98477@stormcage.americas.sgi.com> (raw)
In-Reply-To: <20160512064835.GB30717@gmail.com>
On Thu, May 12, 2016 at 08:48:35AM +0200, Ingo Molnar wrote:
> I suppose the SGI/UV code is the only one using 7 arguments or more? Might make
> sense to point that out in the changelog.
First off, to everybody, sorry for the delayed responses. I've been
AFK for a few days and forgot to set my vacation notice :(
Yes, I believe that's it. I didn't do a full audit, but a quick glance
at the other users of this call showed that nobody else appears to be
using that many args.
> Just curious, how did you find this bug? It's a pretty obscure one, of the
> 'developer tears out hairs from frustruation' type ...
Yes, this one was a real puzzle to figure out. Basically I just stepped
through the assembly code from a known good point to see how we ended up
where we did. I quite a bit of help from the vets around here, as well
as from our simulator that I used to step through our early boot code to
find the problem.
The real hair pulling mostly came from trying to figure out *WHY* we
were putting the return address in this seemingly random spot on the
stack. After thoroughly re-reading assorted Intel (et. al.) docs about
a hundred times, I was able to piece together what I thought was
supposed to be going on here. The solution may be simple, but arriving
there was anything but that :)
- Alex
next prev parent reply other threads:[~2016-05-16 16:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 19:55 [RFC PATCH 0/2] Fix EFI runtime calls on SGI UV Alex Thorlton
2016-05-11 19:55 ` [PATCH 1/2] Create UV efi_call macros Alex Thorlton
2016-05-12 6:46 ` Ingo Molnar
2016-05-12 7:35 ` Ard Biesheuvel
2016-05-12 8:17 ` Ingo Molnar
2016-05-16 23:00 ` Alex Thorlton
2016-05-12 12:06 ` Matt Fleming
2016-05-16 22:58 ` Alex Thorlton
2016-05-17 12:11 ` Matt Fleming
2016-05-17 20:14 ` Alex Thorlton
2016-05-11 19:55 ` [PATCH 2/2] Fix efi_call Alex Thorlton
2016-05-12 6:48 ` Ingo Molnar
2016-05-12 11:43 ` Matt Fleming
2016-05-16 16:24 ` Alex Thorlton [this message]
2016-05-12 11:41 ` Matt Fleming
2016-05-16 16:25 ` Alex Thorlton
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=20160516162455.GD98477@stormcage.americas.sgi.com \
--to=athorlton@sgi.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=rja@sgi.com \
--cc=sivanich@sgi.com \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
--cc=x86@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
all inboxes | Powered by JetHome®