gecko-dev/dom/media/gmp/GMPUtils.h

99 строки
2.2 KiB
C
Исходник Обычный вид История

/* -*- Mode: C++; tab-width: 2; indent-tabs-mode: nil; c-basic-offset: 2 -*- */
/* This Source Code Form is subject to the terms of the Mozilla Public
* License, v. 2.0. If a copy of the MPL was not distributed with this
* file, You can obtain one at http://mozilla.org/MPL/2.0/. */
#ifndef GMPUtils_h_
#define GMPUtils_h_
#include "mozilla/UniquePtr.h"
#include "mozilla/RefPtr.h"
#include "mozilla/AbstractThread.h"
#include "nsStringFwd.h"
#include "nsTArray.h"
#include "nsCOMPtr.h"
#include "nsClassHashtable.h"
#define CHROMIUM_CDM_API "chromium-cdm8-host4"
class nsIFile;
class nsISimpleEnumerator;
namespace mozilla {
template<typename T>
struct DestroyPolicy
{
void operator()(T* aGMPObject) const {
aGMPObject->Destroy();
}
};
template<typename T>
using GMPUniquePtr = mozilla::UniquePtr<T, DestroyPolicy<T>>;
void
SplitAt(const char* aDelims,
const nsACString& aInput,
nsTArray<nsCString>& aOutTokens);
nsCString
ToHexString(const nsTArray<uint8_t>& aBytes);
nsCString
ToHexString(const uint8_t* aBytes, uint32_t aLength);
bool
FileExists(nsIFile* aFile);
// Enumerate directory entries for a specified path.
class DirectoryEnumerator {
public:
enum Mode {
DirsOnly, // Enumeration only includes directories.
FilesAndDirs // Enumeration includes directories and non-directory files.
};
DirectoryEnumerator(nsIFile* aPath, Mode aMode);
already_AddRefed<nsIFile> Next();
private:
Mode mMode;
nsCOMPtr<nsISimpleEnumerator> mIter;
};
class GMPInfoFileParser {
public:
bool Init(nsIFile* aFile);
bool Contains(const nsCString& aKey) const;
nsCString Get(const nsCString& aKey) const;
private:
nsClassHashtable<nsCStringHashKey, nsCString> mValues;
};
bool
ReadIntoString(nsIFile* aFile,
nsCString& aOutDst,
size_t aMaxLength);
bool
HaveGMPFor(const nsCString& aAPI,
nsTArray<nsCString>&& aTags);
void
LogToConsole(const nsAString& aMsg);
RefPtr<AbstractThread>
GetGMPAbstractThread();
Bug 1351953 - Pre-allocate shmems for the CDM process to use for storing decrypted and audio samples. r=gerald Makes transfer of samples between the content and CDM processes use shmems. The Chromium CDM API requires us to implement a synchronous interface to supply buffers to the CDM for it to write decrypted samples into. We want our buffers to be backed by shmems, in order to reduce the overhead of transferring decoded frames. However due to sandboxing restrictions, the CDM process cannot allocate shmems itself. We don't want to be doing synchronous IPC to request shmems from the content process, nor do we want to have to do intr IPC or make async IPC conform to the sync allocation interface. So instead we have the content process pre-allocate a set of shmems and give them to the CDM process in advance of them being needed. When the CDM needs to allocate a buffer for storing a decrypted sample, the CDM host gives it one of these shmems' buffers. When this is sent back to the content process, we copy the result out (uploading to a GPU surface for video frames), and send the shmem back to the CDM process so it can reuse it. We predict the size of buffer the CDM will allocate, and prepopulate the CDM's list of shmems with shmems of at least that size, plus a bit of padding for safety. We pad frames out to be the next multiple of 16, as we've seen some decoders do that. Normally the CDM won't allocate more than one buffer at once, but we've seen cases where it allocates two buffers, returns one and holds onto the other. So the minimum number of shmems we give to the CDM must be at least two, and the default is three for safety. MozReview-Commit-ID: 5FaWAst3aeh --HG-- extra : rebase_source : a0cb126e72bfb2905bcdf02e864dc654e8340410
2017-03-28 08:59:11 +03:00
// Returns the number of bytes required to store an aWidth x aHeight image in
// I420 format, padded so that the width and height are multiples of 16.
size_t
Bug 1351953 - Pre-allocate shmems for the CDM process to use for storing decrypted and audio samples. r=gerald Makes transfer of samples between the content and CDM processes use shmems. The Chromium CDM API requires us to implement a synchronous interface to supply buffers to the CDM for it to write decrypted samples into. We want our buffers to be backed by shmems, in order to reduce the overhead of transferring decoded frames. However due to sandboxing restrictions, the CDM process cannot allocate shmems itself. We don't want to be doing synchronous IPC to request shmems from the content process, nor do we want to have to do intr IPC or make async IPC conform to the sync allocation interface. So instead we have the content process pre-allocate a set of shmems and give them to the CDM process in advance of them being needed. When the CDM needs to allocate a buffer for storing a decrypted sample, the CDM host gives it one of these shmems' buffers. When this is sent back to the content process, we copy the result out (uploading to a GPU surface for video frames), and send the shmem back to the CDM process so it can reuse it. We predict the size of buffer the CDM will allocate, and prepopulate the CDM's list of shmems with shmems of at least that size, plus a bit of padding for safety. We pad frames out to be the next multiple of 16, as we've seen some decoders do that. Normally the CDM won't allocate more than one buffer at once, but we've seen cases where it allocates two buffers, returns one and holds onto the other. So the minimum number of shmems we give to the CDM must be at least two, and the default is three for safety. MozReview-Commit-ID: 5FaWAst3aeh --HG-- extra : rebase_source : a0cb126e72bfb2905bcdf02e864dc654e8340410
2017-03-28 08:59:11 +03:00
I420FrameBufferSizePadded(int32_t aWidth, int32_t aHeight);
} // namespace mozilla
#endif