From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from nat-hk.nvidia.com (nat-hk.nvidia.com [203.18.50.4]) by mx.groups.io with SMTP id smtpd.web11.5595.1570764615609346440 for ; Thu, 10 Oct 2019 20:30:16 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@nvidia.com header.s=n1 header.b=HD79vVip; spf=pass (domain: nvidia.com, ip: 203.18.50.4, mailfrom: ashishsingha@nvidia.com) Received: from hkpgpgate102.nvidia.com (Not Verified[10.18.92.9]) by nat-hk.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Fri, 11 Oct 2019 11:30:13 +0800 Received: from HKMAIL102.nvidia.com ([10.18.16.11]) by hkpgpgate102.nvidia.com (PGP Universal service); Thu, 10 Oct 2019 20:30:13 -0700 X-PGP-Universal: processed; by hkpgpgate102.nvidia.com on Thu, 10 Oct 2019 20:30:13 -0700 Received: from HKMAIL103.nvidia.com (10.18.16.12) by HKMAIL102.nvidia.com (10.18.16.11) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 11 Oct 2019 03:30:12 +0000 Received: from NAM03-DM3-obe.outbound.protection.outlook.com (104.47.41.54) by HKMAIL103.nvidia.com (10.18.16.12) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 11 Oct 2019 03:30:12 +0000 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=d/QYo8+LSrGJW/wXGJ/wQ+h+A/uKS8yxN+iEWTnVUlnB9LqFqiF1Xmt/NSxt07vxFIuHW/9vqs3T9DhBZKf8cHehoJLIq4k9VBK3bS6jpUNrOP0g3ggMXuvyd9jEqIQxQM+7InaFB3O95/8aJjBwX8pdnYH4Lq91W3m+8rMzyi3OQg0cc8Ya9xbDfeI207KkHW+ndcIqzTZPnbCUt45OG4jtBtOgVq6A0KjDsgnqFPtujZzaM0hjWLm0SrHySU1OfQJL+sTen/b1hSIu4FATN+ZN4SDu9fuo+1ShaBpm9PxhvC4ZrazNBwGDMKF6p7QLu9TBFktZ6Ctg1ykLJt3Iqg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=EIte2gbIfIbKls27/1/HNmT8BlobYcpLbhgu9aVLsB4=; b=Tr+wjb/uldSoJn7GmEQ8PigPzfcgp6YCeF+H8Wr4Qttfy32HP9TeGnXCDkWZ5DRKsz2ZkXRaihSbSt+jA///CnRs/LAoLsBY7JGXbdUNRfMfiken+fUipH5oaQKb7UJlywGWe3evcsCprQ6AfhIgnAX6VgBFrB/pf/1Gn3y2ZAaJDRcn7iXU7ETbTRgKFZmHGNBN4rMEP0FI/dowoLSo/NrystIFkv2J5B3kRqzNfVnnLaWC1yhfSTY3RHWVkoQrkE/4ECh1v24ncWnlP7guqGC7udrMqFmPucN0wHvTpYokrKWizzaJs2RVMfPW7kIurfsHubrkNQxX9hJIA7oWvQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nvidia.com; dmarc=pass action=none header.from=nvidia.com; dkim=pass header.d=nvidia.com; arc=none Received: from DM6PR12MB3324.namprd12.prod.outlook.com (20.178.31.154) by DM6PR12MB3689.namprd12.prod.outlook.com (10.255.76.94) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.19; Fri, 11 Oct 2019 03:30:10 +0000 Received: from DM6PR12MB3324.namprd12.prod.outlook.com ([fe80::1807:a182:87ae:55de]) by DM6PR12MB3324.namprd12.prod.outlook.com ([fe80::1807:a182:87ae:55de%5]) with mapi id 15.20.2327.026; Fri, 11 Oct 2019 03:30:10 +0000 From: "Ashish Singhal" To: "Wu, Hao A" , "devel@edk2.groups.io" , "Ni, Ray" Subject: Re: [edk2-devel] [PATCH] MdeModulePkg/XhciDxe: Fix Aligned Page Allocation Thread-Topic: [edk2-devel] [PATCH] MdeModulePkg/XhciDxe: Fix Aligned Page Allocation Thread-Index: AQHVfsNV/8sSJTw/YUqQWeYilI1PdqdTF8OAgAAGroCAAAOUAIABBmEGgACZ/oCAAAcD4A== Date: Fri, 11 Oct 2019 03:30:09 +0000 Message-ID: References: <9ce268553db91fbe7fb13e2205d0e1611e1d0212.1570640221.git.ashishsingha@nvidia.com> , In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: MSIP_Label_6b558183-044c-4105-8d9c-cea02a2a3d86_Enabled=True; MSIP_Label_6b558183-044c-4105-8d9c-cea02a2a3d86_SiteId=43083d15-7273-40c1-b7db-39efd9ccc17a; MSIP_Label_6b558183-044c-4105-8d9c-cea02a2a3d86_Owner=ashishsingha@nvidia.com; MSIP_Label_6b558183-044c-4105-8d9c-cea02a2a3d86_SetDate=2019-10-11T03:30:07.5155426Z; MSIP_Label_6b558183-044c-4105-8d9c-cea02a2a3d86_Name=Unrestricted; MSIP_Label_6b558183-044c-4105-8d9c-cea02a2a3d86_Application=Microsoft Azure Information Protection; MSIP_Label_6b558183-044c-4105-8d9c-cea02a2a3d86_ActionId=702c5c97-0584-4f7a-8736-22a9c05c650a; MSIP_Label_6b558183-044c-4105-8d9c-cea02a2a3d86_Extended_MSFT_Method=Automatic authentication-results: spf=none (sender IP is ) smtp.mailfrom=ashishsingha@nvidia.com; x-originating-ip: [8.46.90.104] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 7d9ecd88-fa0b-444f-047c-08d74dfb51d4 x-ms-traffictypediagnostic: DM6PR12MB3689: x-ms-exchange-purlcount: 5 x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:10000; x-forefront-prvs: 0187F3EA14 x-forefront-antispam-report: SFV:NSPM;SFS:(10009020)(4636009)(136003)(366004)(396003)(39860400002)(346002)(376002)(51874003)(13464003)(189003)(199004)(6506007)(478600001)(7696005)(2501003)(26005)(8936002)(102836004)(9326002)(53546011)(6116002)(3846002)(790700001)(76176011)(229853002)(186003)(71200400001)(66946007)(76116006)(256004)(14444005)(71190400001)(66446008)(66476007)(66556008)(64756008)(25786009)(74316002)(2906002)(486006)(316002)(476003)(446003)(11346002)(110136005)(6246003)(236005)(55016002)(54896002)(52536014)(14454004)(5660300002)(86362001)(66066001)(9686003)(81166006)(81156014)(8676002)(76236002)(6306002)(33656002)(7736002)(6436002)(99286004)(606006);DIR:OUT;SFP:1101;SCL:1;SRVR:DM6PR12MB3689;H:DM6PR12MB3324.namprd12.prod.outlook.com;FPR:;SPF:None;LANG:en;PTR:InfoNoRecords;MX:1;A:1; received-spf: None (protection.outlook.com: nvidia.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: wwbuKkBdYq+2/e8xbfZq5ALqkx9VR75YJDaiPeOU+OM25hx/IYc+ac35VDIG+etI3QQFo7TFYiqEsJtE4Q109TWoL9kOFel34BuozWaCuP4oep+O9sl1bWUsBm8gDvviZoUaqSQnF5DdrcKb2dJpLoWdzrs3OJZrdwfqkHDuliMdJMcOWWgt/aTgQVIGstVBpIGcbMi13JndCh9a/Dqz0xDBHFVbnNBxc2H+bRtj5cY2csPAaK4/ZWo/+pTa1sYWAki13Xwfe8aW+gebD+7pFM+A3/LrYd9xED2ZJHwvP9Uk5Swqwh/UDpKzDMohoD/VvpaI5mPT6qElxxi1oc6tRRabTYlrryocP8EXRAppzoD8txDktjzesE1h1qt7Gi5DpdDSXZWOxq+khBGjaR7tOtZUaELH7l1NhW3rtZzxGsSGhtexYpVmiBmaSIeLMrcPwrk3ySKx79jGNioXB7DBuA== x-ms-exchange-transport-forked: True MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: 7d9ecd88-fa0b-444f-047c-08d74dfb51d4 X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Oct 2019 03:30:09.9714 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 43083d15-7273-40c1-b7db-39efd9ccc17a X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: tqEV4USrqIiv6BEGAg5gWm0uEXVr5NoP0IJgImN/AFdRVQtMMnN+4rWHAmMC/RBZCcPZWTkhf+jEDtuwGvcrtQ== X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR12MB3689 Return-Path: ashishsingha@nvidia.com X-OriginatorOrg: Nvidia.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1570764613; bh=EIte2gbIfIbKls27/1/HNmT8BlobYcpLbhgu9aVLsB4=; h=X-PGP-Universal:ARC-Seal:ARC-Message-Signature: ARC-Authentication-Results:From:To:Subject:Thread-Topic: Thread-Index:Date:Message-ID:References:In-Reply-To: Accept-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator:msip_labels: authentication-results:x-originating-ip:x-ms-publictraffictype: x-ms-office365-filtering-correlation-id:x-ms-traffictypediagnostic: x-ms-exchange-purlcount:x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers:x-forefront-prvs: x-forefront-antispam-report:received-spf: x-ms-exchange-senderadcheck:x-microsoft-antispam: x-microsoft-antispam-message-info:x-ms-exchange-transport-forked: MIME-Version:X-MS-Exchange-CrossTenant-Network-Message-Id: X-MS-Exchange-CrossTenant-originalarrivaltime: X-MS-Exchange-CrossTenant-fromentityheader: X-MS-Exchange-CrossTenant-id:X-MS-Exchange-CrossTenant-mailboxtype: X-MS-Exchange-CrossTenant-userprincipalname: X-MS-Exchange-Transport-CrossTenantHeadersStamped:X-OriginatorOrg: Content-Language:Content-Type; b=HD79vVipEjFfS5BznMer4/kgVdS2uILaoEkrY0u2O0W+tPHgQ6XH3kJ+LMRD/SdUt mRm6lE2NoKRcxlxUnnCTDR+xtkiCStdEKHqs6DwsWM9u5qgPnEjNdUO0QZsB/NaLQa kOUCyJLdd3+wEfH9WVsFfY5xXDhEJ/ALU0mLsN9OLG2A50+dLzaPTe5LBwaJUjNhvq Wdz5nX6ZpM67uop/CHJ7i1zzCuhLPsLQGfFfXbi9lOk9p4Zm/SLClPLnK64VKkqnHE JyaS5aqpm/qU4PBTDRszADxdA8wxTzj4QcARrvggA4+6yS/5HJUAm+quq0IReqfG67 e0fXgQB1BhlXQ== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_DM6PR12MB3324761284AEDB43A389C39CBA970DM6PR12MB3324namp_" --_000_DM6PR12MB3324761284AEDB43A389C39CBA970DM6PR12MB3324namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello Hao, What is your motivation towards using IoMMUPei for memory allocation now i= nstead of Pei Services? The fix would be simple if we just change the numbe= r of pages needed to accommodate for the alignment. The call to free the pa= ges would not do anything. If we use IoMMUPei, we may need to change function definition for allocate= to return how many pages were allocated for each call so that freeing can = be done correctly as well. This may need more refactoring of the code that = initially thought of. Thanks Ashish From: Wu, Hao A Sent: Thursday, October 10, 2019 9:00 PM To: devel@edk2.groups.io; Ashish Singhal ; Ni, Ra= y Subject: RE: [edk2-devel] [PATCH] MdeModulePkg/XhciDxe: Fix Aligned Page A= llocation Thanks Ashish, Please help to send out the fix for XhciPei in a separate patch as well. I can help to see if verification can be done on my side. Best Regards, Hao Wu From: devel@edk2.groups.io [mailto:devel@edk2= .groups.io] On Behalf Of Ashish Singhal Sent: Friday, October 11, 2019 1:51 AM To: Wu, Hao A; devel@edk2.groups.io; Ni, Ray Subject: Re: [edk2-devel] [PATCH] MdeModulePkg/XhciDxe: Fix Aligned Page A= llocation Hello Hao, I agree that for completeness we should fix the issue in both DXE as well = as PEI but on my target, we do not have any PEI phase for me to be able to = verify any change that I will be making. If you still want, I can still mak= e the change so that someone else can verify or we can have someone else fi= x PEI and push my change meanwhile to fix the issue in DXE. Thanks Ashish ________________________________ From: Wu, Hao A > Sent: Wednesday, October 9, 2019 8:09 PM To: Ashish Singhal >; devel@edk2.groups.io >; Ni, Ray > Subject: RE: [PATCH] MdeModulePkg/XhciDxe: Fix Aligned Page Allocation > -----Original Message----- > From: Ashish Singhal [mailto:ashishsingha@nvidia.com] > Sent: Thursday, October 10, 2019 9:58 AM > To: Wu, Hao A; devel@edk2.groups.io; Ni, Ra= y > Subject: RE: [PATCH] MdeModulePkg/XhciDxe: Fix Aligned Page Allocation > > Hello Hao, > > I can see that the PEI also has the same issue and take a look at that a= s well > but I have no way to verify that as we are not using it. For the change = I have > made in DXE, I have verified it with an alignment of 4K and 64K. Is it possible for you to verify the PEI case with a test PEI module that performs read operation to a USB storage device? I think this will trigger the affecting codes. In my opinion, it would be better for the fix to be complete. Best Regards, Hao Wu > > Thanks > Ashish > > -----Original Message----- > From: Wu, Hao A > > Sent: Wednesday, October 9, 2019 7:33 PM > To: Ashish Singhal >; devel@edk2.groups.io; Ni, > Ray > > Subject: RE: [PATCH] MdeModulePkg/XhciDxe: Fix Aligned Page Allocation > > > -----Original Message----- > > From: Ashish Singhal [mailto:ashishsingha@nvidia.com] > > Sent: Thursday, October 10, 2019 1:02 AM > > To: devel@edk2.groups.io; Wu, Hao A; Ni, = Ray > > Cc: Ashish Singhal > > Subject: [PATCH] MdeModulePkg/XhciDxe: Fix Aligned Page Allocation > > > > While allocating pages aligned at an alignment higher than 4K, > > allocate memory taking into consideration the padding required for > > that alignment. The calls to free pages takes care of this already. > > > > Signed-off-by: Ashish Singhal > > > --- > > MdeModulePkg/Bus/Pci/XhciDxe/UsbHcMem.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/MdeModulePkg/Bus/Pci/XhciDxe/UsbHcMem.c > > b/MdeModulePkg/Bus/Pci/XhciDxe/UsbHcMem.c > > index fd79988..aa69c47 100644 > > --- a/MdeModulePkg/Bus/Pci/XhciDxe/UsbHcMem.c > > +++ b/MdeModulePkg/Bus/Pci/XhciDxe/UsbHcMem.c > > @@ -656,7 +656,7 @@ UsbHcAllocateAlignedPages ( > > PciIo, > > AllocateAnyPages, > > EfiBootServicesData, > > - Pages, > > + RealPages, > > &Memory, > > 0 > > ); > > > Hello, > > The change looks good to me. > > Just a couple of things to confirm: > > 1. I think there is a similar case within the XhciPei driver Could you h= elp to > resolve it as well? > > I think for the PEI counterpart you may need to update both > UsbHcAllocateAlignedPages() and UsbHcFreeAlignedPages(), since the > IOMMU helper functions like IoMmuAllocateBuffer() and IoMmuFreeBuffer() > might not be suitable now. Instead, I think services in the IoMmu PPI ca= n be > used. > > 2. Could you help to provide the information on what test has been done = for > the proposed patch? > > Thanks in advance. > > Best Regards, > Hao Wu > > > > -- > > 2.7.4 > > ------------------------------------------------------------------------= ----------- > This email message is for the sole use of the intended recipient(s) and = may > contain > confidential information. Any unauthorized review, use, disclosure or > distribution > is prohibited. If you are not the intended recipient, please contact th= e > sender by > reply email and destroy all copies of the original message. > ------------------------------------------------------------------------= ----------- --_000_DM6PR12MB3324761284AEDB43A389C39CBA970DM6PR12MB3324namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello Hao,

 

