From patchwork Thu Oct 26 22:45:27 2000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jeremy Fitzhardinge X-Patchwork-Id: 33 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 26 Oct 2000 18:45:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 26 Oct 2000 18:45:46 -0400 Received: from adsl-206-170-148-147.dsl.snfc21.pacbell.net ([206.170.148.147]:46607 "HELO gw.goop.org") by vger.kernel.org with SMTP id ; Thu, 26 Oct 2000 18:45:30 -0400 Date: Thu, 26 Oct 2000 15:45:27 -0700 From: Jeremy Fitzhardinge To: Linux Kernel , linus@goop.org Subject: [PATCH] address-space identification for /proc Message-ID: <20001026154527.A30463@goop.org> Mail-Followup-To: Jeremy Fitzhardinge , Linux Kernel , linus@goop.org Mime-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi, /proc has no way to indicate whether tasks share an address space. This one-liner patch adds a new ASID: field to /proc//status so there's some way to see address-space sharing between tasks. While this is hardly a bug-fix, it is a pretty useful thing to know which is otherwise completely absent. J --- ../2.3/fs/proc/array.c Mon Oct 9 17:03:53 2000 +++ linux/fs/proc/array.c Thu Oct 26 15:20:52 2000 @@ -294,6 +294,7 @@ for(line=0;(len=sprintf_regs(line,buffer,task,NULL,NULL))!=0;line++) buffer+=len; #endif + buffer += sprintf("ASID: %p\n", mm); return buffer - orig; }