From: George Dunlap <george.dunlap@citrix.com>
To: Paul Durrant <paul.durrant@citrix.com>, xen-devel@lists.xenproject.org
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Jan Beulich <jbeulich@suse.com>,
Daniel De Graaf <dgdegra@tycho.nsa.gov>
Subject: Re: [PATCH v3 3/8] dm_op: convert HVMOP_track_dirty_vram
Date: Mon, 16 Jan 2017 15:12:59 +0000 [thread overview]
Message-ID: <ef8e68f4-b28d-4fcc-cda5-c477c91e9c07@citrix.com> (raw)
In-Reply-To: <1484233120-2015-4-git-send-email-paul.durrant@citrix.com>
On 12/01/17 14:58, Paul Durrant wrote:
> The handle type passed to the underlying shadow and hap functions is
> changed for compatibility with the new hypercall buffer.
>
> NOTE: This patch also modifies the type of the 'nr' parameter of
> xc_hvm_track_dirty_vram() from uint64_t to uint32_t. In practice
> the value passed was always truncated to 32 bits.
>
> Suggested-by: Jan Beulich <jbeulich@suse.com>
> Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
mm-bits:
Acked-by: George Dunlap <george.dunlap@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-16 15:13 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 14:58 [PATCH v3 0/8] New hypercall for device models Paul Durrant
2017-01-12 14:58 ` [PATCH v3 1/8] public / x86: Introduce __HYPERCALL_dm_op Paul Durrant
2017-01-12 15:33 ` Andrew Cooper
2017-01-12 16:10 ` Paul Durrant
2017-01-12 16:29 ` Jan Beulich
2017-01-13 9:05 ` Paul Durrant
2017-01-13 10:30 ` Jan Beulich
2017-01-13 10:47 ` Paul Durrant
2017-01-13 10:44 ` Wei Liu
2017-01-13 12:03 ` Andrew Cooper
2017-01-13 12:47 ` Jan Beulich
2017-01-16 16:05 ` Andrew Cooper
2017-01-16 16:16 ` Jan Beulich
2017-01-16 17:07 ` Paul Durrant
2017-01-16 17:18 ` Jan Beulich
2017-01-17 11:22 ` Andrew Cooper
2017-01-17 12:29 ` George Dunlap
2017-01-17 15:06 ` Andrew Cooper
2017-01-17 15:37 ` Jan Beulich
2017-01-17 12:42 ` Jan Beulich
2017-01-17 15:13 ` Andrew Cooper
2017-01-17 15:31 ` Jan Beulich
2017-01-12 14:58 ` [PATCH v3 2/8] dm_op: convert HVMOP_*ioreq_server* Paul Durrant
2017-01-12 16:30 ` Jan Beulich
2017-01-12 14:58 ` [PATCH v3 3/8] dm_op: convert HVMOP_track_dirty_vram Paul Durrant
2017-01-13 11:45 ` Jan Beulich
2017-01-13 11:46 ` Paul Durrant
2017-01-13 13:22 ` Tim Deegan
2017-01-16 15:12 ` George Dunlap [this message]
2017-01-12 14:58 ` [PATCH v3 4/8] dm_op: convert HVMOP_set_pci_intx_level, HVMOP_set_isa_irq_level, and Paul Durrant
2017-01-12 14:58 ` [PATCH v3 5/8] dm_op: convert HVMOP_modified_memory Paul Durrant
2017-01-13 11:51 ` Jan Beulich
2017-01-13 11:54 ` Paul Durrant
2017-01-12 14:58 ` [PATCH v3 6/8] dm_op: convert HVMOP_set_mem_type Paul Durrant
2017-01-13 11:54 ` Jan Beulich
2017-01-12 14:58 ` [PATCH v3 7/8] dm_op: convert HVMOP_inject_trap and HVMOP_inject_msi Paul Durrant
2017-01-12 14:58 ` [PATCH v3 8/8] x86/hvm: serialize trap injecting producer and consumer Paul Durrant
2017-01-12 16:28 ` Andrew Cooper
2017-01-12 16:41 ` Jan Beulich
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=ef8e68f4-b28d-4fcc-cda5-c477c91e9c07@citrix.com \
--to=george.dunlap@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=paul.durrant@citrix.com \
--cc=tim@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 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).