From: "Gerd Hoffmann" <kraxel@redhat.com>
To: devel@edk2.groups.io
Cc: Ard Biesheuvel <ardb@kernel.org>,
Jordan Justen <jordan.l.justen@intel.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Jiewen Yao <jiewen.yao@intel.com>,
Michael Brown <mcb30@ipxe.org>
Subject: Re: [edk2-devel] [PATCH 1/1] OvmfPkg/IoMmuDxe: add locking to IoMmuAllocateCommonBuffer
Date: Thu, 20 Jul 2023 12:22:19 +0200 [thread overview]
Message-ID: <tcmrhu5cd7yyvwi2s5yvr5c3brzlvfqyhthar7766i465bolbn@4suiccwedevr> (raw)
In-Reply-To: <mwte5ibx5yfsm3kgfrkbiy3qkf77uft5foswbrina56jdvquqc@wsqunp37wiif>
Hi,
> Not sure why InternalAllocateBuffer() doesn't update mReservedMemBitmap
> itself. That would be needed to protect the allocation code paths with
> InterlockedCompareExchange32() too.
Not a straight forward conversion, current code copies around bitmap
snippets, so this logic needs a rewrite to work with
InterlockedCompareExchange32(). Don't have the time to do that now
(leaving tomorrow for my three week summer vacation ...).
take care,
Gerd
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#107095): https://edk2.groups.io/g/devel/message/107095
Mute This Topic: https://groups.io/mt/100251949/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2023-07-20 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 8:24 [edk2-devel] [PATCH 1/1] OvmfPkg/IoMmuDxe: add locking to IoMmuAllocateCommonBuffer Gerd Hoffmann
2023-07-20 8:34 ` Ard Biesheuvel
2023-07-20 9:00 ` Gerd Hoffmann
2023-07-20 10:22 ` Gerd Hoffmann [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=tcmrhu5cd7yyvwi2s5yvr5c3brzlvfqyhthar7766i465bolbn@4suiccwedevr \
--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