From: Jan Beulich <jbeulich@suse.com>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Wei Liu" <wl@xen.org>, "Roger Pau Monné" <roger.pau@citrix.com>,
"George Dunlap" <George.Dunlap@eu.citrix.com>,
"Tim Deegan" <tim@xen.org>
Subject: [PATCH 0/5] x86/p2m: hook adjustments
Date: Wed, 28 Oct 2020 10:20:33 +0100 [thread overview]
Message-ID: <29d30de1-2a8d-aee2-d3c3-331758766fc9@suse.com> (raw)
This started out with me getting confused by the two write_p2m_entry()
hooks we have - there really ought to be no more than one, or if two
were absolutely needed they imo would better have distinct names. Other
adjustment opportunities (and I hope they're improvements) were found
while getting rid of that one unnecessary layer of indirect calls.
1: p2m: paging_write_p2m_entry() is a private function
2: p2m: collapse the two ->write_p2m_entry() hooks
3: p2m: suppress audit_p2m hook when possible
4: HAP: move nested-P2M flush calculations out of locked region
5: [RFC] p2m: split write_p2m_entry() hook
Jan
next reply other threads:[~2020-10-28 9:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 9:20 Jan Beulich [this message]
2020-10-28 9:22 ` [PATCH 1/5] x86/p2m: paging_write_p2m_entry() is a private function Jan Beulich
2020-11-10 10:27 ` Roger Pau Monné
2020-11-10 10:32 ` Jan Beulich
2020-10-28 9:22 ` [PATCH 2/5] x86/p2m: collapse the two ->write_p2m_entry() hooks Jan Beulich
2020-10-29 20:36 ` Tim Deegan
2020-11-10 11:06 ` Roger Pau Monné
2020-11-10 13:51 ` Jan Beulich
2020-11-18 9:44 ` Roger Pau Monné
2020-10-28 9:23 ` [PATCH 3/5] x86/p2m: suppress audit_p2m hook when possible Jan Beulich
2020-11-10 11:30 ` Roger Pau Monné
2020-11-10 13:21 ` Jan Beulich
2020-11-10 14:01 ` Roger Pau Monné
2020-10-28 9:24 ` [PATCH 4/5] x86/HAP: move nested-P2M flush calculations out of locked region Jan Beulich
2020-11-10 11:38 ` Roger Pau Monné
2020-10-28 9:24 ` [PATCH 5/5] x86/p2m: split write_p2m_entry() hook Jan Beulich
2020-10-29 20:46 ` Tim Deegan
2020-11-10 13:59 ` Roger Pau Monné
2020-11-10 14:50 ` Jan Beulich
2020-11-11 12:17 ` Roger Pau Monné
2020-11-12 12:29 ` Jan Beulich
2020-11-12 13:07 ` Roger Pau Monné
2020-11-12 14:04 ` Jan Beulich
2020-11-12 17:52 ` Tim Deegan
2020-11-13 9:52 ` Jan Beulich
2020-11-18 9:22 ` Roger Pau Monné
2020-11-18 9:31 ` Roger Pau Monné
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=29d30de1-2a8d-aee2-d3c3-331758766fc9@suse.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=roger.pau@citrix.com \
--cc=tim@xen.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.