From: Laszlo Ersek <lersek@redhat.com>
To: "Zeng, Star" <star.zeng@intel.com>,
Brijesh Singh <brijesh.singh@amd.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: Tom Lendacky <Thomas.Lendacky@amd.com>,
"Dong, Eric" <eric.dong@intel.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>
Subject: Re: [RFC PATCH 1/1] OvmfPkg/QemuFlash: Fix Runtime variable access when SEV is enabled
Date: Thu, 28 Jun 2018 15:15:50 +0200 [thread overview]
Message-ID: <e505b448-16cf-bac4-7bc4-10f7124e65d2@redhat.com> (raw)
In-Reply-To: <0C09AFA07DD0434D9E2A0C6AEB0483103BB5E096@shsmsx102.ccr.corp.intel.com>
On 06/28/18 08:25, Zeng, Star wrote:
> My understanding is MMIO is not managed by UEFI memory services, but GCD services.
> PI spec says " If the memory range specified by BaseAddress and Length is of type EfiGcdMemoryTypeSystemMemory or EfiGcdMemoryTypeMoreReliable, then the memory range may be automatically *allocated* for use by the *UEFI memory services*." in AddMemorySpace() description.
>
> For MMIO, the code needs to use AddMemorySpace() + AllocateMemorySpace().
Right, after seeing today the (updated) AllocatePages() failure,
reported by Brijesh, I came to the same conclusion. Thank you for
correcting my initial suggestion! It's not easy to keep this details in
mind :)
Laszlo
next prev parent reply other threads:[~2018-06-28 13:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 19:46 [RFC PATCH 1/1] OvmfPkg/QemuFlash: Fix Runtime variable access when SEV is enabled Brijesh Singh
2018-06-27 12:54 ` Laszlo Ersek
2018-06-27 16:34 ` Brijesh Singh
2018-06-27 16:37 ` Brijesh Singh
2018-06-27 16:59 ` Laszlo Ersek
2018-06-27 17:49 ` Brijesh Singh
2018-06-28 6:25 ` Zeng, Star
2018-06-28 13:15 ` Laszlo Ersek [this message]
2018-06-28 12:57 ` Laszlo Ersek
2018-06-28 13:21 ` Laszlo Ersek
2018-06-28 13:27 ` Brijesh Singh
2018-06-28 6:16 ` Zeng, Star
2018-06-28 13:13 ` Laszlo Ersek
2018-06-29 2:37 ` Zeng, Star
-- strict thread matches above, loose matches on Subject: below --
2018-06-26 19:39 Brijesh Singh
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=e505b448-16cf-bac4-7bc4-10f7124e65d2@redhat.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