All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Keir Fraser <keir@xen.org>, Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86: Don't honour ACPI indicating absence of CMOS RTC
Date: Tue, 17 Jun 2014 11:47:10 -0400	[thread overview]
Message-ID: <20140617154710.GB7205@laptop.dumpdata.com> (raw)
In-Reply-To: <53A07700020000780001B26F@mail.emea.novell.com>

On Tue, Jun 17, 2014 at 04:12:32PM +0100, Jan Beulich wrote:
> >>> On 17.06.14 at 16:58, <andrew.cooper3@citrix.com> wrote:
> > This reverts f74556693 "x86: honor ACPI indicating absence of CMOS RTC"
> > 
> > Certain HP Gen8 BIOSes have started setting this bit despite an RTC CMOS 
> > being present and working.
> > 
> > Their reasonsing is to prevent EFI-booted OSes from playing with the CMOS,
> > combined with the erroneous assumption that the only OSes using legacy boot
> > are too old to know about ACPI v5 and therefore to understand this bit.
> 
> Which implies you can boot from EFI on those systems, which is
> precisely what the panic message says you ought to do. Why do
> you not boot via EFI in the first place?

You can swap between legacy and EFI in the BIOS. Customers can choose
either option.

> 
> > As a result, the change being reverted prevented modern Xen from booting on
> > modern HP hardware, despite older Xen working perfectly fine on the same
> > hardware.
> 
> Still, the flag has a purpose, and HP assigning a slightly non-standard
> meaning to it doesn't mean we should outright revert that change.
> Options I could live with (short of them revisiting the bogus assumption)
> are
> - a command line option suppressing the mandated behavior,
> - a DMI quirk suppressing the mandated behavior,
> - code probing for a functional CMOS RTC gating the panic()
>   invocation.

That is probably the best option. The DMI is going to get large
as it would probably include the G8 family.
> 
> Jan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2014-06-17 15:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17 14:58 [PATCH] x86: Don't honour ACPI indicating absence of CMOS RTC Andrew Cooper
2014-06-17 15:12 ` Jan Beulich
2014-06-17 15:47   ` Konrad Rzeszutek Wilk [this message]
2014-06-17 16:01     ` Jan Beulich
2014-06-17 16:31       ` Konrad Rzeszutek Wilk
2014-06-18 12:00         ` Jan Beulich
2014-06-18 13:06           ` Konrad Rzeszutek Wilk
2014-06-18 13:40             ` Jan Beulich
2014-06-17 17:01   ` Andrew Cooper
2014-06-18 12:02     ` 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=20140617154710.GB7205@laptop.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=keir@xen.org \
    --cc=xen-devel@lists.xen.org \
    /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.