From: Jon Derrick <jonathan.derrick@intel.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>, <linux-pci@vger.kernel.org>,
Pawel Baldysiak <pawel.baldysiak@intel.com>,
Artur Paszkiewicz <artur.paszkiewicz@intel.com>,
Keith Busch <keith.busch@intel.com>,
Dave Fugate <david.fugate@intel.com>,
Andy Shevchenko <andriy.shevchenko@intel.com>,
Jon Derrick <jonathan.derrick@intel.com>
Subject: [PATCH 0/3] Expose VMD BIOS domain info
Date: Wed, 16 Oct 2019 11:04:45 -0600 [thread overview]
Message-ID: <1571245488-3549-1-git-send-email-jonathan.derrick@intel.com> (raw)
In order to provide better VMD userspace management support, VMD needs to know
its instance number in the platform. VMDs can be enabled or disabled, so a
simple enumeration can't explicitly determine the instance number of the VMD.
To assist userspace with management tasks, VMD BIOS writes the VMD instance
number and socket number into the first enabled root port's IO Base/Limit
registers prior to OS handoff. VMD driver can capture this information and
expose it to userspace.
This set exposes hardware-specific details of the VMD configuration as written
by the VMD-enabled BIOS. This data is restored to the same location on reset or
module unload. This set reuses the serialized child device configuration
accessors for proper ordering and write flushing.
Jon Derrick (3):
PCI: vmd: Add helpers to access device config space
PCI: vmd: Expose VMD details from BIOS
PCI: vmd: Restore domain info during resets/unloads
drivers/pci/controller/vmd.c | 147 ++++++++++++++++++++++++++++++++++++++-----
1 file changed, 133 insertions(+), 14 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-10-16 23:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 17:04 Jon Derrick [this message]
2019-10-16 17:04 ` [PATCH 1/3] PCI: vmd: Add helpers to access device config space Jon Derrick
2019-10-16 17:04 ` [PATCH 2/3] PCI: vmd: Expose VMD details from BIOS Jon Derrick
2019-10-31 11:37 ` Lorenzo Pieralisi
2019-11-01 13:16 ` Andrew Murray
2019-11-01 14:24 ` Derrick, Jonathan
2019-11-01 14:44 ` Andrew Murray
2019-11-01 21:53 ` Bjorn Helgaas
2019-11-01 22:16 ` Derrick, Jonathan
2019-11-04 18:07 ` Lorenzo Pieralisi
2019-11-05 10:12 ` Lorenzo Pieralisi
2019-11-05 21:32 ` Derrick, Jonathan
2019-11-05 22:22 ` Keith Busch
2019-11-05 22:38 ` Derrick, Jonathan
2019-11-05 22:45 ` Keith Busch
2020-01-27 10:38 ` Lorenzo Pieralisi
2020-01-27 23:48 ` Derrick, Jonathan
2019-10-16 17:04 ` [PATCH 3/3] PCI: vmd: Restore domain info during resets/unloads Jon Derrick
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=1571245488-3549-1-git-send-email-jonathan.derrick@intel.com \
--to=jonathan.derrick@intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=artur.paszkiewicz@intel.com \
--cc=david.fugate@intel.com \
--cc=helgaas@kernel.org \
--cc=keith.busch@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=pawel.baldysiak@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 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).