From: Andrew Cooper <Andrew.Cooper3@citrix.com>
To: Jan Beulich <jbeulich@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Wei Liu <wl@xen.org>, Roger Pau Monne <roger.pau@citrix.com>,
"Tim (Xen.org)" <tim@xen.org>,
George Dunlap <George.Dunlap@citrix.com>
Subject: Re: [PATCH 00/11] x86/shadow: misc tidying
Date: Fri, 6 Jan 2023 02:03:59 +0000 [thread overview]
Message-ID: <2e261172-76b3-936d-e95c-e12ed6acf7bd@citrix.com> (raw)
In-Reply-To: <074dc3bb-6057-4f61-d516-d0fe3551165c@suse.com>
On 05/01/2023 3:57 pm, Jan Beulich wrote:
> ... or so I hope. The main observation was that we still have both
> hash_vcpu_for_each() and hash_domain_for_each(), where the latter was
foreach
> introduced in 2014/15 to replace the former. Only some eight years
> later we can now complete this conversion. Everything else addresses
> other things noticed along the road.
Wow, it has been a long time. That was the start of the "make Xen not
fall over NULL pointers if the toolstack issues some hypercalls out of
order", a task that is still ongoing...
>
> 01: replace sh_reset_l3_up_pointers()
> 02: convert sh_audit_flags()'es 1st parameter to domain
> 03: drop hash_vcpu_foreach()
> 04: rename hash_domain_foreach()
> 05: move bogus HVM checks in sh_pagetable_dying()
> 06: drop a few uses of mfn_valid()
> 07: L2H shadow type is PV32-only
> 08: reduce effort of hash calculation
> 09: simplify conditionals in sh_{get,put}_ref()
> 10: correct shadow type bounds checks
> 11: sh_remove_all_mappings() is HVM-only
Everything without code queries, Acked-by: Andrew Cooper
<andrew.cooper3@citrix.com>
prev parent reply other threads:[~2023-01-06 2:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 15:57 [PATCH 00/11] x86/shadow: misc tidying Jan Beulich
2023-01-05 15:59 ` [PATCH 01/11] x86/shadow: replace sh_reset_l3_up_pointers() Jan Beulich
2023-01-06 0:55 ` Andrew Cooper
2023-01-09 8:35 ` Jan Beulich
2023-01-05 15:59 ` [PATCH 02/11] x86/shadow: convert sh_audit_flags()'es 1st parameter to domain Jan Beulich
2023-01-05 15:59 ` [PATCH 03/11] x86/shadow: drop hash_vcpu_foreach() Jan Beulich
2023-01-05 16:00 ` [PATCH 04/11] x86/shadow: rename hash_domain_foreach() Jan Beulich
2023-01-05 16:04 ` [PATCH 05/11] x86/shadow: move bogus HVM checks in sh_pagetable_dying() Jan Beulich
2023-01-06 1:00 ` Andrew Cooper
2023-01-09 8:39 ` Jan Beulich
2023-01-05 16:04 ` [PATCH 06/11] x86/shadow: drop a few uses of mfn_valid() Jan Beulich
2023-01-06 1:02 ` Andrew Cooper
2023-01-09 8:42 ` Jan Beulich
2023-01-05 16:05 ` [PATCH 07/11] x86/shadow: L2H shadow type is PV32-only Jan Beulich
2023-01-06 1:31 ` Andrew Cooper
2023-01-09 9:12 ` Jan Beulich
2023-01-05 16:05 ` [PATCH 08/11] x86/shadow: reduce effort of hash calculation Jan Beulich
2023-01-06 2:03 ` Andrew Cooper
2023-01-09 9:48 ` Jan Beulich
2023-01-05 16:06 ` [PATCH 09/11] x86/shadow: simplify conditionals in sh_{get,put}_ref() Jan Beulich
2023-01-05 16:07 ` [PATCH 10/11] x86/shadow: correct shadow type bounds checks Jan Beulich
2023-01-05 16:07 ` [PATCH 11/11] x86/shadow: sh_remove_all_mappings() is HVM-only Jan Beulich
2023-01-06 2:03 ` Andrew Cooper [this message]
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=2e261172-76b3-936d-e95c-e12ed6acf7bd@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=jbeulich@suse.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.