From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, Keir Fraser <keir@xen.org>
Subject: Re: [PATCH] x86/HVM: 32-bit IN result must be zero-extended to 64 bits
Date: Tue, 5 Nov 2013 09:53:55 +0000 [thread overview]
Message-ID: <5278C033.2000408@citrix.com> (raw)
In-Reply-To: <5278BE8D02000078000FF631@nat28.tlf.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 2296 bytes --]
On 05/11/13 08:46, Jan Beulich wrote:
> Just like for all other operations with 32-bit operand size.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> --- a/xen/arch/x86/hvm/io.c
> +++ b/xen/arch/x86/hvm/io.c
> @@ -221,13 +221,15 @@ int handle_mmio_with_translation(unsigne
> return handle_mmio();
> }
>
> -int handle_pio(uint16_t port, int size, int dir)
> +int handle_pio(uint16_t port, unsigned int size, int dir)
> {
> struct vcpu *curr = current;
> struct hvm_vcpu_io *vio = &curr->arch.hvm_vcpu.hvm_io;
> unsigned long data, reps = 1;
> int rc;
>
> + ASSERT((size - 1) < 4 && size != 3);
> +
> if ( dir == IOREQ_WRITE )
> data = guest_cpu_user_regs()->eax;
>
> @@ -237,7 +239,12 @@ int handle_pio(uint16_t port, int size,
> {
> case X86EMUL_OKAY:
> if ( dir == IOREQ_READ )
> - memcpy(&guest_cpu_user_regs()->eax, &data, vio->io_size);
> + {
> + if ( size == 4 ) /* Needs zero extension. */
> + guest_cpu_user_regs()->eax = (uint32_t)data;
This would be a rather more clear as guest_cpu_user_regs()->rax, with
makes the 0-extension more obvious than remembering that eax is a 64bit
value in Xen. However, I guess consistency with the surrounding code is
important, and it is spelt out in a comment.
Either way,
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
> + else
> + memcpy(&guest_cpu_user_regs()->eax, &data, size);
> + }
> break;
> case X86EMUL_RETRY:
> if ( vio->io_state != HVMIO_awaiting_completion )
> --- a/xen/include/asm-x86/hvm/io.h
> +++ b/xen/include/asm-x86/hvm/io.h
> @@ -119,7 +119,7 @@ void send_timeoffset_req(unsigned long t
> void send_invalidate_req(void);
> int handle_mmio(void);
> int handle_mmio_with_translation(unsigned long gva, unsigned long gpfn);
> -int handle_pio(uint16_t port, int size, int dir);
> +int handle_pio(uint16_t port, unsigned int size, int dir);
> void hvm_interrupt_post(struct vcpu *v, int vector, int type);
> void hvm_io_assist(void);
> void hvm_dpci_eoi(struct domain *d, unsigned int guest_irq,
>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 3228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-11-05 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 8:46 [PATCH] x86/HVM: 32-bit IN result must be zero-extended to 64 bits Jan Beulich
2013-11-05 9:53 ` Andrew Cooper [this message]
2013-11-05 10:07 ` Jan Beulich
2013-11-05 13:24 ` Keir Fraser
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=5278C033.2000408@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.