From: Alex Williamson <alex.williamson@redhat.com>
To: Fred Gao <fred.gao@intel.com>
Cc: kvm@vger.kernel.org, intel-gfx@lists.freedesktop.org,
Zhenyu Wang <zhenyuw@linux.intel.com>,
Swee Yee Fonn <swee.yee.fonn@intel.com>
Subject: Re: [PATCH v5] vfio/pci: Add support for opregion v2.1+
Date: Tue, 6 Apr 2021 13:37:28 -0600 [thread overview]
Message-ID: <20210406133728.23ecb592@omen> (raw)
In-Reply-To: <20210325170953.24549-1-fred.gao@intel.com>
On Fri, 26 Mar 2021 01:09:53 +0800
Fred Gao <fred.gao@intel.com> wrote:
> Before opregion version 2.0 VBT data is stored in opregion mailbox #4,
> but when VBT data exceeds 6KB size and cannot be within mailbox #4
> then from opregion v2.0+, Extended VBT region, next to opregion is
> used to hold the VBT data, so the total size will be opregion size plus
> extended VBT region size.
>
> Since opregion v2.0 with physical host VBT address would not be
> practically available for end user and guest can not directly access
> host physical address, so it is not supported.
>
> Cc: Zhenyu Wang <zhenyuw@linux.intel.com>
> Signed-off-by: Swee Yee Fonn <swee.yee.fonn@intel.com>
> Signed-off-by: Fred Gao <fred.gao@intel.com>
> ---
> drivers/vfio/pci/vfio_pci_igd.c | 53 +++++++++++++++++++++++++++++++++
> 1 file changed, 53 insertions(+)
Applied to vfio next branch for v5.13. Thanks,
Alex
prev parent reply other threads:[~2021-04-06 19:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 17:12 [PATCH v1] vfio/pci: Add support for opregion v2.0+ Fred Gao
2020-12-02 18:57 ` Alex Williamson
2020-12-03 9:21 ` Gao, Fred
2020-12-03 23:38 ` Alex Williamson
2021-01-18 12:38 ` [PATCH v2] " Fred Gao
2021-01-21 20:33 ` Alex Williamson
2021-02-02 5:09 ` Zhenyu Wang
2021-02-08 17:02 ` [PATCH v3] vfio/pci: Add support for opregion v2.1+ Fred Gao
2021-03-02 13:02 ` [PATCH v4] " Fred Gao
2021-03-19 19:26 ` Alex Williamson
2021-03-25 8:50 ` Gao, Fred
2021-03-25 17:09 ` [PATCH v5] " Fred Gao
2021-03-30 9:08 ` Zhenyu Wang
2021-04-06 19:37 ` Alex Williamson [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=20210406133728.23ecb592@omen \
--to=alex.williamson@redhat.com \
--cc=fred.gao@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kvm@vger.kernel.org \
--cc=swee.yee.fonn@intel.com \
--cc=zhenyuw@linux.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