From: Jan Beulich <jbeulich@suse.com>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Paul Durrant" <paul@xen.org>, "Wei Liu" <wl@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: [PATCH v3 0/2] x86: RTC handling adjustments
Date: Wed, 15 Jul 2020 13:54:36 +0200 [thread overview]
Message-ID: <5426dd6f-50cd-dc23-5c6b-0ab631d98d38@suse.com> (raw)
The first patch addresses a recent regression and hence ought to be
considered for 4.14, despite it getting late. I noticed the problem
while re-basing the 2nd patch here, which I decided to now re-post
despite the original discussion on v1 not having lead to any clear
result (i.e. the supposed "leave Dom0 handle the RTC" has never
materialized over the past almost 5 years), while I still think
that the changed code is at least a little bit of improvement.
1: restore pv_rtc_handler() invocation
2: detect CMOS aliasing on ports other than 0x70/0x71
Jan
next reply other threads:[~2020-07-15 11:55 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 11:54 Jan Beulich [this message]
2020-07-15 11:56 ` [PATCH v3 1/2] x86: restore pv_rtc_handler() invocation Jan Beulich
2020-07-15 12:13 ` Roger Pau Monné
2020-07-15 12:36 ` Jan Beulich
2020-07-15 13:32 ` Roger Pau Monné
2020-07-15 13:51 ` Jan Beulich
2020-07-15 14:51 ` Roger Pau Monné
2020-07-16 10:06 ` Jan Beulich
2020-07-16 10:31 ` Roger Pau Monné
2020-07-16 10:52 ` Jan Beulich
2020-07-20 15:28 ` Andrew Cooper
2020-07-20 16:27 ` Jan Beulich
2020-07-21 6:36 ` Jan Beulich
2020-07-15 12:31 ` Paul Durrant
2020-07-15 11:57 ` [PATCH v3 2/2] x86: detect CMOS aliasing on ports other than 0x70/0x71 Jan Beulich
2020-07-20 11:11 ` Roger Pau Monné
2023-03-17 16:12 ` Roger Pau Monné
2023-03-20 8:32 ` [PATCH v4] " Jan Beulich
2023-03-21 14:12 ` Roger Pau Monné
2023-03-22 9:55 ` Jan Beulich
2023-03-23 12:29 ` Roger Pau Monné
2023-03-23 14:26 ` Jan Beulich
2023-03-27 15:44 ` Jan Beulich
2023-03-23 14:49 ` Roger Pau Monné
2023-03-23 16:08 ` Jan Beulich
2023-03-23 16:40 ` Roger Pau Monné
2023-03-27 15:46 ` Jan Beulich
2023-03-27 15:44 ` Jan Beulich
2023-03-30 10:40 ` [PATCH v5] " Jan Beulich
2023-04-03 11:09 ` Roger Pau Monné
2023-04-03 11:26 ` Jan Beulich
2023-04-03 11:44 ` Roger Pau Monné
2023-04-03 12:24 ` Jan Beulich
2023-04-18 9:24 ` [PATCH v6] " Jan Beulich
2023-04-18 11:35 ` Roger Pau Monné
2023-04-19 7:56 ` Jan Beulich
2023-04-19 10:45 ` Roger Pau Monné
2023-04-19 13:58 ` Jan Beulich
2023-04-19 15:55 ` Roger Pau Monné
2023-04-20 8:31 ` Jan Beulich
2023-04-20 14:31 ` Roger Pau Monné
2023-04-20 14:55 ` 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=5426dd6f-50cd-dc23-5c6b-0ab631d98d38@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=paul@xen.org \
--cc=roger.pau@citrix.com \
--cc=wl@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.