public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Alexander Kuleshov <kuleshovmail@gmail.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Michael Holzheu <holzheu@linux.vnet.ibm.com>,
	Tony Luck <tony.luck@intel.com>,
	David Hildenbrand <dahi@linux.vnet.ibm.com>,
	linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] s390/crash_dump: Use PFN_PHYS and PFN_DOWN macros
Date: Fri, 18 Sep 2015 13:19:28 +0200	[thread overview]
Message-ID: <20150918111928.GB3986@osiris> (raw)
In-Reply-To: <1442343278-10641-1-git-send-email-kuleshovmail@gmail.com>

On Wed, Sep 16, 2015 at 12:54:38AM +0600, Alexander Kuleshov wrote:
> The <linux/pfn.h> provides PFN_PHYS and PFN_DOWN macros for the
> getting page frame number and physical address of a page frame number.
> This patch replaces (pfn << PAGE_SHIFT) and (addr >> PAGE_SHIFT)
> expressions with the PFN_PHYS and PFN_DOWN macros.
> 
> Signed-off-by: Alexander Kuleshov <kuleshovmail@gmail.com>
> ---
>  arch/s390/kernel/crash_dump.c | 18 ++++++++++--------
>  1 file changed, 10 insertions(+), 8 deletions(-)
> 
> diff --git a/arch/s390/kernel/crash_dump.c b/arch/s390/kernel/crash_dump.c
> index 1e4fcfa..f8da32c 100644
> --- a/arch/s390/kernel/crash_dump.c
> +++ b/arch/s390/kernel/crash_dump.c
> @@ -136,7 +136,7 @@ ssize_t copy_oldmem_page(unsigned long pfn, char *buf, size_t csize,
> 
>  	if (!csize)
>  		return 0;
> -	src = (pfn << PAGE_SHIFT) + offset;
> +	src = (PFN_PHYS(pfn)) + offset;
>  	if (OLDMEM_BASE)
>  		return copy_oldmem_page_kdump(buf, csize, src, userbuf);
>  	else
> @@ -156,16 +156,17 @@ static int remap_oldmem_pfn_range_kdump(struct vm_area_struct *vma,
>  	unsigned long size_old;
>  	int rc;
> 
> -	if (pfn < OLDMEM_SIZE >> PAGE_SHIFT) {
> -		size_old = min(size, OLDMEM_SIZE - (pfn << PAGE_SHIFT));
> +	if (pfn < PFN_DOWN(OLDMEM_SIZE)) {
> +		size_old = min(size,
> +			OLDMEM_SIZE - (unsigned long)(PFN_PHYS(pfn)));

Cleanup patches like this are supposed to increase readability. That's
certainly not the case here.
Therefore I'm not applying this one.

Thanks,
Heiko


      reply	other threads:[~2015-09-18 11:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15 18:54 [PATCH 2/2] s390/crash_dump: Use PFN_PHYS and PFN_DOWN macros Alexander Kuleshov
2015-09-18 11:19 ` Heiko Carstens [this message]

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=20150918111928.GB3986@osiris \
    --to=heiko.carstens@de.ibm.com \
    --cc=dahi@linux.vnet.ibm.com \
    --cc=holzheu@linux.vnet.ibm.com \
    --cc=kuleshovmail@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=tony.luck@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox