|| ||Linus Torvalds <torvalds-AT-linux-foundation.org> |
|| ||David Ahern <dsahern-AT-gmail.com> |
|| ||Re: [GIT PULL] perf changes for v3.8 |
|| ||Wed, 12 Dec 2012 20:46:26 -0800|
|| ||Ingo Molnar <mingo-AT-kernel.org>,
Linux Kernel Mailing List <linux-kernel-AT-vger.kernel.org>,
Arnaldo Carvalho de Melo <acme-AT-infradead.org>,
Peter Zijlstra <a.p.zijlstra-AT-chello.nl>,
Thomas Gleixner <tglx-AT-linutronix.de>,
Andrew Morton <akpm-AT-linux-foundation.org>|
|| ||Article, Thread
On Wed, Dec 12, 2012 at 8:31 PM, David Ahern <email@example.com> wrote:
> See commit 26a4f3c0. But that was not enough.
Why? Make the people who run virtualization do the extra work. Things
never worked for them anyway, so forcing *them* to set a flag to get a
working thing is sane.
Forcing everybody else to set a flag is insane. See?
Your "that was not enough" is insane. It's purely about which *default
convention* you choose. The "if (!event->attr.exclude_guest)" test is
the wrong default convention, and it *should* have been "if
(event->attr.include_guest)" with the virtualization people forced to
Claiming that there is some hardware overrun is silly, since that's
totally *independent* of the choice of which way the flag works!
> Requiring exclude_guest was
> another required piece. If you want to see the discussion:
The only thing that discussion shows is that people were *AWARE* that
this was a stupid change. I see Peter pointing out that this breaks
peoples existing working setups.
You broke the WORKING case for old binaries in order to give an error
return in a case that NEVER EVEN WORKED with those binaries. Don't you
see how insane that is?
The 'H' flag is totally the wrong way around. Exactly because it only
"fixes" a case that was already working, and makes a case that never
worked anyway now return an error value. That's not sane. Since the
old broken case never worked, nobody can have depended on it. See why
I'm saying that it's the people who use virtualization who should be
forced to use the new flag, not the other way around?
to post comments)