archive mirror
 help / color / mirror / Atom feed
From: "Slark Xiao" <>
To: "Loic Poulain" <>
Cc: "Manivannan Sadhasivam" <>,
	 "" <>,
Subject: Re:Re: Does MHI driver support DMA remapping?
Date: Fri, 14 Oct 2022 19:17:42 +0800 (CST)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

At 2022-10-13 15:07:21, "Loic Poulain" <> wrote:
>Hi Slark,
>On Thu, 13 Oct 2022 at 05:25, Slark Xiao <> wrote:
>> Hi,
>>   I have a question about the DMA feature on our MHI driver. Does MHI support DMA remapping feature?
>>   This is the reference description from Windows OS:
>> To ensure compatibility with Kernel DMA Protection and DMAGuard Policy, PCIe device drivers can opt into Direct Memory Access (DMA) remapping.
>> DMA remapping for device drivers protects against memory corruption and malicious DMA attacks, and provides a higher level of compatibility for devices. Also, devices with DMA remapping-compatible drivers can start and perform DMA regardless of lock screen status.
>I assume this is all about IOMMU? then AFAIK it should be supported by
>the driver, not because the driver does anything special to handle it,
>but because it uses the standard dma helpers. So if there is an IOMMU
>in between, indicated in e.g. devicetree or ACPI, the different device
>IOVA spaces will be managed/isolated automatically via the IOMMU

Hi Loic,
  Thanks for your great explanation.
   And I have one more concern, until now, we still don't know how to use the diag port "wwan0qcdm0".
   It doesn't like Qualcomm traditional USB diag port that we can use QXDM (though this is a non-open tool and seems only accept USB diag port) or some other serial tool to collect debug log.
   Is there any method to collect debug log based on this port?


      reply	other threads:[~2022-10-14 11:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2022-10-13  7:07 ` Does MHI driver support DMA remapping? Loic Poulain
2022-10-14 11:17   ` Slark Xiao [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-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).