public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: "Milosek, Damian" <damian.milosek@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"sami.mujawar@arm.com" <sami.mujawar@arm.com>,
	 "Yao, Jiewen" <jiewen.yao@intel.com>
Subject: Re: [edk2-devel] [PATCH] StandaloneMmPkg/StandaloneMmMemLib: Update AARCH64 address size
Date: Tue, 24 Jan 2023 13:32:51 +0100	[thread overview]
Message-ID: <CAMj1kXFvNxFaGHVWX+MQydJB=g=iVaGuj=4yBkbtRgFtnOeqFQ@mail.gmail.com> (raw)
In-Reply-To: <MW5PR11MB588224EE72BE5AB3CE6BA76395C99@MW5PR11MB5882.namprd11.prod.outlook.com>

On Tue, 24 Jan 2023 at 13:20, Milosek, Damian <damian.milosek@intel.com> wrote:
>
>
>
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Ard Biesheuvel
> Sent: Monday, January 23, 2023 6:46 PM
> To: Milosek, Damian <damian.milosek@intel.com>
> Cc: devel@edk2.groups.io; sami.mujawar@arm.com; Yao, Jiewen <jiewen.yao@intel.com>
> Subject: Re: [edk2-devel] [PATCH] StandaloneMmPkg/StandaloneMmMemLib: Update AARCH64 address size
>
> On Mon, 23 Jan 2023 at 17:14, Milosek, Damian <damian.milosek@intel.com> wrote:
> >
> >
> >
> > -----Original Message-----
> > From: Ard Biesheuvel <ardb@kernel.org>
> > Sent: Monday, January 23, 2023 5:05 PM
> > To: Milosek, Damian <damian.milosek@intel.com>
> > Cc: devel@edk2.groups.io; sami.mujawar@arm.com; Yao, Jiewen
> > <jiewen.yao@intel.com>
> > Subject: Re: [PATCH] StandaloneMmPkg/StandaloneMmMemLib: Update
> > AARCH64 address size
> >
> > On Mon, 23 Jan 2023 at 16:51, Milosek, Damian <damian.milosek@intel.com> wrote:
> > >
> > >
> > >
> > >
> > >
> > > From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of
> > > Milosek, Damian
> > > Sent: Monday, January 16, 2023 2:51 PM
> > > To: devel@edk2.groups.io
> > > Cc: Milosek, Damian <damian.milosek@intel.com>
> > > Subject: [edk2-devel] [PATCH] StandaloneMmPkg/StandaloneMmMemLib:
> > > Update AARCH64 address size
> > >
> > >
> > >
> > > Enable StandaloneMmMemLib to use longer physical addresses than 36 bits.
> > >
> >
> > What is the purpose of this change?
> >
> > - Making this Lib working for newer systems that use longer addresses.
> >
>
> What is the symptom? How is it failing currently?
>
> - Failure occurs in the first check in MmIsBufferOutsideMmValid () function when using longer address.
>
> > > According to ARM "Learn the architecture - AArch64 memory management"
> > >
> > > since Armv8.2-A physical address size was extended to 52 bits.
> > >
> > > https://developer.arm.com/documentation/101811/0102/Address-spaces
> > >
> >
> > This is an optional extension. Which hardware are you using that implements this extension?
> >
> > - System with Armv9-A Neoverse CPU cores.
> >
>
> Which system? What does the memory map look like?
>
> - It is not productized yet so cannot give any more info. However it seems that specific system is not relevant here.
>   Current definition assumes max 36 bits for AARCH64 which is not the case anymore.
>

Fair enough.

The problem with 52 bit support is that when using 4k pages (which is
the only page size supported by EFI), the page table entry layout is
different, and the shareability of a region is derived in a different
manner. None of this is implemented in the MMU library, and I would
actually prefer to avoid this if possible.

We can increase this to 48 without any problems, though.

      reply	other threads:[~2023-01-24 12:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <173AEF7243293292.25137@groups.io>
2023-01-23 15:51 ` [PATCH] StandaloneMmPkg/StandaloneMmMemLib: Update AARCH64 address size Milosek, Damian
2023-01-23 16:05   ` Ard Biesheuvel
2023-01-23 16:13     ` Milosek, Damian
2023-01-23 17:46       ` Ard Biesheuvel
2023-01-24 12:20         ` [edk2-devel] " Milosek, Damian
2023-01-24 12:32           ` Ard Biesheuvel [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-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='CAMj1kXFvNxFaGHVWX+MQydJB=g=iVaGuj=4yBkbtRgFtnOeqFQ@mail.gmail.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