On Thu, Oct 28, 2021 at 1:25 PM HAGIO KAZUHITO(萩尾 一仁)
<k-hagio-ab(a)nec.com> wrote:
-----Original Message-----
> On Wed, Oct 27, 2021 at 11:17 AM HAGIO KAZUHITO(萩尾 一仁) <k-hagio-ab(a)nec.com
<mailto:k-hagio-ab@nec.com>
> > wrote:
>
>
> Hi Pingfan, Lianbo,
>
> -----Original Message-----
> > On Mon, Oct 25, 2021 at 4:43 PM HAGIO KAZUHITO(萩尾 一仁)
> > <k-hagio-ab(a)nec.com <mailto:k-hagio-ab@nec.com> > wrote:
> > >
> > > Hi,
> > >
> > > Here is a patch for the issue reported by Ankur.
> > > Could you help test this with your ramdumps and arm64 machines?
> > >
> > The patch looks good to me. And I will schedule a machine to have a
test.
>
> Pingfan, thank you for the check and test, it's very helpful.
>
> Ankur told me that the patch was working fine.
>
> Lianbo, my understanding is that to get a raw ramdump, hardware functionality
>
>
>
> I mean that the raw dumpfile had been generated on my machine, but it didn't
reproduce
> this issue. :-)
oh ok, I misread your email.. Thanks for the test and ack.
Besides, this patch also works fine on dump core which has
vmcore_info. Hence no regression.