public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch 0/4] kernel salinfo changes
Date: Thu, 30 Oct 2003 22:16:23 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106755236412598@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106750258117748@msgid-missing>

On Thursday 30 October 2003 1:28 am, Keith Owens wrote:
> patch 1 - Print the header from INIT records, correct typo in sal.h.
> patch 2 - Clean up kernel salinfo state checking.
> patch 3 - Add the ability for user space salinfo to ask kernel salinfo
>           and/or the prom to decode the oem data sections of SAL records.

Thanks for splitting these up nicely.  I applied patches 1 and 2.

I haven't had time to investigate the problem I was having with
"cat $DATA", and I'm going on vacation for a week starting
tomorrow.  So I'll have to look at that when I get back.

As for patch 3, that's an interesting concept.  My initial reaction
is that it seems sort of backwards to put this sort of "binary ->
ASCII" decoding mechanism into the kernel or the prom.

I can see that it might be convenient to be able to stash all
that secret IP in the prom, and it certainly does address the
problem of version skew, but it just seems wrong to get the
kernel in the middle, ferrying data back and forth.

HP has the same problem, of course, with wanting to protect
the meaning of the OEM data, so I had imagined some sort
of binary-only user-level decoder, or perhaps a generic
open-source decoder to which one could add proprietary
plugins.

If you really want the decoding in the prom, what about a
module that allowed you to make arbitrary SAL calls from
user-land?

Bjorn


  reply	other threads:[~2003-10-30 22:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-30  8:28 [patch 0/4] kernel salinfo changes Keith Owens
2003-10-30 22:16 ` Bjorn Helgaas [this message]
2003-10-30 22:50 ` Keith Owens

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=marc-linux-ia64-106755236412598@msgid-missing \
    --to=bjorn.helgaas@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