From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, Keir Fraser <keir@xen.org>
Subject: Re: [PATCH] x86: detect CMOS aliasing on ports other then 0x70/0x71
Date: Tue, 29 Sep 2015 14:25:17 +0100 [thread overview]
Message-ID: <560A913D.2050605@citrix.com> (raw)
In-Reply-To: <5605455702000078000A58C6@prv-mh.provo.novell.com>
On 25/09/15 12:00, Jan Beulich wrote:
>>>> On 25.09.15 at 11:55, <andrew.cooper3@citrix.com> wrote:
>> It is safe for the SMM handler to use CMOS if it returns the index
>> register back to how it found it. Furthermore, I am willing to bet that
>> there real SMM handlers out there which do do this.
> So what options do you see then here? Don't do anything (drop the
> patch) seems the only one I can see not getting in conflict with SMI.
> Yet using the patch as is would not make anything less safe, it would
> just have the potential of not always making things as safe as they
> could be.
Given some orthogonal interaction with cmos-rtc-probe recently, I am
fairly sure that we can remove all real RTC interaction from Xen.
Dom0 is required to provide fine-grained time via XENPF_settime{32,64}
which gives an absolute time to seed the other domain wallclocks with.
The RTC was assumed always to be in UTC, which allows full date and time
information to be derived.
It would certainly simplify things to leave all of the RTC in dom0's hand.
~Andrew
next prev parent reply other threads:[~2015-09-29 13:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 13:10 [PATCH] x86: detect CMOS aliasing on ports other then 0x70/0x71 Jan Beulich
2015-09-23 18:34 ` Andrew Cooper
2015-09-24 8:11 ` Jan Beulich
2015-09-25 9:55 ` Andrew Cooper
2015-09-25 11:00 ` Jan Beulich
2015-09-29 13:25 ` Andrew Cooper [this message]
2015-09-29 13:42 ` 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=560A913D.2050605@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xenproject.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.