From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19035 invoked by alias); 4 Apr 2014 09:44:20 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 19016 invoked by uid 89); 4 Apr 2014 09:44:18 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.2 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mga02.intel.com Received: from mga02.intel.com (HELO mga02.intel.com) (134.134.136.20) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 04 Apr 2014 09:44:17 +0000 Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 04 Apr 2014 02:44:14 -0700 X-ExtLoop1: 1 Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155]) by orsmga001.jf.intel.com with ESMTP; 04 Apr 2014 02:44:13 -0700 Received: from irsmsx104.ger.corp.intel.com ([169.254.5.2]) by IRSMSX102.ger.corp.intel.com ([169.254.2.45]) with mapi id 14.03.0123.003; Fri, 4 Apr 2014 10:42:47 +0100 From: "Metzger, Markus T" To: Eli Zaretskii CC: "palves@redhat.com" , "jan.kratochvil@redhat.com" , "gdb-patches@sourceware.org" Subject: RE: [rfc] btrace: control memory access during replay Date: Fri, 04 Apr 2014 09:44:00 -0000 Message-ID: References: <1396601781-25010-1-git-send-email-markus.t.metzger@intel.com> <8361mpa1z9.fsf@gnu.org> In-Reply-To: <8361mpa1z9.fsf@gnu.org> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2014-04/txt/msg00058.txt.bz2 > -----Original Message----- > From: Eli Zaretskii [mailto:eliz@gnu.org] > Sent: Friday, April 04, 2014 11:17 AM > The ChangeLog entry should state the name(s) of the node(s) in which > you make changes. Thanks, will add it. > Other than that, the documentation parts are approved. However, I > wonder whether "allow-memory-access" is a good name for a setting > which actually allows access to writable portion of the memory. IOW, > even when the value is OFF, we do allow access to memory, just not the > writable portion of it. Agreed; allow-access-to-writable-memory-while-replaying is a bit long, thou= gh. Let's hear what others say about the feature in general. I remember that Jan requested something like this. If the feature itself is approved, I'll try to find a better name. regards, markus. Intel GmbH Dornacher Strasse 1 85622 Feldkirchen/Muenchen, Deutschland Sitz der Gesellschaft: Feldkirchen bei Muenchen Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk Registergericht: Muenchen HRB 47456 Ust.-IdNr./VAT Registration No.: DE129385895 Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052