x86/msr.c generalize to any input msr
Subsystems (3)
PATCH 1/1 x86/msr.c generalize to any input msr
If an MSR description is provided as input by the user, run the test against that MSR. This allows the user to run tests on custom MSR's.
Otherwise run all default tests.
--- x86/msr.c | 48 ++++++++++++++++++++++++++++++++++-------------- 1 file changed, 34 insertions(+), 14 deletions(-)
x86/msr.c +34 -14
@@ -3,6 +3,7 @@#include "libcflat.h" #include "processor.h" #include "msr.h" +#include <stdlib.h> struct msr_info {int index;
@@ -77,25 +78,44 @@ static void test_rdmsr_fault(struct msr_info *msr) "Expected #GP on RDSMR(%s), got vector %d", msr->name, vector); } +static void test_msr (struct msr_info *msr,bool is_64bit_host) +{ +if (is_64bit_host || !msr->is_64bit_only) { +test_msr_rw (msr, msr->value); + +/* +* The 64-bit only MSRs that take an address always perform +* canonical checks on both Intel and AMD. +*/ +if (msr->is_64bit_only && + msr->value == addr_64) +test_wrmsr_fault (msr,NONCANONICAL ); + }else { +test_wrmsr_fault (msr, msr->value); +test_rdmsr_fault (msr); + } +} +int main (int ac,char **av) {bool is_64bit_host =this_cpu_has (X86_FEATURE_LM );int i; -for (i =0 ; i <ARRAY_SIZE (msr_info); i++) { -if (is_64bit_host || !msr_info[i].is_64bit_only) { -test_msr_rw (&msr_info[i], msr_info[i].value); - -/* -* The 64-bit only MSRs that take an address always perform -* canonical checks on both Intel and AMD. -*/ -if (msr_info[i].is_64bit_only && - msr_info[i].value == addr_64) -test_wrmsr_fault (&msr_info[i],NONCANONICAL ); - }else { -test_wrmsr_fault (&msr_info[i], msr_info[i].value); -test_rdmsr_fault (&msr_info[i]); +if (ac ==4 ) { +char msr_name[16 ]; +int index =strtoul (av[1 ],NULL ,0x10 ); +snprintf (msr_name,sizeof (msr_name),"MSR:0x%x" , index); + +struct msr_info msr = { + .index = index, + .name = msr_name, + .is_64bit_only = !strcmp (av[3 ],"0" ), + .value =strtoul (av[2 ],NULL ,0x10 ) + }; +test_msr (&msr, is_64bit_host); + }else { +for (i =0 ; i <ARRAY_SIZE (msr_info); i++) { +test_msr (&msr_info[i], is_64bit_host); } }
Signature · 1 line
2.20.1
Hi Daniele!
Quoted 5 lines · yqwfh
If an MSR description is provided as input by the user, run the test against that MSR. This allows the user to run tests on custom MSR's.
Otherwise run all default tests.
This patch description is missing the rationale. It comes through lightly where you say "This allows the user to run tests on custom MSRs", but that still doesn't explain why you would need that functionality.
The most important piece to transmit in the patch description is always the "Why". Only after that it sorted, you move on to a quick "How".
Quoted 2 lines
Signed-off-by Daniele Ahmed <[email protected]>
Please send the email from the same account that your SoB line quotes :)
It usually also helps to CC people that worked on the same file before. Usually, get_maintainers.pl should extract that list automatically for you but I realized that there is no such file in the kvm-unit-tests tree even though we have a MAINTAINERS one.
Paolo, what is the method you'd prefer to determine who to CC on kvm-unit-tests submissions?
Quoted 28 lines
--- x86/msr.c | 48 ++++++++++++++++++++++++++++++++++-------------- 1 file changed, 34 insertions(+), 14 deletions(-)x86/msr.c +9
-0@@ -3,6 +3,7 @@#include "libcflat.h" #include "processor.h" #include "msr.h" +#include <stdlib.h> struct msr_info {int index;@@ -77,25 +78,44 @@ static void test_rdmsr_fault(struct msr_info *msr) "Expected #GP on RDSMR(%s), got vector %d", msr->name, vector); } +static void test_msr (struct msr_info *msr,bool is_64bit_host) +{ +if (is_64bit_host || !msr->is_64bit_only) { +test_msr_rw (msr, msr->value); + +/* +* The 64-bit only MSRs that take an address always perform +* canonical checks on both Intel and AMD.
x86/msr.c static void test_rdmsr_fault(struct msr_info *msr) · line 98
Quoted 10 lines
x86/msr.c +10
-0+*/ +if (msr->is_64bit_only && + msr->value == addr_64) +test_wrmsr_fault (msr,NONCANONICAL ); + }else { +test_wrmsr_fault (msr, msr->value); +test_rdmsr_fault (msr); + } +} +
I would prefer if you separate the "extract individual MSR logic into function" part from the "Add a new mode of operation to test a particular MSR" part into two separate patches. That way it's easier to review.
Quoted 10 lines
x86/msr.c +0
-5int main (int ac,char **av) {bool is_64bit_host =this_cpu_has (X86_FEATURE_LM );int i; -for (i =0 ; i <ARRAY_SIZE (msr_info); i++) { -if (is_64bit_host || !msr_info[i].is_64bit_only) { -test_msr_rw (&msr_info[i], msr_info[i].value); - -/*
x86/msr.c static void test_rdmsr_fault(struct msr_info *msr) · line 104
Quoted 10 lines
x86/msr.c +1
-9-* The 64-bit only MSRs that take an address always perform -* canonical checks on both Intel and AMD. -*/ -if (msr_info[i].is_64bit_only && - msr_info[i].value == addr_64) -test_wrmsr_fault (&msr_info[i],NONCANONICAL ); - }else { -test_wrmsr_fault (&msr_info[i], msr_info[i].value); -test_rdmsr_fault (&msr_info[i]); +if (ac ==4 ) {
This means you require 3 completely undocumented command line arguments, no? I'm sure even you as the author of this patch will forget what they are in 2 years :).
Shouldn't there be some documentation that explains users that and how they can use this special mode of operation somewhere?
x86/msr.c static void test_rdmsr_fault(struct msr_info *msr) · line 112
Quoted 8 lines
x86/msr.c +8
-0+char msr_name[16 ]; +int index =strtoul (av[1 ],NULL ,0x10 ); +snprintf (msr_name,sizeof (msr_name),"MSR:0x%x" , index); + +struct msr_info msr = { + .index = index, + .name = msr_name, + .is_64bit_only = !strcmp (av[3 ],"0" ),
Why do you need to pass this when you invoke the test manually?
x86/msr.c static void test_rdmsr_fault(struct msr_info *msr) · line 113
Quoted 1 line
x86/msr.c +1
-0+ .value = strtoul(av[2], NULL, 0x10)
Overall, the command line parsing is pretty ad hoc and wouldn't scale well with updates. Paolo, is there any common theme on command line argument passing? Do we do things like command line options? Help texts? Do we have something even remotely similar to getopt?
Thanks,
Alex
x86/msr.c static void test_rdmsr_fault(struct msr_info *msr) · line 121
Quoted 9 lines
x86/msr.c +5
-0+ }; +test_msr (&msr, is_64bit_host); + }else { +for (i =0 ; i <ARRAY_SIZE (msr_info); i++) { +test_msr (&msr_info[i], is_64bit_host); } }
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879
Paolo Bonzini
maintainerQuoted 3 lines · Alexander Graf
Usually, get_maintainers.pl should extract that list automatically for you but I realized that there is no such file in the kvm-unit-tests tree even though we have a
MAINTAINERSone.Paolo, what is the method you'd prefer to determine who to CC on kvm-unit-tests submissions?
Let's add a get_maintainers.pl script. We might also start accepting merge requests on gitlab though...
Paolo
PATCH v2 1/3 lib/string: Add stroull and strtoll
In reply to Alexander GrafFrom: Daniele Ahmed <[email protected]>
Add the two functions strtoull and strtoll.
This is in preparation for an update
in x86/msr.c to write 64b values
that are given as inputs as strings by
a user.
--- lib/stdlib.h | 2 ++ lib/string.c | 74 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 76 insertions(+)
lib/stdlib.h +2 -0
@@ -9,5 +9,7 @@long int strtol (const char *nptr,char **endptr,int base);unsigned long int strtoul (const char *nptr,char **endptr,int base); +long long int strtoll (const char *nptr,char **endptr,int base); +unsigned long long strtoull (const char *nptr,char **endptr,int base);#endif /* _STDLIB_H_ */
lib/string.c +74 -0
80 lines not on this page · raw message
Signature · 12 lines
2.32.0 Amazon Development Center Germany GmbH Krausenstr. 38 10117 Berlin Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B Sitz: Berlin Ust-ID: DE 289 237 879
PATCH v2 2/3 x86/msr.c refactor out generic test logic
From: Daniele Ahmed <[email protected]>
Move the generic MSR test logic to its own function.
--- x86/msr.c | 33 +++++++++++++++++++-------------- 1 file changed, 19 insertions(+), 14 deletions(-)
x86/msr.c +19 -14
@@ -77,26 +77,31 @@ static void test_rdmsr_fault(struct msr_info *msr) "Expected #GP on RDSMR(%s), got vector %d", msr->name, vector); } +static void test_msr (struct msr_info *msr,bool is_64bit_host) +{ +if (is_64bit_host || !msr->is_64bit_only) { +test_msr_rw (msr, msr->value); + +/* +* The 64-bit only MSRs that take an address always perform +* canonical checks on both Intel and AMD. +*/ +if (msr->is_64bit_only && + msr->value == addr_64) +test_wrmsr_fault (msr,NONCANONICAL ); + }else { +test_wrmsr_fault (msr, msr->value); +test_rdmsr_fault (msr); + } +} +int main (int ac,char **av) {bool is_64bit_host =this_cpu_has (X86_FEATURE_LM );int i;for (i =0 ; i <ARRAY_SIZE (msr_info); i++) { -if (is_64bit_host || !msr_info[i].is_64bit_only) { -test_msr_rw (&msr_info[i], msr_info[i].value); - -/* -* The 64-bit only MSRs that take an address always perform -* canonical checks on both Intel and AMD. -*/ -if (msr_info[i].is_64bit_only && - msr_info[i].value == addr_64) -test_wrmsr_fault (&msr_info[i],NONCANONICAL ); - }else { -test_wrmsr_fault (&msr_info[i], msr_info[i].value); -test_rdmsr_fault (&msr_info[i]); - } +test_msr (&msr_info[i], is_64bit_host); }return report_summary ();
Signature · 12 lines
2.32.0 Amazon Development Center Germany GmbH Krausenstr. 38 10117 Berlin Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B Sitz: Berlin Ust-ID: DE 289 237 879
Re: [kvm-unit-tests PATCH v2 2/3] [kvm-unit-tests PATCH] x86/msr.c refactor out generic test logic
Quoted 5 lines · On 27.09.21 17:30, [email protected] wrote:
From: Daniele Ahmed <[email protected]>
Move the generic MSR test logic to its own function.
Signed-off-by Daniele Ahmed <[email protected]>
Alex
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879
PATCH v2 3/3 x86/msr.c generalize to any input msr
In reply to [email protected]From: Daniele Ahmed <[email protected]>
If an MSR description is provided as input by the user, run the test against that MSR. This allows the user to run tests on custom MSR's.
Otherwise run all default tests.
This is to validate custom MSR handling in user space with an easy-to-use tool. This kvm-unit-test submodule is a perfect fit. I'm extending it with a mode that takes an MSR index and a value to test arbitrary MSR accesses.
--- x86/msr.c | 29 +++++++++++++++++++++++++++-- 1 file changed, 27 insertions(+), 2 deletions(-)
x86/msr.c +27 -2
@@ -3,6 +3,17 @@#include "libcflat.h" #include "processor.h" #include "msr.h" +#include <stdlib.h> + +/** +* This test allows two modes: +* 1. Default: the `msr_info' array contains the default test configurations +* 2. Custom: by providing command line arguments it is possible to test any MSR and value +* Parameters order: +* 1. msr index as a base 16 number +* 2. value as a base 16 number +* 3. "0" if the msr is available only in 64b hosts, any other string otherwise +*/ struct msr_info {int index;
@@ -100,8 +111,22 @@ int main(int ac, char **av)bool is_64bit_host =this_cpu_has (X86_FEATURE_LM );int i; -for (i =0 ; i <ARRAY_SIZE (msr_info); i++) { -test_msr (&msr_info[i], is_64bit_host); +if (ac ==4 ) { +char msr_name[16 ]; +int index =strtoul (av[1 ],NULL ,0x10 ); +snprintf (msr_name,sizeof (msr_name),"MSR:0x%x" , index); + +struct msr_info msr = { + .index = index, + .name = msr_name, + .is_64bit_only = !strcmp (av[3 ],"0" ), + .value =strtoull (av[2 ],NULL ,0x10 ) + }; +test_msr (&msr, is_64bit_host); + }else { +for (i =0 ; i <ARRAY_SIZE (msr_info); i++) { +test_msr (&msr_info[i], is_64bit_host); + } }return report_summary ();
Signature · 12 lines
2.32.0 Amazon Development Center Germany GmbH Krausenstr. 38 10117 Berlin Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B Sitz: Berlin Ust-ID: DE 289 237 879
Paolo Bonzini
maintainerQuoted 6 lines · On 27/09/21 17:30, [email protected] wrote:
From: Daniele Ahmed <[email protected]>
If an MSR description is provided as input by the user, run the test against that MSR. This allows the user to run tests on custom MSR's.
Quoted 8 lines
Otherwise run all default tests.
This is to validate custom MSR handling in user space with an easy-to-use tool. This kvm-unit-test submodule is a perfect fit. I'm extending it with a mode that takes an MSR index and a value to test arbitrary MSR accesses.
Signed-off-by Daniele Ahmed <[email protected]>
I don't understand; is this a debugging tool, or is it meant to be driven by another test suite?
I'm not sure this fits the purpose of kvm-unit-tests very well, though.
An alternative is BITS (https://github.com/biosbits/bits/), which is
relatively easy to use and comes with Python bindings to RDMSR/WRMSR.
Paolo
Hi Paolo,
This would be to test the handling of specific MSR's, both the purposes you mention.
It may not cover all possible cases. I'm extending the kvm unit tests for others who might have similar needs. I looked up BITS and it seems like it's been unmaintained for many years now (although it could still be useful). Let me know if you don't think this is the right place for this change. I've seen other tests that take custom values to be used inside the tests.
Thank you
On 28/09/2021, 17:37, "Paolo Bonzini" <[email protected]> wrote:
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
On 27/09/21 17:30, [email protected] wrote:
> From: Daniele Ahmed <[email protected]>
>
> If an MSR description is provided as input by the user, > run the test against that MSR. This allows the user to > run tests on custom MSR's.
>
> Otherwise run all default tests.
>
> This is to validate custom MSR handling in user space > with an easy-to-use tool. This kvm-unit-test submodule > is a perfect fit. I'm extending it with a mode that > takes an MSR index and a value to test arbitrary MSR accesses. >
> Signed-off-by: Daniele Ahmed <[email protected]>
I don't understand; is this a debugging tool, or is it meant to be driven by another test suite?
I'm not sure this fits the purpose of kvm-unit-tests very well, though.
An alternative is BITS (https://github.com/biosbits/bits/), which is
relatively easy to use and comes with Python bindings to RDMSR/WRMSR.
Paolo
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879
Paolo Bonzini
maintainerQuoted 6 lines · On 27/09/21 17:30, [email protected] wrote:
From: Daniele Ahmed <[email protected]>
If an MSR description is provided as input by the user, run the test against that MSR. This allows the user to run tests on custom MSR's.
Quoted 8 lines
Otherwise run all default tests.
This is to validate custom MSR handling in user space with an easy-to-use tool. This kvm-unit-test submodule is a perfect fit. I'm extending it with a mode that takes an MSR index and a value to test arbitrary MSR accesses.
Signed-off-by Daniele Ahmed <[email protected]>
Queued, thanks. I removed the "64-bit only" functionality because, for manual invocation, you can just not run the test when running on 32-bit targets.
Paolo
Quoted 52 lines
--- x86/msr.c | 29 +++++++++++++++++++++++++++-- 1 file changed, 27 insertions(+), 2 deletions(-)x86/msr.c +27
-2@@ -3,6 +3,17 @@#include "libcflat.h" #include "processor.h" #include "msr.h" +#include <stdlib.h> + +/** +* This test allows two modes: +* 1. Default: the `msr_info' array contains the default test configurations +* 2. Custom: by providing command line arguments it is possible to test any MSR and value +* Parameters order: +* 1. msr index as a base 16 number +* 2. value as a base 16 number +* 3. "0" if the msr is available only in 64b hosts, any other string otherwise +*/ struct msr_info {int index;@@ -100,8 +111,22 @@ int main(int ac, char **av)bool is_64bit_host =this_cpu_has (X86_FEATURE_LM );int i; -for (i =0 ; i <ARRAY_SIZE (msr_info); i++) { -test_msr (&msr_info[i], is_64bit_host); +if (ac ==4 ) { +char msr_name[16 ]; +int index =strtoul (av[1 ],NULL ,0x10 ); +snprintf (msr_name,sizeof (msr_name),"MSR:0x%x" , index); + +struct msr_info msr = { + .index = index, + .name = msr_name, + .is_64bit_only = !strcmp (av[3 ],"0" ), + .value =strtoull (av[2 ],NULL ,0x10 ) + }; +test_msr (&msr, is_64bit_host); + }else { +for (i =0 ; i <ARRAY_SIZE (msr_info); i++) { +test_msr (&msr_info[i], is_64bit_host); + } }return report_summary ();
Re: [kvm-unit-tests PATCH v2 1/3] lib/string: Add stroull and strtoll
In reply to [email protected]Quoted 115 lines · On Mon, Sep 27, 2021 at 03:30:26PM +0000, [email protected] wrote:
From: Daniele Ahmed <[email protected]>
Add the two functions strtoull and strtoll.
This is in preparation for an update
inx86/msr.cto write 64b values
that are given as inputs as strings by
a user.Signed-off-by Daniele Ahmed <[email protected]>--- lib/stdlib.h | 2 ++ lib/string.c | 74 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 76 insertions(+)lib/stdlib.h +2
-0@@ -9,5 +9,7 @@long int strtol (const char *nptr,char **endptr,int base);unsigned long int strtoul (const char *nptr,char **endptr,int base); +long long int strtoll (const char *nptr,char **endptr,int base); +unsigned long long strtoull (const char *nptr,char **endptr,int base);#endif /* _STDLIB_H_ */ lib/string.c +74
-0@@ -242,6 +242,80 @@ unsigned long int strtoul(const char *nptr, char **endptr, int base)return __strtol (nptr, endptr, base, false); } +static unsigned long long __strtoll (const char *nptr,char **endptr, +int base,bool is_signed) { +unsigned long long acc =0 ; +const char *s = nptr; +int neg, c; + +assert (base ==0 || (base >=2 && base <=36 )); + +while (isspace (*s)) + s++; + +if (*s =='-' ) { + neg =1 ; + s++; + }else { + neg =0 ; +if (*s =='+' ) + s++; + } + +if (base ==0 || base ==16 ) { +if (*s =='0' ) { + s++; +if (*s =='x' || *s =='X' ) { + s++; + base =16 ; + }else if (base ==0 ) + base =8 ; + }else if (base ==0 ) + base =10 ; + } + +while (*s) { +if (*s >='0' && *s <'0' + base && *s <='9' ) + c = *s -'0' ; +else if (*s >='a' && *s <'a' + base -10 ) + c = *s -'a' +10 ; +else if (*s >='A' && *s <'A' + base -10 ) + c = *s -'A' +10 ; +else +break ; + +if (is_signed) { +long long sacc = (long long )acc; +assert (!check_mul_overflow (sacc, base)); +assert (!check_add_overflow (sacc * base, c)); + }else { +assert (!check_mul_overflow (acc, base)); +assert (!check_add_overflow (acc * base, c)); + } + + acc = acc * base + c; + s++; + } + +if (neg) + acc = -acc; + +if (endptr) + *endptr = (char *)s; + +return acc; +} + +long long int strtoll (const char *nptr,char **endptr,int base) +{ +return __strtoll (nptr, endptr, base, true); +} + +unsigned long long int strtoull (const char *nptr,char **endptr,int base) +{ +return __strtoll (nptr, endptr, base, false); +} +long atol (const char *ptr) {return strtol (ptr,NULL ,10 );Signature · 1 line
2.32.0
Hi Daniele,
I just sent an alternative to this patch which doesn't requiring duplicating as much code.
Thanks,
drew
Quoted 12 lines
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879