All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Lianbo Jiang <lijiang@redhat.com>
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
	tglx@linutronix.de, mingo@redhat.com, akpm@linux-foundation.org,
	dave.hansen@linux.intel.com, luto@kernel.org,
	peterz@infradead.org, x86@kernel.org, hpa@zytor.com,
	dyoung@redhat.com, bhe@redhat.com, Thomas.Lendacky@amd.com
Subject: Re: [PATCH 1/2 v10] x86/mm, resource: add a new I/O resource descriptor 'IORES_DESC_RESERVED'
Date: Fri, 29 Mar 2019 11:39:58 +0100	[thread overview]
Message-ID: <20190329103958.GC21152@zn.tnic> (raw)
In-Reply-To: <20190329065649.12468-2-lijiang@redhat.com>

On Fri, Mar 29, 2019 at 02:56:48PM +0800, Lianbo Jiang wrote:
> When doing kexec_file_load(), the first kernel needs to pass the e820
> reserved ranges to the second kernel, because some devices may use it
> in kdump kernel, such as PCI devices.
> 
> But, the kernel can not exactly match the e820 reserved ranges when
> walking through the iomem resources via the 'IORES_DESC_NONE', because
> there are several types of e820 that are described as the 'IORES_DESC_NONE'
> type. Please refer to the e820_type_to_iores_desc().
> 
> Therefore, add a new I/O resource descriptor 'IORES_DESC_RESERVED' for
> the iomem resources search interfaces. It is helpful to exactly match
> the reserved resource ranges when walking through iomem resources.
> 
> In addition, since the new descriptor 'IORES_DESC_RESERVED' has been
> created for the reserved areas, the code originally related to the
> descriptor 'IORES_DESC_NONE' also need to be updated.
> 
> Suggested-by: Borislav Petkov <bp@suse.de>
> Signed-off-by: Lianbo Jiang <lijiang@redhat.com>
> ---
>  arch/x86/kernel/e820.c |  2 +-
>  arch/x86/mm/ioremap.c  | 16 ++++++++++++++--
>  include/linux/ioport.h |  1 +
>  3 files changed, 16 insertions(+), 3 deletions(-)
> 
> diff --git a/arch/x86/kernel/e820.c b/arch/x86/kernel/e820.c
> index 2879e234e193..16fcde196243 100644
> --- a/arch/x86/kernel/e820.c
> +++ b/arch/x86/kernel/e820.c
> @@ -1050,10 +1050,10 @@ static unsigned long __init e820_type_to_iores_desc(struct e820_entry *entry)
>  	case E820_TYPE_NVS:		return IORES_DESC_ACPI_NV_STORAGE;
>  	case E820_TYPE_PMEM:		return IORES_DESC_PERSISTENT_MEMORY;
>  	case E820_TYPE_PRAM:		return IORES_DESC_PERSISTENT_MEMORY_LEGACY;
> +	case E820_TYPE_RESERVED:	return IORES_DESC_RESERVED;
>  	case E820_TYPE_RESERVED_KERN:	/* Fall-through: */
>  	case E820_TYPE_RAM:		/* Fall-through: */
>  	case E820_TYPE_UNUSABLE:	/* Fall-through: */
> -	case E820_TYPE_RESERVED:	/* Fall-through: */
>  	default:			return IORES_DESC_NONE;
>  	}
>  }
> diff --git a/arch/x86/mm/ioremap.c b/arch/x86/mm/ioremap.c
> index 0029604af8a4..5671ec24df49 100644
> --- a/arch/x86/mm/ioremap.c
> +++ b/arch/x86/mm/ioremap.c
> @@ -81,9 +81,21 @@ static bool __ioremap_check_ram(struct resource *res)
>  	return false;
>  }
>  
> -static int __ioremap_check_desc_other(struct resource *res)

I can see this patch doesn't build even without applying and building
it.

How about you build-test your stuff before submitting?

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: Lianbo Jiang <lijiang@redhat.com>
Cc: Thomas.Lendacky@amd.com, x86@kernel.org, bhe@redhat.com,
	peterz@infradead.org, dave.hansen@linux.intel.com,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	mingo@redhat.com, luto@kernel.org, hpa@zytor.com,
	tglx@linutronix.de, dyoung@redhat.com, akpm@linux-foundation.org
