From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Wei Liu" <wl@xen.org>, "Roger Pau Monné" <roger.pau@citrix.com>,
"George Dunlap" <george.dunlap@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v2 2/6] x86/P2M: relax permissions of PVH Dom0's MMIO entries
Date: Mon, 6 Sep 2021 20:23:24 +0100 [thread overview]
Message-ID: <80dc4625-a53e-1f18-2a77-a4e45c690cc2@citrix.com> (raw)
In-Reply-To: <28646a17-420e-bfaf-8f7d-6d109818ffc3@suse.com>
On 06/09/2021 16:55, Jan Beulich wrote:
> On 06.09.2021 17:48, Andrew Cooper wrote:
>> On 02/09/2021 09:33, Jan Beulich wrote:
>>> To become independent of the sequence of mapping operations, permit
>>> "access" to accumulate for Dom0, noting that there's not going to be an
>>> introspection agent for it which this might interfere with. While e.g.
>>> ideally only ROM regions would get mapped with X set, getting there is
>>> quite a bit of work.
>> ?
>>
>> That's literally the opposite of what needs to happen to fix this bug.
>> Introspection is the only interface which should be restricting X
>> permissions.
> What agent would be handling access violations in Dom0?
None. dom0 really shouldn't have any NX mappings in the first place.
~Andrew
next prev parent reply other threads:[~2021-09-06 19:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 8:30 [PATCH v2 0/6] x86/PVH: Dom0 building adjustments Jan Beulich
2021-09-02 8:32 ` [PATCH v2 1/6] x86/P2M: relax guarding of MMIO entries Jan Beulich
2021-09-06 15:54 ` Andrew Cooper
2021-09-02 8:33 ` [PATCH v2 2/6] x86/P2M: relax permissions of PVH Dom0's " Jan Beulich
2021-09-06 15:48 ` Andrew Cooper
2021-09-06 15:55 ` Jan Beulich
2021-09-06 19:23 ` Andrew Cooper [this message]
2021-09-02 8:33 ` [PATCH v2 3/6] x86/PVH: improve Dom0 memory size calculation Jan Beulich
2021-09-02 8:34 ` [PATCH v2 4/6] x86/PV: properly set shadow allocation for Dom0 Jan Beulich
2021-09-02 8:35 ` [PATCH v2 5/6] x86/PVH: actually show Dom0's register state from debug key '0' Jan Beulich
2021-09-02 8:36 ` [PATCH v2 6/6] x86/HVM: skip offline vCPU-s when dumping VMCBs/VMCSes Jan Beulich
2021-09-02 11:42 ` [PATCH v2 0/6] x86/PVH: Dom0 building adjustments Jan Beulich
2021-09-02 12:15 ` Juergen Gross
2021-09-02 12:39 ` Jan Beulich
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=80dc4625-a53e-1f18-2a77-a4e45c690cc2@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.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.