From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Keir Fraser <keir@xen.org>,
paul.durrant@citrix.com, Tim Deegan <tim@xen.org>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86/HVM: tie RTC emulation mode to enabling of Viridian emulation
Date: Tue, 2 Jul 2013 11:10:26 +0100 [thread overview]
Message-ID: <51D2A712.4030806@citrix.com> (raw)
In-Reply-To: <51D2973102000078000E21A5@nat28.tlf.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 4092 bytes --]
On 02/07/13 08:02, Jan Beulich wrote:
> As the mode not conforming to the hardware specification (by allowing
> the guest to skip the REG C reads in its interrupt handler) is a
> Viridian invention, it seems logical to tie this mode to that extension
> being enabled. If the extension is disabled, proper hardware emulation
> will be done instead.
>
> The main thing necessary here is the synchronization of the RTC
> emulation code and the setting of the respective flag in hvmloader's
> creation of the ACPI WAET table.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
This looks to be safe migrating forwards
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
>
> --- a/tools/firmware/hvmloader/acpi/acpi2_0.h
> +++ b/tools/firmware/hvmloader/acpi/acpi2_0.h
> @@ -304,6 +304,9 @@ struct acpi_20_waet {
> uint32_t flags;
> };
>
> +#define ACPI_WAET_RTC_NO_ACK (1<<0) /* RTC requires no int acknowledge */
> +#define ACPI_WAET_TIMER_ONE_READ (1<<1) /* PM timer requires only one read */
> +
> /*
> * Multiple APIC Flags.
> */
> --- a/tools/firmware/hvmloader/acpi/build.c
> +++ b/tools/firmware/hvmloader/acpi/build.c
> @@ -22,8 +22,10 @@
> #include "ssdt_tpm.h"
> #include "ssdt_pm.h"
> #include "../config.h"
> +#include "../hypercall.h"
> #include "../util.h"
> #include <xen/hvm/hvm_xs_strings.h>
> +#include <xen/hvm/params.h>
>
> #define ACPI_MAX_SECONDARY_TABLES 16
>
> @@ -189,6 +191,7 @@ static struct acpi_20_hpet *construct_hp
> static struct acpi_20_waet *construct_waet(void)
> {
> struct acpi_20_waet *waet;
> + xen_hvm_param_t param;
>
> waet = mem_alloc(sizeof(*waet), 16);
> if (!waet) return NULL;
> @@ -196,6 +199,19 @@ static struct acpi_20_waet *construct_wa
> memcpy(waet, &Waet, sizeof(*waet));
>
> waet->header.length = sizeof(*waet);
> +
> + /*
> + * Check whether Viridian emulation is enabled: The state of the RTC
> + * flag getting passed to the guest must be in sync with the mode
> + * selection in the hypervisor RTC emulation code.
> + */
> + param.domid = DOMID_SELF;
> + param.index = HVM_PARAM_VIRIDIAN;
> + if ( hypercall_hvm_op(HVMOP_get_param, ¶m) )
> + BUG();
> + if ( param.value )
> + waet->flags |= ACPI_WAET_RTC_NO_ACK;
> +
> set_checksum(waet, offsetof(struct acpi_header, checksum), sizeof(*waet));
>
> return waet;
> --- a/tools/firmware/hvmloader/acpi/static_tables.c
> +++ b/tools/firmware/hvmloader/acpi/static_tables.c
> @@ -136,16 +136,6 @@ struct acpi_20_rsdp Rsdp = {
> .length = sizeof(struct acpi_20_rsdp)
> };
>
> -#define ACPI_WAET_RTC_NO_ACK (1<<0) /* RTC requires no int acknowledge */
> -#define ACPI_WAET_TIMER_ONE_READ (1<<1) /* PM timer requires only one read */
> -
> -/*
> - * The state of the RTC flag getting passed to the guest must be in
> - * sync with the mode selection in the hypervisor RTC emulation code.
> - */
> -#define ACPI_WAET_FLAGS (ACPI_WAET_RTC_NO_ACK | \
> - ACPI_WAET_TIMER_ONE_READ)
> -
> struct acpi_20_waet Waet = {
> .header = {
> .signature = ACPI_2_0_WAET_SIGNATURE,
> @@ -157,7 +147,7 @@ struct acpi_20_waet Waet = {
> .creator_id = ACPI_CREATOR_ID,
> .creator_revision = ACPI_CREATOR_REVISION
> },
> - .flags = ACPI_WAET_FLAGS
> + .flags = ACPI_WAET_TIMER_ONE_READ
> };
>
> /*
> --- a/xen/arch/x86/hvm/rtc.c
> +++ b/xen/arch/x86/hvm/rtc.c
> @@ -51,7 +51,9 @@ enum rtc_mode {
> };
>
> /* This must be in sync with how hvmloader sets the ACPI WAET flags. */
> -#define mode_is(d, m) ((void)(d), rtc_mode_##m == rtc_mode_no_ack)
> +#define mode_is(d, m) (is_viridian_domain(d) ? \
> + rtc_mode_##m == rtc_mode_no_ack : \
> + rtc_mode_##m == rtc_mode_strict)
> #define rtc_mode_is(s, m) mode_is(vrtc_domain(s), m)
>
> static void rtc_copy_date(RTCState *s);
>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 4871 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2013-07-02 10:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 7:02 [PATCH] x86/HVM: tie RTC emulation mode to enabling of Viridian emulation Jan Beulich
2013-07-02 8:01 ` Paul Durrant
2013-07-02 8:22 ` Jan Beulich
2013-07-02 8:34 ` Paul Durrant
2013-07-02 9:11 ` Tim Deegan
2013-07-02 9:27 ` Jan Beulich
2013-07-02 9:51 ` Tim Deegan
2013-07-02 10:22 ` Jan Beulich
2013-07-02 10:35 ` Tim Deegan
2013-07-02 13:01 ` George Dunlap
2013-07-02 14:04 ` Jan Beulich
2013-07-02 14:23 ` Tim Deegan
2013-07-02 14:19 ` Konrad Rzeszutek Wilk
2013-07-02 14:38 ` Jan Beulich
2013-07-02 10:10 ` Andrew Cooper [this message]
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=51D2A712.4030806@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=paul.durrant@citrix.com \
--cc=tim@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 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).