From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: "Boeuf, Sebastien" <sebastien.boeuf@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Justen, Jordan L" <jordan.l.justen@intel.com>,
"kraxel@redhat.com" <kraxel@redhat.com>
Subject: Re: [PATCH 0/4] OvmfPkg: CloudHv: Reduce PIO and MMIO accesses
Date: Thu, 2 Jun 2022 08:57:19 +0000 [thread overview]
Message-ID: <MW4PR11MB587210111802F76CCBC708B98CDE9@MW4PR11MB5872.namprd11.prod.outlook.com> (raw)
In-Reply-To: <cover.1652186234.git.sebastien.boeuf@intel.com>
Acked-by: Jiewen Yao <Jiewen.yao@intel.com>
I notice the PR failed - https://github.com/tianocore/edk2/pull/2875
I just want to double confirm, do you have a success PR for this patch set?
Thank you
Yao Jiewen
> -----Original Message-----
> From: Boeuf, Sebastien <sebastien.boeuf@intel.com>
> Sent: Tuesday, May 10, 2022 8:51 PM
> To: devel@edk2.groups.io
> Cc: Yao, Jiewen <jiewen.yao@intel.com>; Justen, Jordan L
> <jordan.l.justen@intel.com>; kraxel@redhat.com; Boeuf, Sebastien
> <sebastien.boeuf@intel.com>
> Subject: [PATCH 0/4] OvmfPkg: CloudHv: Reduce PIO and MMIO accesses
>
> From: Sebastien Boeuf <sebastien.boeuf@intel.com>
>
> The goal of this series is to reduce the amount of inappropriate PIO
> and MMIO accesses generated by the firmware when running on Cloud
> Hypervisor.
>
> For MMIO accesses, it is about providing the right base address where
> the firmware will be loaded by the VMM in order to avoid unexpected
> accesses to some address ranges.
>
> For PIO accesses, it is about preventing some read/write to be performed
> in the first place, as we know the underlying device is not emulated by
> Cloud Hypervisor.
>
> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
>
> Sebastien Boeuf (4):
> OvmfPkg: CloudHv: Fix FW_BASE_ADDRESS
> OvmfPkg: Check for QemuFwCfg availability before accessing it
> OvmfPkg: CloudHv: Rely on QemuFwCfgLibNull implementation
> OvmfPkg: Don't access A20 gate register on Cloud Hypervisor
>
> OvmfPkg/CloudHv/CloudHvDefines.fdf.inc | 65 +++++++++++++++++++
> OvmfPkg/CloudHv/CloudHvX64.dsc | 4 +-
> OvmfPkg/CloudHv/CloudHvX64.fdf | 2 +-
> OvmfPkg/Library/PlatformInitLib/Platform.c | 13 ++--
> .../QemuBootOrderLib/QemuBootOrderLib.c | 8 ++-
> 5 files changed, 82 insertions(+), 10 deletions(-)
> create mode 100644 OvmfPkg/CloudHv/CloudHvDefines.fdf.inc
>
> --
> 2.32.0
next prev parent reply other threads:[~2022-06-02 8:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 12:50 [PATCH 0/4] OvmfPkg: CloudHv: Reduce PIO and MMIO accesses Boeuf, Sebastien
2022-05-10 12:50 ` [PATCH 1/4] OvmfPkg: CloudHv: Fix FW_BASE_ADDRESS Boeuf, Sebastien
2022-05-10 12:50 ` [PATCH 2/4] OvmfPkg: Check for QemuFwCfg availability before accessing it Boeuf, Sebastien
2022-05-10 12:50 ` [PATCH 3/4] OvmfPkg: CloudHv: Rely on QemuFwCfgLibNull implementation Boeuf, Sebastien
2022-05-10 12:50 ` [PATCH 4/4] OvmfPkg: Don't access A20 gate register on Cloud Hypervisor Boeuf, Sebastien
2022-05-23 13:25 ` [PATCH 0/4] OvmfPkg: CloudHv: Reduce PIO and MMIO accesses Boeuf, Sebastien
2022-06-02 8:57 ` Yao, Jiewen [this message]
2022-06-02 9:04 ` Boeuf, Sebastien
2022-06-02 9:29 ` Boeuf, Sebastien
2022-06-02 9:52 ` Yao, Jiewen
2022-06-03 10:52 ` Yao, Jiewen
2022-06-03 11:04 ` Boeuf, Sebastien
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-list 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=MW4PR11MB587210111802F76CCBC708B98CDE9@MW4PR11MB5872.namprd11.prod.outlook.com \
--to=devel@edk2.groups.io \
/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