From: "Chris Friesen" <cfriesen@nortel.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Doug Thompson <norsk5@yahoo.com>,
ncunningham-lkml@crca.org.au, Pavel Machek <pavel@suse.cz>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
bluesmoke-devel@lists.sourceforge.net
Subject: Re: marching through all physical memory in software
Date: Mon, 02 Feb 2009 12:29:45 -0600 [thread overview]
Message-ID: <49873B99.3070405@nortel.com> (raw)
In-Reply-To: <m1wscc7fop.fsf@fess.ebiederm.org>
Eric W. Biederman wrote:
> Thinking about it. We only care about memory the kernel is using so the memory
> maps the BIOS supplies the kernel should be sufficient. We have weird corner
> cases like ACPI but not handling those in the first pass and getting
> something working should be fine.
Agreed.
The next question is who handles the conversion of the various different
arch-specific BIOS mappings to a standard format that we can feed to the
background "scrub" code. Is this something that belongs in the edac
memory controller code, or would it live in /arch/foo somewhere?
Chris
WARNING: multiple messages have this Message-ID (diff)
From: "Chris Friesen" <cfriesen@nortel.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Doug Thompson <norsk5@yahoo.com>,
ncunningham-lkml@crca.org.au, Pavel Machek <pavel@suse.cz>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
bluesmoke-devel@lists.sourceforge.net
Subject: Re: marching through all physical memory in software
Date: Mon, 02 Feb 2009 12:29:45 -0600 [thread overview]
Message-ID: <49873B99.3070405@nortel.com> (raw)
In-Reply-To: <m1wscc7fop.fsf@fess.ebiederm.org>
Eric W. Biederman wrote:
> Thinking about it. We only care about memory the kernel is using so the memory
> maps the BIOS supplies the kernel should be sufficient. We have weird corner
> cases like ACPI but not handling those in the first pass and getting
> something working should be fine.
Agreed.
The next question is who handles the conversion of the various different
arch-specific BIOS mappings to a standard format that we can feed to the
background "scrub" code. Is this something that belongs in the edac
memory controller code, or would it live in /arch/foo somewhere?
Chris
--
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:[~2009-02-02 18:30 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <715599.77204.qm@web50111.mail.re2.yahoo.com>
2009-01-30 19:32 ` marching through all physical memory in software Eric W. Biederman
2009-01-30 19:32 ` Eric W. Biederman
2009-01-30 20:20 ` Tim Small
2009-01-30 20:20 ` Tim Small
2009-01-31 3:54 ` Eric W. Biederman
2009-01-31 3:54 ` Eric W. Biederman
2009-01-31 12:48 ` Tim Small
2009-01-31 12:48 ` Tim Small
2009-01-31 13:43 ` Henrique de Moraes Holschuh
2009-01-31 13:43 ` Henrique de Moraes Holschuh
2009-01-31 21:27 ` Pavel Machek
2009-01-31 21:27 ` Pavel Machek
2009-02-01 1:25 ` Henrique de Moraes Holschuh
2009-02-01 1:25 ` Henrique de Moraes Holschuh
2009-01-30 21:10 ` Nigel Cunningham
2009-01-30 21:10 ` Nigel Cunningham
2009-02-02 18:29 ` Chris Friesen [this message]
2009-02-02 18:29 ` Chris Friesen
2009-02-02 22:45 ` Valdis.Kletnieks
2009-02-03 14:31 ` Chris Friesen
2009-02-03 14:31 ` Chris Friesen
2009-02-03 22:25 ` Pavel Machek
2009-02-03 22:25 ` Pavel Machek
2009-02-04 16:03 ` Chris Friesen
2009-02-04 16:03 ` Chris Friesen
2009-02-04 16:47 ` Dave Jiang
2009-02-04 16:47 ` Dave Jiang
2009-01-26 15:38 Chris Friesen
2009-01-26 15:59 ` Arjan van de Ven
2009-01-27 18:29 ` Chris Friesen
2009-01-27 20:16 ` Eric W. Biederman
2009-01-27 20:16 ` Eric W. Biederman
2009-01-28 19:38 ` Pavel Machek
2009-01-28 19:38 ` Pavel Machek
2009-01-30 9:05 ` Nigel Cunningham
2009-01-30 9:05 ` Nigel Cunningham
2009-01-30 9:13 ` Pavel Machek
2009-01-30 9:13 ` Pavel Machek
2009-01-30 13:00 ` Nigel Cunningham
2009-01-30 13:00 ` Nigel Cunningham
2009-02-06 9:00 ` Andi Kleen
2009-02-07 3:03 ` Henrique de Moraes Holschuh
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=49873B99.3070405@nortel.com \
--to=cfriesen@nortel.com \
--cc=arjan@infradead.org \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ncunningham-lkml@crca.org.au \
--cc=norsk5@yahoo.com \
--cc=pavel@suse.cz \
/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.