From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jan Beulich <JBeulich@suse.com>, Keir Fraser <keir@xen.org>,
Wei Wang <wei.wang2@amd.com>,
Andre Przywara <andre.przywara@amd.com>,
Christoph Egger <christoph.egger@amd.com>,
"xiantao.zhang@intel.com" <xiantao.zhang@intel.com>,
Eddie Dong <eddie.dong@intel.com>
Subject: Other PCI devices to mark mark as read-only for dom0
Date: Fri, 22 Jun 2012 10:04:24 +0100 [thread overview]
Message-ID: <4FE43518.9070106@citrix.com> (raw)
Following Jan's infrastructure to mark certain PCI devices as read only,
I think it wise to now consider what other PCI devices should really be
read only to dom0.
My preliminary thoughts include:
* PCI serial devices which Xen is configured to use
* Chipset devices (AMD IOMMU covered by previous patch)
* Cpu information
Are there any others I have overlooked, or reasons that dom0 should be
able to write to these areas?
On a related note, should there be a mechanism for dom0 to determine
which PCI configuration areas are read only to itself?
--
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com
next reply other threads:[~2012-06-22 9:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 9:04 Andrew Cooper [this message]
2012-06-22 9:24 ` Other PCI devices to mark mark as read-only for dom0 Sander Eikelenboom
2012-06-22 10:11 ` Andrew Cooper
2012-06-22 9:43 ` Jan Beulich
2012-06-22 10:08 ` Andrew Cooper
2012-06-22 11:23 ` Jan Beulich
2012-06-22 12:06 ` Andrew Cooper
2012-06-22 12:20 ` Jan Beulich
2012-06-22 12:30 ` Andrew Cooper
2012-06-22 11:30 ` Jan Beulich
2012-06-22 12:27 ` Andrew Cooper
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=4FE43518.9070106@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=andre.przywara@amd.com \
--cc=christoph.egger@amd.com \
--cc=eddie.dong@intel.com \
--cc=keir@xen.org \
--cc=wei.wang2@amd.com \
--cc=xen-devel@lists.xen.org \
--cc=xiantao.zhang@intel.com \
/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.