All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lev Makhlis <mlev@despammed.com>
To: "Andi Kleen" <ak@muc.de>, "Michael Brown" <mebrown@michaels-house.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.4] add SMBIOS information to /proc/smbios -- UPDATED
Date: Sat, 1 May 2004 16:00:44 -0500	[thread overview]
Message-ID: <200405011700.44518.mlev@despammed.com> (raw)

> > -- This information is, in the very near future, _not_ going to be
> > static anymore. There will be systems that update the information in
> > dynamically during SMIs.
>
> That's fine - /dev/mem can handle that too. An user will have to
> poll for changes anyways, so having it it /proc does not have
> any advantages.

One problem is that /dev/mem access isn't atomic.  You need to read
a pointer, then follow the pointer to read data.  If the pointer changes
in the middle, you lose.  That said, I don't see any mechanism that
helps avoid that in kernel, either.


             reply	other threads:[~2004-05-01 21:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-01 21:00 Lev Makhlis [this message]
2004-05-01 21:20 ` [PATCH 2.4] add SMBIOS information to /proc/smbios -- UPDATED Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2004-05-03 23:49 Michael_E_Brown
     [not found] <1QvX0-A4-29@gated-at.bofh.it>
2004-04-30 19:22 ` Andi Kleen
2004-05-01  3:30   ` Michael Brown
2004-05-01  3:43     ` Michael Brown
2004-05-01 15:01     ` Andi Kleen
2004-04-30  2:21 Michael Brown
2004-04-30  3:34 ` viro
2004-04-30  4:37   ` Michael Brown
2004-05-03 23:40 ` Marcelo Tosatti

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=200405011700.44518.mlev@despammed.com \
    --to=mlev@despammed.com \
    --cc=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mebrown@michaels-house.net \
    /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.