public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: John Blackwood <john.blackwood@ccur.com>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: Kdump issue with percpu_alloc=lpage
Date: Thu, 19 Nov 2009 09:33:43 -0500	[thread overview]
Message-ID: <20091119143343.GB8741@redhat.com> (raw)
In-Reply-To: <4B03BD7A.9040500@kernel.org>

On Wed, Nov 18, 2009 at 06:25:14PM +0900, Tejun Heo wrote:
> Hello,
> 
> 10/29/2009 06:22 AM, John Blackwood wrote:
> >> Thanks Tejun. percpu_to_phys() makes sense to me also. John, would you
> >> like to post a patch for this.
> > 
> > Hi Vivek,
> > 
> > I'm probably not really NUMA/vm savy enough to attempt a patch
> > for approval at LKML.
> > 
> > But maybe someone else more qualified can take up the cause.
> 
> Is this still necessary for the current upstream where lpage allocator
> is gone (but vmalloc mapping is still there)?
> 

Hi Tejun,

I did load a kdump kernel on 32-rc7 and it worked fine. But I guess in
this case memory might have come from linearly mapped region.

If the default per cpu allocator can get memory from vmalloc region also, then
I think we will need this function which can map virtual address to
physical address.

Are there multiple allocators now? If yes, what are the command line
options and I can try to use some other allocator and see if I can force
the condition where memory comes from vmalloc region and I observe the
crash.

Once I can reproduce it, I can also send you the fix you suggested.

Thanks
Vivek

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

  reply	other threads:[~2009-11-19 14:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-28 21:22 Kdump issue with percpu_alloc=lpage John Blackwood
2009-11-18  9:25 ` Tejun Heo
2009-11-19 14:33   ` Vivek Goyal [this message]
2009-11-19 14:45     ` Tejun Heo
2009-11-19 15:05       ` Vivek Goyal
2009-11-19 15:20         ` John Blackwood
2009-11-19 16:23       ` Vivek Goyal
2009-11-19 16:31         ` Tejun Heo
2009-11-19 16:36           ` Vivek Goyal
  -- strict thread matches above, loose matches on Subject: below --
2009-10-27 19:16 John Blackwood
2009-10-27 19:24 ` 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=20091119143343.GB8741@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=john.blackwood@ccur.com \
    --cc=kexec@lists.infradead.org \
    --cc=tj@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