Message ID | 5fa229fc-9514-abc6-5e72-2447a2c637d0@gmail.com (mailing list archive) |
---|---|
Headers | show |
Series | Fixes to debugging facilities | expand |
On 21.08.2023 17:55, Jinoh Kang wrote: > This is a rebased version of Andrew Cooper's debugging facilities patch: > https://lore.kernel.org/xen-devel/1528120755-17455-1-git-send-email-andrew.cooper3@citrix.com/ > >> So this started as a small fix for the vmentry failure (penultimate patch), >> and has snowballed... >> >> I'm fairly confident that everything involving DEBUGCTL.BTF is broken, and >> there are definitely bugs with configuring DEBUGCTL.RTM (which really isn't >> helped by the fact that the GCC TSX intrinsics render the resulting code >> un-debuggable.) I'll defer fixing these swamps for now. >> >> The first 4 patches probably want backporting to the stable trees, so I've >> taken care to move them ahead of patch 6 for backport reasons. While all >> fixes would ideally be backported, I can't find a way of fixing %dr6 merging >> (as it needs to be done precicely once) without a behavioural change in the >> monitor subsystem. >> >> Patch 8 probably breaks introspection, so can't be taken at this point. See >> that patch for discussion of the problem and my best guess at a solution. > > 6 out of 11 patches from the 2018 patch series above, including the > vmentry failure fix, have already been committed. This covers the > remaining 5 patches. One important formal question: Where did Andrew's S-o-b go on all of the patches? Jan
On 8/22/23 15:16, Jan Beulich wrote: > One important formal question: Where did Andrew's S-o-b go on all of the > patches? Thanks for catching it. Looks like I confused the submission process with that of another (non-LF) project. I'll re-read the docs to see if I missed something else w.r.t. tagging rules. > > Jan