From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86/hvm: increase struct hvm_vcpu_io's mmio_large_read[]
Date: Wed, 27 Jun 2012 15:50:01 +0100 [thread overview]
Message-ID: <CC10DC29.36A99%keir.xen@gmail.com> (raw)
In-Reply-To: <4FEB290B020000780008C3BB@nat28.tlf.novell.com>
On 27/06/2012 14:38, "Jan Beulich" <JBeulich@suse.com> wrote:
> Since the emulator now supports a few 256-bit memory operations, this
> array needs to follow (and the comments should, too).
>
> To limit growth, re-order the mmio_large_write_* fields so that the
> two mmio_large_*_bytes fields end up adjacent to each other.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Keir Fraser <keir@xen.org>
> --- a/xen/include/asm-x86/hvm/vcpu.h
> +++ b/xen/include/asm-x86/hvm/vcpu.h
> @@ -59,13 +59,13 @@ struct hvm_vcpu_io {
> unsigned long mmio_gva;
> unsigned long mmio_gpfn;
>
> - /* We may read up to m128 as a number of device-model transactions. */
> + /* We may read up to m256 as a number of device-model transactions. */
> paddr_t mmio_large_read_pa;
> - uint8_t mmio_large_read[16];
> + uint8_t mmio_large_read[32];
> unsigned int mmio_large_read_bytes;
> - /* We may write up to m128 as a number of device-model transactions. */
> - paddr_t mmio_large_write_pa;
> + /* We may write up to m256 as a number of device-model transactions. */
> unsigned int mmio_large_write_bytes;
> + paddr_t mmio_large_write_pa;
> };
>
> #define VMCX_EADDR (~0ULL)
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2012-06-27 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 13:38 [PATCH] x86/hvm: increase struct hvm_vcpu_io's mmio_large_read[] Jan Beulich
2012-06-27 14:50 ` Keir Fraser [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=CC10DC29.36A99%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--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).