public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: "Zeng, Star" <star.zeng@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Laszlo Ersek (lersek@redhat.com)" <lersek@redhat.com>,
	"Ni, Ruiyu" <ruiyu.ni@intel.com>
Subject: Re: [PATCH] IntelSiliconPkg/VTdDxe: Change EBS Event TPL to CALLBACK.
Date: Thu, 26 Oct 2017 06:50:41 +0000	[thread overview]
Message-ID: <74D8A39837DF1E4DA445A8C0B3885C503AA04F32@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <0C09AFA07DD0434D9E2A0C6AEB0483103B9AE45B@shsmsx102.ccr.corp.intel.com>

Yes, this PCI patch will be submitted soon. :)

Thank you
Yao Jiewen

> -----Original Message-----
> From: Zeng, Star
> Sent: Thursday, October 26, 2017 2:18 PM
> To: Yao, Jiewen <jiewen.yao@intel.com>; edk2-devel@lists.01.org
> Cc: Laszlo Ersek (lersek@redhat.com) <lersek@redhat.com>; Zeng, Star
> <star.zeng@intel.com>
> Subject: RE: [PATCH] IntelSiliconPkg/VTdDxe: Change EBS Event TPL to CALLBACK.
> 
> So there will be a guidance for this " PCI device disable BME at NOTIFY " to be
> documented?
> 
> Thanks,
> Star
> -----Original Message-----
> From: Yao, Jiewen
> Sent: Thursday, October 26, 2017 2:03 PM
> To: Zeng, Star <star.zeng@intel.com>; edk2-devel@lists.01.org
> Cc: Laszlo Ersek (lersek@redhat.com) <lersek@redhat.com>
> Subject: RE: [PATCH] IntelSiliconPkg/VTdDxe: Change EBS Event TPL to CALLBACK.
> 
> Right. In the future, we will let PCI device disable BME at NOTIFY.
> 
> So we let IOMMU use CALLBACK, to make sure BME is disabled before IOMMU is
> disabled.
> 
> Thank you
> Yao Jiewen
> 
> > -----Original Message-----
> > From: Zeng, Star
> > Sent: Thursday, October 26, 2017 1:55 PM
> > To: Yao, Jiewen <jiewen.yao@intel.com>; edk2-devel@lists.01.org
> > Cc: Laszlo Ersek (lersek@redhat.com) <lersek@redhat.com>; Zeng, Star
> > <star.zeng@intel.com>
> > Subject: RE: [PATCH] IntelSiliconPkg/VTdDxe: Change EBS Event TPL to
> CALLBACK.
> >
> > I am confused.
> >
> > Is this patch to make the device driver's EBS event notification to be
> > run before IntelVTdDxe's EBS event notification?
> >
> > If yes, this patch seemingly can only make sure the behavior when the
> > device driver's EBS event notification is at NOTIFY, but not CALLBACK.
> >
> >
> > Thanks,
> > Star
> > -----Original Message-----
> > From: Yao, Jiewen
> > Sent: Thursday, October 26, 2017 1:16 PM
> > To: Zeng, Star <star.zeng@intel.com>; edk2-devel@lists.01.org
> > Cc: Laszlo Ersek (lersek@redhat.com) <lersek@redhat.com>
> > Subject: RE: [PATCH] IntelSiliconPkg/VTdDxe: Change EBS Event TPL to
> CALLBACK.
> >
> > That is fine.
> >
> > Here, disabling IOMMU means to disable the protection and allow all
> > DMA access.
> > I do not think it will bring any functional impact.
> >
> > Thank you
> > Yao Jiewen
> >
> >
> > > -----Original Message-----
> > > From: Zeng, Star
> > > Sent: Thursday, October 26, 2017 12:58 PM
> > > To: Yao, Jiewen <jiewen.yao@intel.com>; edk2-devel@lists.01.org
> > > Cc: Laszlo Ersek (lersek@redhat.com) <lersek@redhat.com>; Zeng, Star
> > > <star.zeng@intel.com>
> > > Subject: RE: [PATCH] IntelSiliconPkg/VTdDxe: Change EBS Event TPL to
> > CALLBACK.
> > >
> > > Some device driver may also have exit boot service event at
> > > CALLBACK, for example AtaPassThruExitBootServices() that was added by
> Laszlo.
> > >
> > >
> > > Thanks,
> > > Star
> > > -----Original Message-----
> > > From: Yao, Jiewen
> > > Sent: Thursday, October 26, 2017 10:14 AM
> > > To: edk2-devel@lists.01.org
> > > Cc: Zeng, Star <star.zeng@intel.com>
> > > Subject: [PATCH] IntelSiliconPkg/VTdDxe: Change EBS Event TPL to CALLBACK.
> > >
> > > Change ExitBootServices TPL to CALLBACK, so that a device can
> > > disable BME before IOMMU grants access right.
> > >
> > > Cc: Star Zeng <star.zeng@intel.com>
> > > Contributed-under: TianoCore Contribution Agreement 1.1
> > > Signed-off-by: Jiewen Yao <jiewen.yao@intel.com>
> > > ---
> > >  IntelSiliconPkg/Feature/VTd/IntelVTdDxe/DmaProtection.c | 4 ++--
> > >  1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/IntelSiliconPkg/Feature/VTd/IntelVTdDxe/DmaProtection.c
> > > b/IntelSiliconPkg/Feature/VTd/IntelVTdDxe/DmaProtection.c
> > > index f5de01f..4a4d82e 100644
> > > --- a/IntelSiliconPkg/Feature/VTd/IntelVTdDxe/DmaProtection.c
> > > +++ b/IntelSiliconPkg/Feature/VTd/IntelVTdDxe/DmaProtection.c
> > > @@ -483,7 +483,7 @@ InitializeDmaProtection (
> > >
> > >    Status = gBS->CreateEventEx (
> > >                    EVT_NOTIFY_SIGNAL,
> > > -                  TPL_NOTIFY,
> > > +                  TPL_CALLBACK,
> > >                    OnExitBootServices,
> > >                    NULL,
> > >                    &gEfiEventExitBootServicesGuid, @@ -492,7 +492,7
> > > @@ InitializeDmaProtection (
> > >    ASSERT_EFI_ERROR (Status);
> > >
> > >    Status = EfiCreateEventLegacyBootEx (
> > > -             TPL_NOTIFY,
> > > +             TPL_CALLBACK,
> > >               OnLegacyBoot,
> > >               NULL,
> > >               &LegacyBootEvent
> > > --
> > > 2.7.4.windows.1



  reply	other threads:[~2017-10-26  6:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26  2:13 [PATCH] IntelSiliconPkg/VTdDxe: Change EBS Event TPL to CALLBACK Jiewen Yao
2017-10-26  4:58 ` Zeng, Star
2017-10-26  5:15   ` Yao, Jiewen
2017-10-26  5:55     ` Zeng, Star
2017-10-26  6:03       ` Yao, Jiewen
2017-10-26  6:18         ` Zeng, Star
2017-10-26  6:50           ` Yao, Jiewen [this message]
2017-10-26  6:54             ` Zeng, Star
2017-10-26  6:55               ` Yao, Jiewen
2017-10-26  7:53               ` Laszlo Ersek
2017-10-26  8:10                 ` Zeng, Star
2017-10-26 13:07                   ` Laszlo Ersek
2017-10-26 13:36                     ` Yao, Jiewen
2017-10-26 15:06                       ` Laszlo Ersek
2017-10-27  0:34                         ` Yao, Jiewen
2017-10-27  0:53                           ` Ni, Ruiyu
2017-10-27  1:47                             ` Yao, Jiewen
2017-10-27  2:37                               ` Ni, Ruiyu
2017-10-27  3:50                                 ` Yao, Jiewen
2017-10-27 16:41                               ` Laszlo Ersek
2017-10-28  5:15                                 ` Yao, Jiewen

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=74D8A39837DF1E4DA445A8C0B3885C503AA04F32@shsmsx102.ccr.corp.intel.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