From: Tigran Aivazian <tigran@veritas.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Hugh Dickins <hugh@veritas.com>, <torvalds@transmeta.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] don't create regular files in devfs (fwd)
Date: Tue, 14 Jan 2003 11:48:58 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.33.0301141145370.1241-100000@einstein31.homenet> (raw)
In-Reply-To: <20030114113135.A14279@lst.de>
On Tue, 14 Jan 2003, Christoph Hellwig wrote:
> On Tue, Jan 14, 2003 at 09:34:52AM +0000, Tigran Aivazian wrote:
> > Hi Christoph,
> >
> > I don't know about mtrr (probably does it for the same reason) but the
> > reason why microcode driver uses a regular file is because it needs
> > something that only regular files can provide --- the file size.
> >
> > This is an easy external "signifier" as to whether a successfull microcode
> > update has occurred or not.
>
> It seems to work without that feature on systems that don't have devfs..
Of course it works without it. I never said it is a required feature, only
a very nice to have. Namely:
a) if devfs is available it provides a regular file whose size can be
examined by applications and content read/written without much "fuss". In
particular it is very convenient to say "vi microcode" and examine the
content directly. If it was a device node then this would have been
impossible.
b) if devfs is not available then a limited basic functionality is
provided --- i.e. just update the microcode on CPU(s) and write the log
messages in the kernel log.
Btw, having a size of mtrr is also useful for a similar reason.
Regards
Tigran
next prev parent reply other threads:[~2003-01-14 11:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0301131851060.9994-100000@localhost.localdomain>
2003-01-14 9:34 ` [PATCH] don't create regular files in devfs (fwd) Tigran Aivazian
2003-01-14 10:31 ` Christoph Hellwig
2003-01-14 11:48 ` Tigran Aivazian [this message]
2003-01-14 11:54 ` Tigran Aivazian
2003-01-14 12:50 ` Christoph Hellwig
2003-01-14 16:32 ` Tigran Aivazian
2003-01-14 16:50 ` Arjan van de Ven
2003-01-14 15:59 ` Patrick Mochel
2003-01-14 17:31 ` Tigran Aivazian
2003-01-14 17:29 ` Tigran Aivazian
2003-01-14 17:40 ` Dave Jones
2003-01-24 6:19 ` Tigran Aivazian
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=Pine.LNX.4.33.0301141145370.1241-100000@einstein31.homenet \
--to=tigran@veritas.com \
--cc=hch@lst.de \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).