diff mbox

[v2,07/12] hdat: Add new fields to proc_init_data structure

Message ID 1477751795-20128-8-git-send-email-hegdevasant@linux.vnet.ibm.com
State Accepted
Headers show

Commit Message

Vasant Hegde Oct. 29, 2016, 2:36 p.m. UTC
Latest spec added two new fields to proc_init_data structure.
I don't think we have to pass any data in these new fields.

Signed-off-by: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
---
 hdata/spira.h | 2 ++
 1 file changed, 2 insertions(+)

Comments

Stewart Smith Dec. 20, 2016, 6:15 a.m. UTC | #1
Vasant Hegde <hegdevasant@linux.vnet.ibm.com> writes:
> Latest spec added two new fields to proc_init_data structure.
> I don't think we have to pass any data in these new fields.
>
> Signed-off-by: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
> ---
>  hdata/spira.h | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/hdata/spira.h b/hdata/spira.h
> index dee9902..0a7a173 100644
> --- a/hdata/spira.h
> +++ b/hdata/spira.h
> @@ -205,6 +205,8 @@ struct proc_init_data {
>  	struct {
>  		__be64	nia;
>  		__be64	msr;
> +		__be64	nia_charm_time;
> +		__be64	msr_charm_time;
>  	} regs;
>  } __packed __align(0x10);

What is CHARM time?

Looks like this was added in v9.13a - is there any version in the
structure that indicates this change? How would we work out it's there
or not?
Stewart Smith Dec. 21, 2016, 4:33 a.m. UTC | #2
Vasant Hegde <hegdevasant@linux.vnet.ibm.com> writes:
> Latest spec added two new fields to proc_init_data structure.
> I don't think we have to pass any data in these new fields.
>
> Signed-off-by: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
> ---
>  hdata/spira.h | 2 ++
>  1 file changed, 2 insertions(+)

Merged to master as of 4c47f77b14879ecd5b248fdf0f69a3c4fa218001
diff mbox

Patch

diff --git a/hdata/spira.h b/hdata/spira.h
index dee9902..0a7a173 100644
--- a/hdata/spira.h
+++ b/hdata/spira.h
@@ -205,6 +205,8 @@  struct proc_init_data {
 	struct {
 		__be64	nia;
 		__be64	msr;
+		__be64	nia_charm_time;
+		__be64	msr_charm_time;
 	} regs;
 } __packed __align(0x10);