From: Jan Kiszka <jan.kiszka@web.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH] trace-cmd: Fix reporting of unknown SVM exit reasons
Date: Wed, 1 Jun 2016 12:06:40 +0200 [thread overview]
Message-ID: <574EB3B0.7060304@web.de> (raw)
In-Reply-To: <20160531112321.0c7897a4@grimm.local.home>
On 2016-05-31 17:23, Steven Rostedt wrote:
> On Sun, 22 May 2016 18:02:31 +0200
> Jan Kiszka <jan.kiszka@web.de> wrote:
>
> Hi Jan,
>
> I finally got around to looking at your patches (not much to do on a 12
> hour layover :-p).
>
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> On AMD, exist code -1 is also a possible value, but we use it for
>> terminating the list of known exit reasons. This leads to EXIT_ERR
>> being reported for unkown ones. Fix this by using an NULL string
>> pointer as terminal.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>> plugin_kvm.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/plugin_kvm.c b/plugin_kvm.c
>> index 15a6f4c..99e920f 100644
>> --- a/plugin_kvm.c
>> +++ b/plugin_kvm.c
>> @@ -208,12 +208,12 @@ struct str_values {
>>
>> static struct str_values vmx_exit_reasons[] = {
>> VMX_EXIT_REASONS
>> - { NULL, -1}
>> + { }
>
> Just a preference, but I would rather this still explicitly show the
> NULL. The second value is meaningless with the change below. Thus, I'm
> going to nuke these two hunks and just add the last one, which should
> still work for you.
Fine for me.
Thanks,
Jan
>
> If not, let me know, or just tell me this weekend ;-) (I wont be
> pushing this to my main server till I get back anyway)
>
> -- Steve
>
>> };
>>
>> static struct str_values svm_exit_reasons[] = {
>> SVM_EXIT_REASONS
>> - { NULL, -1}
>> + { }
>> };
>>
>> static struct isa_exit_reasons {
>> @@ -237,7 +237,7 @@ static const char *find_exit_reason(unsigned isa, int val)
>> }
>> if (!strings)
>> return "UNKNOWN-ISA";
>> - for (i = 0; strings[i].val >= 0; i++)
>> + for (i = 0; strings[i].str; i++)
>> if (strings[i].val == val)
>> break;
>>
>
prev parent reply other threads:[~2016-06-01 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-22 16:02 [PATCH] trace-cmd: Fix reporting of unknown SVM exit reasons Jan Kiszka
2016-05-31 15:23 ` Steven Rostedt
2016-06-01 10:06 ` Jan Kiszka [this message]
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=574EB3B0.7060304@web.de \
--to=jan.kiszka@web.de \
--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