Hi Bhupesh,
-Original Message-
> > Hopefully I'd like to release the next version of makedumpfile next week.
> >
> > So I'm going to merge the modified 1/3 patch and your 2/3 patch separately
> > from 3/3, I think it can use "MAX_PHYSMEM_BITS" and reduce
> > distribution-specific
> >
Hi Kazu,
On Wed, Nov 11, 2020 at 6:05 AM HAGIO KAZUHITO(萩尾 一仁)
wrote:
>
> Hi Bhupesh,
>
> -Original Message-
> > Hi Bhupesh,
> >
> > sorry for my scattered comments.
> >
> > As for 1/3 and 2/3, I think we can merge them separately with 3/3, right?
> > so if you can ack the updated 1/3 I
Hi Bhupesh,
-Original Message-
> Hi Bhupesh,
>
> sorry for my scattered comments.
>
> As for 1/3 and 2/3, I think we can merge them separately with 3/3, right?
> so if you can ack the updated 1/3 I sent, I will merge them first.
> Could you check it?
Hopefully I'd like to release the
Hi Bhupesh,
sorry for my scattered comments.
As for 1/3 and 2/3, I think we can merge them separately with 3/3, right?
so if you can ack the updated 1/3 I sent, I will merge them first.
Could you check it?
As for 3/3, you introduced a couple of new ways, so I'd like to discuss
whether there is
Changes since v4:
- v4 can be seen here:
https://www.spinics.net/lists/kexec/msg23850.html
- Removed the patch (via [PATCH 4/4] in v3) which marked '--mem-usage'
option as unsupported for arm64 architecture, as we now have a mechanism
to read the 'vabits_actual' value from
