On 25 November 2014 at 16:50, Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote: > > > On 25/11/2014 17:35, Alexander Graf wrote: >> Unfortunately on ARM you also have a few other constraints - the debug >> register space is partitioned into magic super debug registers at the >> top (with an implementation specific amount) and normal debug registers >> in the lower end of the space. > > Does the gdbstub ever need to use the magic super debug registers? No. The extra features of the trailing registers in the range are "context matching", which means you can set them up as "breakpoint on this context ID" or "breakpoint on this VMID" [read: breakpoints specific to a particular process ID or particular VM], generally as linked breakpoints adding a constraint to a plain address-match breakpoint register. The gdbstub doesn't use context bps and I don't think Linux does either (though of course it might in future). -- PMM _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
