mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	hpa@linux.intel.com, Avi Kivity <avi@redhat.com>,
	mjg@redhat.com, MarceloTosatti <mtosatti@redhat.com>,
	johnstultz <johnstul@us.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86, efi: Don't recursively acquire rtc_lock
Date: Tue, 16 Aug 2011 10:14:28 +0100	[thread overview]
Message-ID: <1313486068.3436.116.camel@mfleming-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <4E4A28AE0200007800051605@nat28.tlf.novell.com>

On Tue, 2011-08-16 at 07:22 +0100, Jan Beulich wrote:
> >>> On 15.08.11 at 20:18, Matt Fleming <matt@console-pimps.org> wrote:
> > On Wed, 2011-08-10 at 14:12 +0100, Jan Beulich wrote:
> >> Bottom line - the fix here is needed for 32-bit booting only (and
> >> hence isn't - afaic - as critical as I first thought). But the adjustment
> >> I'm holding is a necessary one (and I don't even understand why,
> >> when 32- and 64-bit EFI code got merged, this was left 32-bit only),
> >> and the NX consolidation change needs to be fixed too (basically as
> >> a prerequisite).
> > 
> > But the rtc-lock patch is independent and can be merged on its own,
> > right? Sure the other issues need fixing but there's no sense in holding
> > up the rtc-lock patch, since with it applied my machine actually boots.
> 
> Oh, yes, absolutely - I'm actually waiting for this one to get applied so
> that the enabling of the use of the EFI RTC routines on x86-64 won't
> cause the same problem there.

OK cool, thanks Jan. I suspect Ingo will pick this up, or Thomas once
he's worked through his email backlog ;-)

-- 
Matt Fleming, Intel Open Source Technology Center


  reply	other threads:[~2011-08-16  9:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2011-08-05 17:02 Jan Beulich
2011-08-04  2:53 Jan Beulich
2011-08-04  3:04 ` Matthew Garrett
2011-08-04  9:33 ` Matt Fleming
2011-08-03 21:04 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

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=1313486068.3436.116.camel@mfleming-mobl1.ger.corp.intel.com \
    --to=matt@console-pimps.org \
    --cc=JBeulich@novell.com \
    --cc=avi@redhat.com \
    --cc=hpa@linux.intel.com \
    --cc=jeremy.fitzhardinge@citrix.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mjg@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=tglx@linutronix.de \
    /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®