On Tue, Jan 9, 2018 at 10:12 AM, AKASHI Takahiro
wrote:
> Bhupesh,
>
> On Tue, Jan 09, 2018 at 01:30:07AM +0530, Bhupesh Sharma wrote:
>> Hello Akashi,
>>
>> On Tue, Dec 26, 2017 at 8:26 AM, Bhupesh Sharma wrote:
>> > On Tue, Dec 26, 2017 at 7:58
On Tue, Dec 26, 2017 at 02:58:45PM +0800, Dave Young wrote:
> On 12/26/17 at 08:26am, Bhupesh Sharma wrote:
> > On Tue, Dec 26, 2017 at 7:58 AM, AKASHI Takahiro
> > wrote:
> > > On Tue, Dec 26, 2017 at 09:35:17AM +0800, Dave Young wrote:
> > >> [snip]
> > >> > > >
On Tue, Dec 26, 2017 at 02:56:36PM +0800, Dave Young wrote:
> On 12/26/17 at 11:28am, AKASHI Takahiro wrote:
> > On Tue, Dec 26, 2017 at 09:35:17AM +0800, Dave Young wrote:
> > > [snip]
> > > > > > Well, we may be able to change pr_warn() to pr_warn_once() here, but
> > > > > > I hope that adding
Bhupesh,
On Tue, Jan 09, 2018 at 01:30:07AM +0530, Bhupesh Sharma wrote:
> Hello Akashi,
>
> On Tue, Dec 26, 2017 at 8:26 AM, Bhupesh Sharma wrote:
> > On Tue, Dec 26, 2017 at 7:58 AM, AKASHI Takahiro
> > wrote:
> >> On Tue, Dec 26, 2017 at
Hello Akashi,
On Tue, Dec 26, 2017 at 8:26 AM, Bhupesh Sharma wrote:
> On Tue, Dec 26, 2017 at 7:58 AM, AKASHI Takahiro
> wrote:
>> On Tue, Dec 26, 2017 at 09:35:17AM +0800, Dave Young wrote:
>>> [snip]
>>> > > > Well, we may be able to change
On 12/26/17 at 08:26am, Bhupesh Sharma wrote:
> On Tue, Dec 26, 2017 at 7:58 AM, AKASHI Takahiro
> wrote:
> > On Tue, Dec 26, 2017 at 09:35:17AM +0800, Dave Young wrote:
> >> [snip]
> >> > > > Well, we may be able to change pr_warn() to pr_warn_once() here, but
> >> >
On 12/26/17 at 11:28am, AKASHI Takahiro wrote:
> On Tue, Dec 26, 2017 at 09:35:17AM +0800, Dave Young wrote:
> > [snip]
> > > > > Well, we may be able to change pr_warn() to pr_warn_once() here, but
> > > > > I hope that adding "numa=off" to kernel command line should also work.
> > > >
> > > >
On Tue, Dec 26, 2017 at 7:58 AM, AKASHI Takahiro
wrote:
> On Tue, Dec 26, 2017 at 09:35:17AM +0800, Dave Young wrote:
>> [snip]
>> > > > Well, we may be able to change pr_warn() to pr_warn_once() here, but
>> > > > I hope that adding "numa=off" to kernel command line
On Tue, Dec 26, 2017 at 09:35:17AM +0800, Dave Young wrote:
> [snip]
> > > > Well, we may be able to change pr_warn() to pr_warn_once() here, but
> > > > I hope that adding "numa=off" to kernel command line should also work.
> > >
> > > Hmm, adding "numa=off" to crashkernel bootargs works, and
[snip]
> > > Well, we may be able to change pr_warn() to pr_warn_once() here, but
> > > I hope that adding "numa=off" to kernel command line should also work.
> >
> > Hmm, adding "numa=off" to crashkernel bootargs works, and TBH it was
> > my initial thought process as well, but I am not sure if
On 12/26/17 at 01:44am, Bhupesh Sharma wrote:
> On Mon, Dec 25, 2017 at 8:55 AM, AKASHI Takahiro
> wrote:
> > On Sun, Dec 24, 2017 at 01:21:02AM +0530, Bhupesh Sharma wrote:
> >> On Fri, Dec 22, 2017 at 2:03 PM, AKASHI Takahiro
> >> wrote:
On Mon, Dec 25, 2017 at 8:55 AM, AKASHI Takahiro
wrote:
> On Sun, Dec 24, 2017 at 01:21:02AM +0530, Bhupesh Sharma wrote:
>> On Fri, Dec 22, 2017 at 2:03 PM, AKASHI Takahiro
>> wrote:
>> > On Thu, Dec 21, 2017 at 05:36:30PM +0530, Bhupesh
On Sun, Dec 24, 2017 at 01:21:02AM +0530, Bhupesh Sharma wrote:
> On Fri, Dec 22, 2017 at 2:03 PM, AKASHI Takahiro
> wrote:
> > On Thu, Dec 21, 2017 at 05:36:30PM +0530, Bhupesh Sharma wrote:
> >> Hello Akashi,
> >>
> >> On Thu, Dec 21, 2017 at 4:04 PM, AKASHI Takahiro
On Fri, Dec 22, 2017 at 2:03 PM, AKASHI Takahiro
wrote:
> On Thu, Dec 21, 2017 at 05:36:30PM +0530, Bhupesh Sharma wrote:
>> Hello Akashi,
>>
>> On Thu, Dec 21, 2017 at 4:04 PM, AKASHI Takahiro
>> wrote:
>> > Bhupesh,
>> >
>> > Can you test
On Thu, Dec 21, 2017 at 05:36:30PM +0530, Bhupesh Sharma wrote:
> Hello Akashi,
>
> On Thu, Dec 21, 2017 at 4:04 PM, AKASHI Takahiro
> wrote:
> > Bhupesh,
> >
> > Can you test the patch attached below, please?
> >
> > It is intended to retain already-reserved regions
Hello Akashi,
On Thu, Dec 21, 2017 at 4:04 PM, AKASHI Takahiro
wrote:
> Bhupesh,
>
> Can you test the patch attached below, please?
>
> It is intended to retain already-reserved regions (ACPI reclaim memory
> in this case) in system ram (i.e. memblock.memory) without
Bhupesh,
Can you test the patch attached below, please?
It is intended to retain already-reserved regions (ACPI reclaim memory
in this case) in system ram (i.e. memblock.memory) without explicitly
exporting them via usable-memory-range.
(I still have to figure out what the side-effect of this
On Tue, Dec 19, 2017 at 6:39 PM, Ard Biesheuvel
wrote:
> On 19 December 2017 at 07:09, AKASHI Takahiro
> wrote:
>> On Mon, Dec 18, 2017 at 01:40:09PM +0800, Dave Young wrote:
>>> On 12/15/17 at 05:59pm, AKASHI Takahiro wrote:
>>> > On Wed,
On Tue, Dec 19, 2017 at 10:31 AM, AKASHI Takahiro
wrote:
> On Mon, Dec 18, 2017 at 02:29:05PM +0530, Bhupesh SHARMA wrote:
>>
>> [snip..]
>>
>> [0.00] linux,usable-memory-range base e80, size 2000
>> [0.00] - e80 , 2000
>> [
On 19 December 2017 at 07:09, AKASHI Takahiro
wrote:
> On Mon, Dec 18, 2017 at 01:40:09PM +0800, Dave Young wrote:
>> On 12/15/17 at 05:59pm, AKASHI Takahiro wrote:
>> > On Wed, Dec 13, 2017 at 12:17:22PM +, Ard Biesheuvel wrote:
>> > > On 13 December 2017 at
On Mon, Dec 18, 2017 at 01:40:09PM +0800, Dave Young wrote:
> On 12/15/17 at 05:59pm, AKASHI Takahiro wrote:
> > On Wed, Dec 13, 2017 at 12:17:22PM +, Ard Biesheuvel wrote:
> > > On 13 December 2017 at 12:16, AKASHI Takahiro
> > > wrote:
> > > > On Wed, Dec 13,
On Tue, Dec 19, 2017 at 02:58:20AM +0530, Bhupesh Sharma wrote:
> Hi Dave,
>
> On Mon, Dec 18, 2017 at 10:46 AM, Dave Young wrote:
> > kexec@fedoraproject... is for Fedora kexec scripts discussion, changed it
> > to ke...@lists.infradead.org
> >
> > Also add linux-acpi list
>
On Mon, Dec 18, 2017 at 02:29:05PM +0530, Bhupesh SHARMA wrote:
>
> [snip..]
>
> [0.00] linux,usable-memory-range base e80, size 2000
> [0.00] - e80 , 2000
> [0.00] linux,usable-memory-range base 396c, size a
> [0.00] - 396c , a
On Mon, Dec 18, 2017 at 4:48 PM, AKASHI Takahiro
wrote:
> Bhupesh,
>
> On Mon, Dec 18, 2017 at 02:29:05PM +0530, Bhupesh SHARMA wrote:
>> On Mon, Dec 18, 2017 at 11:24 AM, AKASHI Takahiro
>> wrote:
>> > On Mon, Dec 18, 2017 at 01:16:57PM
Hi Dave,
On Mon, Dec 18, 2017 at 10:46 AM, Dave Young wrote:
> kexec@fedoraproject... is for Fedora kexec scripts discussion, changed it
> to ke...@lists.infradead.org
>
> Also add linux-acpi list
> On 12/18/17 at 02:31am, Bhupesh Sharma wrote:
>> On Fri, Dec 15, 2017 at 3:05
Bhupesh,
On Mon, Dec 18, 2017 at 02:29:05PM +0530, Bhupesh SHARMA wrote:
> On Mon, Dec 18, 2017 at 11:24 AM, AKASHI Takahiro
> wrote:
> > On Mon, Dec 18, 2017 at 01:16:57PM +0800, Dave Young wrote:
> >> kexec@fedoraproject... is for Fedora kexec scripts discussion,
On Mon, Dec 18, 2017 at 11:24 AM, AKASHI Takahiro
wrote:
> On Mon, Dec 18, 2017 at 01:16:57PM +0800, Dave Young wrote:
>> kexec@fedoraproject... is for Fedora kexec scripts discussion, changed it
>> to ke...@lists.infradead.org
>>
>> Also add linux-acpi list
>
> Thank
On Mon, Dec 18, 2017 at 01:16:57PM +0800, Dave Young wrote:
> kexec@fedoraproject... is for Fedora kexec scripts discussion, changed it
> to ke...@lists.infradead.org
>
> Also add linux-acpi list
Thank you.
> On 12/18/17 at 02:31am, Bhupesh Sharma wrote:
> > On Fri, Dec 15, 2017 at 3:05 PM, Ard
Fix the kexec list address.
On 12/18/17 at 01:40pm, Dave Young wrote:
> On 12/15/17 at 05:59pm, AKASHI Takahiro wrote:
> > On Wed, Dec 13, 2017 at 12:17:22PM +, Ard Biesheuvel wrote:
> > > On 13 December 2017 at 12:16, AKASHI Takahiro
> > > wrote:
> > > > On Wed,
On 12/15/17 at 05:59pm, AKASHI Takahiro wrote:
> On Wed, Dec 13, 2017 at 12:17:22PM +, Ard Biesheuvel wrote:
> > On 13 December 2017 at 12:16, AKASHI Takahiro
> > wrote:
> > > On Wed, Dec 13, 2017 at 10:49:27AM +, Ard Biesheuvel wrote:
> > >> On 13 December
kexec@fedoraproject... is for Fedora kexec scripts discussion, changed it
to ke...@lists.infradead.org
Also add linux-acpi list
On 12/18/17 at 02:31am, Bhupesh Sharma wrote:
> On Fri, Dec 15, 2017 at 3:05 PM, Ard Biesheuvel
> wrote:
> > On 15 December 2017 at 09:59,
On Fri, Dec 15, 2017 at 3:05 PM, Ard Biesheuvel
wrote:
> On 15 December 2017 at 09:59, AKASHI Takahiro
> wrote:
>> On Wed, Dec 13, 2017 at 12:17:22PM +, Ard Biesheuvel wrote:
>>> On 13 December 2017 at 12:16, AKASHI Takahiro
>>>
On 15 December 2017 at 09:59, AKASHI Takahiro
wrote:
> On Wed, Dec 13, 2017 at 12:17:22PM +, Ard Biesheuvel wrote:
>> On 13 December 2017 at 12:16, AKASHI Takahiro
>> wrote:
>> > On Wed, Dec 13, 2017 at 10:49:27AM +, Ard Biesheuvel
On Wed, Dec 13, 2017 at 12:17:22PM +, Ard Biesheuvel wrote:
> On 13 December 2017 at 12:16, AKASHI Takahiro
> wrote:
> > On Wed, Dec 13, 2017 at 10:49:27AM +, Ard Biesheuvel wrote:
> >> On 13 December 2017 at 10:26, AKASHI Takahiro
> >>
Hi Ard, Akashi,
On Wed, Dec 13, 2017 at 5:47 PM, Ard Biesheuvel
wrote:
> On 13 December 2017 at 12:16, AKASHI Takahiro
> wrote:
>> On Wed, Dec 13, 2017 at 10:49:27AM +, Ard Biesheuvel wrote:
>>> On 13 December 2017 at 10:26, AKASHI
On 13 December 2017 at 12:16, AKASHI Takahiro
wrote:
> On Wed, Dec 13, 2017 at 10:49:27AM +, Ard Biesheuvel wrote:
>> On 13 December 2017 at 10:26, AKASHI Takahiro
>> wrote:
>> > Bhupesh, Ard,
>> >
>> > On Wed, Dec 13, 2017 at
On Wed, Dec 13, 2017 at 10:49:27AM +, Ard Biesheuvel wrote:
> On 13 December 2017 at 10:26, AKASHI Takahiro
> wrote:
> > Bhupesh, Ard,
> >
> > On Wed, Dec 13, 2017 at 03:21:59AM +0530, Bhupesh Sharma wrote:
> >> Hi Ard, Akashi
> >>
> > (snip)
> >
> >> Looking
On 13 December 2017 at 10:26, AKASHI Takahiro
wrote:
> Bhupesh, Ard,
>
> On Wed, Dec 13, 2017 at 03:21:59AM +0530, Bhupesh Sharma wrote:
>> Hi Ard, Akashi
>>
> (snip)
>
>> Looking deeper into the issue, since the arm64 kexec-tools uses the
>>
Bhupesh, Ard,
On Wed, Dec 13, 2017 at 03:21:59AM +0530, Bhupesh Sharma wrote:
> Hi Ard, Akashi
>
(snip)
> Looking deeper into the issue, since the arm64 kexec-tools uses the
> 'linux,usable-memory-range' dt property to allow crash dump kernel to
> identify its own usable memory and exclude, at
Hi Ard, Akashi
On Mon, Dec 4, 2017 at 7:32 PM, Ard Biesheuvel
wrote:
> On 26 November 2017 at 08:29, Bhupesh SHARMA wrote:
>> Hi Akashi,
>>
>> On Thu, Nov 16, 2017 at 12:30 PM, AKASHI Takahiro
>> wrote:
>>>
[snip]
> > diff --git a/arch/arm64/kernel/setup.c b/arch/arm64/kernel/setup.c
> > index 7768423b39d3..61d867647cca 100644
> > --- a/arch/arm64/kernel/setup.c
> > +++ b/arch/arm64/kernel/setup.c
> > @@ -213,7 +213,7 @@ static void __init request_standard_resources(void)
> >
> >
Bhupesh,
On Wed, Nov 15, 2017 at 04:28:55PM +0530, Bhupesh Sharma wrote:
>
(snip)
> # dmesg | grep -B 2 -i "ACPI reclaim"
> [0.00] efi: 0x3967-0x396b [Runtime Code |RUN| |
> | | | | | |WB|WT|WC|UC]
> [0.00] efi: 0x396c-0x3970 [Boot
Hi Ard, Akashi,
On 11/14/2017 04:50 PM, Ard Biesheuvel wrote:
On 13 November 2017 at 09:27, AKASHI Takahiro
wrote:
Hi,
On Fri, Nov 10, 2017 at 05:41:56PM +0530, Bhupesh Sharma wrote:
Resent with Akashi's correct email address.
On Fri, Nov 10, 2017 at 5:39 PM,
On 13 November 2017 at 09:27, AKASHI Takahiro
wrote:
> Hi,
>
> On Fri, Nov 10, 2017 at 05:41:56PM +0530, Bhupesh Sharma wrote:
>> Resent with Akashi's correct email address.
>>
>> On Fri, Nov 10, 2017 at 5:39 PM, Bhupesh Sharma wrote:
>> > Hi Ard,
Hi,
On Fri, Nov 10, 2017 at 05:41:56PM +0530, Bhupesh Sharma wrote:
> Resent with Akashi's correct email address.
>
> On Fri, Nov 10, 2017 at 5:39 PM, Bhupesh Sharma wrote:
> > Hi Ard, Akashi
> >
> > I have met an issue on an arm64 board using the latest master branch from
Resent with Akashi's correct email address.
On Fri, Nov 10, 2017 at 5:39 PM, Bhupesh Sharma wrote:
> Hi Ard, Akashi
>
> I have met an issue on an arm64 board using the latest master branch from
> Linus.
>
> I think I have a dirty hack to avoid the issue, but would want more
Hi Ard, Akashi
I have met an issue on an arm64 board using the latest master branch from Linus.
I think I have a dirty hack to avoid the issue, but would want more
opinions from you as it might break crashkernel dump on other arm64
machines.
1. This arm64 machine supports acpi only boot mode
47 matches
Mail list logo