All of lore.kernel.org
 help / color / mirror / Atom feed
From: wangkefeng.wang@huawei.com (Kefeng Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: mm: dump: Use VA_START directly instead of private LOWEST_ADDR
Date: Sun, 14 Feb 2016 16:57:18 +0800	[thread overview]
Message-ID: <56C0416E.6050908@huawei.com> (raw)
In-Reply-To: <20160201102345.GB674@leverpostej>

Hi Catalin and Will,  ping...

On 2016/2/1 18:23, Mark Rutland wrote:
> On Sat, Jan 30, 2016 at 03:55:21PM +0800, Kefeng Wang wrote:
>> Use VA_START macro in asm/memory.h instead of private LOWEST_ADDR
>> definition in dump.c.
>>
>> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> 
> FWIW:
> 
> Acked-by: Mark Rutland <mark.rutland@arm.com>
> 
> Mark.
> 
>> ---
>>  arch/arm64/mm/dump.c | 4 +---
>>  1 file changed, 1 insertion(+), 3 deletions(-)
>>
>> diff --git a/arch/arm64/mm/dump.c b/arch/arm64/mm/dump.c
>> index 0adbebb..b3c62b1 100644
>> --- a/arch/arm64/mm/dump.c
>> +++ b/arch/arm64/mm/dump.c
>> @@ -27,8 +27,6 @@
>>  #include <asm/pgtable.h>
>>  #include <asm/pgtable-hwdef.h>
>>  
>> -#define LOWEST_ADDR	(UL(0xffffffffffffffff) << VA_BITS)
>> -
>>  struct addr_marker {
>>  	unsigned long start_address;
>>  	const char *name;
>> @@ -316,7 +314,7 @@ static int ptdump_show(struct seq_file *m, void *v)
>>  		.marker = address_markers,
>>  	};
>>  
>> -	walk_pgd(&st, &init_mm, LOWEST_ADDR);
>> +	walk_pgd(&st, &init_mm, VA_START);
>>  
>>  	note_page(&st, 0, 0, 0);
>>  	return 0;
>> -- 
>> 2.6.0.GIT
>>
>>
>> _______________________________________________
>> linux-arm-kernel mailing list
>> linux-arm-kernel at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>>
> 
> .
> 

  reply	other threads:[~2016-02-14  8:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-30  7:55 [PATCH] arm64: mm: dump: Use VA_START directly instead of private LOWEST_ADDR Kefeng Wang
2016-02-01 10:23 ` Mark Rutland
2016-02-14  8:57   ` Kefeng Wang [this message]
2016-02-15 10:09     ` Catalin Marinas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56C0416E.6050908@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.