public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: edk2-devel-01 <edk2-devel@lists.01.org>,
	Laszlo Ersek <lersek@redhat.com>,
	 Michael D Kinney <michael.d.kinney@intel.com>,
	Liming Gao <liming.gao@intel.com>
Subject: Re: [PATCH 1/3] MdePkg/Misc: Move ARM* BaseMemoryLibStm to MdePkg
Date: Fri, 2 Sep 2016 17:07:48 +0100	[thread overview]
Message-ID: <CAKv+Gu-zJ=tPnJsE1YByxxxjtftLCknAuamXbSXKyvCEx3DpYA@mail.gmail.com> (raw)
In-Reply-To: <20160902152351.GB4715@bivouac.eciton.net>

On 2 September 2016 at 16:23, Leif Lindholm <leif.lindholm@linaro.org> wrote:
> On Fri, Sep 02, 2016 at 04:02:44PM +0100, Ard Biesheuvel wrote:
>> > On 2 sep. 2016, at 15:29, Leif Lindholm <leif.lindholm@linaro.org> wrote:
>> >
>> > Recent changes to the BaseMemoryLib implementations in MdePkg,
>> > and other changes dependent on these, left all ARM* platforms
>> > unbuildable. To avoid this sort of thing in the future, move
>> > the ARM* BaseMemoryLib implementations to the same locations
>> > as the other ones.
>>
>> Can't we just get rid of the stm version, and move everything to the
>> generic version? Copying all this crap into MdePkg does not seem
>> like an improvement to me at all.
>
> This isn't a proposed alternative to your patchset, this is an
> alternative to reverting all of the other BaseMemoryLib changes.
> I'm happy to throw it away next week if we can get something better in
> by then.
>
>> The AArch64 optdxe changes i proposed are arguably as harmless,
>
> Yes, but that leaves ARM broken.
>

Not necessarily. ARM can use the generic BaseMemoryLib in MdePkg

>> since they don't affect any other arch either. And the stm aarch64
>> versions are plain c to begin with
>
> And I want to discuss that next week. Against the backdrop of a
> working master branch.
>

My concern is that having an 'ARM' flavor of BaseMemoryLib in MdePkg/
will make it more difficult rather than easier to simply add ARM
support to the existing non-sse/mmx ones

Added the fact that the Stm is not in great shape, I would really
prefer to get rid of it rather than 'promote' it to the standard ARM
implementation. Note that we will need another round of updates to the
platform .DSCs when we remove the Stm version again.


  reply	other threads:[~2016-09-02 16:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02 14:29 [PATCH 0/3] MdePkg/Misc: fix Arm BaseMemoryLib Leif Lindholm
2016-09-02 14:29 ` [PATCH 1/3] MdePkg/Misc: Move ARM* BaseMemoryLibStm to MdePkg Leif Lindholm
2016-09-02 15:02   ` Ard Biesheuvel
2016-09-02 15:23     ` Leif Lindholm
2016-09-02 16:07       ` Ard Biesheuvel [this message]
2016-09-02 18:05         ` Leif Lindholm
2016-09-02 18:11           ` Ard Biesheuvel
2016-09-02 18:32             ` Leif Lindholm
2016-09-02 18:45               ` Ard Biesheuvel
2016-09-02 19:18                 ` Leif Lindholm
2016-09-02 19:24                   ` Laszlo Ersek
2016-09-02 14:29 ` [PATCH 2/3] MdePkg/BaseMemoryLibStm: implement new IsZeroGuid() API function Leif Lindholm
2016-09-02 14:29 ` [PATCH 3/3] MdePkg/BaseMemoryLibStm: implement new IsZeroBuffer() " Leif Lindholm
2016-09-02 14:48 ` [PATCH 0/3] MdePkg/Misc: fix Arm BaseMemoryLib Laszlo Ersek
2016-09-02 14:53   ` Laszlo Ersek
2016-09-02 16:02     ` Leif Lindholm
2016-09-02 15:49 ` Kinney, Michael D
2016-09-02 15:57   ` Leif Lindholm
2016-09-02 15:59     ` Andrew Fish

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='CAKv+Gu-zJ=tPnJsE1YByxxxjtftLCknAuamXbSXKyvCEx3DpYA@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