[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160602162335.GV242721@stormcage.americas.sgi.com>
Date: Thu, 2 Jun 2016 11:23:35 -0500
From: Alex Thorlton <athorlton@....com>
To: Matt Fleming <matt@...eblueprint.co.uk>
Cc: Alex Thorlton <athorlton@....com>, linux-kernel@...r.kernel.org,
Borislav Petkov <bp@...e.de>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, Mike Travis <travis@....com>,
Russ Anderson <rja@....com>,
Dimitri Sivanich <sivanich@....com>, x86@...nel.org,
linux-efi@...r.kernel.org, Mark Rutland <mark.rutland@....com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>
Subject: Re: [PATCH 1/3] Convert efi_call_virt to efi_call_virt_generic
On Thu, Jun 02, 2016 at 04:41:14PM +0100, Matt Fleming wrote:
> Oops, you're missing updates to the 32-bit version and ARM/arm64,
> which results in this,
>
> drivers/firmware/efi/runtime-wrappers.c: In function ‘virt_efi_get_time’:
> arch/x86/include/asm/efi.h:46:4: error: ‘efi_efi’ undeclared (first use in this function)
> ((efi_##f##_t __attribute__((regparm(0)))*) \
> ^
>
> but that's easily fixed up.
Oops! Sorry about that. I had done a pretty recent pull before I did
my last build, but it was probably before these updates came in. I'll
rebase my patches onto the latest tip kernel and fix this.
> > +/*
> > + * Wrap around the new efi_call_virt_generic macros so that the
> > + * code doesn't get too cluttered
> > + */
> > +#define efi_call_virt(f, args...) \
> > + efi_call_virt_generic(efi.systab->runtime, f, args)
> > +#define __efi_call_virt(f, args...) \
> > + __efi_call_virt_generic(efi.systab->runtime, f, args)
> > +
> > +void efi_call_virt_check_flags(unsigned long flags, const char *call)
> > {
> > unsigned long cur_flags, mismatch;
> >
>
> I'm not crazy about using "generic" in the name. How about
> efi_call_virt_function() or efi_call_virt_pointer()?
I'm not married to "generic." I'll change it to efi_call_virt_pointer.
I think efi_call_virt_function is a little confusing/redundant, since a
call is always to a function, right?
I will fix this stuff up and send a v2.
Thanks for looking this over, Matt!
- Alex
Powered by blists - more mailing lists