public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Muli Ben-Yehuda <muli@cs.technion.ac.il>,
	"Jon D. Mason" <jdmason@kudzu.us>, Baoquan He <bhe@redhat.com>,
	kexec@lists.infradead.org, x86@kernel.org,
	linux-kernel@vger.kernel.org, WANG Chao <chaowang@redhat.com>
Subject: Re: [PATCH v2] x86, calgary: use 8M TCE table size by default
Date: Thu, 20 Mar 2014 09:01:57 -0700	[thread overview]
Message-ID: <532B10F5.9010709@zytor.com> (raw)
In-Reply-To: <20140320155411.GC29549@redhat.com>

On 03/20/2014 08:54 AM, Vivek Goyal wrote:
> Hi hpa,
> 
> I am wondering how to make progress on calgary issue now. We do want to
> cleanup kexec-tools code and move to passing memory ranges in bootparams.
> 
> I see two choices here.
> 
> - Take this patch in so that new kernel code will work with modified
>   kexec-tools without any user intervention. (Both first and second kernel
>   need to be new). 
> 
> - Don't take this patch in and calgary will be broken with new
>   kexec-tools. And that will always require manual user intervention
>   from user to force passing memmap on command line.
> 
> I kind of prefer the first option so that even if there are some calgary
> machines out there, they will work automatically with new kernel and
> will require manual intervention only for old kernels and new kexec-tool
> cobination.
> 
> But I can live with second option too if that's everybody agrees to and
> hopefully we don't get lots of reports of breaking kdump with kexec-tools
> upgrade.
> 

The patch seems simple enough and doesn't require any new command line
hacks.  It has been widely reviewed and acked, so I'll pick it up.

	-hpa



  reply	other threads:[~2014-03-20 16:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 14:52 [PATCH v2] x86, calgary: use 8M TCE table size by default WANG Chao
2014-03-10 15:45 ` Vivek Goyal
2014-03-10 15:54   ` Muli Ben-Yehuda
2014-03-11  5:26     ` Jon Mason
2014-03-12  2:32       ` WANG Chao
2014-03-20 15:54 ` Vivek Goyal
2014-03-20 16:01   ` H. Peter Anvin [this message]
2014-03-20 22:15 ` [tip:x86/platform] x86, calgary: Use " tip-bot for WANG Chao
2014-04-11  2:55 ` tip-bot for WANG Chao

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=532B10F5.9010709@zytor.com \
    --to=hpa@zytor.com \
    --cc=bhe@redhat.com \
    --cc=chaowang@redhat.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