| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Fix one issue because some field in nand device is not save/restore
Change-Id: I025addf4ddaea8420f6328b5e58c8514604b1719
Signed-off-by: Gao, Fengqian <fengqian.gao@intel.com>
Signed-off-by: Jiang, Yunhong <yunhong.jiang@intel.com>
Signed-off-by: Nakajima, Jun <jun.nakajiama@intel.com>
|
|
|
|
|
|
|
|
|
| |
Forces overwriting (truncating) of the userimage-qemu.img file on condition that
it is being initialized from userimage.img file. If *-qemu file is not truncated
the system will pick up on artifacts located behind the overwritten area of
the *-qemu.img file.
Change-Id: I091dff0069d7049588b11c4654fe134947db101b
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently NAND device driver need 8 MMIO access for goldfish nand device access.
MMIO access is expensive in virtualization environment because each MMIO access
will cause a context switch from in-kernel module to qemu user space process.
Through introducing a new batch command, these multiple MMIO access can be
combined into one, thus improve virtualization perofrmance. The booting time in
KVM environment is reduced from 25~26 seconds to 20~21 seconds.
A kernel patch is required to utilize this new batch command.
The patched kernel will detect the batch support through a new flags in
goldfish nand device, while current kernel is not impacted.
Change-Id: Ia460b1ba3c6fde5b1fc6101bb66f8f58e46e6a78
Signed-off-by: Xin Xiaohui <xiaohui.xin@intel.com>
Signed-off-by: Zhang Xiantao <xiantao.zhang@intel.com>
Signed-off-by: Jiang Yunhong <yunhong.jiang@intel.com>
Signed-off-by: Nakajima Jun <jun.nakajima@intel.com>
|
|
|
|
|
|
|
|
|
| |
file.
This only happened for fresh newly-created AVDs. Existing ones used for testing
the emulator already had a cache.img and booted properly.
Change-Id: I87901ea5fb1dc6aa7d2bb3dd191de58d972c386f
|
|
|
|
|
|
|
|
|
|
| |
This patch enables KVM mode on x86 Linux to boost performance of x86 emulaiton
if the hardware-based virtualization feature is present on the host machine.
Change-Id: I4b24474b3ec115a3b9a7bf017801f4f610253b09
Signed-off-by: Xiaohui Xin <xiaohui.xin@intel.com>
Signed-off-by: Yunhong Jiang <yunhong.jiang@intel.com>
Signed-off-by: Jun Nakajima <jun.nakajima@intel.com>
|
|
|
|
| |
Change-Id: I3c2b4668593391026da028194503fc87246e44ba
|
|
|
|
| |
Change-Id: I1f887e6f8fc38e43b1fff3f7bab3814b52542762
|
|
|
|
|
|
|
|
| |
Also stored some other parameters, speculatively.
Guard ftruncate and lseek against EINTR
Change-Id: I4237640318564db6c375a90415097c00e4fcafaa
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is needed if there's already a /tmp/android which the current user
can't access on the system. It would prevent the emulator from starting
with a cryptic error message:
NAND: could not create temp file for system NAND disk image: Permission deniedemulator: User-config was not changed.
SDK Bug: 3154431
Change-Id: Iefe7fd6a5139da545aaef5670fb7f42d210d0edc
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch fixes saving and restoring the state of the emulated NAND
disks, by copying all contents of each disk into the snapshot file.
During restore the disks are then entirely overwritten with the
snapshot contents.
The main issue with this approach is that the size of the disk
snapshots is determined by the maximum capacity of the disk in
question, rather than the actual size of the underlying file, which
may be considerably smaller. The difference is filled with padding.
Unfortunately, obvious approaches to avoid this padding result in
incorrect state after restoring.
Change-Id: I4abe329ff2cf2f159c3d6dfc206959614cc4ca35
|
|
|
|
|
|
|
| |
This forces -Wall during the build. Note that this patch doesn't
remove all warnings, but most of the remaining ones are from upstream anyway.
Change-Id: I8808d8495e99866e156ce5780d2e3c305eab491f
|
|
|
|
| |
Change-Id: Ide3914fa52f62f618d39ac20f02bce8185a6805a
|
|
|
|
| |
Change-Id: I67152761977b330e3f4c1bbe3d8eb99e48e2e7e7
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change integrates many changes from the upstream QEMU sources.
Its main purpose is to enable correct ARMv6 and ARMv7 support to the
Android emulator. Due to the nature of the upstream code base, this
unfortunately also required changes to many other parts of the source.
Note that to ensure easier integrations in the future, some source files
and directories that have heavy Android-specific customization have been
renamed with an -android suffix. The original files are still there for
easier integration tracking, but *never* compiled. For example:
net.c net-android.c
qemu-char.c qemu-char-android.c
slirp/ slirp-android/
etc...
Tested on linux-x86, darwin-x86 and windows host machines.
|
| |
|
| |
|
| |
|
|
|