From: WANG Chao <chaowang@redhat.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Baoquan He <bhe@redhat.com>,
x86@kernel.org, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Muli Ben-Yehuda <muli@cs.technion.ac.il>,
"Jon D. Mason" <jdmason@kudzu.us>
Subject: Re: [PATCH] x86, calgary: use 8M TCE table size by default
Date: Fri, 7 Mar 2014 23:52:04 +0800 [thread overview]
Message-ID: <20140307155204.GC30641@dhcp-17-89.nay.redhat.com> (raw)
In-Reply-To: <20140307141413.GF1326@redhat.com>
Hi, Vivek
On 03/07/14 at 09:14am, Vivek Goyal wrote:
> On Fri, Mar 07, 2014 at 04:10:16PM +0800, WANG Chao wrote:
>
> [..]
> > }
> >
> > - specified_table_size = determine_tce_table_size((is_kdump_kernel() ?
> > - saved_max_pfn : max_pfn) * PAGE_SIZE);
> > + specified_table_size = determine_tce_table_size();
>
> I don't think you can get rid of saved_max_pfn right away. What if
> somebody is using old first kernel and new second kernel. Then old kernel
> will still be using a table size which is smaller than 8M.
If TCE table size is hard coded to 8M, the new 1st kernel can never be
compatible with the old 2nd kernel. Because old kernel's TCE table size
is depending on saved_max_pfn, which could be from 64K to 8M, not
necessarily the hard coded value 8M.
If we want to drop saved_max_pfn once and for all, that's a trade-off
which is worth doing. Because as Muli pointed out last time, there are
very few people likely running upstream kernel on calgary machine. And
most of them would use the same kernel as 1st and 2nd kernel. For the
very very few people who suffers from it, we can always encourage them
to use the same kernel for 1st and 2nd kernel or other solutions we
have.
Thanks
WANG Chao
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2014-03-07 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 8:10 [PATCH] x86, calgary: use 8M TCE table size by default WANG Chao
2014-03-07 14:14 ` Vivek Goyal
2014-03-07 15:52 ` WANG Chao [this message]
2014-03-07 16:09 ` Vivek Goyal
2014-03-09 7:08 ` Muli Ben-Yehuda
2014-03-10 8:38 ` WANG Chao
2014-03-10 12:38 ` 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=20140307155204.GC30641@dhcp-17-89.nay.redhat.com \
--to=chaowang@redhat.com \
--cc=bhe@redhat.com \
--cc=hpa@zytor.com \
--cc=jdmason@kudzu.us \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=muli@cs.technion.ac.il \
--cc=vgoyal@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox