From: Paolo Bonzini <pbonzini@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
acme@kernel.org
Subject: Re: [PATCH] tools lib traceevent: update KVM plugin
Date: Tue, 20 Oct 2015 17:49:22 +0200 [thread overview]
Message-ID: <56266282.3040109@redhat.com> (raw)
In-Reply-To: <20151020114811.772dff41@gandalf.local.home>
On 20/10/2015 17:48, Steven Rostedt wrote:
> On Tue, 20 Oct 2015 17:37:43 +0200
> Paolo Bonzini <pbonzini@redhat.com> wrote:
>
>> However, it frankly seems a bit academic. The parsing _will_ work,
>> apart from printing a nonsensical role just like it has always done for
>> the past four years.
>
> I'm not going to be too picky about it. But things like this may seem
> academic, but it's also what we forget about, and people still use
> 2.6.32 kernels, and this may come back and bite us later.
>
> But it's more likely to bite you than me, so if you don't think it's
> worth while, then I'm not going to push it.
Thanks. The role is not going to matter except in really weird cases
and hopefully those are just not there in 2.6.32 kernels. Thanks also
for educating me so I won't get it wrong in the future!
Paolo
next prev parent reply other threads:[~2015-10-20 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 10:28 [PATCH] tools lib traceevent: update KVM plugin Paolo Bonzini
2015-10-09 20:10 ` Paolo Bonzini
2015-10-20 14:32 ` Arnaldo Carvalho de Melo
2015-10-20 14:44 ` Steven Rostedt
2015-10-20 15:19 ` Paolo Bonzini
2015-10-20 15:26 ` Steven Rostedt
2015-10-20 15:37 ` Paolo Bonzini
2015-10-20 15:48 ` Steven Rostedt
2015-10-20 15:49 ` Paolo Bonzini [this message]
2015-10-20 15:50 ` Arnaldo Carvalho de Melo
2015-10-20 16:21 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56266282.3040109@redhat.com \
--to=pbonzini@redhat.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).