From: Matthew Garrett <mjg59@srcf.ucam.org>
To: john stultz <johnstul@us.ibm.com>
Cc: Matt Fleming <matt@console-pimps.org>,
linux-kernel@vger.kernel.org,
Matt Fleming <matt.fleming@linux.intel.com>,
Jan Beulich <JBeulich@novell.com>,
"H. Peter Anvin" <hpa@linux.intel.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: Thu, 4 Aug 2011 12:36:56 +0100 [thread overview]
Message-ID: <20110804113655.GA30077@srcf.ucam.org> (raw)
In-Reply-To: <CANcMJZDqYJHTTPifrxr7cDVA_S+PRwy6AzjO-54ucvpnyoRADA@mail.gmail.com>
On Thu, Aug 04, 2011 at 03:22:24AM -0700, john stultz wrote:
> Sorry if this should be obvious, but is there a reason your not using
> your own internal lock for serializing the efi bits rather then using
> the rtc_lock?
On x86 systems the EFI clock is almost certainly the AT RTC, so it's
necessary to serialise accesses between EFI and the traditional clock
interface.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2011-08-04 11:37 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
2011-08-04 10:22 ` john stultz
2011-08-04 10:36 ` Matt Fleming
2011-08-04 11:36 ` Matthew Garrett [this message]
-- 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=20110804113655.GA30077@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=JBeulich@novell.com \
--cc=a.zummo@towertech.it \
--cc=fenghua.yu@intel.com \
--cc=hpa@linux.intel.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@linux.intel.com \
--cc=matt@console-pimps.org \
--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 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.