| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 04 Dec 2008 11:38:17 -0800 From: David Daney <ddaney@...iumnetworks.com> To: prasad@...ux.vnet.ibm.com CC: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Alan Stern <stern@...land.harvard.edu>, Roland McGrath <roland@...hat.com>, akpm@...ux-foundation.org, mingo@...e.hu, richardj_moore@...ibm.com Subject: Re: [RFC Patch 1/9] Introducing generic hardware breakpoint handler interfaces K.Prasad wrote: [...] > + * len and type values are defined in include/asm/hw_breakpoint.h. > + * Available values vary according to the architecture. On i386 the > + * possibilities are: > + * > + * HW_BREAKPOINT_LEN_1 > + * HW_BREAKPOINT_LEN_2 > + * HW_BREAKPOINT_LEN_4 > + * HW_BREAKPOINT_LEN_EXECUTE > + * HW_BREAKPOINT_RW > + * HW_BREAKPOINT_READ > + * HW_BREAKPOINT_EXECUTE > + * > + * On other architectures HW_BREAKPOINT_LEN_8 may be available, and the > + * 1-, 2-, and 4-byte lengths may be unavailable. There also may be > + * HW_BREAKPOINT_WRITE. You can use #ifdef to check at compile time. > + */ On MIPS we support breakpoint lengths that are powers of 2 between 8 and 4096. Do you really want symbolic values for these? The debuggers have to do calculations with the length values, so translating between the symbolic values and numeric values would be tedious at best. David Daney -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists