From: Anthony PERARD <anthony.perard@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Anthony PERARD <anthony.perard@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Jan Beulich <jbeulich@suse.com>
Subject: [PATCH 0/3] Rework vlapic timer to behave more like real-hardware
Date: Thu, 23 Mar 2017 11:46:58 +0000 [thread overview]
Message-ID: <20170323114701.25207-1-anthony.perard@citrix.com> (raw)
Hi,
When developing PVH for OVMF, I've used the lapic timer. It turns out that the
way it is used by OVMF did not work with Xen [1]. I tried to find out how
real-hw behave, and write a XTF tests [2]. And this patch series tries to fix
the behavior of the vlapic timer.
About the TSC-deadline mode, I've only make changes by reading the Intel
manual, I did not have real-hardward which support it.
Thanks,
[1] https://lists.xenproject.org/archives/html/xen-devel/2016-12/msg00959.html
[2] https://lists.xenproject.org/archives/html/xen-devel/2017-03/msg02533.html
Anthony PERARD (3):
x86/vlapic: Fix vLAPIC Timer to behave more like real-hw
x86/vlapic: Handle change of timer Divide Configuration Register
x86/vlapic: Reset LAPIC Timer only on TSC Deadline mode change
xen/arch/x86/hvm/vlapic.c | 147 ++++++++++++++++++++++++++++++++++++----------
1 file changed, 116 insertions(+), 31 deletions(-)
--
Anthony PERARD
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-03-23 11:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 11:46 Anthony PERARD [this message]
2017-03-23 11:46 ` [PATCH 1/3] x86/vlapic: Fix vLAPIC Timer to behave more like real-hw Anthony PERARD
2017-03-24 9:32 ` Jan Beulich
2017-03-23 11:47 ` [PATCH 2/3] x86/vlapic: Handle change of timer Divide Configuration Register Anthony PERARD
2017-03-24 9:43 ` Jan Beulich
2017-03-23 11:47 ` [PATCH 3/3] x86/vlapic: Reset LAPIC Timer only on TSC Deadline mode change Anthony PERARD
2017-03-24 9:54 ` 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=20170323114701.25207-1-anthony.perard@citrix.com \
--to=anthony.perard@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).