From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Grzegorz Uriasz <gorbak25@gmail.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
jakub@bartmin.ski, qemu-devel@nongnu.org,
marmarek@invisiblethingslab.com,
Anthony Perard <anthony.perard@citrix.com>,
j.nowak26@student.uw.edu.pl, xen-devel@lists.xenproject.org,
contact@puzio.waw.pl
Subject: Re: [PATCH] hw/xen_pt: Don't grant opregion permissions
Date: Mon, 15 Jun 2020 14:47:58 +0200 [thread overview]
Message-ID: <20200615124758.GF735@Air-de-Roger> (raw)
In-Reply-To: <2157e10d63619d43151fe8b8ca913b44c54aba6e.1592176600.git.gorbak25@gmail.com>
On Sun, Jun 14, 2020 at 11:21:09PM +0000, Grzegorz Uriasz wrote:
> With the upstreaming of linux based stubdomains to xen, qemu can't
> assume it runs inside dom0 - permission assignment must be moved to
> libxl running in dom0. This xen patch:
> https://lists.xenproject.org/archives/html/xen-devel/2020-06/msg00973.html
> implements granting the required permissions to the stubdomain running
> qemu. This patch removes granting opregion permissions in qemu - this
> should be fine as when qemu is running inside dom0 the memory mapping will
> be successfully created without first explicitly granting the permission.
In order to avoid breaking certain libxl - QEMU combinations, could
you make the check below non-fatal?
So that the current code can be kept for dom0 while not throwing an
error when used inside of a stub domain?
Thanks, Roger.
prev parent reply other threads:[~2020-06-15 12:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 23:21 [PATCH] hw/xen_pt: Don't grant opregion permissions Grzegorz Uriasz
2020-06-15 6:10 ` Philippe Mathieu-Daudé
2020-06-15 12:47 ` Roger Pau Monné [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=20200615124758.GF735@Air-de-Roger \
--to=roger.pau@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=contact@puzio.waw.pl \
--cc=gorbak25@gmail.com \
--cc=j.nowak26@student.uw.edu.pl \
--cc=jakub@bartmin.ski \
--cc=marmarek@invisiblethingslab.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).