All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Paul Durrant <paul@xen.org>
Cc: xen-devel@lists.xenproject.org,
	"Paul Durrant" <pdurrant@amazon.com>,
	"Julien Grall" <julien@xen.org>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"George Dunlap" <george.dunlap@citrix.com>,
	"Ian Jackson" <ian.jackson@eu.citrix.com>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Wei Liu" <wl@xen.org>,
	"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH v7 1/9] xen/common: introduce a new framework for save/restore of 'domain' context
Date: Wed, 26 Aug 2020 15:53:54 +0200	[thread overview]
Message-ID: <5578c3fb-e35d-bb89-79f7-003e642492ab@suse.com> (raw)
In-Reply-To: <9873d112-0d87-d871-3911-3527d79a0b56@suse.com>

On 26.08.2020 15:32, Jan Beulich wrote:
> On 18.08.2020 12:30, Paul Durrant wrote:
>> v7:
>>  - Add an option to domain_load_end() to ignore unconsumed data, which will
>>    be needed by a subsequent patch
> 
> May I suggest to name the parameter "ignore_tail" instead of
> "ignore_data", as typically you don't mean to ignore all of
> it?

Hmm, looking at patch 7 it's indeed all of the body which gets
ignored. Not sure what the longer term expectations here are.

Jan


  reply	other threads:[~2020-08-26 13:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-18 10:30 [PATCH v7 0/9] domain context infrastructure Paul Durrant
2020-08-18 10:30 ` [PATCH v7 1/9] xen/common: introduce a new framework for save/restore of 'domain' context Paul Durrant
2020-08-26 13:32   ` Jan Beulich
2020-08-26 13:53     ` Jan Beulich [this message]
2020-09-04 17:31       ` Paul Durrant
2020-08-18 10:30 ` [PATCH v7 2/9] xen/common/domctl: introduce XEN_DOMCTL_get/setdomaincontext Paul Durrant
2020-08-18 10:30 ` [PATCH v7 3/9] tools/misc: add xen-domctx to present domain context Paul Durrant
2020-08-18 10:30 ` [PATCH v7 4/9] docs/specs: add missing definitions to libxc-migration-stream Paul Durrant
2020-08-18 10:30 ` [PATCH v7 5/9] docs / tools: specific migration v4 to include DOMAIN_CONTEXT Paul Durrant
2020-08-18 10:30 ` [PATCH v7 6/9] tools/libxc: split restore handler handle_shared_info() functionality Paul Durrant
2020-08-18 10:30 ` [PATCH v7 7/9] common/domain: add a domain context record for shared_info Paul Durrant
2020-08-26 13:57   ` Jan Beulich
2020-09-04 17:29     ` Paul Durrant
2020-09-07  7:01       ` Jan Beulich
2020-09-07  7:11         ` [EXTERNAL] " Paul Durrant
2020-09-15 14:20       ` Durrant, Paul
2020-08-18 10:30 ` [PATCH v7 8/9] x86/time: add a domain context record for tsc_info Paul Durrant
2020-08-26 14:02   ` Jan Beulich
2020-08-28 11:08     ` [EXTERNAL] " Paul Durrant
2020-08-28 15:53       ` Jan Beulich
2020-08-28 16:36         ` Paul Durrant
2020-08-31  7:23           ` Jan Beulich
2020-08-18 10:30 ` [PATCH v7 9/9] tools/libxc: add DOMAIN_CONTEXT records to the migration stream Paul Durrant

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=5578c3fb-e35d-bb89-79f7-003e642492ab@suse.com \
    --to=jbeulich@suse.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=julien@xen.org \
    --cc=paul@xen.org \
    --cc=pdurrant@amazon.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=wl@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.