From: Jan Beulich <jbeulich@suse.com>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Tim Deegan" <tim@xen.org>,
"George Dunlap" <george.dunlap@citrix.com>,
"Wei Liu" <wl@xen.org>, "Roger Pau Monné" <roger.pau@citrix.com>
Subject: [PATCH v2 0/4] x86: mm (mainly shadow) adjustments
Date: Tue, 21 Apr 2020 11:08:26 +0200 [thread overview]
Message-ID: <9d4b738a-4487-6bfc-3076-597d074c7b47@suse.com> (raw)
(Not so) large (anymore) parts of this series are to further
isolate pieces which are needed for HVM only, and hence would
better not be built with HVM=n. But there are also a few other
items which I've noticed along the road, including the new in
v2 4th patch.
1: mm: no-one passes a NULL domain to init_xen_l4_slots()
2: shadow: sh_update_linear_entries() is a no-op for PV
3: mm: monitor table is HVM-only
4: adjustments to guest handle treatment
Jan
next reply other threads:[~2020-04-21 9:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 9:08 Jan Beulich [this message]
2020-04-21 9:11 ` [PATCH v2 1/4] x86/mm: no-one passes a NULL domain to init_xen_l4_slots() Jan Beulich
2020-04-21 16:40 ` Roger Pau Monné
2020-05-05 6:31 ` Jan Beulich
2020-05-07 17:26 ` Andrew Cooper
2020-05-08 7:45 ` Jan Beulich
2020-04-21 9:11 ` [PATCH v2 2/4] x86/shadow: sh_update_linear_entries() is a no-op for PV Jan Beulich
2020-04-22 6:47 ` Tim Deegan
2020-04-21 9:12 ` [PATCH v2 3/4] x86/mm: monitor table is HVM-only Jan Beulich
2020-04-21 9:13 ` [PATCH v2 4/4] x86: adjustments to guest handle treatment Jan Beulich
2020-04-21 17:30 ` Roger Pau Monné
2020-04-21 18:44 ` Julien Grall
2020-04-22 7:56 ` Roger Pau Monné
2020-04-22 8:06 ` Julien Grall
2020-04-22 8:17 ` Julien Grall
2020-04-22 9:32 ` Jan Beulich
2020-04-29 13:22 ` Julien Grall
2020-04-22 8:26 ` Roger Pau Monné
2020-04-22 9:27 ` Jan Beulich
2020-05-05 6:26 ` Jan Beulich
2020-05-06 9:45 ` Julien Grall
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=9d4b738a-4487-6bfc-3076-597d074c7b47@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@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.