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 19:11:02 +0100	[thread overview]
Message-ID: <CAKv+Gu9HLDJQyDM0_SM4phFkTaZRmMQ5FKOikqeAujYurJu3mg@mail.gmail.com> (raw)
In-Reply-To: <20160902180513.GE4715@bivouac.eciton.net>

On 2 September 2016 at 19:05, Leif Lindholm <leif.lindholm@linaro.org> wrote:
> On Fri, Sep 02, 2016 at 05:07:48PM +0100, Ard Biesheuvel wrote:
>> > 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
>
> OK, but that's still yet another change.
>
>> >> 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
>
> I don't share that concern. I am entirely serious about nuking it next
> week if we come to an agreement on a better solution.
> And I'm happy to take on the drudgery of fixing up all the platforms.
>
> (As a side note, this is an excellent example of why we need to
> create reusable config fragments - fixing all ARM platforms to use the
> correct library should be at most a two-liner in one place in edk2.)
>
>> 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.
>
> My main concern is leaving the master branch unusable for ARM during
> the Labor Day weekend. If we don't resolve this tonight, with the best
> will in the world we won't be back to a functioning master before
> Tuesday evening.
>

I agree that fixing the branch now would be nice. I just don't
understand why fixing BaseMemoryLibStm in place is not a better
solution, especially if we are nuking it anyway next week. That way,
we have to change all the platforms only a single time.


  reply	other threads:[~2016-09-02 18:11 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
2016-09-02 18:05         ` Leif Lindholm
2016-09-02 18:11           ` Ard Biesheuvel [this message]
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+Gu9HLDJQyDM0_SM4phFkTaZRmMQ5FKOikqeAujYurJu3mg@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