Hi Akashi,
On 26/04/18 08:40, AKASHI Takahiro wrote:
> On Wed, Apr 25, 2018 at 02:22:07PM +0100, James Morse wrote:
>> On 25/04/18 10:20, AKASHI Takahiro wrote:
>>> On Tue, Apr 24, 2018 at 05:08:57PM +0100, James Morse wrote:
If we squash the memblock_reserved() stuff down so it appears as a
James,
On Wed, Apr 25, 2018 at 02:22:07PM +0100, James Morse wrote:
> Hi Akashi,
>
> On 25/04/18 10:20, AKASHI Takahiro wrote:
> > On Tue, Apr 24, 2018 at 05:08:57PM +0100, James Morse wrote:
> >> On 16/04/18 11:08, AKASHI Takahiro wrote:
> >>> On Thu, Apr 12, 2018 at 05:01:52PM +0100, James Mors
Hi Akashi,
On 25/04/18 10:20, AKASHI Takahiro wrote:
> On Tue, Apr 24, 2018 at 05:08:57PM +0100, James Morse wrote:
>> On 16/04/18 11:08, AKASHI Takahiro wrote:
>>> On Thu, Apr 12, 2018 at 05:01:52PM +0100, James Morse wrote:
On 05/04/18 03:42, AKASHI Takahiro wrote:
> On Mon, Apr 02, 201
On Tue, Apr 24, 2018 at 05:08:57PM +0100, James Morse wrote:
> Hi Akashi,
>
> On 16/04/18 11:08, AKASHI Takahiro wrote:
> > On Thu, Apr 12, 2018 at 05:01:52PM +0100, James Morse wrote:
> >> On 05/04/18 03:42, AKASHI Takahiro wrote:
> >>> On Mon, Apr 02, 2018 at 10:53:32AM +0900, AKASHI Takahiro wr
Hi Akashi,
On 16/04/18 11:08, AKASHI Takahiro wrote:
> On Thu, Apr 12, 2018 at 05:01:52PM +0100, James Morse wrote:
>> On 05/04/18 03:42, AKASHI Takahiro wrote:
>>> On Mon, Apr 02, 2018 at 10:53:32AM +0900, AKASHI Takahiro wrote:
Basically, changes that I made on /proc/iomem in my new format
On Thu, Apr 12, 2018 at 05:01:52PM +0100, James Morse wrote:
> Hi Akashi,
>
> Sorry I've been sluggish on this issue,
>
> On 05/04/18 03:42, AKASHI Takahiro wrote:
> > On Mon, Apr 02, 2018 at 10:53:32AM +0900, AKASHI Takahiro wrote:
> >> On Tue, Mar 27, 2018 at 02:32:49PM +0100, James Morse wrote
Hi Akashi,
Sorry I've been sluggish on this issue,
On 05/04/18 03:42, AKASHI Takahiro wrote:
> On Mon, Apr 02, 2018 at 10:53:32AM +0900, AKASHI Takahiro wrote:
>> On Tue, Mar 27, 2018 at 02:32:49PM +0100, James Morse wrote:
>>> On 27/03/18 11:16, AKASHI Takahiro wrote:
On Tue, Mar 20, 2018 a
On Mon, Apr 02, 2018 at 10:53:32AM +0900, AKASHI Takahiro wrote:
> James,
>
> My apologies for slow response. I had a long weekend.
>
> On Tue, Mar 27, 2018 at 02:32:49PM +0100, James Morse wrote:
> > Hi Akashi,
> >
> > On 27/03/18 11:16, AKASHI Takahiro wrote:
> > > On Tue, Mar 20, 2018 at 01:1
James,
My apologies for slow response. I had a long weekend.
On Tue, Mar 27, 2018 at 02:32:49PM +0100, James Morse wrote:
> Hi Akashi,
>
> On 27/03/18 11:16, AKASHI Takahiro wrote:
> > On Tue, Mar 20, 2018 at 01:18:34AM +0530, Bhupesh Sharma wrote:
> >> On 03/14/2018 01:59 PM, AKASHI Takahiro wr
Hi Akashi,
On 27/03/18 11:16, AKASHI Takahiro wrote:
> On Tue, Mar 20, 2018 at 01:18:34AM +0530, Bhupesh Sharma wrote:
>> On 03/14/2018 01:59 PM, AKASHI Takahiro wrote:
>>> Currently, there is a inconsistent view between (A) and the mainline's:
>>> see (A-1) and (B-1). If this is really a matter,
Ard, Bhupesh,
Thank you for your comments.
On Tue, Mar 20, 2018 at 01:18:34AM +0530, Bhupesh Sharma wrote:
> On 03/14/2018 01:59 PM, AKASHI Takahiro wrote:
> >In the last couples of months, there were some problems reported [1],[2]
> >around arm64 kexec/kdump. Where those phenomenon look differen
On 03/14/2018 01:59 PM, AKASHI Takahiro wrote:
In the last couples of months, there were some problems reported [1],[2]
around arm64 kexec/kdump. Where those phenomenon look different,
the root cause would be that kexec/kdump doesn't take into account
crucial "reserved" regions of system memory a
On 15 March 2018 at 04:41, AKASHI Takahiro wrote:
> On Wed, Mar 14, 2018 at 08:39:23AM +, Ard Biesheuvel wrote:
>> On 14 March 2018 at 08:29, AKASHI Takahiro
>> wrote:
>> > In the last couples of months, there were some problems reported [1],[2]
>> > around arm64 kexec/kdump. Where those phe
On Wed, Mar 14, 2018 at 08:39:23AM +, Ard Biesheuvel wrote:
> On 14 March 2018 at 08:29, AKASHI Takahiro wrote:
> > In the last couples of months, there were some problems reported [1],[2]
> > around arm64 kexec/kdump. Where those phenomenon look different,
> > the root cause would be that kex
On 14 March 2018 at 08:29, AKASHI Takahiro wrote:
> In the last couples of months, there were some problems reported [1],[2]
> around arm64 kexec/kdump. Where those phenomenon look different,
> the root cause would be that kexec/kdump doesn't take into account
> crucial "reserved" regions of syste
15 matches
Mail list logo