From: Igor Druzhinin <igor.druzhinin@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>, Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xenproject.org,
Ian Jackson <ian.jackson@eu.citrix.com>,
Jan Beulich <jbeulich@suse.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH] acpi: set correct address of the control/event blocks in the FADT
Date: Tue, 29 Aug 2017 14:37:50 +0100 [thread overview]
Message-ID: <c5361c8c-cf6f-a6d6-3fce-36fb8f7a3d05@citrix.com> (raw)
In-Reply-To: <20170829133328.i2cjb2qybqhwzguw@citrix.com>
On 29/08/17 14:33, Wei Liu wrote:
> On Tue, Aug 29, 2017 at 02:24:49PM +0100, Andrew Cooper wrote:
>> On 29/08/17 09:50, Roger Pau Monne wrote:
>>> Commit 149c6b unmasked an issue long present in Xen: the control/event
>>> block addresses provided in the ACPI FADT table where hardcoded to the
>>> V1 version. This was papered over because hvmloader would also always
>>> set HVM_PARAM_ACPI_IOPORTS_LOCATION to 1 regardless of the BIOS
>>> version.
>>>
>>> Fix this by passing the address of the control/event blocks to
>>> acpi_build_tables, so the values can be properly set in the FADT
>>> table provided to the guest.
>>>
>>> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
>>> ---
>>> Cc: Igor Druzhinin <igor.druzhinin@citrix.com>
>>> Cc: Jan Beulich <jbeulich@suse.com>
>>> Cc: Andrew Cooper <andrew.cooper3@citrix.com>
>>> Cc: Ian Jackson <ian.jackson@eu.citrix.com>
>>> Cc: Wei Liu <wei.liu2@citrix.com>
>>> ---
>>> This commit should fix the qumu-trad Windows errors seen by osstest.
>>
>> This changes windows behaviour, but does not fix windows. Windows now
>> boots, but waits forever while trying to reboot after installing PV
>> drivers. There is no hint in the qemu log that the ACPI shutdown event
>> was received.
>>
>> Unless someone has some very quick clever ideas, the original fix will
>> need reverting.
>
> If I don't get a new fix by the end of today I'm going to revert Igor's
> patch (but keep Roger's patch in tree).
>
I guess the easiest way to overcome it would be to set "qemu-xen" as a
device-model in libxl unconditionally.
Igor
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-08-29 13:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 8:50 [PATCH] acpi: set correct address of the control/event blocks in the FADT Roger Pau Monne
2017-08-29 9:08 ` Jan Beulich
2017-08-29 9:17 ` Roger Pau Monne
2017-08-29 9:25 ` Wei Liu
2017-08-29 9:31 ` Roger Pau Monne
2017-08-29 9:41 ` Jan Beulich
2017-08-29 9:42 ` Wei Liu
2017-08-29 13:24 ` Andrew Cooper
2017-08-29 13:33 ` Wei Liu
2017-08-29 13:37 ` Igor Druzhinin [this message]
2017-08-29 13:51 ` Wei Liu
2017-08-29 13:53 ` Igor Druzhinin
2017-08-29 14:01 ` Wei Liu
2017-08-29 13:43 ` Jan Beulich
2017-08-29 13:46 ` Wei Liu
2017-08-29 13:55 ` Jan Beulich
2017-08-29 13:42 ` Jan Beulich
2017-08-29 14:26 ` Igor Druzhinin
2017-08-29 14:36 ` Roger Pau Monne
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=c5361c8c-cf6f-a6d6-3fce-36fb8f7a3d05@citrix.com \
--to=igor.druzhinin@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=wei.liu2@citrix.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).