All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt@codeblueprint.co.uk>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
	linux-efi@vger.kernel.org, Peter Jones <pjones@redhat.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [tip regression]  efi: Allow drivers to reserve boot services forever == toxic
Date: Sat, 17 Sep 2016 20:58:54 +0100	[thread overview]
Message-ID: <20160917195853.GG16797@codeblueprint.co.uk> (raw)
In-Reply-To: <1474043695.3854.3.camel@gmail.com>

On Fri, 16 Sep, at 06:34:55PM, Mike Galbraith wrote:
> On Fri, 2016-09-16 at 15:30 +0100, Matt Fleming wrote:
> > On Fri, 16 Sep, at 12:00:59PM, Mike Galbraith wrote:
> > > 
> > > Ok, here's the whole thing just in case.  Hope it's not too big.
> >  
> > [...]
> > 
> > > [    0.000000] esrt: Reserving ESRT space from 0x00000000def87998 to 0x00000000def879d0.
> > 
> > OK, that's 56 bytes and yet I realise that at no point in the
> > efi_mem_reserve() call path do we round up to the nearest page size
> > even though the EFI memory map only deals with EFI_PAGE_SIZE regions.
> > 
> > Could you try this patch?
> 
> No dice.  The numbers changed, but box still goes *poof*.
> 
> ---
>  arch/x86/platform/efi/quirks.c |    4 ++++
>  1 file changed, 4 insertions(+)
> 
> --- a/arch/x86/platform/efi/quirks.c
> +++ b/arch/x86/platform/efi/quirks.c
> @@ -227,7 +227,11 @@ void __init efi_arch_mem_reserve(phys_ad
>  	efi_memmap_insert(&efi.memmap, new, &mr);
>  	early_memunmap(new, new_size);
>  
> +#if 0
>  	efi_memmap_install(new_phys, num_entries);
> +#else
> +	printk(KERN_DEBUG "MIKE efi_memmap_install(0x%Lx, %d);\n", new_phys, num_entries);
> +#endif
>  }
>  
>  /*
> 
> homer:..debug/tracing # journalctl|grep MIKE
> virgin+above
> Sep 16 15:51:15 homer kernel: MIKE efi_memmap_install(0x9d640, 51);
> Sep 16 15:55:07 homer kernel: MIKE efi_memmap_install(0x9d640, 51);
> +patch+above
> Sep 16 18:13:46 homer kernel: MIKE efi_memmap_install(0x9d600, 53);

These addresses are pretty low. Can you try the hacky patch plus
Ricardo's change in commit 3dad6f7f6975 ("x86/efi: Defer efi_esrt_init
until after memblock_x86_fill"). He fixed a bug where it's possible to
run out of memblock regions.

WARNING: multiple messages have this Message-ID (diff)
From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: Mike Galbraith <umgwanakikbuti-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>,
	LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Peter Jones <pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Ard Biesheuvel
	<ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: Re: [tip regression]  efi: Allow drivers to reserve boot services forever == toxic
Date: Sat, 17 Sep 2016 20:58:54 +0100	[thread overview]
Message-ID: <20160917195853.GG16797@codeblueprint.co.uk> (raw)
In-Reply-To: <1474043695.3854.3.camel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On Fri, 16 Sep, at 06:34:55PM, Mike Galbraith wrote:
> On Fri, 2016-09-16 at 15:30 +0100, Matt Fleming wrote:
> > On Fri, 16 Sep, at 12:00:59PM, Mike Galbraith wrote:
> > > 
> > > Ok, here's the whole thing just in case.  Hope it's not too big.
> >  
> > [...]
> > 
> > > [    0.000000] esrt: Reserving ESRT space from 0x00000000def87998 to 0x00000000def879d0.
> > 
> > OK, that's 56 bytes and yet I realise that at no point in the
> > efi_mem_reserve() call path do we round up to the nearest page size
> > even though the EFI memory map only deals with EFI_PAGE_SIZE regions.
> > 
> > Could you try this patch?
> 
> No dice.  The numbers changed, but box still goes *poof*.
> 
> ---
>  arch/x86/platform/efi/quirks.c |    4 ++++
>  1 file changed, 4 insertions(+)
> 
> --- a/arch/x86/platform/efi/quirks.c
> +++ b/arch/x86/platform/efi/quirks.c
> @@ -227,7 +227,11 @@ void __init efi_arch_mem_reserve(phys_ad
>  	efi_memmap_insert(&efi.memmap, new, &mr);
>  	early_memunmap(new, new_size);
>  
> +#if 0
>  	efi_memmap_install(new_phys, num_entries);
> +#else
> +	printk(KERN_DEBUG "MIKE efi_memmap_install(0x%Lx, %d);\n", new_phys, num_entries);
> +#endif
>  }
>  
>  /*
> 
> homer:..debug/tracing # journalctl|grep MIKE
> virgin+above
> Sep 16 15:51:15 homer kernel: MIKE efi_memmap_install(0x9d640, 51);
> Sep 16 15:55:07 homer kernel: MIKE efi_memmap_install(0x9d640, 51);
> +patch+above
> Sep 16 18:13:46 homer kernel: MIKE efi_memmap_install(0x9d600, 53);

These addresses are pretty low. Can you try the hacky patch plus
Ricardo's change in commit 3dad6f7f6975 ("x86/efi: Defer efi_esrt_init
until after memblock_x86_fill"). He fixed a bug where it's possible to
run out of memblock regions.

  reply	other threads:[~2016-09-17 19:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-16  6:05 [tip regression] efi: Allow drivers to reserve boot services forever == toxic Mike Galbraith
2016-09-16  9:31 ` Matt Fleming
2016-09-16 10:00   ` Mike Galbraith
2016-09-16 10:00     ` Mike Galbraith
2016-09-16 14:30     ` Matt Fleming
2016-09-16 14:30       ` Matt Fleming
2016-09-16 14:45       ` Mark Rutland
2016-09-16 14:45         ` Mark Rutland
2016-09-16 18:26         ` Mike Galbraith
2016-09-16 18:26           ` Mike Galbraith
2016-09-19  8:56           ` Mark Rutland
2016-09-19  8:56             ` Mark Rutland
2016-09-16 16:34       ` Mike Galbraith
2016-09-16 16:34         ` Mike Galbraith
2016-09-17 19:58         ` Matt Fleming [this message]
2016-09-17 19:58           ` Matt Fleming
2016-09-18  6:09           ` Mike Galbraith
2016-09-18  6:09             ` Mike Galbraith
2016-09-19 11:15             ` Matt Fleming
2016-09-19 11:15               ` 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=20160917195853.GG16797@codeblueprint.co.uk \
    --to=matt@codeblueprint.co.uk \
    --cc=ard.biesheuvel@linaro.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pjones@redhat.com \
    --cc=umgwanakikbuti@gmail.com \
    /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.