public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ashish Singhal" <ashishsingha@nvidia.com>
To: <devel@edk2.groups.io>, <hao.a.wu@intel.com>, <ray.ni@intel.com>,
	<jbrasen@nvidia.com>
Cc: Ashish Singhal <ashishsingha@nvidia.com>
Subject: [PATCH v4 0/2] Fix Aligned Page Allocation For XHCI
Date: Tue, 15 Oct 2019 11:20:45 -0600	[thread overview]
Message-ID: <cover.1571159369.git.ashishsingha@nvidia.com> (raw)

This patch set is an attempt to fix the error where we allocate incorrectly
aligned memory for XHCI PEI and DXE. The change for DXE phase has been verified
already but change for PEI needs to be verified by Hao as I do not have a
setup to be able to verify that.

The change in DXE just updates a parameter passed in to allocate aligned memory.
The change in PEI adds a new function to allocate aligned memory. There was no
need to add separate function to free aligned pages as unaligned pages have been
already freed during allocation function and the aligned one can be freed using
the existing function.

Ashish Singhal (2):
  MdeModulePkg/XhciDxe: Fix Aligned Page Allocation
  MdeModulePkg/XhciPei: Fix Aligned Page Allocation

 MdeModulePkg/Bus/Pci/XhciDxe/UsbHcMem.c |   2 +-
 MdeModulePkg/Bus/Pci/XhciPei/DmaMem.c   | 128 ++++++++++++++++++++++++++++++++
 MdeModulePkg/Bus/Pci/XhciPei/UsbHcMem.c |  25 +------
 MdeModulePkg/Bus/Pci/XhciPei/XhcPeim.h  |  28 +++++++
 4 files changed, 161 insertions(+), 22 deletions(-)

-- 
2.7.4


             reply	other threads:[~2019-10-15 17:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-15 17:20 Ashish Singhal [this message]
2019-10-15 17:20 ` [PATCH v4 1/2] MdeModulePkg/XhciDxe: Fix Aligned Page Allocation Ashish Singhal
2019-10-16  2:11   ` [edk2-devel] " Wu, Hao A
2019-10-15 17:20 ` [PATCH v4 2/2] MdeModulePkg/XhciPei: " Ashish Singhal
2019-10-16  2:13   ` Wu, Hao A
2019-10-17  2:43     ` Wu, Hao A
2019-10-21  1:02 ` [edk2-devel] [PATCH v4 0/2] Fix Aligned Page Allocation For XHCI Wu, Hao A

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=cover.1571159369.git.ashishsingha@nvidia.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