From: Wei Liu <wei.liu2@citrix.com>
To: Tim Deegan <tim@xen.org>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>, Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [PATCH RFC 2/2] x86/mm: PG_translate implies PG_refcounts
Date: Thu, 24 Aug 2017 11:07:24 +0100 [thread overview]
Message-ID: <20170824100724.fcp3gdvieehtqa2p@citrix.com> (raw)
In-Reply-To: <20170824100536.6a6q4w6c53lyc4wj@citrix.com>
On Thu, Aug 24, 2017 at 11:05:36AM +0100, Wei Liu wrote:
> On Thu, Aug 24, 2017 at 11:02:33AM +0100, Tim Deegan wrote:
> > At 16:58 +0100 on 23 Aug (1503507504), Wei Liu wrote:
> > > After 404595352 ("x86/paging: Enforce PG_external == PG_translate ==
> > > PG_refcounts"), PG_refcounts and PG_translate always need to be set
> > > together.
> > >
> > > Squash PG_refcounts to simplify code. All calls paging_mode_refcounts
> > > are replaced by calls to paging_mode_translate.
> >
> > Would it be a good idea to merge all three and have only PG_external?
> >
>
> My reverse-engineering is that when PV guest is migrated it has
> PG_external and (the new) PG_translate.
Sorry, I meant (!PG_external && PG_translate)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-08-24 10:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 15:58 [PATCH RFC 0/2] Misc paging code clean up Wei Liu
2017-08-23 15:58 ` [PATCH RFC 1/2] xen: remove CONFIG_PAGING_ASSISTANCE Wei Liu
2017-08-23 16:04 ` Jan Beulich
2017-08-24 10:04 ` Tim Deegan
2017-08-24 10:15 ` Jan Beulich
2017-08-24 10:42 ` Julien Grall
2017-08-23 15:58 ` [PATCH RFC 2/2] x86/mm: PG_translate implies PG_refcounts Wei Liu
2017-08-23 16:18 ` Wei Liu
2017-08-24 10:02 ` Tim Deegan
2017-08-24 10:05 ` Wei Liu
2017-08-24 10:07 ` Wei Liu [this message]
2017-08-24 10:09 ` Andrew Cooper
2017-08-24 10:11 ` Wei Liu
2017-08-24 10:15 ` Tim Deegan
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=20170824100724.fcp3gdvieehtqa2p@citrix.com \
--to=wei.liu2@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=tim@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.