From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Tamas K Lengyel <tamas.k.lengyel@gmail.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: Re: [Xen-devel] [PATCH] xen/arm: Restrict access to most HVM_PARAM's
Date: Wed, 19 Feb 2020 19:54:29 +0000 [thread overview]
Message-ID: <ad15e00d-a78c-aa83-7ddd-8af4fe895026@citrix.com> (raw)
In-Reply-To: <CABfawh==BEes5nvt=FD4waOb4pAgANGV+nPG1+XQ=CkgZ8FRGA@mail.gmail.com>
On 19/02/2020 16:44, Tamas K Lengyel wrote:
> On Mon, Feb 10, 2020 at 11:46 AM Andrew Cooper
> <andrew.cooper3@citrix.com> wrote:
>> ARM currently has no restrictions on toolstack and guest access to the entire
>> HVM_PARAM block. As the paging/monitor/sharing features aren't under security
>> support, this doesn't need an XSA.
> There is no paging or sharing implementation on ARM anyway.
Great.
> A cc would have been nice though.
Sorry. I didn't consider this something other than "clean up the
parameter handling". It was based on which parameters were referenced
in common or arm specific code.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-02-19 19:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 18:45 [Xen-devel] [PATCH] xen/arm: Restrict access to most HVM_PARAM's Andrew Cooper
2020-02-19 15:53 ` Julien Grall
2020-02-19 19:01 ` Andrew Cooper
2020-02-19 16:44 ` Tamas K Lengyel
2020-02-19 19:54 ` Andrew Cooper [this message]
2020-02-19 19:30 ` Andrew Cooper
2020-02-21 12:37 ` 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=ad15e00d-a78c-aa83-7ddd-8af4fe895026@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=tamas.k.lengyel@gmail.com \
--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.