From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 564 invoked by alias); 14 Apr 2004 11:44:46 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 557 invoked from network); 14 Apr 2004 11:44:44 -0000 Received: from unknown (HELO miranda.se.axis.com) (193.13.178.2) by sources.redhat.com with SMTP; 14 Apr 2004 11:44:44 -0000 Received: from axis.com (ironmaiden.se.axis.com [10.13.8.120]) by miranda.se.axis.com (8.12.9/8.12.9/Debian-5local0.1) with ESMTP id i3EBihUm023855 for ; Wed, 14 Apr 2004 13:44:43 +0200 Message-ID: <407D242B.109@axis.com> Date: Wed, 14 Apr 2004 11:44:00 -0000 From: Orjan Friberg Organization: Axis Communications User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 MIME-Version: 1.0 To: gdb-patches@sources.redhat.com Subject: Multiplexed registers and invalidating the register cache Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-04/txt/msg00282.txt.bz2 Hi all, I'm working on support for a CPU where some of the registers are in a bank selected by another register, meaning that changing the bank select register changes the contents (and meaning) for a whole set of other registers. The target is a remote stub, and the way I've pictured this in my head a change to the bank select register (via a 'P' packet) invalidates the register cache, causing the whole register contents to be fetched again (with a 'g' packet). (The remote stub needs to re-read the affected registers upon the write of the bank select register, of course.) Is there some sort of "write register" hook I could use to indicate that the registers should be fetched again if the bank select register is written to? I followed what happens when doing a "set $register", but I couldn't find any such hook in that path. -- Orjan Friberg Axis Communications