From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Tim Deegan <tim@xen.org>,
keir@xen.org, jbeulich@suse.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] x86: Expose hypervisor's PVH support via xen_caps
Date: Fri, 23 May 2014 11:08:33 -0400 [thread overview]
Message-ID: <537F6471.40000@oracle.com> (raw)
In-Reply-To: <537F6287.5070705@citrix.com>
On 05/23/2014 11:00 AM, Andrew Cooper wrote:
> On 23/05/14 15:55, Boris Ostrovsky wrote:
>> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>> ---
>> xen/arch/x86/setup.c | 5 +++++
>> 1 file changed, 5 insertions(+)
> If the plan is to try and PVH and HVM back into one mode as far as Xen
> is concerned, doesn't this become redundant?
Yes, I was thinking about this but we currently don't have (or, rather,
I can't think of) a good way to determine whether we can start a PVH
guest. We can grep the log but that doesn't feel like a particularly
good solution.
One option could be to postpone this patch until 4.5 freezes and see
whether we indeed followed up on the plan and if we didn't then
integrate it.
-boris
>
> ~Andrew
>
>> diff --git a/xen/arch/x86/setup.c b/xen/arch/x86/setup.c
>> index b2a808a..59b31b1 100644
>> --- a/xen/arch/x86/setup.c
>> +++ b/xen/arch/x86/setup.c
>> @@ -1462,6 +1462,11 @@ void arch_get_xen_caps(xen_capabilities_info_t *info)
>> safe_strcat(*info, s);
>> snprintf(s, sizeof(s), "hvm-%d.%d-x86_64 ", major, minor);
>> safe_strcat(*info, s);
>> + if ( hvm_funcs.pvh_supported )
>> + {
>> + snprintf(s, sizeof(s), "pvh-%d.%d-x86_64 ", major, minor);
>> + safe_strcat(*info, s);
>> + }
>> }
>> }
>>
next prev parent reply other threads:[~2014-05-23 15:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 14:55 [PATCH] x86: Expose hypervisor's PVH support via xen_caps Boris Ostrovsky
2014-05-23 15:00 ` Andrew Cooper
2014-05-23 15:08 ` Boris Ostrovsky [this message]
2014-05-23 15:20 ` Andrew Cooper
2014-05-23 15:32 ` Boris Ostrovsky
2014-05-23 15:35 ` Roger Pau Monné
2014-05-23 15:53 ` Boris Ostrovsky
2014-05-28 9:42 ` Ian Campbell
2014-05-28 18:18 ` boris ostrovsky
2014-05-28 21:12 ` Mukesh Rathor
2014-05-26 9:33 ` Jan Beulich
2014-05-27 3:03 ` 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=537F6471.40000@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--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).