public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: John Blackwood <john.blackwood@ccur.com>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: Kdump issue with percpu_alloc=lpage
Date: Fri, 20 Nov 2009 01:31:22 +0900	[thread overview]
Message-ID: <4B0572DA.3030508@kernel.org> (raw)
In-Reply-To: <20091119162329.GA2923@redhat.com>

Hello,

11/20/2009 01:23 AM, Vivek Goyal wrote:
> I implemented your suggested function. This patch seems to be fixing the
> issue. Does it look good to you?
> 
> Please let me know if you want me to post it to lkml or you will pull it
> in your tree and push it to Linus.

Please post it to lkml and cc me.  I'll push it to Linus afterwards.

> Index: linux9/mm/percpu.c
> ===================================================================
> --- linux9.orig/mm/percpu.c	2009-11-12 19:46:07.000000000 -0500
> +++ linux9/mm/percpu.c	2009-11-19 10:55:35.000000000 -0500
> @@ -2069,3 +2069,12 @@ void __init setup_per_cpu_areas(void)
>  		__per_cpu_offset[cpu] = delta + pcpu_unit_offsets[cpu];
>  }
>  #endif /* CONFIG_HAVE_SETUP_PER_CPU_AREA */
> +
> +unsigned long long per_cpu_ptr_to_phys(void *addr)

Maybe phys_addr_t?

Thanks.

-- 
tejun

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

  reply	other threads:[~2009-11-19 16:29 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
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 [this message]
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=4B0572DA.3030508@kernel.org \
    --to=tj@kernel.org \
    --cc=john.blackwood@ccur.com \
    --cc=kexec@lists.infradead.org \
    --cc=vgoyal@redhat.com \
    /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