What is your motivation towards using IoMMUPei for= memory allocation now instead of Pei Services? The fix would be simple if = we just change the number of pages needed to accommodate for the alignment. The call to free the pages would not do anything.=

 

If we use IoMMUPei, we may need to change function= definition for allocate to return how many pages were allocated for each c= all so that freeing can be done correctly as well. This may need more refactoring of the code that initially thought of.

 

Thanks

Ashish

 

From: Wu, Hao A <hao.a.wu@intel.= com>
Sent: Thursday, October 10, 2019 9:00 PM
To: devel@edk2.groups.io; Ashish Singhal <ashishsingha@nvidia.co= m>; Ni, Ray <ray.ni@intel.com>
Subject: RE: [edk2-devel] [PATCH] MdeModulePkg/XhciDxe: Fix Aligned= Page Allocation

 

Thanks Ashish,

 

Please help to send out the fix for = XhciPei in a separate patch as well.

I can help to see if verification ca= n be done on my side.

 

Best Regards,

Hao Wu

 

From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of Ashish Singhal
Sent: Friday, October 11, 2019 1:51 AM
To: Wu, Hao A; devel@edk2.g= roups.io; Ni, Ray
Subject: Re: [edk2-devel] [PATCH] MdeModulePkg/XhciDxe: Fix Aligned= Page Allocation

 

