mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Len Brown <lenb@kernel.org>
Subject: Re: [Update][PATCH] ACPI: Rework acpi_get_child() to be more efficient
Date: Fri, 04 Jan 2013 22:38:51 +0100	[thread overview]
Message-ID: <6591808.qVVzyd5JNI@vostro.rjw.lan> (raw)
In-Reply-To: <14285317.C5USrgceVP@vostro.rjw.lan>

On Wednesday, December 26, 2012 11:42:49 PM Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Subject: ACPI: Rework acpi_get_child() to be more efficient
> 
> Observe that acpi_get_child() doesn't need to use the helper
> struct acpi_find_child structure and change it to work without it.
> Also, using acpi_get_object_info() to get the output of _ADR for the
> given device is overkill, because that function does much more than
> just evaluating _ADR (let alone the additional memory allocation
> done by it).
> 
> Moreover, acpi_get_child() doesn't need to loop any more once it has
> found a matching handle, so make it stop in that case.  To prevent
> the results from changing, make it use do_acpi_find_child() as
> a post-order callback.
> 
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
> 
> The difference from the previous version is the replacement of
> acpi_get_object_info() with the direct execution of _ADR, which is
> more straightforward.

There seem to be no objections, most likely due to the holiday period
that has just ended, but if there are still none, I'm going to push this
for v3.9.

Thanks,
Rafael


> ---
>  drivers/acpi/glue.c |   33 ++++++++++++---------------------
>  1 file changed, 12 insertions(+), 21 deletions(-)
> 
> Index: linux/drivers/acpi/glue.c
> ===================================================================
> --- linux.orig/drivers/acpi/glue.c
> +++ linux/drivers/acpi/glue.c
> @@ -93,40 +93,31 @@ static int acpi_find_bridge_device(struc
>  	return ret;
>  }
>  
> -/* Get device's handler per its address under its parent */
> -struct acpi_find_child {
> -	acpi_handle handle;
> -	u64 address;
> -};
> -
> -static acpi_status
> -do_acpi_find_child(acpi_handle handle, u32 lvl, void *context, void **rv)
> +static acpi_status do_acpi_find_child(acpi_handle handle, u32 lvl_not_used,
> +				      void *addr_p, void **ret_p)
>  {
> +	unsigned long long addr;
>  	acpi_status status;
> -	struct acpi_device_info *info;
> -	struct acpi_find_child *find = context;
>  
> -	status = acpi_get_object_info(handle, &info);
> -	if (ACPI_SUCCESS(status)) {
> -		if ((info->address == find->address)
> -			&& (info->valid & ACPI_VALID_ADR))
> -			find->handle = handle;
> -		kfree(info);
> +	status = acpi_evaluate_integer(handle, METHOD_NAME__ADR, NULL, &addr);
> +	if (ACPI_SUCCESS(status) && addr == *((u64 *)addr_p)) {
> +		*ret_p = handle;
> +		return AE_CTRL_TERMINATE;
>  	}
>  	return AE_OK;
>  }
>  
>  acpi_handle acpi_get_child(acpi_handle parent, u64 address)
>  {
> -	struct acpi_find_child find = { NULL, address };
> +	void *ret = NULL;
>  
>  	if (!parent)
>  		return NULL;
> -	acpi_walk_namespace(ACPI_TYPE_DEVICE, parent,
> -			    1, do_acpi_find_child, NULL, &find, NULL);
> -	return find.handle;
> -}
>  
> +	acpi_walk_namespace(ACPI_TYPE_DEVICE, parent, 1, NULL,
> +			    do_acpi_find_child, &address, &ret);
> +	return (acpi_handle)ret;
> +}
>  EXPORT_SYMBOL(acpi_get_child);
>  
>  static int acpi_bind_one(struct device *dev, acpi_handle handle)
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

      reply	other threads:[~2013-01-04 21:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19 11:27 [PATCH] " Rafael J. Wysocki
2012-12-26 22:42 ` [Update][PATCH] " Rafael J. Wysocki
2013-01-04 21:38   ` Rafael J. Wysocki [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=6591808.qVVzyd5JNI@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®