[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <877eoass40.fsf@concordia.ellerman.id.au>
Date: Fri, 11 May 2018 15:01:35 +1000
From: Michael Ellerman <mpe@...erman.id.au>
To: Alastair D'Silva <alastair@....ibm.com>,
linuxppc-dev@...ts.ozlabs.org
Cc: mikey@...ling.org, arnd@...db.de, linux-doc@...r.kernel.org,
malat@...ian.org, gregkh@...uxfoundation.org, corbet@....net,
vaibhav@...ux.vnet.ibm.com, npiggin@...il.com,
linux-kernel@...r.kernel.org, fbarrat@...ux.vnet.ibm.com,
aneesh.kumar@...ux.vnet.ibm.com, andrew.donnellan@....ibm.com,
pombredanne@...b.com, felix@...ux.vnet.ibm.com,
sukadev@...ux.vnet.ibm.com, Alastair D'Silva <alastair@...ilva.org>
Subject: Re: [PATCH v3 5/7] ocxl: Expose the thread_id needed for wait on POWER9
"Alastair D'Silva" <alastair@....ibm.com> writes:
> diff --git a/include/uapi/misc/ocxl.h b/include/uapi/misc/ocxl.h
> index 0af83d80fb3e..8d2748e69c84 100644
> --- a/include/uapi/misc/ocxl.h
> +++ b/include/uapi/misc/ocxl.h
> @@ -48,6 +48,15 @@ struct ocxl_ioctl_metadata {
> __u64 reserved[13]; // Total of 16*u64
> };
>
> +struct ocxl_ioctl_p9_wait {
> + __u16 thread_id; // The thread ID required to wake this thread
> + __u16 reserved1;
> + __u32 reserved2;
> + __u64 reserved3[3];
> +};
> +
> +};
> +
O_o
???
cheers
Powered by blists - more mailing lists