Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: WANG Chao <chaowang@redhat.com>
To: Muli Ben-Yehuda <muli@il.ibm.com>,
	"Jon D. Mason" <jdmason@kudzu.us>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>, Vivek Goyal <vgoyal@redhat.com>,
	Yinghai Lu <yinghai@kernel.org>
Cc: discuss@x86-64.org, x86@kernel.org, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: How could we get rid of saved_max_pfn for calgary iommu?
Date: Wed, 19 Feb 2014 14:18:24 +0800	[thread overview]
Message-ID: <20140219061824.GA29703@dhcp-17-89.nay.redhat.com> (raw)

Hi, All

arch/x86/kernel/pci-calgary.c is the only user of saved_max_pfn today:

int __init detect_calgary(void)
{
	[..]
	specified_table_size = determine_tce_table_size((is_kdump_kernel() ?
					saved_max_pfn : max_pfn) * PAGE_SIZE);
	[..]
}

saved_max_pfn is the real mem size and is calculated by 1st kernel E820
memmap which is passed in by 2nd kernel's boot_params (done by kexec):

	saved_max_pfn = e820_end_of_ram_pfn();

After saved_max_pfn has been set, memmap=exactmap will reset the E820
provided by boot_params and use the user defined E820 instead.

Now we want to get rid of memmap=exactmap and directly pass the E820
memmap by boot_params for some reason (eg. exactmap may exceed the cmdline
size and also isn't compatible with kaslr).

However saved_max_pfn becomes the obstacle for obsoleting exactmap.
Because it needs two conditions: first kernel's E820 map and
memmap=exactmap cmdline.

So I'm wondering if it's possible to get rid of saved_max_pfn totally in
calgary code. Or we can get saved_max_pfn using a different way, for
example calculated in 1st kernel and passed in to 2nd kernel by cmdline.

Thanks
WANG Chao

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

             reply	other threads:[~2014-02-19  6:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19  6:18 WANG Chao [this message]
2014-02-20  0:04 ` How could we get rid of saved_max_pfn for calgary iommu? Jon Mason
2014-02-20  2:36   ` Vivek Goyal
2014-02-21  7:47     ` WANG Chao
2014-02-21  8:18   ` Baoquan He
2014-03-05  5:36 ` WANG Chao
2014-03-06  6:47   ` Muli Ben-Yehuda
2014-03-06  6:50     ` H. Peter Anvin
2014-03-06  7:00       ` Muli Ben-Yehuda
2014-03-06 14:46         ` Jon Mason
2014-03-09  7:06           ` Muli Ben-Yehuda
2014-03-11  5:20             ` Jon Mason
2014-03-06 16:05     ` Vivek Goyal

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=20140219061824.GA29703@dhcp-17-89.nay.redhat.com \
    --to=chaowang@redhat.com \
    --cc=discuss@x86-64.org \
    --cc=hpa@zytor.com \
    --cc=jdmason@kudzu.us \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=muli@il.ibm.com \
    --cc=tglx@linutronix.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