From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andi Kleen <ak@muc.de>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Doug Thompson <norsk5@yahoo.com>,
akpm@osdl.org, mm-commits@vger.kernel.org, norsk5@xmission.com,
linux-kernel@vger.kernel.org
Subject: Re: + edac-new-opteron-athlon64-memory-controller-driver.patch added to -mm tree
Date: Thu, 06 Jul 2006 19:34:58 +0100 [thread overview]
Message-ID: <1152210898.13734.12.camel@localhost.localdomain> (raw)
In-Reply-To: <20060706180826.GA95795@muc.de>
Ar Iau, 2006-07-06 am 20:08 +0200, ysgrifennodd Andi Kleen:
> > No. There is a status report that tells you which pieces of hardware
> > your memory controller sees. It is just a simple list.
>
> Ok but that could be also done easily in user space that reads
> PCI config space. No need for a complicated kernel driver at all.
The same is true of writing a file system and disk driver so I'm a bit
confused why you think poking around in PCI space from user space is an
argument or given how often such stuff breaks and how messy it gets (eg
X) that we want to encourage it
next prev parent reply other threads:[~2006-07-06 18:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060701150430.GA38488@muc.de>
[not found] ` <20060703172633.50366.qmail@web50109.mail.yahoo.com>
[not found] ` <20060703184836.GA46236@muc.de>
[not found] ` <1151962114.16528.18.camel@localhost.localdomain>
2006-07-04 9:23 ` Andi Kleen
2006-07-04 10:09 ` Alan Cox
2006-07-04 11:34 ` Andi Kleen
2006-07-05 22:08 ` Alan Cox
2006-07-05 22:04 ` Andi Kleen
2006-07-06 6:12 ` Eric W. Biederman
2006-07-06 13:01 ` Andi Kleen
2006-07-06 15:31 ` Eric W. Biederman
2006-07-06 16:51 ` Andi Kleen
2006-07-06 17:46 ` Eric W. Biederman
2006-07-06 18:08 ` Andi Kleen
2006-07-06 18:34 ` Alan Cox [this message]
2006-07-06 18:27 ` Andi Kleen
2006-07-06 19:09 ` Eric W. Biederman
2006-07-06 19:18 ` Andi Kleen
2006-07-06 19:43 ` Eric W. Biederman
2006-07-06 18:43 ` Eric W. Biederman
2006-07-05 17:39 ` Doug Thompson
2006-07-05 19:39 ` Andi Kleen
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=1152210898.13734.12.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=norsk5@xmission.com \
--cc=norsk5@yahoo.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
Powered by JetHome