From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: x86@kernel.org, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, horms@verge.net.au,
Thomas Renninger <trenn@suse.de>,
vgoyal@redhat.com
Subject: Re: [PATCH 2/2] x86 e820: Introduce memmap=resetusablemap for kdump usage
Date: Mon, 28 Jan 2013 19:33:52 -0800 [thread overview]
Message-ID: <5ea70988-10fb-4153-9482-75507efe0b07@email.android.com> (raw)
In-Reply-To: <CAE9FiQUDP9x+6CZKyW8CVq7YWy+zQwSTqm67G-AuX0=LYgqf6A@mail.gmail.com>
I guess that very limited use might make sense.
Yinghai Lu <yinghai@kernel.org> wrote:
>On Mon, Jan 28, 2013 at 6:27 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>> To be more clear: the max_pfn stuff seems like a relic of the past,
>and I am wondering what it would take to get rid of it.
>>
>> It clearly has the wrong semantics, except perhaps in the most
>trivial allocator models.
>>
>one thing i think could be : use that decide if we need iommu/swiotlb.
>like in
>arch/x86/kernel/amd_gart_64.c
>arch/x86/kernel/pci-swiotlb.c
>drivers/iommu/amd_iommu.c
>...
>
>Yinghai
--
Sent from my mobile phone. Please excuse brevity and lack of formatting.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-01-29 3:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 15:20 [PATCH 0/2] Only parse exactmap once, introduce memmap=resetusablemap Thomas Renninger
2013-01-22 15:20 ` [PATCH 1/2] x86 e820: Check for exactmap appearance when parsing first memmap option Thomas Renninger
2013-01-22 19:33 ` Yinghai Lu
2013-01-29 1:09 ` H. Peter Anvin
2013-01-29 2:01 ` Yinghai Lu
2013-01-22 15:20 ` [PATCH 2/2] x86 e820: Introduce memmap=resetusablemap for kdump usage Thomas Renninger
2013-01-22 15:54 ` H. Peter Anvin
2013-01-22 16:23 ` Thomas Renninger
2013-01-22 16:32 ` H. Peter Anvin
[not found] ` <CAE9FiQWJqWQJhoJb2dBn=iAsKjxuf3MJro-jz+6k+WNZor8-xQ@mail.gmail.com>
2013-01-24 4:07 ` Yinghai Lu
2013-01-29 1:05 ` Thomas Renninger
2013-01-29 1:11 ` H. Peter Anvin
2013-01-29 2:10 ` Yinghai Lu
2013-01-29 2:11 ` H. Peter Anvin
2013-01-29 2:19 ` Yinghai Lu
2013-01-29 2:20 ` H. Peter Anvin
2013-01-29 2:27 ` H. Peter Anvin
2013-01-29 2:31 ` Yinghai Lu
2013-01-29 3:33 ` H. Peter Anvin [this message]
2013-01-29 9:47 ` Thomas Renninger
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=5ea70988-10fb-4153-9482-75507efe0b07@email.android.com \
--to=hpa@zytor.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trenn@suse.de \
--cc=vgoyal@redhat.com \
--cc=x86@kernel.org \
--cc=yinghai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox