[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v4 3/8] dm_op: convert HVMOP_track_dirty_vram

To: "Paul Durrant" <paul.durrant@xxxxxxxxxx>
From: "Jan Beulich" <JBeulich@xxxxxxxx>
Date: Fri, 20 Jan 2017 09:20:59 -0700
Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>, Ian Jackson <ian.jackson@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 20 Jan 2017 16:21:13 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

>>> On 17.01.17 at 18:29, <paul.durrant@xxxxxxxxxx> wrote:
> v4:
> - Knock-on changes from compat code in dm.c. Not adding Jan's R-b since
>   the patch has fundamentally changed.

I must be missing something, as I can't seem to spot any meaningful
compat handling related changes. Could you clarify?

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

Follow-Ups:
- Re: [Xen-devel] [PATCH v4 3/8] dm_op: convert HVMOP_track_dirty_vram
  - From: Paul Durrant
- Re: [Xen-devel] [PATCH v4 3/8] dm_op: convert HVMOP_track_dirty_vram
  - From: Paul Durrant

References:
- [Xen-devel] [PATCH v4 0/8] New hypercall for device models
  - From: Paul Durrant
- [Xen-devel] [PATCH v4 3/8] dm_op: convert HVMOP_track_dirty_vram
  - From: Paul Durrant

Prev by Date: Re: [Xen-devel] [PATCH v4 1/8] public / x86: Introduce __HYPERCALL_dm_op...
Next by Date: Re: [Xen-devel] [PATCH v12 00/10] x86: multiboot2 protocol support
Previous by thread: Re: [Xen-devel] [PATCH v4 3/8] dm_op: convert HVMOP_track_dirty_vram
Next by thread: Re: [Xen-devel] [PATCH v4 3/8] dm_op: convert HVMOP_track_dirty_vram
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.