From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Mon, 25 Nov 2002 13:00:57 +0100 (CET) Received: from mx2.mips.com ([206.31.31.227]:8141 "EHLO mx2.mips.com") by linux-mips.org with ESMTP id ; Mon, 25 Nov 2002 13:00:56 +0100 Received: from newman.mips.com (ns-dmz [206.31.31.225]) by mx2.mips.com (8.12.5/8.12.5) with ESMTP id gAPC0jNf007316; Mon, 25 Nov 2002 04:00:45 -0800 (PST) Received: from grendel (grendel [192.168.236.16]) by newman.mips.com (8.9.3/8.9.0) with SMTP id EAA00114; Mon, 25 Nov 2002 04:00:43 -0800 (PST) Message-ID: <00d001c2947a$d71231d0$10eca8c0@grendel> From: "Kevin D. Kissell" To: "atul srivastava" , "Ralf Baechle" Cc: References: <20021125100152.6471.qmail@mailweb33.rediffmail.com> Subject: Re: Re: watch exception only for kseg0 addresses..? Date: Mon, 25 Nov 2002 13:04:28 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 704 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: kevink@mips.com Precedence: bulk X-list: linux-mips > > Beyond that there > > are at least two different formats of watch registers implemented > > in actual silicon, the original R4000-style and the MIPS32/MIPS64 > > style watch registers and the kernel's watch code only know the R4000 > > style. > > my cpu manual ( IDT RC32334) talks about two watch registers > CP0_IWATCH and CP0_DWATCH where it is required to just put desired > VIRTUAL( bits 2--31) addresses to be watched , there is no mention > of CP0_WATCHLO and CP0_WATCHHI . Your CPU would appear to be neither MIPS32/MIPS64 compliant nor R4000 backward-compatible. The designers may have sought to simplify the use of watch registers in user space, apparently at the price of the restriction you are seeing. > additionally i guees for userspace virtual watch register problem, > the hardware takes care of all , i just need to specify my virual > address this is what i understand from my manual. > > and one more problem i face when i try to debug a mysterious page > fault problem, that i get my watch exception but after page fault > ..hence I can't really debug , shouldn't the priority of watch > exceptions should be higher than atleast instruction fetch > exception.? or the scope of debugging by watch exception is > limited by design..... Does your CPU implement EJTAG? Kevin K. From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <00d001c2947a$d71231d0$10eca8c0@grendel> From: "Kevin D. Kissell" References: <20021125100152.6471.qmail@mailweb33.rediffmail.com> Subject: Re: Re: watch exception only for kseg0 addresses..? Date: Mon, 25 Nov 2002 13:04:28 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-Path: Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org To: atul srivastava , Ralf Baechle Cc: linux-mips@linux-mips.org Message-ID: <20021125120428.piDSbXZwLJoGjlUbnMmor2N4aw3Rh0UytHEVoktZU30@z> > > Beyond that there > > are at least two different formats of watch registers implemented > > in actual silicon, the original R4000-style and the MIPS32/MIPS64 > > style watch registers and the kernel's watch code only know the R4000 > > style. > > my cpu manual ( IDT RC32334) talks about two watch registers > CP0_IWATCH and CP0_DWATCH where it is required to just put desired > VIRTUAL( bits 2--31) addresses to be watched , there is no mention > of CP0_WATCHLO and CP0_WATCHHI . Your CPU would appear to be neither MIPS32/MIPS64 compliant nor R4000 backward-compatible. The designers may have sought to simplify the use of watch registers in user space, apparently at the price of the restriction you are seeing. > additionally i guees for userspace virtual watch register problem, > the hardware takes care of all , i just need to specify my virual > address this is what i understand from my manual. > > and one more problem i face when i try to debug a mysterious page > fault problem, that i get my watch exception but after page fault > ..hence I can't really debug , shouldn't the priority of watch > exceptions should be higher than atleast instruction fetch > exception.? or the scope of debugging by watch exception is > limited by design..... Does your CPU implement EJTAG? Kevin K.