From: Bernhard Walle <bwalle@suse.de>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH] Implement support for mem command line parameter
Date: Tue, 10 Jun 2008 21:31:58 +0200 [thread overview]
Message-ID: <20080610213158.44e2139c@kopernikus.site> (raw)
In-Reply-To: <20080610030051.GB25390@redhat.com>
* Vivek Goyal <vgoyal@redhat.com> [2008-06-09 23:00]:
>
> > Right. I just checked with 2.6.22.5 (openSUSE 10.3 kernel), and
> >
> > - i386: /proc/iomem contains full memory
> > - x86_64: /proc/iomem contains truncated memory
> >
> > After the x86 merge, x86_64 now has the behaviour of i386.
> >
>
> Cool. Now atleast behavior across x86 and x86_64 is same.
After studying the code, well, that was wrong. I tested again:
- i386: /proc/iomem contains truncated memory
- x86_64: /proc/iomem contains full memroy
And after the merge, it stays the same, i.e. /proc/iomem in i386 is
truncated.
Sorry for the confusion. :-|
The question is: Is that "accidentally" or by design. The file
Documentation/kernel-parameters.txt:
[X86-32] Use together with memmap= to avoid physical
address space collisions. Without memmap= PCI devices
could be placed at addresses belonging to unused RAM.
implies that it's "by design".
(And EFI code might be different again. However, I have no non-IA64
EFI machine to test.)
Bernhard
--
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-06-10 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 23:29 [PATCH] Implement support for mem command line parameter Bernhard Walle
2008-06-03 3:04 ` Vivek Goyal
2008-06-09 21:57 ` Bernhard Walle
2008-06-10 3:00 ` Vivek Goyal
2008-06-10 19:31 ` Bernhard Walle [this message]
2008-06-11 15:12 ` 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=20080610213158.44e2139c@kopernikus.site \
--to=bwalle@suse.de \
--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