Hello Hao,

 

I agree that for completeness we should fix the issue i= n both DXE as well as PEI but on my target, we do not have any PEI phase fo= r me to be able to verify any change that I will be making. If you still want, I can still make the change so that someone= else can verify or we can have someone else fix PEI and push my change mea= nwhile to fix the issue in DXE.

 

Thanks

Ashish


From: Wu, H= ao A <hao.a.wu@intel.com> Sent: Wednesday, October 9, 2019 8:09 PM
To: Ashish Singhal <a= shishsingha@nvidia.com>; devel@edk2.groups.io <devel@edk2.groups.io>; Ni, Ray &l= t;ray.ni@intel.com>
Subject: RE: [PATCH] MdeModulePkg/XhciDxe: Fix Aligned Page Allocat= ion

 

> -----Original= Message-----
> From: Ashish Singhal [mail= to:ashishsingha@nvidia.com]
> Sent: Thursday, October 10, 2019 9:58 AM
> To: Wu, Hao A; devel@edk2.gro= ups.io; Ni, Ray
> Subject: RE: [PATCH] MdeModulePkg/XhciDxe: Fix Aligned Page Allocatio= n
>
> Hello Hao,
>
> I can see that the PEI also has the same issue and take a look at tha= t as well
> but I have no way to verify that as we are not using it. For the chan= ge I have
> made in DXE, I have verified it with an alignment of 4K and 64K.


