mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Albert Cahalan" <acahalan@gmail.com>
To: linux-kernel@vger.kernel.org, johnpol@2ka.mipt.ru,
	matthltc@us.ibm.com, guillaume.thouvenin@bull.net,
	michael.kerrisk@gmx.net, sekharan@us.ibm.com
Subject: Re: [RFC][PATCH 3/3] Process events biarch bug: New process events connector value
Date: Wed, 28 Jun 2006 02:00:33 -0400	[thread overview]
Message-ID: <787b0d920606272300p46fae7e0n34ee8fa6e78b4fb3@mail.gmail.com> (raw)

Matt Helsley writes:

> "Deprecate" existing Process Events connector interface
> and add a new one that works cleanly on biarch platforms.
>
> Any expansion of the previous event structure would break
> userspace's ability to workaround the biarch incompatibility
> problem. Hence this patch creates a new interface and generates
> events (for both when necessary).

I haven't yet seen a good explanation of what this is or does,
but I suspect it may be useful for the "top" program or for a
debugger. In either case, I am a highly interested party.
I maintain top as part of the procps package. People pay me to
hack on debuggers.

Mind pointing me to some documentation and an explanation of why
the feature was added? Is there a man page? (there should be)

Perhaps there is no need to support 32-bit apps using this on
64-bit systems. Obviously the 32-on-64 nonsense must include
full debugger support (else you can't work on it very well),
and I suppose there is a desire to support various proprietary
bits of junk like the Flash player, but... there is a place to
just draw the line.

             reply	other threads:[~2006-06-28  6:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28  6:00 Albert Cahalan [this message]
     [not found] <20060627112644.804066367@localhost.localdomain>
2006-06-27 11:49 ` Matt Helsley
2006-06-27 19:14   ` Chandra Seetharaman
2006-06-27 21:39     ` Matt Helsley
2006-06-27 23:54       ` Chandra Seetharaman
2006-06-28  1:29         ` Matt Helsley
2006-06-28  5:53       ` Evgeniy Polyakov
2006-06-30  8:46         ` Evgeniy Polyakov

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=787b0d920606272300p46fae7e0n34ee8fa6e78b4fb3@mail.gmail.com \
    --to=acahalan@gmail.com \
    --cc=guillaume.thouvenin@bull.net \
    --cc=johnpol@2ka.mipt.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthltc@us.ibm.com \
    --cc=michael.kerrisk@gmx.net \
    --cc=sekharan@us.ibm.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

all inboxes | Powered by JetHome®