From: Tim Deegan <tim@xen.org>
To: Jan Beulich <jbeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Wei Liu" <wl@xen.org>, "Roger Pau Monné" <roger.pau@citrix.com>,
"George Dunlap" <george.dunlap@citrix.com>,
"Kevin Tian" <kevin.tian@intel.com>,
"Jun Nakajima" <jun.nakajima@intel.com>
Subject: Re: [PATCH 1/2] x86/mm: don't open-code p2m_is_pod()
Date: Thu, 2 Dec 2021 19:10:24 +0000 [thread overview]
Message-ID: <YakaIHomlrAsPXNG@deinos.phlegethon.org> (raw)
In-Reply-To: <a1110809-b4fb-c53e-5f46-dc7628165634@suse.com>
At 12:01 +0100 on 01 Dec (1638360084), Jan Beulich wrote:
> Replace all comparisons against p2m_populate_on_demand (outside of
> switch() statements) with the designated predicate.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Tim Deegan <tim@xen.org>
next prev parent reply other threads:[~2021-12-02 19:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 11:00 [PATCH 0/2] x86/mm: XSA-389 follow-up Jan Beulich
2021-12-01 11:01 ` [PATCH 1/2] x86/mm: don't open-code p2m_is_pod() Jan Beulich
2021-12-01 11:22 ` Andrew Cooper
2021-12-02 19:10 ` Tim Deegan [this message]
2021-12-01 11:02 ` [PATCH 2/2] x86/PoD: move increment of entry count Jan Beulich
2021-12-01 11:27 ` Andrew Cooper
2021-12-01 11:50 ` Jan Beulich
2021-12-01 11:52 ` Jan Beulich
2021-12-01 15:40 ` Andrew Cooper
2022-01-04 10:57 ` [PATCH v2] " Jan Beulich
2022-01-27 15:04 ` Ping: " Jan Beulich
2022-02-24 13:04 ` Ping²: " Jan Beulich
2024-03-11 16:04 ` George Dunlap
2024-03-12 13:17 ` Jan Beulich
2024-03-12 15:22 ` [PATCH v3] x86/PoD: tie together P2M update and " Jan Beulich
2024-03-13 10:58 ` George Dunlap
2024-03-13 12:19 ` Jan Beulich
2024-03-13 12:25 ` George Dunlap
2024-03-13 12:25 ` George Dunlap
2024-03-13 14:00 ` [PATCH v4] " Jan Beulich
2024-03-13 16:31 ` George Dunlap
2024-03-14 6:59 ` Jan Beulich
2024-03-19 13:22 ` [PATCH v5] " Jan Beulich
2024-03-20 9:50 ` George Dunlap
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=YakaIHomlrAsPXNG@deinos.phlegethon.org \
--to=tim@xen.org \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=roger.pau@citrix.com \
--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.