A question about memblock.reserved
Hello all,
I mm/memblock.c I see this struct memblock memblock which is initialized
with empty list.
static struct memblock_region
memblock_memory_init_regions[INIT_MEMBLOCK_REGIONS] __initdata_memblock;
static struct memblock_region
memblock_reserved_init_regions[INIT_MEMBLOCK_RESERVED_REGIONS]
__initdata_memblock;
#ifdef CONFIG_HAVE_MEMBLOCK_PHYS_MAP
static struct memblock_region
memblock_physmem_init_regions[INIT_PHYSMEM_REGIONS];
#endif
struct memblock memblock __initdata_memblock = {
.memory.regions = memblock_memory_init_regions,
.memory.cnt = 1,/* empty dummy entry */
.memory.max = INIT_MEMBLOCK_REGIONS,
.memory.name= "memory",
.reserved.regions = memblock_reserved_init_regions,
.reserved.cnt = 1,/* empty dummy entry */
.reserved.max = INIT_MEMBLOCK_RESERVED_REGIONS,
.reserved.name = "reserved",
.bottom_up = false,
.current_limit = MEMBLOCK_ALLOC_ANYWHERE,
};
And I guess this struct will be filled during early boot and used during
boot. (I saw somewhere the memory regions are later moved to buddy
allocation system for normal use).
My question is : we can speicify "reserved-memory" in the device tree. Some
drivers use the reserved memory for its own use.
Then, are the 'reserved-memory' regions are put into this memblock.reserved
regions during the boot process?(I mean during dtb parsing).
Thank you!
Chan Kim
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Workaround to send patch with git send email and gmail account
On Wed, Jun 22, 2022 at 05:04:26PM +0100, Jules Irenge wrote: > Now that google has disabled less secure app, I would like to know what are > the alternative to send patch when one uses gmail ? > I tried with git-send email but to no avail. Anyone with some workaround on > this please You can still do it if you set 2-factor auth and create an app password. https://support.google.com/mail/answer/185833 -K ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Workaround to send patch with git send email and gmail account
On 6/22/22 18:04, Jules Irenge wrote: Now that google has disabled less secure app, I would like to know what are the alternative to send patch when one uses gmail ? I tried with git-send email but to no avail. Anyone with some workaround on this please Thanks, Jules Hi, I am still using gmail as before. I switched on dual factor authentication and I have an app password for mutt. Then everything is as before. Bye Philipp ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Workaround to send patch with git send email and gmail account
Now that google has disabled less secure app, I would like to know what are the alternative to send patch when one uses gmail ? I tried with git-send email but to no avail. Anyone with some workaround on this please Thanks, Jules *..* ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: When reviewers stop responding
On Wed, Jun 22, 2022 at 06:20:04AM +0200, Philipp Hortmann wrote: > On 6/7/22 19:23, Greg KH wrote: > > And again, please help review code, otherwise you are just asking others > > to do work for you, which if you think about it, could be construed as a > > bit selfish, and I don't think you mean it to be. > > Hi Greg, > > this applies to me. I promise to improve. But this topic is not enough > advertised. Everywhere information about patches can be found. But how to do > a correct Reviewed-by: or Tested-by: is not so good documented. > > I bought hardware to improve and did one "Tested-by:" of the patch: > > [PATCH v2 0/5] Fixed some coding style issues and spelling > from Chang Yu > > https://lore.kernel.org/linux-staging/91c9a0de-76f8-37fb-31b4-4401a6e35...@gmail.com/T/#t > > Did I do something wrong or was I just unlucky? > > Is 24 hours quick enough response? Sometimes, yes, it is. Other times I get to patches quicker than that as I batch them up and process them once or twice a week. You just got unlucky and reviewed it after I had applied the changes, but that was not the case for your other series you reviewed today. thanks for the review, it's always appreciated. greg k-h ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
