linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Gavin Shan <gshan@redhat.com>
Cc: mark.rutland@arm.com, catalin.marinas@arm.com,
	james.morse@arm.com, shan.gavin@gmail.com, will@kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 14/17] drivers/firmware/sdei: Move struct sdei_event to header file
Date: Thu, 23 Jul 2020 16:19:49 +0100	[thread overview]
Message-ID: <20200723161949.00000061@Huawei.com> (raw)
In-Reply-To: <20200722095740.28560-15-gshan@redhat.com>

On Wed, 22 Jul 2020 19:57:37 +1000
Gavin Shan <gshan@redhat.com> wrote:

> This moves struct sdei_event to the header file so that it can be
> dereferenced by external modules. This is needed by the code to
> virtualize SDEI functionality, as part of the arm64/kvm.
> 
> Signed-off-by: Gavin Shan <gshan@redhat.com>
Hi Gavin,

One question inline.

Jonathan

> ---
> v2: Derived from "drivers/firmware/sdei: Identify event by struct"
> ---
>  drivers/firmware/arm_sdei.c | 20 ------------
>  include/linux/arm_sdei.h    | 61 ++++++++++++++++++++++++-------------
>  2 files changed, 40 insertions(+), 41 deletions(-)
> 
> diff --git a/drivers/firmware/arm_sdei.c b/drivers/firmware/arm_sdei.c
> index a52dcff59a20..bdd2de0149c0 100644
> --- a/drivers/firmware/arm_sdei.c
> +++ b/drivers/firmware/arm_sdei.c
> @@ -44,26 +44,6 @@ static asmlinkage void (*sdei_firmware_call)(unsigned long function_id,
>  /* entry point from firmware to arch asm code */
>  static unsigned long sdei_entry_point;
>  
> -struct sdei_event {
> -	/* These three are protected by the sdei_list_lock */
> -	struct list_head	list;
> -	bool			reregister;
> -	bool			reenable;
> -
> -	u32			event_num;
> -	u8			type;
> -	u8			priority;
> -
> -	/* This pointer is handed to firmware as the event argument. */
> -	union {
> -		/* Shared events */
> -		struct sdei_registered_event *registered;
> -
> -		/* CPU private events */
> -		struct sdei_registered_event __percpu *private_registered;
> -	};
> -};
> -
>  /* Take the mutex for any API call or modification. Take the mutex first. */
>  static DEFINE_MUTEX(sdei_events_lock);
>  
> diff --git a/include/linux/arm_sdei.h b/include/linux/arm_sdei.h
> index 0a241c5c911d..fdc2f868d84b 100644
> --- a/include/linux/arm_sdei.h
> +++ b/include/linux/arm_sdei.h
> @@ -22,6 +22,46 @@
>   */
>  typedef int (sdei_event_callback)(u32 event, struct pt_regs *regs, void *arg);
>  
> +/*
> + * This struct represents an event that has been registered. The driver
> + * maintains a list of all events, and which ones are registered. (Private
> + * events have one entry in the list, but are registered on each CPU).
> + * A pointer to this struct is passed to firmware, and back to the event
> + * handler. The event handler can then use this to invoke the registered
> + * callback, without having to walk the list.
> + *
> + * For CPU private events, this structure is per-cpu.
> + */
> +struct sdei_registered_event {
> +	/* For use by arch code: */
> +	struct pt_regs          interrupted_regs;
> +
> +	sdei_event_callback	*callback;
> +	void			*callback_arg;
> +	u32			 event_num;
> +	u8			 priority;
> +};
> +
> +struct sdei_event {
> +	/* These three are protected by the sdei_list_lock */

As this patch leaves the sdei_list_lock as local to arm_sdei.c, is this comment still valid?

> +	struct list_head	list;
> +	bool			reregister;
> +	bool			reenable;
> +
> +	u32			event_num;
> +	u8			type;
> +	u8			priority;
> +
> +	/* This pointer is handed to firmware as the event argument. */
> +	union {
> +		/* Shared events */
> +		struct sdei_registered_event *registered;
> +
> +		/* CPU private events */
> +		struct sdei_registered_event __percpu *private_registered;
> +	};
> +};
> +
>  /*
>   * Register your callback to claim an event. The event must be described
>   * by firmware.
> @@ -51,27 +91,6 @@ static inline int sdei_mask_local_cpu(void) { return 0; }
>  static inline int sdei_unmask_local_cpu(void) { return 0; }
>  #endif /* CONFIG_ARM_SDE_INTERFACE */
>  
> -
> -/*
> - * This struct represents an event that has been registered. The driver
> - * maintains a list of all events, and which ones are registered. (Private
> - * events have one entry in the list, but are registered on each CPU).
> - * A pointer to this struct is passed to firmware, and back to the event
> - * handler. The event handler can then use this to invoke the registered
> - * callback, without having to walk the list.
> - *
> - * For CPU private events, this structure is per-cpu.
> - */
> -struct sdei_registered_event {
> -	/* For use by arch code: */
> -	struct pt_regs          interrupted_regs;
> -
> -	sdei_event_callback	*callback;
> -	void			*callback_arg;
> -	u32			 event_num;
> -	u8			 priority;
> -};
> -
>  /* The arch code entry point should then call this when an event arrives. */
>  int notrace sdei_event_handler(struct pt_regs *regs,
>  			       struct sdei_registered_event *arg);



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-07-23 15:22 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22  9:57 [PATCH v2 00/17] Refactor SDEI client driver Gavin Shan
2020-07-22  9:57 ` [PATCH v2 01/17] drivers/firmware/sdei: Remove sdei_is_err() Gavin Shan
2020-07-22  9:57 ` [PATCH v2 02/17] drivers/firmware/sdei: Common block for failing path in sdei_event_create() Gavin Shan
2020-07-22  9:57 ` [PATCH v2 03/17] drivers/firmware/sdei: Retrieve event number from event instance Gavin Shan
2020-07-22  9:57 ` [PATCH v2 04/17] drivers/firmware/sdei: Avoid nested statements in sdei_init() Gavin Shan
2020-07-22  9:57 ` [PATCH v2 05/17] drivers/firmware/sdei: Unregister driver on error " Gavin Shan
2020-07-22  9:57 ` [PATCH v2 06/17] drivers/firmware/sdei: Remove duplicate check in sdei_get_conduit() Gavin Shan
2020-07-22  9:57 ` [PATCH v2 07/17] drivers/firmware/sdei: Remove Drop redundant error message in sdei_probe() Gavin Shan
2020-07-22  9:57 ` [PATCH v2 08/17] drivers/firmware/sdei: Remove while loop in sdei_event_register() Gavin Shan
2020-07-22  9:57 ` [PATCH v2 09/17] drivers/firmware/sdei: Remove while loop in sdei_event_unregister() Gavin Shan
2020-07-23 15:51   ` Jonathan Cameron
2020-07-27  0:22     ` Gavin Shan
2020-07-22  9:57 ` [PATCH v2 10/17] drivers/firmware/sdei: Cleanup on cross call function Gavin Shan
2020-07-23 15:52   ` Jonathan Cameron
2020-07-27  0:33     ` Gavin Shan
2020-07-27  8:58       ` Jonathan Cameron
2020-07-27  9:45         ` Gavin Shan
2020-07-22  9:57 ` [PATCH v2 11/17] drivers/firmware/sdei: Introduce sdei_do_local_call() Gavin Shan
2020-07-23 15:25   ` Jonathan Cameron
2020-07-27  0:41     ` Gavin Shan
2020-07-22  9:57 ` [PATCH v2 12/17] drivers/firmware/sdei: Remove _sdei_event_register() Gavin Shan
2020-07-23 15:25   ` Jonathan Cameron
2020-07-27  0:42     ` Gavin Shan
2020-07-22  9:57 ` [PATCH v2 13/17] drivers/firmware/sdei: Remove _sdei_event_unregister() Gavin Shan
2020-07-22  9:57 ` [PATCH v2 14/17] drivers/firmware/sdei: Move struct sdei_event to header file Gavin Shan
2020-07-23 15:19   ` Jonathan Cameron [this message]
2020-07-27  0:46     ` Gavin Shan
2020-07-27  9:02       ` Jonathan Cameron
2020-07-27  9:59         ` Gavin Shan
2020-07-27 13:50           ` Jonathan Cameron
2020-07-28  2:52             ` Gavin Shan
2020-07-22  9:57 ` [PATCH v2 15/17] drivers/firmware/sdei: Identify event by struct sdei_event Gavin Shan
2020-07-22  9:57 ` [PATCH v2 16/17] drivers/firmware/sdei: Retrieve event signaled property on registration Gavin Shan
2020-07-23 15:24   ` Jonathan Cameron
2020-07-27  0:53     ` Gavin Shan
2020-07-27  9:04       ` Jonathan Cameron
2020-07-27 10:03         ` Gavin Shan
2020-07-27 13:56           ` Jonathan Cameron
2020-07-28  2:56             ` Gavin Shan
2020-07-22  9:57 ` [PATCH v2 17/17] drivers/firmware/sdei: Add sdei_event_get_info() Gavin Shan

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=20200723161949.00000061@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=catalin.marinas@arm.com \
    --cc=gshan@redhat.com \
    --cc=james.morse@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=shan.gavin@gmail.com \
    --cc=will@kernel.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).