https://bugzilla.novell.com/show_bug.cgi?id=692553 https://bugzilla.novell.com/show_bug.cgi?id=692553#c Philipp Thomas <pth@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pth@novell.com AssignedTo|pth@novell.com |tonyj@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=692553 https://bugzilla.novell.com/show_bug.cgi?id=692553#c1 --- Comment #1 from Tony Jones <tonyj@novell.com> 2011-05-14 05:28:38 UTC --- Yes. It's been a long time since the last oprofile release. I just pushed all the relevant hw enablement changes to: https://build.opensuse.org/package/show?package=oprofile&project=home%3Ajones_tony%3Abranches%3Adevel%3Atools factory devel repo: http://download.opensuse.org/repositories/home:/jones_tony:/branches:/devel:... I'll try and verify I've not broken existing hw/functionality (that I have easy access to) over the weekend and then push to Factory. As far as CodeAnalyst, I'm not sure what I think about the private oprofile. Changelog isn't populated beyond 0.9.6 so hard to know whats in there. I guess I'd prefer that we just keep the factory oprofile up to date wrt necessary changes and use that. Is this not possible? Doesn't appear that suravee.suthikulpanit@amd.com has a BZ account. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=692553 https://bugzilla.novell.com/show_bug.cgi?id=692553#c3 --- Comment #3 from Tony Jones <tonyj@novell.com> 2011-05-16 21:46:11 UTC --- (In reply to comment #2)

I suggested using the sources in CodeAnalyst because I don't know if a cvs version of oprofile can make its way into a stable release (it is not sure that oprofile 0.9.7 will be out for opensuse 12.1). Source from CodeAnalyst should obviously have been tested inside AMD staff.

Of course using the latest cvs revision might be better as it should support newer cpu (like future ivi bridge, maybe bulldozer too), but I doubt it comply with opensuse policy to bring only stable package to the distribution.

It sounds like oprofile 0.9.7 is imminent. This said, once it's released I expect an equivalent long delay before 0.9.8 so this issue will arise again. I'll have to check what the policy is but I'm not expecting it to be as draconian as you imply. We used to take snapshot releases of systemtap, which is nothing more than a point in time in the git repo, so not sure why oprofile would be different but I will check. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.