Is it possible for you to verify the PEI case with a test PEI module that<= br> performs read operation to a USB storage device? I think this will trigger=
the affecting codes.

In my opinion, it would be better for the fix to be complete.

Best Regards,
Hao Wu


>
> Thanks
> Ashish
>
> -----Original Message-----
> From: Wu, Hao A <hao.a.wu@in= tel.com>
> Sent: Wednesday, October 9, 2019 7:33 PM
> To: Ashish Singhal <ash= ishsingha@nvidia.com>; devel@edk2.groups.io; Ni,
> Ray <ray.ni@intel.com><= br> > Subject: RE: [PATCH] MdeModulePkg/XhciDxe: Fix Aligned Page Allocatio= n
>
> > -----Original Message-----
> > From: Ashish Singhal [mailto:ashishsingha@nvidia.com]
> > Sent: Thursday, October 10, 2019 1:02 AM
> > To: devel@edk2.groups.io= ; Wu, Hao A; Ni, Ray
> > Cc: Ashish Singhal
> > Subject: [PATCH] MdeModulePkg/XhciDxe: Fix Aligned Page Allocati= on
> >
> > While allocating pages aligned at an alignment higher than 4K, > > allocate memory taking into consideration the padding required f= or
> > that alignment. The calls to free pages takes care of this alrea= dy.
> >
> > Signed-off-by: Ashish Singhal <ashishsingha@nvidia.com>
> > ---
> >  MdeModulePkg/Bus/Pci/XhciDxe/UsbHcMem.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/MdeModulePkg/Bus/Pci/XhciDxe/UsbHcMem.c
> > b/MdeModulePkg/Bus/Pci/XhciDxe/UsbHcMem.c
> > index fd79988..aa69c47 100644
> > --- a/MdeModulePkg/Bus/Pci/XhciDxe/UsbHcMem.c
> > +++ b/MdeModulePkg/Bus/Pci/XhciDxe/UsbHcMem.c
> > @@ -656,7 +656,7 @@ UsbHcAllocateAlignedPages (
> >           = ;             P= ciIo,
> >           = ;             A= llocateAnyPages,
> >           = ;             E= fiBootServicesData,
> > -          &nb= sp;           Pages,
> > +          = ;            RealPag= es,
> >           = ;             &= amp;Memory,
> >           = ;             0=
> >           = ;             )= ;
>
>
> Hello,
>
> The change looks good to me.
>
> Just a couple of things to confirm:
>
> 1. I think there is a similar case within the XhciPei driver Could yo= u help to
> resolve it as well?
>
> I think for the PEI counterpart you may need to update both
> UsbHcAllocateAlignedPages() and UsbHcFreeAlignedPages(), since the > IOMMU helper functions like IoMmuAllocateBuffer() and IoMmuFreeBuffer= ()
> might not be suitable now. Instead, I think services in the IoMmu PPI= can be
> used.
>
> 2. Could you help to provide the information on what test has been do= ne for
> the proposed patch?
>
> Thanks in advance.
>
> Best Regards,
> Hao Wu
>
>
> > --
> > 2.7.4
>
> ---------------------------------------------------------------------= --------------
> This email message is for the sole use of the intended recipient(s) a= nd may
> contain
> confidential information.  Any unauthorized review, use, disclos= ure or
> distribution
> is prohibited.  If you are not the intended recipient, please co= ntact the
> sender by
> reply email and destroy all copies of the original message.
> ---------------------------------------------------------------------= --------------

--_000_DM6PR12MB3324761284AEDB43A389C39CBA970DM6PR12MB3324namp_--