From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1838 invoked by alias); 11 Oct 2019 18:17:55 -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 1817 invoked by uid 89); 11 Oct 2019 18:17:55 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-5.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_JMF_BL,SPF_HELO_PASS autolearn=no version=3.3.1 spammy=H*RU:sk:cm13.we, HX-Spam-Relays-External:sk:cm13.we, HX-Spam-Relays-External:100.42.49.6, H*RU:100.42.49.6 X-HELO: gateway21.websitewelcome.com Received: from gateway21.websitewelcome.com (HELO gateway21.websitewelcome.com) (192.185.45.2) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 11 Oct 2019 18:17:53 +0000 Received: from cm13.websitewelcome.com (cm13.websitewelcome.com [100.42.49.6]) by gateway21.websitewelcome.com (Postfix) with ESMTP id 3E16941098946 for ; Fri, 11 Oct 2019 13:17:51 -0500 (CDT) Received: from box5379.bluehost.com ([162.241.216.53]) by cmsmtp with SMTP id IzU7iPqRH3Qi0IzU7iwU0q; Fri, 11 Oct 2019 13:17:51 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tromey.com; s=default; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=RcYiOFd6hwg18dkiHHCHlgHM/jjCVYetWzhx9cBzLs8=; b=L0FuNlDiO04Qz1tRiTzCnybjhs 87CiNgq9wGkAHwgbKfurJyVyDKnjUN5RsRWJsWMY2PnEDo2xYvFxDbEy5VAFYENYrye4L18ERGmQY H/kDTysYbarS+BBGMi7CN95bK; Received: from 174-29-53-230.hlrn.qwest.net ([174.29.53.230]:42094 helo=murgatroyd) by box5379.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from ) id 1iIzU6-003M5n-TG; Fri, 11 Oct 2019 12:17:51 -0600 From: Tom Tromey To: Alan Hayward Cc: "gdb-patches\@sourceware.org" , nd Subject: Re: [RFC] AArch64 Memory tagging support References: <1E24219E-DBAD-4F6A-87CC-5B3E232E2234@arm.com> Date: Fri, 11 Oct 2019 18:17:00 -0000 In-Reply-To: <1E24219E-DBAD-4F6A-87CC-5B3E232E2234@arm.com> (Alan Hayward's message of "Wed, 21 Aug 2019 10:39:13 +0000") Message-ID: <87sgnz2lki.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2019-10/txt/msg00301.txt.bz2 >>>>> "Alan" == Alan Hayward writes: Alan> This is a rough design for implementing ARMv8.5 MTE support in GDB, Alan> detailing the UI changes and sketching out the internals. Alan> Memory accesses inside GDB Alan> It should be enough for AArch64 to override target_xfer_partial. Alan> If the process is using memory tags, and the address contains a LT, then Alan> call PEEKDATATAG for the memory range being accessed and check if the access Alan> would succeed. If it doesn't then print just the first failure to the screen. Alan> If it does succeed then call the overridden function to access the memory. Another thing to consider is that you will probably want remote protocol support for this. Tom