From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Keir Fraser <keir@xen.org>
Subject: Re: [PATCH] x86/PVH: replace bogus assertion with conditional
Date: Fri, 31 Oct 2014 10:45:25 +0000 [thread overview]
Message-ID: <54536845.2000703@citrix.com> (raw)
In-Reply-To: <545376090200007800043E08@mail.emea.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 1202 bytes --]
On 31/10/14 10:44, Jan Beulich wrote:
> While PVH guests currently have to start in 64-bit mode, nothing keeps
> them from entering compatibility mode via a suitable ring-0 code
> selector and making a hypercall from there. Fail such attempts rather
> than asserting they won't happen.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
>
> --- a/xen/arch/x86/hvm/hvm.c
> +++ b/xen/arch/x86/hvm/hvm.c
> @@ -4876,10 +4876,10 @@ int hvm_do_hypercall(struct cpu_user_reg
> regs->r8, regs->r9);
> curr->arch.hvm_vcpu.hcall_64bit = 0;
> }
> + else if ( unlikely(is_pvh_vcpu(curr)) )
> + regs->_eax = -ENOSYS; /* PVH 32bitfixme. */
> else
> {
> - ASSERT(!is_pvh_vcpu(curr)); /* PVH 32bitfixme. */
> -
> HVM_DBG_LOG(DBG_LEVEL_HCALL, "hcall%u(%x, %x, %x, %x, %x, %x)", eax,
> (uint32_t)regs->ebx, (uint32_t)regs->ecx,
> (uint32_t)regs->edx, (uint32_t)regs->esi,
>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 2106 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:[~2014-10-31 10:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 10:44 [PATCH] x86/PVH: replace bogus assertion with conditional Jan Beulich
2014-10-31 10:45 ` 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=54536845.2000703@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@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 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.