On Tue, May 17, 2016 at 01:11:22PM +0100, Matt Fleming wrote:
> On Mon, 16 May, at 05:58:40PM, Alex Thorlton wrote:
> >
> > I was simply re-using the efi_call implementation. Boris suggested that
> > I re-write this using the efi_call_virt macro, so I just went with that.
> > It all seems to
On Tue, May 17, 2016 at 01:11:22PM +0100, Matt Fleming wrote:
> On Mon, 16 May, at 05:58:40PM, Alex Thorlton wrote:
> >
> > I was simply re-using the efi_call implementation. Boris suggested that
> > I re-write this using the efi_call_virt macro, so I just went with that.
> > It all seems to
On Mon, 16 May, at 05:58:40PM, Alex Thorlton wrote:
>
> I was simply re-using the efi_call implementation. Boris suggested that
> I re-write this using the efi_call_virt macro, so I just went with that.
> It all seems to work just fine, so I don't see much reason to stray away
> from that
On Mon, 16 May, at 05:58:40PM, Alex Thorlton wrote:
>
> I was simply re-using the efi_call implementation. Boris suggested that
> I re-write this using the efi_call_virt macro, so I just went with that.
> It all seems to work just fine, so I don't see much reason to stray away
> from that
On Thu, May 12, 2016 at 10:17:39AM +0200, Ingo Molnar wrote:
> > Fine by me, although having a newline after arch_efi_call_virt_setup()
> > but not before arch_efi_call_virt_teardown() seems rather arbitrary
>
> It's an oversight! :-)
>
> #define efi_call_virt(f, args...)
On Thu, May 12, 2016 at 10:17:39AM +0200, Ingo Molnar wrote:
> > Fine by me, although having a newline after arch_efi_call_virt_setup()
> > but not before arch_efi_call_virt_teardown() seems rather arbitrary
>
> It's an oversight! :-)
>
> #define efi_call_virt(f, args...)
On Thu, May 12, 2016 at 01:06:00PM +0100, Matt Fleming wrote:
> (Adding author of arch_efi_call code)
>
> On Wed, 11 May, at 02:55:44PM, Alex Thorlton wrote:
> > We need a slightly different macro than the standard efi_call_virt,
> > since those macros all assume that the function pointer, f,
On Thu, May 12, 2016 at 01:06:00PM +0100, Matt Fleming wrote:
> (Adding author of arch_efi_call code)
>
> On Wed, 11 May, at 02:55:44PM, Alex Thorlton wrote:
> > We need a slightly different macro than the standard efi_call_virt,
> > since those macros all assume that the function pointer, f,
(Adding author of arch_efi_call code)
On Wed, 11 May, at 02:55:44PM, Alex Thorlton wrote:
> We need a slightly different macro than the standard efi_call_virt,
> since those macros all assume that the function pointer, f, that gets
> passed in will live somewhere in efi.systab->runtime. Our EFI
(Adding author of arch_efi_call code)
On Wed, 11 May, at 02:55:44PM, Alex Thorlton wrote:
> We need a slightly different macro than the standard efi_call_virt,
> since those macros all assume that the function pointer, f, that gets
> passed in will live somewhere in efi.systab->runtime. Our EFI
* Ard Biesheuvel wrote:
> On 12 May 2016 at 08:46, Ingo Molnar wrote:
> >
> > * Alex Thorlton wrote:
> >
> >> +#define efi_call_virt(f, args...)\
> >> +({
* Ard Biesheuvel wrote:
> On 12 May 2016 at 08:46, Ingo Molnar wrote:
> >
> > * Alex Thorlton wrote:
> >
> >> +#define efi_call_virt(f, args...)\
> >> +({ \
> >> + efi_status_t __s;
On 12 May 2016 at 08:46, Ingo Molnar wrote:
>
> * Alex Thorlton wrote:
>
>> +#define efi_call_virt(f, args...)\
>> +({ \
>> + efi_status_t __s;
On 12 May 2016 at 08:46, Ingo Molnar wrote:
>
> * Alex Thorlton wrote:
>
>> +#define efi_call_virt(f, args...)\
>> +({ \
>> + efi_status_t __s;
* Alex Thorlton wrote:
> +#define efi_call_virt(f, args...)\
> +({ \
> + efi_status_t __s; \
> + unsigned long flags;
* Alex Thorlton wrote:
> +#define efi_call_virt(f, args...)\
> +({ \
> + efi_status_t __s; \
> + unsigned long flags;
We need a slightly different macro than the standard efi_call_virt,
since those macros all assume that the function pointer, f, that gets
passed in will live somewhere in efi.systab->runtime. Our EFI function
pointer lives in efi.uv_systab, so we can't use the standard macros out
of the box.
We need a slightly different macro than the standard efi_call_virt,
since those macros all assume that the function pointer, f, that gets
passed in will live somewhere in efi.systab->runtime. Our EFI function
pointer lives in efi.uv_systab, so we can't use the standard macros out
of the box.
18 matches
Mail list logo