There is no point in saving the address of the address space lock in the address space structure anymore, since this lock is always the address creation lock of the owner process,

and there's always an owner process now.

svn path=/trunk/; revision=34878
This commit is contained in:
ReactOS Portable Systems Group 2008-07-28 00:56:39 +00:00
parent 71f2416876
commit 34954b16a4
2 changed files with 2 additions and 5 deletions

View file

@ -253,7 +253,6 @@ typedef struct _MEMORY_AREA
typedef struct _MADDRESS_SPACE
{
PMEMORY_AREA MemoryAreaRoot;
PEX_PUSH_LOCK Lock;
} MADDRESS_SPACE, *PMADDRESS_SPACE;
typedef struct
@ -1576,14 +1575,14 @@ VOID
MmLockAddressSpace(PMADDRESS_SPACE AddressSpace)
{
KeEnterCriticalRegion();
ExAcquirePushLockExclusive(AddressSpace->Lock);
ExAcquirePushLockExclusive((PEX_PUSH_LOCK)&CONTAINING_RECORD(AddressSpace, EPROCESS, VadRoot)->AddressCreationLock);
}
FORCEINLINE
VOID
MmUnlockAddressSpace(PMADDRESS_SPACE AddressSpace)
{
ExReleasePushLock(AddressSpace->Lock);
ExReleasePushLock((PEX_PUSH_LOCK)&CONTAINING_RECORD(AddressSpace, EPROCESS, VadRoot)->AddressCreationLock);
KeLeaveCriticalRegion();
}

View file

@ -32,8 +32,6 @@ MmInitializeAddressSpace(PEPROCESS Process,
PMADDRESS_SPACE AddressSpace)
{
AddressSpace->MemoryAreaRoot = NULL;
AddressSpace->Lock = (PEX_PUSH_LOCK)&Process->AddressCreationLock;
ExInitializePushLock((PULONG_PTR)AddressSpace->Lock);
return STATUS_SUCCESS;
}