From: Matthew Wilcox <matthew@wil.cx>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
andi@firstfloor.org, "linux-mm@kvack.org" <linux-mm@kvack.org>,
"tony.luck@intel.com" <tony.luck@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
pbadari@us.ibm.com,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>
Subject: Re: [Question] How to represent SYSTEM_RAM in kerenel/resouce.c
Date: Wed, 03 Oct 2007 16:43:13 +0000 [thread overview]
Message-ID: <20071003164313.GH12049@parisc-linux.org> (raw)
In-Reply-To: <1191429433.4939.49.camel@localhost>
On Wed, Oct 03, 2007 at 09:37:13AM -0700, Dave Hansen wrote:
> I think we should take system ram out of the iomem file, at least.
Rubbish. iomem is a representation of the physical addresses in the
system as seen from the CPU's perspective. As I said in my previous
mail in this thread, if you attempt to map a device's BAR over the top
of physical RAM, things will go poorly for you.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Wilcox <matthew@wil.cx>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
andi@firstfloor.org, "linux-mm@kvack.org" <linux-mm@kvack.org>,
"tony.luck@intel.com" <tony.luck@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
pbadari@us.ibm.com,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>
Subject: Re: [Question] How to represent SYSTEM_RAM in kerenel/resouce.c
Date: Wed, 3 Oct 2007 10:43:13 -0600 [thread overview]
Message-ID: <20071003164313.GH12049@parisc-linux.org> (raw)
In-Reply-To: <1191429433.4939.49.camel@localhost>
On Wed, Oct 03, 2007 at 09:37:13AM -0700, Dave Hansen wrote:
> I think we should take system ram out of the iomem file, at least.
Rubbish. iomem is a representation of the physical addresses in the
system as seen from the CPU's perspective. As I said in my previous
mail in this thread, if you attempt to map a device's BAR over the top
of physical RAM, things will go poorly for you.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Wilcox <matthew@wil.cx>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
andi@firstfloor.org, "linux-mm@kvack.org" <linux-mm@kvack.org>,
"tony.luck@intel.com" <tony.luck@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
pbadari@us.ibm.com,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>
Subject: Re: [Question] How to represent SYSTEM_RAM in kerenel/resouce.c
Date: Wed, 3 Oct 2007 10:43:13 -0600 [thread overview]
Message-ID: <20071003164313.GH12049@parisc-linux.org> (raw)
In-Reply-To: <1191429433.4939.49.camel@localhost>
On Wed, Oct 03, 2007 at 09:37:13AM -0700, Dave Hansen wrote:
> I think we should take system ram out of the iomem file, at least.
Rubbish. iomem is a representation of the physical addresses in the
system as seen from the CPU's perspective. As I said in my previous
mail in this thread, if you attempt to map a device's BAR over the top
of physical RAM, things will go poorly for you.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-10-03 16:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 1:31 [Question] How to represent SYSTEM_RAM in kerenel/resouce.c KAMEZAWA Hiroyuki
2007-10-03 1:31 ` KAMEZAWA Hiroyuki
2007-10-03 1:31 ` KAMEZAWA Hiroyuki
2007-10-03 1:52 ` Matthew Wilcox
2007-10-03 1:52 ` Matthew Wilcox
2007-10-03 1:52 ` Matthew Wilcox
2007-10-03 4:57 ` KAMEZAWA Hiroyuki
2007-10-03 4:57 ` KAMEZAWA Hiroyuki
2007-10-03 4:57 ` KAMEZAWA Hiroyuki
2007-11-01 9:21 ` [PATCH] Add IORESOUCE_BUSY flag for System RAM (Re: [Question] How to represent SYSTEM_RAM in kerene Yasunori Goto
2007-11-01 9:21 ` [PATCH] Add IORESOUCE_BUSY flag for System RAM (Re: [Question] How to represent SYSTEM_RAM in kerenel/resouce.c) Yasunori Goto
2007-11-01 9:21 ` Yasunori Goto
2007-11-01 15:25 ` [PATCH] Add IORESOUCE_BUSY flag for System RAM (Re: [Question] Badari Pulavarty
2007-11-01 16:28 ` [PATCH] Add IORESOUCE_BUSY flag for System RAM (Re: [Question] How to represent SYSTEM_RAM in kerenel/resouce.c) Badari Pulavarty
2007-11-01 16:28 ` Badari Pulavarty
2007-11-06 2:23 ` [PATCH] Add IORESOUCE_BUSY flag for System RAM take 2 Yasunori Goto
2007-11-06 2:23 ` Yasunori Goto
2007-11-06 2:23 ` Yasunori Goto
2007-10-03 16:37 ` [Question] How to represent SYSTEM_RAM in kerenel/resouce.c Dave Hansen
2007-10-03 16:37 ` Dave Hansen
2007-10-03 16:37 ` Dave Hansen
2007-10-03 16:43 ` Matthew Wilcox [this message]
2007-10-03 16:43 ` Matthew Wilcox
2007-10-03 16:43 ` Matthew Wilcox
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=20071003164313.GH12049@parisc-linux.org \
--to=matthew@wil.cx \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=haveblue@us.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pbadari@us.ibm.com \
--cc=tony.luck@intel.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.