From: Jan Beulich <jbeulich@suse.com>
To: Jason Andryuk <jandryuk@gmail.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Ian Jackson <iwj@xenproject.org>, Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>
Subject: Re: [PATCH] libelf: Handle PVH kernels lacking ENTRY elfnote
Date: Mon, 19 Oct 2020 09:38:30 +0200 [thread overview]
Message-ID: <d10143d9-0082-fa09-3ef0-2d13e5ee54ef@suse.com> (raw)
In-Reply-To: <CAKf6xpv9qHJydjQ_TyZEKZAK14T4m2GLLqEwyMTraUxqvg+1Xw@mail.gmail.com>
On 16.10.2020 18:28, Jason Andryuk wrote:
> Looks like we can pass XC_DOM_PV_CONTAINER/XC_DOM_HVM_CONTAINER down
> into elf_xen_parse(). Then we would just validate phys_entry for HVM
> and virt_entry for PV. Does that sound reasonable?
I think so, yes. Assuming of course that you'll convert the XC_DOM_*
into a boolean, so that the hypervisor's use of libelf/ can also be
suitably adjusted.
Jan
next prev parent reply other threads:[~2020-10-19 7:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 15:31 [PATCH] libelf: Handle PVH kernels lacking ENTRY elfnote Jason Andryuk
2020-10-14 15:52 ` Wei Liu
2020-10-14 16:02 ` Jan Beulich
2020-10-14 16:27 ` Jason Andryuk
2020-10-15 7:00 ` Jan Beulich
2020-10-15 14:50 ` Jason Andryuk
2020-10-15 15:14 ` Jan Beulich
2020-10-15 17:27 ` Andrew Cooper
2020-10-16 16:28 ` Jason Andryuk
2020-10-19 7:38 ` Jan Beulich [this message]
2020-10-19 15:26 ` Jason Andryuk
2020-10-19 15:36 ` Jan Beulich
2020-10-15 15:03 ` Roger Pau Monné
2020-10-14 16:12 ` Jürgen Groß
2020-10-14 16:27 ` Jason Andryuk
2020-10-15 4:17 ` Jürgen Groß
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=d10143d9-0082-fa09-3ef0-2d13e5ee54ef@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=iwj@xenproject.org \
--cc=jandryuk@gmail.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--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 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).