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: Pedro Falcato <pedro.falcato@gmail.com>,
	Jiewen Yao <jiewen.yao@intel.com>,
	 Michael Brown <mcb30@ipxe.org>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	 Michael Roth <michael.roth@amd.com>
Subject: Re: [edk2-devel] [RFC/RFT PATCH] OvmfPkg/IoMmuDxe: don't rely on TPLs for re-entrancy
Date: Mon, 28 Aug 2023 13:13:20 +0200	[thread overview]
Message-ID: <CAMj1kXF22MKxjwtaPq+FzvJ6fD3hABrG-7WUuYYhbSH9YHhCoA@mail.gmail.com> (raw)
In-Reply-To: <4bd53ehby2cto5n2venjfkucot5ayj2xtsl7z6diegh6llrpm2@tj5oh6txxjck>

On Mon, 28 Aug 2023 at 11:16, Gerd Hoffmann <kraxel@redhat.com> wrote:
>
>   Hi,
>
> > I have tried the patch below, and I don't see any slowdowns with or
> > without the patch, running both DEBUG and RELEASE builds under
> > ordinary KVM/nested-virt. Note that the change in the first hunk will
> > cause the ASSERT()s removed in the other hunks to trigger so the code
> > is definitely being exercised.
>
> QE team tested again with fresh builds, the slowdown isn't there any
> more.  Not fully clear where it came from, but most likely not from
> this patch.
>
> Only 20 successful test runs so far, which a good start, but with
> a reproduce rate below 20% not that much.    I'll post an update
> when it I get more results.
>

Excellent, thanks for the update.


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#108057): https://edk2.groups.io/g/devel/message/108057
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-28 11:13 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
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 [this message]
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=CAMj1kXF22MKxjwtaPq+FzvJ6fD3hABrG-7WUuYYhbSH9YHhCoA@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