From: Toshi Kani <toshi.kani@hp.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
linux-mm@kvack.org
Subject: Re: [PATCH 1/3] ACPI / scan: Change ordering of locks for device hotplug
Date: Fri, 30 Aug 2013 18:17:37 -0600 [thread overview]
Message-ID: <1377908257.10300.896.camel@misato.fc.hp.com> (raw)
In-Reply-To: <1752041.76DW3TEE1A@vostro.rjw.lan>
On Thu, 2013-08-29 at 23:15 +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> Change the ordering of device hotplug locks in scan.c so that
> acpi_scan_lock is always acquired after device_hotplug_lock.
>
> This will make it possible to use device_hotplug_lock around some
> code paths that acquire acpi_scan_lock safely (most importantly
> system suspend and hibernation). Apart from that, acpi_scan_lock
> is platform-specific and device_hotplug_lock is general, so the
> new ordering appears to be more appropriate from the overall
> design viewpoint.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Toshi Kani <toshi.kani@hp.com>
Thanks,
-Toshi
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Toshi Kani <toshi.kani@hp.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
linux-mm@kvack.org
Subject: Re: [PATCH 1/3] ACPI / scan: Change ordering of locks for device hotplug
Date: Fri, 30 Aug 2013 18:17:37 -0600 [thread overview]
Message-ID: <1377908257.10300.896.camel@misato.fc.hp.com> (raw)
In-Reply-To: <1752041.76DW3TEE1A@vostro.rjw.lan>
On Thu, 2013-08-29 at 23:15 +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> Change the ordering of device hotplug locks in scan.c so that
> acpi_scan_lock is always acquired after device_hotplug_lock.
>
> This will make it possible to use device_hotplug_lock around some
> code paths that acquire acpi_scan_lock safely (most importantly
> system suspend and hibernation). Apart from that, acpi_scan_lock
> is platform-specific and device_hotplug_lock is general, so the
> new ordering appears to be more appropriate from the overall
> design viewpoint.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Toshi Kani <toshi.kani@hp.com>
Thanks,
-Toshi
next prev parent reply other threads:[~2013-08-31 0:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 21:12 [PATCH 0/3] ACPI / hotplug / mm: Rework mutual exclusion between hibernation and memory hotplug Rafael J. Wysocki
2013-08-29 21:12 ` Rafael J. Wysocki
2013-08-29 21:15 ` [PATCH 1/3] ACPI / scan: Change ordering of locks for device hotplug Rafael J. Wysocki
2013-08-29 21:15 ` Rafael J. Wysocki
2013-08-31 0:17 ` Toshi Kani [this message]
2013-08-31 0:17 ` Toshi Kani
2013-08-29 21:17 ` [PATCH 2/3] PM / hibernate: Create memory bitmaps after freezing user space Rafael J. Wysocki
2013-08-29 21:17 ` Rafael J. Wysocki
2013-08-29 21:18 ` [PATCH 3/3] PM / hibernate / memory hotplug: Rework mutual exclusion Rafael J. Wysocki
2013-08-29 21:18 ` Rafael J. Wysocki
2013-08-31 0:23 ` Toshi Kani
2013-08-31 0:23 ` Toshi Kani
2013-08-31 0:39 ` Rafael J. Wysocki
2013-08-31 0:39 ` Rafael J. Wysocki
2013-08-31 0:35 ` Toshi Kani
2013-08-31 0:35 ` Toshi Kani
2013-08-31 0:50 ` Rafael J. Wysocki
2013-08-31 0:50 ` Rafael J. Wysocki
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=1377908257.10300.896.camel@misato.fc.hp.com \
--to=toshi.kani@hp.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.