From: Bernhard Walle <bwalle@suse.de>
To: kexec@lists.infradead.org
Subject: Re: linux-next: Tree for July 18: warning at kernel/lockdep.c:2068 trace_hardirqs_on_caller
Date: Mon, 21 Jul 2008 17:00:54 +0200 [thread overview]
Message-ID: <20080721170054.3283b6cc@halley.suse.de> (raw)
In-Reply-To: <20080721145417.GE4451@redhat.com>
* Vivek Goyal [2008-07-21 10:54]:
>
> On Mon, Jul 21, 2008 at 03:47:33PM +0200, Bernhard Walle wrote:
> > * Vivek Goyal [2008-07-21 09:39]:
> > >
> > > But the point is, if /sys/devices/system/memory also represents all
> > > the physical memory present in the system then it might be not be
> > > justified to create another similar interface. (Until and unless there
> > > is something unique about /sys/firmware/memmap).
> >
> > But I don't see anything like a physical address there:
> >
> > /sys/devices/system/memory/memory2:
> > -r--r--r-- 1 root root 4096 2008-07-21 15:45 phys_device
> > -r--r--r-- 1 root root 4096 2008-07-21 15:45 phys_index
> > -rw-r--r-- 1 root root 4096 2008-07-21 15:45 state
> >
> > (on a PPC64 machine where SUSE kernel has that interface enabled by
> > default).
> >
> >
> Do you want to respond to lkml and to dave hansen so that he can respond
> back. In this mail only kexec mailing list is there.
Group reply vs. reply. Thanks for noticing. :)
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-07-21 15:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080718195352.e562a00f.sfr@canb.auug.org.au>
[not found] ` <200807190928.33978.m.kozlowski@tuxland.pl>
[not found] ` <19f34abd0807190255x304173d4wf2bfabb2d5bce511@mail.gmail.com>
[not found] ` <19f34abd0807190559y2fe5ebf9h7095793e82de3122@mail.gmail.com>
[not found] ` <20080719221723.GB5578@suse.de>
[not found] ` <19f34abd0807191527u61c5ed61kffe2279c8d46915d@mail.gmail.com>
[not found] ` <19f34abd0807191544nfd73be5nf7dde4b61992a7e8@mail.gmail.com>
[not found] ` <20080719225817.GA6264@suse.de>
[not found] ` <19f34abd0807191611y7cabf405iad307ba79591e04f@mail.gmail.com>
2008-07-20 9:01 ` linux-next: Tree for July 18: warning at kernel/lockdep.c:2068 trace_hardirqs_on_caller Dave Hansen
2008-07-20 9:35 ` Thomas Meyer
2008-07-20 13:03 ` Bernhard Walle
2008-07-20 15:44 ` Bernhard Walle
2008-07-21 13:17 ` Vivek Goyal
2008-07-21 13:25 ` Bernhard Walle
2008-07-21 13:39 ` Vivek Goyal
2008-07-21 13:47 ` Bernhard Walle
2008-07-21 14:54 ` Vivek Goyal
2008-07-21 15:00 ` Bernhard Walle [this message]
2008-07-21 15:00 ` Bernhard Walle
2008-07-22 6:15 ` Yasunori Goto
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=20080721170054.3283b6cc@halley.suse.de \
--to=bwalle@suse.de \
--cc=kexec@lists.infradead.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