Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1190363

Re: [PATCH v2] Do not reserve crashkernel high memory if crashkernel low memory reserving failed

From Yinghai Lu <yinghai@kernel.org>
Newsgroups linux.kernel
Subject Re: [PATCH v2] Do not reserve crashkernel high memory if crashkernel low memory reserving failed
Date 2015-07-23 01:50 +0200
Message-ID <pPbVU-6bx-3@gated-at.bofh.it> (permalink)
References (3 earlier) <pOAD0-249-7@gated-at.bofh.it> <pOB63-2Rd-21@gated-at.bofh.it> <pOBz5-3p0-17@gated-at.bofh.it> <pOLoL-JK-43@gated-at.bofh.it> <pOZi2-3RO-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Wed, Jul 22, 2015 at 3:11 AM, Joerg Roedel <joro@8bytes.org> wrote:
> On Tue, Jul 21, 2015 at 12:22:53PM -0700, Yinghai Lu wrote:
>> On Tue, Jul 21, 2015 at 1:58 AM, Baoquan He <bhe@redhat.com> wrote:
>>
>> > Maybe system which don't need low memory is rare, only for testing?
>>
>> No, it is not rare.
>>
>> All recent intel based systems with iommu support does not need low.
>
> All Intel-IOMMU systems have the iommu disabled by default (at least
> that is the default in most distros). So low memory is definitly needed
> by those systems too.

Do those systems need crashkernel=,high?

Do you mean BIOS have that disabled with not exposing DMAR table ?

kernel for RHEL 6 and RHEL7 have them enabled.
Also opensuse kernel have that enabled too.


>
>> that reserve 256M low always. and those 256M get wasted.
>>
>> That commit should only be used to workaround some systems that
>> have partial iommu support.
>
> We currently lack the infrastructure for that, but I am happy to review
> patches. How about letting subsystems announce their need for low
> crash-kernel memory and allocate based on that?
>
> The subsystems (like iommu or swiotlb code, for example) could even
> announce how much memory they need and we base our allocation on that.

That would be hard, as we don't know if second kernel could take what
kernel parameters.
user could disable iommu etc from command kernel for second kernel.

Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH] Do not reserve crashkernel high memory if crashkernel low memory reserving failed Baoquan He <bhe@redhat.com> - 2015-07-19 13:10 +0200
  Re: [PATCH v2] Do not reserve crashkernel high memory if crashkernel  low memory reserving failed Yinghai Lu <yinghai@kernel.org> - 2015-07-23 01:50 +0200
    Re: [PATCH v2] Do not reserve crashkernel high memory if crashkernel  low memory reserving failed Joerg Roedel <joro@8bytes.org> - 2015-07-27 16:10 +0200
  Re: [PATCH v2] Do not reserve crashkernel high memory if crashkernel  low memory reserving failed Yinghai Lu <yinghai@kernel.org> - 2015-07-23 01:50 +0200
    Re: [PATCH v2] Do not reserve crashkernel high memory if crashkernel  low memory reserving failed Baoquan He <bhe@redhat.com> - 2015-07-28 03:00 +0200
      Re: [PATCH v2] Do not reserve crashkernel high memory if crashkernel  low memory reserving failed Baoquan He <bhe@redhat.com> - 2015-07-28 11:30 +0200
  Re: [PATCH v2] Do not reserve crashkernel high memory if crashkernel  low memory reserving failed Yinghai Lu <yinghai@kernel.org> - 2015-07-23 01:50 +0200
  Re: [PATCH v2] Do not reserve crashkernel high memory if crashkernel  low memory reserving failed Joerg Roedel <joro@8bytes.org> - 2015-07-27 16:50 +0200
  Re: [PATCH v2] Do not reserve crashkernel high memory if crashkernel  low memory reserving failed Joerg Roedel <joro@8bytes.org> - 2015-07-27 16:50 +0200
  Re: [PATCH v2] Do not reserve crashkernel high memory if crashkernel  low memory reserving failed Baoquan He <bhe@redhat.com> - 2015-07-28 01:40 +0200

csiph-web