Subject: Re: [PATCH 1/2 v10] x86/mm, resource: add a new I/O resource descriptor 'IORES_DESC_RESERVED'
Date: Fri, 29 Mar 2019 11:39:58 +0100	[thread overview]
Message-ID: <20190329103958.GC21152@zn.tnic> (raw)
In-Reply-To: <20190329065649.12468-2-lijiang@redhat.com>

On Fri, Mar 29, 2019 at 02:56:48PM +0800, Lianbo Jiang wrote:
> When doing kexec_file_load(), the first kernel needs to pass the e820
> reserved ranges to the second kernel, because some devices may use it
> in kdump kernel, such as PCI devices.
> 
> But, the kernel can not exactly match the e820 reserved ranges when
> walking through the iomem resources via the 'IORES_DESC_NONE', because
> there are several types of e820 that are described as the 'IORES_DESC_NONE'
> type. Please refer to the e820_type_to_iores_desc().
> 
> Therefore, add a new I/O resource descriptor 'IORES_DESC_RESERVED' for
> the iomem resources search interfaces. It is helpful to exactly match
> the reserved resource ranges when walking through iomem resources.
> 
> In addition, since the new descriptor 'IORES_DESC_RESERVED' has been
> created for the reserved areas, the code originally related to the
> descriptor 'IORES_DESC_NONE' also need to be updated.
> 
> Suggested-by: Borislav Petkov <bp@suse.de>
> Signed-off-by: Lianbo Jiang <lijiang@redhat.com>
> ---
>  arch/x86/kernel/e820.c |  2 +-
>  arch/x86/mm/ioremap.c  | 16 ++++++++++++++--
>  include/linux/ioport.h |  1 +
>  3 files changed, 16 insertions(+), 3 deletions(-)
> 
> diff --git a/arch/x86/kernel/e820.c b/arch/x86/kernel/e820.c
> index 2879e234e193..16fcde196243 100644
> --- a/arch/x86/kernel/e820.c
> +++ b/arch/x86/kernel/e820.c
> @@ -1050,10 +1050,10 @@ static unsigned long __init e820_type_to_iores_desc(struct e820_entry *entry)
>  	case E820_TYPE_NVS:		return IORES_DESC_ACPI_NV_STORAGE;
>  	case E820_TYPE_PMEM:		return IORES_DESC_PERSISTENT_MEMORY;
>  	case E820_TYPE_PRAM:		return IORES_DESC_PERSISTENT_MEMORY_LEGACY;
> +	case E820_TYPE_RESERVED:	return IORES_DESC_RESERVED;
>  	case E820_TYPE_RESERVED_KERN:	/* Fall-through: */
>  	case E820_TYPE_RAM:		/* Fall-through: */
>  	case E820_TYPE_UNUSABLE:	/* Fall-through: */
> -	case E820_TYPE_RESERVED:	/* Fall-through: */
>  	default:			return IORES_DESC_NONE;
>  	}
>  }
> diff --git a/arch/x86/mm/ioremap.c b/arch/x86/mm/ioremap.c
> index 0029604af8a4..5671ec24df49 100644
> --- a/arch/x86/mm/ioremap.c
> +++ b/arch/x86/mm/ioremap.c
> @@ -81,9 +81,21 @@ static bool __ioremap_check_ram(struct resource *res)
>  	return false;
>  }
>  
> -static int __ioremap_check_desc_other(struct resource *res)

I can see this patch doesn't build even without applying and building
it.

How about you build-test your stuff before submitting?

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2019-03-29 10:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29  6:56 [PATCH 0/2 v10] add reserved e820 ranges to the kdump kernel e820 table Lianbo Jiang
2019-03-29  6:56 ` Lianbo Jiang
2019-03-29  6:56 ` [PATCH 1/2 v10] x86/mm, resource: add a new I/O resource descriptor 'IORES_DESC_RESERVED' Lianbo Jiang
2019-03-29  6:56   ` Lianbo Jiang
2019-03-29 10:39   ` Borislav Petkov [this message]
2019-03-29 10:39     ` Borislav Petkov
2019-03-29 11:41     ` lijiang
2019-03-29 11:41       ` lijiang
2019-03-29  6:56 ` [PATCH 2/2 v10] x86/kexec_file: add reserved e820 ranges to kdump kernel e820 table Lianbo Jiang
2019-03-29  6:56   ` Lianbo Jiang

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=20190329103958.GC21152@zn.tnic \
    --to=bp@alien8.de \
    --cc=Thomas.Lendacky@amd.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=dyoung@redhat.com \
    --cc=hpa@zytor.com \
    --cc=kexec@lists.infradead.org \
    --cc=lijiang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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.