All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: "Hatayama, Daisuke" <d.hatayama@jp.fujitsu.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"lisa.mitchell@hp.com" <lisa.mitchell@hp.com>,
	"kumagai-atsushi@mxc.nes.nec.co.jp"
	<kumagai-atsushi@mxc.nes.nec.co.jp>,
	"ebiederm@xmission.com" <ebiederm@xmission.com>,
	"cpw@sgi.com" <cpw@sgi.com>
Subject: Re: [PATCH] kdump, oldmem: support mmap on /dev/oldmem
Date: Mon, 11 Feb 2013 15:44:14 -0500	[thread overview]
Message-ID: <20130211204414.GA24936@redhat.com> (raw)
In-Reply-To: <33710E6CAA200E4583255F4FB666C4E20AC67384@G01JPEXMBYT03>

On Fri, Feb 08, 2013 at 12:33:49AM +0000, Hatayama, Daisuke wrote:

[..]
> Also, remap_pfn_range is the function exported into kernel modules, so changing the third argument means changing ABI. Introducing a kind of remap_pfn_range_64 is a good idea? if there's someone needing the feature on 32-bit kernel.

I thought kernel does not care about compatibility with out of tree
modules and any user of in-tree module is updated to use new API. I could
be wrong though...

Thanks
Vivek

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

WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@redhat.com>
To: "Hatayama, Daisuke" <d.hatayama@jp.fujitsu.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"lisa.mitchell@hp.com" <lisa.mitchell@hp.com>,
	"kumagai-atsushi@mxc.nes.nec.co.jp" 
	<kumagai-atsushi@mxc.nes.nec.co.jp>,
	"ebiederm@xmission.com" <ebiederm@xmission.com>,
	"cpw@sgi.com" <cpw@sgi.com>
Subject: Re: [PATCH] kdump, oldmem: support mmap on /dev/oldmem
Date: Mon, 11 Feb 2013 15:44:14 -0500	[thread overview]
Message-ID: <20130211204414.GA24936@redhat.com> (raw)
In-Reply-To: <33710E6CAA200E4583255F4FB666C4E20AC67384@G01JPEXMBYT03>

On Fri, Feb 08, 2013 at 12:33:49AM +0000, Hatayama, Daisuke wrote:

[..]
> Also, remap_pfn_range is the function exported into kernel modules, so changing the third argument means changing ABI. Introducing a kind of remap_pfn_range_64 is a good idea? if there's someone needing the feature on 32-bit kernel.

I thought kernel does not care about compatibility with out of tree
modules and any user of in-tree module is updated to use new API. I could
be wrong though...

Thanks
Vivek

  reply	other threads:[~2013-02-11 20:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04  4:59 [PATCH] kdump, oldmem: support mmap on /dev/oldmem Hatayama, Daisuke
2013-02-05 15:12 ` Vivek Goyal
2013-02-05 15:12   ` Vivek Goyal
2013-02-06  7:24   ` Hatayama, Daisuke
2013-02-06  7:24     ` Hatayama, Daisuke
2013-02-07 15:06     ` Vivek Goyal
2013-02-07 15:06       ` Vivek Goyal
2013-02-08  0:25       ` Hatayama, Daisuke
2013-02-08  0:25         ` Hatayama, Daisuke
2013-02-08  0:33         ` Hatayama, Daisuke
2013-02-08  0:33           ` Hatayama, Daisuke
2013-02-11 20:44           ` Vivek Goyal [this message]
2013-02-11 20:44             ` 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=20130211204414.GA24936@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=cpw@sgi.com \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=ebiederm@xmission.com \
    --cc=kexec@lists.infradead.org \
    --cc=kumagai-atsushi@mxc.nes.nec.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lisa.mitchell@hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.