mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: "Matthew Garrett" <mjg59@srcf.ucam.org>
Cc: <mingo@elte.hu>, <tglx@linutronix.de>,
	<matt.fleming@linux.intel.com>, <linux-kernel@vger.kernel.org>,
	<hpa@zytor.com>
Subject: Re: [PATCH] x86-64: use EFI to deal with platform wall clock
Date: Fri, 25 May 2012 16:00:37 +0100	[thread overview]
Message-ID: <4FBFBAB5020000780008635F@nat28.tlf.novell.com> (raw)
In-Reply-To: <20120516123912.GA20990@srcf.ucam.org>

>>> On 16.05.12 at 14:39, Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> On Wed, May 16, 2012 at 01:18:28PM +0100, Jan Beulich wrote:
>> So I'm afraid if the patch as I provided it isn't acceptable, and
>> if the call to efi_enter_virtual_mode() can't be moved ahead
>> of the one to timekeeping_init(), this winds down to the whole
>> logic needing a re-write.
> 
> I have zero objection to this being cleaned up, but I don't know of any 
> obvious reason why we can't do enter_virtual_mode() earlier.

So this indeed works (moving enter_virual_mode() invocation
to the end of mm_init(), which seems to most logical place to
me) on the single system I can try this out on. I'll submit an
updated patch soon.

Jan


  parent reply	other threads:[~2012-05-25 15:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 12:18 Jan Beulich
2012-05-15 12:47 ` Matthew Garrett
2012-05-15 13:19   ` Jan Beulich
2012-05-15 13:20     ` Matthew Garrett
2012-05-16 12:18       ` Jan Beulich
2012-05-16 12:39         ` Matthew Garrett
2012-05-16 12:59           ` Jan Beulich
2012-05-16 13:07             ` Matthew Garrett
2012-05-17  8:31             ` Matt Fleming
2012-05-25 15:00           ` Jan Beulich [this message]
2012-05-25 15:20 Jan Beulich
2012-05-25 15:24 ` Matthew Garrett
2012-05-25 15:30   ` Jan Beulich
2012-05-25 15:34     ` Matthew Garrett
2012-06-06  9:47       ` Ingo Molnar
2012-05-26 10:26 ` Matt Fleming
2012-06-04  8:11   ` Jan Beulich

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=4FBFBAB5020000780008635F@nat28.tlf.novell.com \
    --to=jbeulich@suse.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@linux.intel.com \
    --cc=mingo@elte.hu \
    --cc=mjg59@srcf.ucam.org \
    --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®