All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Deegan <tim@xen.org>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
	keir@xen.org, andrew.cooper3@citrix.com,
	ian.jackson@eu.citrix.com, david.vrabel@citrix.com,
	Jan Beulich <JBeulich@suse.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH V2] Add flag to start info regarding virtual mapped p2m list
Date: Wed, 4 Mar 2015 12:18:11 +0100	[thread overview]
Message-ID: <20150304111811.GB93945@deinos.phlegethon.org> (raw)
In-Reply-To: <1425466376.25940.134.camel@citrix.com>

At 10:52 +0000 on 04 Mar (1425462776), Ian Campbell wrote:
> On Wed, 2015-03-04 at 11:20 +0100, Juergen Gross wrote:
> > I'd like to do an appropriate change in xl, but I've been told this
> > would make sense only for migration protocol V2. OTOH I don't want to
> > wait for an undefined amount of time until this will be posted, so I
> > sent the ABI change first.
> >
> > I could, of course, wait with the flag bit until xl is ready and post
> > another kernel patch then. Unfortunately this would delay Linux support
> > for automatically be able to run as a pv-domain >500GB further, so I
> > strongly recommend accepting the interface change now.
> 
> Please at least sketch out a design/description of what this flag means
> to the guest and/or tools and what eventual tools support you expect
> will be needed, and perhaps some ideas regarding what that support might
> look like.
> 
> Without this your proposed ABI change is just a random bit in a data
> structure with no context.

If this is just an ordering constraint between kernel and tools work,
maybe we could just define the bit as reserved for now, while the dev work
finishes, and give it a proper name when the toolstack bits go in.

Tim.

  reply	other threads:[~2015-03-04 11:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03  9:29 [PATCH V2] Add flag to start info regarding virtual mapped p2m list Juergen Gross
2015-03-03 10:01 ` Andrew Cooper
2015-03-03 10:27 ` Jan Beulich
     [not found] ` <54F59ABD02000078000658FB@suse.com>
2015-03-03 10:32   ` Juergen Gross
2015-03-03 10:52     ` Jan Beulich
     [not found]     ` <54F5A0920200007800065932@suse.com>
2015-03-03 11:00       ` Juergen Gross
2015-03-03 11:32         ` Jan Beulich
2015-03-04  8:58     ` Jan Beulich
2015-03-04  9:35       ` Ian Campbell
2015-03-04  9:42         ` Jan Beulich
2015-03-04 10:06           ` Ian Campbell
2015-03-04 10:20             ` Juergen Gross
2015-03-04 10:52               ` Ian Campbell
2015-03-04 11:18                 ` Tim Deegan [this message]
2015-03-04 11:22                   ` Juergen Gross
2015-03-04 11:41                     ` Ian Campbell
2015-03-17  5:50                       ` Juergen Gross
2015-03-18  9:59                         ` Ian Campbell
2015-03-18 10:59                           ` Juergen Gross
2015-03-18 11:09                             ` Ian Campbell
2015-03-04 10:59               ` David Vrabel
2015-03-04 11:09                 ` Juergen Gross
2015-03-04 11:18                   ` David Vrabel

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=20150304111811.GB93945@deinos.phlegethon.org \
    --to=tim@xen.org \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jgross@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.