[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v2 RFC 2/4] x86/PV: support data breakpoint extension registers
On Thu, 2014-03-27 at 16:44 +0000, Jan Beulich wrote: > >>> On 27.03.14 at 17:23, <Ian.Campbell@xxxxxxxxxx> wrote: > > On Thu, 2014-03-27 at 16:03 +0000, Jan Beulich wrote: > >> >>> On 27.03.14 at 16:28, <Ian.Campbell@xxxxxxxxxx> wrote: > >> > Do the protocol docs in xg_save_restore need updating due to this > >> > change? > >> > >> Not sure about that - this doesn't seem to talk about what's inside > >> the "bodies". > > > > Is this extending the "VCPU context data"? or one of the XC_SAVE_ID_* > > things? I think it would be worth extending that to indicate the new > > "optional" data, where and what it is etc. > > Yeah, I could probably add a note to the "extv" thing, even if it > doesn't really fit. Sounds good, thanks. > >> > How does N->N+1 migration work out? > >> > >> Since the structure size grows, and that size is embedded in the > >> structure, input coming from N will be treated as not having any > >> MSRs. > > > > This is the size of the "extv" block in the header phase? > > No, the "size" member of struct xen_domctl_ext_vcpucontext. OK, that makes sense. Are you also breaking the 128b limit on the data returned by this struct? Ian. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |