From: Juergen Gross <jgross@suse.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xen/pvh: Indicate XENFEAT_linux_rsdp_unrestricted to Xen
Date: Tue, 10 Apr 2018 07:32:44 +0200 [thread overview]
Message-ID: <c5b43925-4ee4-f64f-a044-3217d8cb116a__28.2991830774293$1523338291$gmane$org@suse.com> (raw)
In-Reply-To: <1523299904-18199-1-git-send-email-boris.ostrovsky@oracle.com>
On 09/04/18 20:51, Boris Ostrovsky wrote:
> Pre-4.17 kernels ignored start_info's rsdp_paddr pointer and instead
> relied on finding RSDP in standard location in BIOS RO memory. This
> has worked since that's where Xen used to place it.
>
> However, with recent Xen change (commit 4a5733771e6f ("libxl: put RSDP
> for PVH guest near 4GB")) it prefers to keep RSDP at a "non-standard"
> address. Even though as of commit b17d9d1df3c3 ("x86/xen: Add pvh
> specific rsdp address retrieval function") Linux is able to find RSDP,
> for back-compatibility reasons we need to indicate to Xen that we can
> handle this, an we do so by setting XENFEAT_linux_rsdp_unrestricted
> flag in ELF notes.
>
> (Also take this opportunity and sync features.h header file with Xen)
>
> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-04-10 5:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 18:51 [PATCH] xen/pvh: Indicate XENFEAT_linux_rsdp_unrestricted to Xen Boris Ostrovsky
2018-04-10 5:32 ` Juergen Gross
2018-04-10 5:32 ` Juergen Gross [this message]
2018-04-10 8:35 ` [Xen-devel] " Wei Liu
2018-04-10 8:35 ` Wei Liu
2018-04-10 13:46 ` Boris Ostrovsky
2018-04-10 13:46 ` Boris Ostrovsky
-- strict thread matches above, loose matches on Subject: below --
2018-04-09 18:51 Boris Ostrovsky
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='c5b43925-4ee4-f64f-a044-3217d8cb116a__28.2991830774293$1523338291$gmane$org@suse.com' \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.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.