All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: paul@xen.org
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Julien Grall <julien@xen.org>, Wei Liu <wl@xen.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Paul Durrant <pdurrant@amazon.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	George Dunlap <george.dunlap@citrix.com>,
	xen-devel@lists.xenproject.org,
	Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: Re: [Xen-devel] [PATCH v6 5/5] domain: use PGC_extra domheap page for shared_info
Date: Tue, 17 Mar 2020 14:14:06 +0100	[thread overview]
Message-ID: <bb08d849-bc56-336c-aedc-baca08aa1f9d@suse.com> (raw)
In-Reply-To: <20200310174917.1514-6-paul@xen.org>

On 10.03.2020 18:49, paul@xen.org wrote:
> From: Paul Durrant <pdurrant@amazon.com>
> 
> Currently shared_info is a shared xenheap page but shared xenheap pages
> complicate future plans for live-update of Xen so it is desirable to,
> where possible, not use them [1]. This patch therefore converts shared_info
> into a PGC_extra domheap page. This does entail freeing shared_info during
> domain_relinquish_resources() rather than domain_destroy() so care is
> needed to avoid de-referencing a NULL shared_info pointer hence some
> extra checks of 'is_dying' are needed.

If there's going to be agreement to follow this route, the implementation,
with a really minor cosmetic adjustment - see below -, looks okay to me.
Nevertheless I continue to dislike the implication from the extra care
that's now needed. As I think I have said before, I'd like to have at
least one other REST maintainer's opinion here.

> --- a/xen/arch/x86/domain.c
> +++ b/xen/arch/x86/domain.c
> @@ -260,9 +260,12 @@ void dump_pageframe_info(struct domain *d)
>  
>      page_list_for_each ( page, &d->extra_page_list )
>      {
> -        printk("    ExtraPage %p: caf=%08lx, taf=%" PRtype_info "\n",
> +        const char *tag = mfn_eq(page_to_mfn(page), d->shared_info.mfn) ?
> +            "[SHARED INFO]" : "";

Please can this be " [SHARED INFO]" with ...

> +        printk("    ExtraPage %p: caf=%08lx, taf=%" PRtype_info " %s\n",

... the blank before the final %s dropped here, such that we won't
have a trailing blank in the output?

Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2020-03-17 13:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10 17:49 [Xen-devel] [PATCH v6 0/5] remove one more shared xenheap page: shared_info paul
2020-03-10 17:49 ` [Xen-devel] [PATCH v6 1/5] domain: introduce alloc/free_shared_info() helpers paul
2020-03-10 17:49 ` [Xen-devel] [PATCH v6 2/5] mm: keep PGC_extra pages on a separate list paul
2020-03-16 16:53   ` Jan Beulich
2020-03-16 18:11     ` Paul Durrant
2020-03-17 10:45       ` Jan Beulich
2020-03-17 10:51         ` Paul Durrant
2020-03-10 17:49 ` [Xen-devel] [PATCH v6 3/5] x86 / ioreq: use a MEMF_no_refcount allocation for server pages paul
2020-03-10 17:49 ` [Xen-devel] [PATCH v6 4/5] mm: add 'is_special_page' inline function paul
2020-03-17 13:06   ` Jan Beulich
2020-03-17 14:47     ` [Xen-devel] [EXTERNAL] " Paul Durrant
2020-03-17 15:01       ` [Xen-devel] " Jan Beulich
2020-03-17 15:23     ` Julien Grall
2020-03-10 17:49 ` [Xen-devel] [PATCH v6 5/5] domain: use PGC_extra domheap page for shared_info paul
2020-03-17 13:14   ` Jan Beulich [this message]
2020-03-17 14:48     ` Durrant, Paul
2020-03-24  9:26   ` Jan Beulich
2020-03-24  9:31     ` Jan Beulich
2020-03-24 14:22   ` Julien Grall
2020-03-24 14:28     ` Durrant, Paul

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=bb08d849-bc56-336c-aedc-baca08aa1f9d@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=konrad.wilk@oracle.com \
    --cc=paul@xen.org \
    --cc=pdurrant@amazon.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.