public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephane Eranian <eranian@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Debian kernel and /proc/pal
Date: Fri, 05 Aug 2005 11:36:54 +0000	[thread overview]
Message-ID: <1123241814.30015.5.camel@uluru.grenoble.hp.com> (raw)

Hello,

I recently used an Itanium machine booted with a 2.6 Linux kernel.
The exact package is:
        kernel-image-2.6.11-1-mckinley-smp_2.6.11-6_ia64.deb

It does appear that this kernel is compiled without CONFIG_PALINFO
which means there is no /proc/pal/cpu* entries.

I don't quite understand what motivates this choice. There is no
sensitive kernel information in there, just processor information
such as cache size, tlb levels, firmware revision numbers. This
information is very useful, some applications make use of it,
such as pfmon for instance. I would hope this is an oversight
on the part of the package maintainer. It did not use to be 
like that.

Any idea as to what happened?

--
-Stephane


             reply	other threads:[~2005-08-05 11:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-05 11:36 Stephane Eranian [this message]
2005-08-08  0:17 ` Debian kernel and /proc/pal Ian Wienand
2005-08-09 16:40 ` dann frazier
2005-08-09 17:43 ` Stephane Eranian
2005-08-09 17:59 ` dann frazier

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=1123241814.30015.5.camel@uluru.grenoble.hp.com \
    --to=eranian@hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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