From: "Jan Beulich" <JBeulich@suse.com>
To: Euan Harris <euan.harris@citrix.com>
Cc: andrew.cooper3@citrix.com, kevin.tian@intel.com,
jun.nakajima@intel.com, xen-devel@lists.xenproject.org
Subject: Re: [PATCH 9/9] x86/vvmx: Use hvm_copy_{to, from}_guest_virt() to read operands
Date: Tue, 28 Nov 2017 01:49:22 -0700 [thread overview]
Message-ID: <5A1D312202000078001929FB@prv-mh.provo.novell.com> (raw)
In-Reply-To: <1509037399-48926-10-git-send-email-euan.harris@citrix.com>
>>> On 26.10.17 at 19:03, <euan.harris@citrix.com> wrote:
In the title please use "read/write" or "access".
> @@ -380,17 +383,7 @@ static int operand_read(void *buf, struct vmx_inst_op *op,
> return X86EMUL_OKAY;
> }
> else
> - {
> - pagefault_info_t pfinfo;
> - int rc = hvm_copy_from_guest_linear(buf, op->mem, bytes, 0, &pfinfo);
> -
> - if ( rc == HVMTRANS_bad_linear_to_gfn )
> - hvm_inject_page_fault(pfinfo.ec, pfinfo.linear);
> - if ( rc != HVMTRANS_okay )
> - return X86EMUL_EXCEPTION;
> -
> - return X86EMUL_OKAY;
> - }
> + return hvm_copy_from_guest_virt(buf, op->seg, op->offset, bytes, 0);
> }
Please also drop the now pointless "else".
> @@ -458,9 +451,8 @@ static int decode_vmx_inst(struct cpu_user_regs *regs,
> {
> struct vcpu *v = current;
> union vmx_inst_info info;
> - struct segment_register seg;
> - unsigned long base, index, seg_base, disp, offset;
> - int scale, size;
> + unsigned long base, index, disp, offset;
> + int scale;
unsigned int please, if you touch it anyway.
> @@ -496,19 +485,12 @@ static int decode_vmx_inst(struct cpu_user_regs *regs,
>
> __vmread(EXIT_QUALIFICATION, &disp);
>
> - size = 1 << (info.fields.addr_size + 1);
> -
> - offset = base + index * scale + disp;
> - base = !mode_64bit || info.fields.segment >= x86_seg_fs ?
> - seg_base + offset : offset;
> - if ( offset + size - 1 < offset ||
> - (mode_64bit ?
> - !is_canonical_address((long)base < 0 ? base :
> - base + size - 1) :
> - offset + size - 1 > seg.limit) )
> - goto gp_fault;
> + decode->op[0].type = VMX_INST_MEMREG_TYPE_MEMORY;
> + decode->op[0].seg = info.fields.segment;
> + decode->op[0].offset = base + index * scale + disp;
> + if ( info.fields.addr_size < 2 )
> + decode->op[0].offset = (uint32_t)decode->op[0].offset;
For 16-bit addressing you need to truncate to 16 bits.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2017-11-28 8:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 17:03 [PATCH 0/9] x86/vvmx: Read instruction operands correctly on VM exit Euan Harris
2017-10-26 17:03 ` [PATCH 1/9] x86/vvmx: Remove enum vmx_regs_enc Euan Harris
2017-10-26 17:03 ` [PATCH 2/9] x86/vvmx: Unify operands in struct vmx_inst_decoded Euan Harris
2017-10-26 17:03 ` [PATCH 3/9] x86/vvmx: Extract operand reading logic into operand_read() Euan Harris
2017-11-27 17:01 ` Jan Beulich
2017-11-27 18:08 ` Andrew Cooper
2017-11-28 8:40 ` Jan Beulich
2017-11-28 8:14 ` Jan Beulich
2017-10-26 17:03 ` [PATCH 4/9] x86/vvmx: Remove unnecessary VMX operand reads Euan Harris
2017-11-02 7:07 ` Tian, Kevin
2017-11-27 17:03 ` Jan Beulich
2017-10-26 17:03 ` [PATCH 5/9] x86/vvmx: Replace direct calls to reg_read() with operand_read() Euan Harris
2017-10-26 17:03 ` [PATCH 6/9] x86/vvmx: Remove operand reading from decode_vmx_inst() Euan Harris
2017-10-26 17:03 ` [PATCH 7/9] x86/vvmx: Use correct sizes when reading operands Euan Harris
2017-11-28 8:32 ` Jan Beulich
2017-12-01 18:45 ` Andrew Cooper
2017-12-04 8:55 ` Jan Beulich
2017-10-26 17:03 ` [PATCH 8/9] x86/hvm: Add hvm_copy_{to, from}_guest_virt() helpers Euan Harris
2017-11-28 8:38 ` Jan Beulich
2017-10-26 17:03 ` [PATCH 9/9] x86/vvmx: Use hvm_copy_{to, from}_guest_virt() to read operands Euan Harris
2017-11-28 8:49 ` Jan Beulich [this message]
2017-10-26 17:59 ` [PATCH 0/9] x86/vvmx: Read instruction operands correctly on VM exit Andrew Cooper
2017-11-02 7:23 ` Tian, Kevin
2017-11-02 18:39 ` Andrew Cooper
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=5A1D312202000078001929FB@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=euan.harris@citrix.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.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 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.