From: "memristor2 via groups.io" <memristor2=proton.me@groups.io>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: [edk2-devel] [Question] What is the propose of BME DMA mitigation
Date: Wed, 19 Jun 2024 07:34:28 +0000 [thread overview]
Message-ID: <1jYET2VgMCs7RY5XlgCWIk8JdP1SLzv0pSnXJj2lsC3tJ5RPhz2YFp1LTHAkc6zBeH7LIBTuVfzyW5pfgYsRmsB_ciLcw4mPcc0aPxJrVDg=@proton.me> (raw)
In-Reply-To: <fRTh7L764jredCy-lQA7V3l-BHqN3Y6BGFlNfJPkrqh4vma1cHWpcKiTrQPyiDQmZd-92wlMb4AlpwPcAkXj12xSvvM2lOMUzNjPvlGuNwk=@proton.me>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
Hello everyone,
I was scrolling through the UEFI HII and encountered an option which i failed to find any proper explanation about it.
Could you please explain point of mitigating DMA access for PCI.Thanks
------- Forwarded Message -------
From: memristor2 <memristor2@proton.me>
Date: On Tuesday, June 18th, 2024 at 4:56 PM
Subject: [Question] What is the propose of BME DMA mitigation
To: discuss@edk2.groups.io <discuss@edk2.groups.io>
> Hello everyone,
> I was scrolling through the UEFI HII and encountered an option which i failed to find any proper explanation about it.
> Could you please explain point of mitigating DMA access for PCI.
> Thanks
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#119629): https://edk2.groups.io/g/devel/message/119629
Mute This Topic: https://groups.io/mt/106756522/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 2091 bytes --]
parent reply other threads:[~2024-06-19 7:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <fRTh7L764jredCy-lQA7V3l-BHqN3Y6BGFlNfJPkrqh4vma1cHWpcKiTrQPyiDQmZd-92wlMb4AlpwPcAkXj12xSvvM2lOMUzNjPvlGuNwk=@proton.me>]
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='1jYET2VgMCs7RY5XlgCWIk8JdP1SLzv0pSnXJj2lsC3tJ5RPhz2YFp1LTHAkc6zBeH7LIBTuVfzyW5pfgYsRmsB_ciLcw4mPcc0aPxJrVDg=@proton.me' \
--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