From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Matt Fleming <matt@console-pimps.org>
Cc: linux-kernel@vger.kernel.org,
Matt Fleming <matt.fleming@linux.intel.com>,
Jan Beulich <JBeulich@novell.com>,
Matthew Garrett <mjg@redhat.com>, Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Alessandro Zummo <a.zummo@towertech.it>
Subject: Re: [PATCH] x86, efi: Don't recursively acquire rtc_lock
Date: Wed, 03 Aug 2011 16:12:31 -0700 [thread overview]
Message-ID: <4E39D5DF.6010104@linux.intel.com> (raw)
In-Reply-To: <1312405454-29386-1-git-send-email-matt@console-pimps.org>
On 08/03/2011 02:04 PM, Matt Fleming wrote:
> From: Matt Fleming <matt.fleming@linux.intel.com>
>
> A deadlock was introduced on x86 in commit ef68c8f87ed1 ("x86:
> Serialize EFI time accesses on rtc_lock") because efi_get_time() and
> friends can be called with rtc_lock already held by
> read_persistent_time(), e.g.
>
> timekeeping_init()
> read_persistent_clock() <-- acquire rtc_lock
> efi_get_time()
> phys_efi_get_time() <-- acquire rtc_lock <DEADLOCK>
>
> Move the locking up into the caller of efi.get_time() and provide some
> wrappers for use in other parts of the kernel instead of calling
> efi.get_time(), etc directly. This way we can hide the rtc_lock dance
> inside of arch/x86.
>
> Cc: Jan Beulich <JBeulich@novell.com>
> Cc: Matthew Garrett <mjg@redhat.com>
> Cc: "H. Peter Anvin" <hpa@linux.intel.com>
> Cc: Tony Luck <tony.luck@intel.com>
> Cc: Fenghua Yu <fenghua.yu@intel.com>
> Cc: Alessandro Zummo <a.zummo@towertech.it>
> Signed-off-by: Matt Fleming <matt.fleming@linux.intel.com>
For the x86 footprint:
Acked-by: H. Peter Anvin <hpa@linux.intel.com>
next prev parent reply other threads:[~2011-08-03 23:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 21:04 [PATCH] x86, efi: Don't recursively acquire rtc_lock Matt Fleming
2011-08-03 23:10 ` Tony Luck
2011-08-03 23:12 ` H. Peter Anvin [this message]
2011-08-04 10:22 ` john stultz
2011-08-04 10:36 ` Matt Fleming
2011-08-04 11:36 ` Matthew Garrett
-- strict thread matches above, loose matches on Subject: below --
2011-08-04 2:53 Jan Beulich
2011-08-04 3:04 ` Matthew Garrett
2011-08-04 9:33 ` Matt Fleming
2011-08-05 17:02 Jan Beulich
2011-08-05 17:04 Jan Beulich
2011-08-08 13:40 ` Matt Fleming
2011-08-08 14:07 ` Jan Beulich
2011-08-10 9:03 ` Ingo Molnar
2011-08-10 9:36 ` Jan Beulich
2011-08-10 9:51 ` Ingo Molnar
2011-08-10 13:12 ` Jan Beulich
2011-08-15 18:18 ` Matt Fleming
2011-08-16 6:22 ` Jan Beulich
2011-08-16 9:14 ` Matt Fleming
2011-08-30 15:45 ` Matthew Garrett
2011-08-30 16:07 ` Matt Fleming
2011-08-30 18:27 ` H. Peter Anvin
2011-08-10 14:55 ` Jan Beulich
2011-08-08 14:18 ` Avi Kivity
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=4E39D5DF.6010104@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=JBeulich@novell.com \
--cc=a.zummo@towertech.it \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@linux.intel.com \
--cc=matt@console-pimps.org \
--cc=mjg@redhat.com \
--cc=tony.luck@intel.com \
/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