From owner-freebsd-arch@FreeBSD.ORG Wed Feb 27 20:56:31 2008 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF70B106566B for ; Wed, 27 Feb 2008 20:56:31 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.69]) by mx1.freebsd.org (Postfix) with ESMTP id A303B8FC19 for ; Wed, 27 Feb 2008 20:56:31 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from mac.com (asmtp006-s [10.150.69.69]) by smtpoutm.mac.com (Xserve/smtpout006/MantshX 4.0) with ESMTP id m1RKuVE8011062; Wed, 27 Feb 2008 12:56:31 -0800 (PST) Received: from mini-g4.jnpr.net (natint3.juniper.net [66.129.224.36]) (authenticated bits=0) by mac.com (Xserve/asmtp006/MantshX 4.0) with ESMTP id m1RKuT87012772 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 27 Feb 2008 12:56:29 -0800 (PST) Message-Id: <4C36D6F7-F329-4C08-91A5-F89FE3C2D811@mac.com> From: Marcel Moolenaar To: Rink Springer In-Reply-To: <20080227204922.GA19591@rink.nu> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Wed, 27 Feb 2008 12:56:28 -0800 References: <8D7D4892-A2E4-42BE-B856-E868E358E5CD@mac.com> <20080227204922.GA19591@rink.nu> X-Mailer: Apple Mail (2.919.2) Cc: FreeBSD Arch Subject: Re: Moving vm_pmap in struct vmspace last X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2008 20:56:31 -0000 On Feb 27, 2008, at 12:49 PM, Rink Springer wrote: > On Wed, Feb 27, 2008 at 12:39:07PM -0800, Marcel Moolenaar wrote: >> The consequence of this patch is that the ABI will be >> broken for all arhcitectures (once). Again, this only >> affects libkvm. Do people see a problem with this change? > > I think this is OK, as long as it's in adequately documented in > UPDATING. The other structs in there won't cause problems, I assume? Correct. -- Marcel Moolenaar xcllnt@mac.com