public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: devel@edk2.groups.io, kraxel@redhat.com
Cc: Jiewen Yao <jiewen.yao@intel.com>, Michael Brown <mcb30@ipxe.org>
Subject: Re: [edk2-devel] [RFC/RFT PATCH] OvmfPkg/IoMmuDxe: don't rely on TPLs for re-entrancy
Date: Wed, 23 Aug 2023 17:11:49 +0200	[thread overview]
Message-ID: <CAMj1kXFc1zEbQ8rjQXG-CKd=zHvM6zxrb0qTQLDoxZVGHXasFQ@mail.gmail.com> (raw)
In-Reply-To: <eomh6rzvqorkqv2jg5aa6ibibenkg6sgpwgwzefipjoaxg2yeh@t4qhjcfthwa6>

On Wed, 23 Aug 2023 at 13:08, Gerd Hoffmann <kraxel@redhat.com> wrote:
>
> On Tue, Aug 22, 2023 at 09:57:12AM +0200, Ard Biesheuvel wrote:
> > On Tue, 22 Aug 2023 at 08:25, Gerd Hoffmann <kraxel@redhat.com> wrote:
> > >
> > > Looks good to me.
> > >
> > > What is the status?  Merged?  Or waiting for testing still?  If so I can
> > > create a test build with the patch and ask our QE department to check
> > > it.
> > >
> >
> > Still waiting for testing, so yes, please test.
>
> Hmm, QE reports back it slows down the boot alot.  No boot hangs yet
> with 12 test runs so far, which isn't that much for a reproduce rate
> below 20% ...
>
> https://bugzilla.redhat.com//show_bug.cgi?id=2211060#c28
>
> So I guess we go with the TPL version for the coming stable tag and
> leave any improvements for later ...
>

Yeah, this was not going to make the stable tag in any case.

The boot speed regression seems odd, though - this is effectively UP
code so there shouldn't be any contention, the only thing this patch
does is ensure that the critical section is restarted if it was
interrupted

Are we comparing apples with apples here?


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#107980): https://edk2.groups.io/g/devel/message/107980
Mute This Topic: https://groups.io/mt/100256049/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2023-08-23 15:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20 13:45 [edk2-devel] [RFC/RFT PATCH] OvmfPkg/IoMmuDxe: don't rely on TPLs for re-entrancy Ard Biesheuvel
2023-07-21 22:55 ` Pedro Falcato
2023-07-24 14:21   ` Ard Biesheuvel
2023-07-24 17:08     ` Pedro Falcato
2023-08-22  6:25 ` Gerd Hoffmann
2023-08-22  7:57   ` Ard Biesheuvel
2023-08-23 11:07     ` Gerd Hoffmann
2023-08-23 15:11       ` Ard Biesheuvel [this message]
2023-08-23 17:18         ` Gerd Hoffmann
2023-08-23 18:10         ` Pedro Falcato
2023-08-24  8:06           ` Gerd Hoffmann
2023-08-24 10:31             ` Ard Biesheuvel
2023-08-28  9:16               ` Gerd Hoffmann
2023-08-28 11:13                 ` Ard Biesheuvel
2023-08-31 16:01                   ` Ard Biesheuvel
2023-09-04 11:45                     ` Gerd Hoffmann
2023-09-04 12:06                       ` Ard Biesheuvel

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='CAMj1kXFc1zEbQ8rjQXG-CKd=zHvM6zxrb0qTQLDoxZVGHXasFQ@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